Frequently asked questions

Fatigue management software tracks workers' hours against defined fatigue rules, maximum shift lengths, rest breaks, consecutive days, and alerts or blocks scheduling decisions that would breach them. In Humanz, these checks run inside the roster itself, so non-compliant shifts are caught before they're confirmed.

Under model WHS laws adopted across most Australian states, employers must manage foreseeable risks, and fatigue is explicitly recognised as one. Safe Work Australia publishes guidance requiring fatigue risk to be identified, assessed and controlled. Software makes that obligation systematic and auditable rather than manual.

No. Humanz manages fatigue risk on the roster side, tracking hours, breaks and consecutive shifts against your policies, with no wearables, cameras or in-cab hardware involved. Detection technology watches the worker in the moment, while Humanz stops the non-compliant shift being scheduled in the first place, so the two can sit together without overlapping.

A policy can set maximum shift lengths, minimum breaks between shifts and after nights, consecutive day and night caps, start-time limits and rolling hour ceilings across 7, 14 and 28 days. Build it once as your business default, then override it per client or site, with the strictest applicable policy always winning.

Yes. Humanz supports layered fatigue policies at business, client and site level. When a worker is rostered to a job, the strictest applicable policy applies automatically, which is exactly how mining and transport client requirements work in practice.

Yes. Humanz handles extended swings, rotating nights and back-to-back patterns natively, tracking cumulative hours across the full cycle, including when workers move between sites or clients.

Yes, where they have permission. Rather than hard-blocking the roster, Humanz shows the exact breach and lets an authorised coordinator continue anyway when there's a genuine reason. Every override is recorded, so you keep a clear audit trail of who accepted which risk and when.

Most teams have fatigue policies configured and running against live rosters within the first week or two of onboarding. Bring your current policy to a demo and we'll show you how it maps into the platform.

A live roster (what vendors variously call a roster system or rostering system) is connected to everything the spreadsheet can't see: worker availability, qualifications, fatigue hours, confirmations and the mobile phones of the people doing the work. Changes propagate instantly, compliance is checked automatically, and you get an audit trail, none of which a spreadsheet can offer.

Yes, natively. Swing patterns, rotating nights and back-to-back cycles are first-class citizens, and FIFO flights and accommodation can be attached directly to the roster with templates and bulk uploads.

Yes. Each worker's profile carries their trades, qualifications and inductions with expiry dates, and fatigue limits are checked as shifts are placed, so a booking that would breach either is flagged before it's confirmed. Expiring credentials surface ahead of time, so renewals happen before they cost anyone a shift.

Yes. Subcontractors are booked from the same scheduling interface as direct employees, each with their own compliance profile, one view of your entire workforce.

Through the Humanz mobile app, upcoming shifts, changes, site details and job briefs, plus one-tap confirmation, availability updates, timesheets and leave requests.

Live availability shows who's free, qualified and compliant right now, and an open shift can be pushed to all of them at once, the first to accept on their phone gets the job. What used to be an hour of ring-arounds becomes a few minutes, with seen/unseen tracking showing exactly who's across the change.

Leave is entered in seconds, with the category, hours and dates on record, and one tick clears every shift that worker held that day. The gaps become visible on the roster immediately, so open shifts can be pushed to available, qualified workers while there's still time to fill them.

Not yet. Today Humanz uses rules-based automation, templates, live availability matching and compliance gates. AI-assisted scheduling is on our roadmap, and we're building it deliberately on those compliance-first foundations.

Subcontractor management software (also sold as subcontractor software, a contractor management system or a contractor management solution) centralises everything about your subcontractor workforce: company and contact details, insurances, licences, tickets, inductions and documents. It connects that record to scheduling and timesheets, so booking a subbie carries the same visibility and compliance checks as rostering an employee.

In Humanz, yes, that's the core design. Both appear in the same scheduling view with their own compliance profiles, so coordinators see the whole workforce and book whoever is available, qualified and compliant.

Each credential has an expiry date, and Humanz fires alerts to the subcontractor and your coordinators ahead of time. If something lapses, the subbie is flagged and can be blocked from new bookings until it's renewed.

Yes. Inductions and requirements are tracked per client and per site, so a subbie cleared for one principal's job is never assumed cleared for the next. Every booking checks against what that specific client and site require, with the evidence stored and ready for whoever asks.

Commonly: current public liability and workers-comp insurance, relevant licences and high-risk work tickets, site and client inductions, SWMS for the scope of work, and evidence of WHS management. Humanz stores all of these against the subcontractor profile and reports on their currency.

Yes. Employees, labour hire and subcontractors all sit on the same platform, with each engagement type carrying its own compliance profile. Coordinators book from one pool with the same gates applied across the lot, so one compliance standard covers everyone on your sites.

Because subbie hours are captured through the same digital timesheet flow as employees, submitted from the field, reviewed and approved with an audit trail, you reconcile invoices against approved hours instead of arguing over handwritten records. Disputes drop, and month-end gets faster.

Subbies use the same Humanz mobile app as employees, for shifts, confirmations, documents and timesheets. It's included, and onboarding a new subcontractor takes minutes.

Workforce management (WFM) software plans and runs the operational side of your workforce: rostering and scheduling, time and attendance, compliance, communication and analytics. It's distinct from HR software, which manages the employment relationship, contracts, performance and payroll administration. The two complement each other.

Australian businesses with field, site or shift-based workforces, construction, mining services, trades, drilling, civil, logistics and manufacturing among them. If your team works away from a desk and your roster changes daily, Humanz was built for you.

Yes. Employees, subcontractors and labour hire sit in the same roster, each with their own compliance profile, so coordinators book whoever is available and qualified from one view. Subbie hours run through the same timesheet and approval flow, keeping one clean record across the whole blended crew.

No, it feeds them. Humanz produces accurate, approved time data that flows to payroll, and handles operational records like onboarding documents and credentials. Your payroll engine and HRIS keep doing what they do best, with far better data.

Yes, through a two-way API integration rather than a file export, so approved hours flow into Xero and the data stays in step both ways. That matters because a one-way export is only ever a snapshot: the moment something is corrected on either side, the two systems disagree until someone reconciles them by hand.

Yes. The Humanz mobile app puts each worker's roster, timesheets, jobs and documents under one My Work menu, with booking requests and updates arriving as notifications. Workers accept jobs, confirm shifts and submit hours from the phone already in their pocket, so nothing extra needs to be rolled out on site.

Yes. Humanz supports Microsoft single sign-on across both the web app and the mobile app, so crews and coordinators use the same credentials they already have and your IT team keeps access control in one place. Removing someone's Microsoft account removes their Humanz access with it.

A typical rollout runs in phases over a few weeks, configuration and master data first, then the scheduler and mobile app, then timesheets and forms. The pace flexes to your business; we support each step rather than working to a rigid clock.

No, most businesses roll out in phases. The scheduler and mobile app usually land first, timesheets follow once rosters are humming, and forms come after that. Every module is included, and you switch each one on when your team is ready.

Humanz is Australian-built with Australian-based support. You talk to the team that builds the product, no offshore ticket queues.

Yes. Swing patterns like 2/1, 8/6 and even time are built as templates and rolled forward, with panels offset automatically and travel days attached to the swing. The scheduler shows every site and crew in one view, from a week to three months out.

Yes. Credentials, inductions, medicals and verifications of competency are tracked per worker with expiry dates, and bookings are checked against the requirements of the specific client and site. A booking that would breach them is flagged before it is confirmed, and expiry alerts fire weeks ahead.

Yes. Fatigue policies layer at business, client and site level, and the strictest applicable rule wins, which is how mine site requirements work in practice. Hours are tracked across every site a worker touches, so the limits hold even when crews move between operations.

Yes. Flights, rooms, vehicles and plant are scheduled beside the people who need them, using templates and bulk uploads for changeovers. When a swing changes, the attached logistics move with it.

Yes. When headcount jumps for a shutdown or turnaround, coordinators book employees, labour hire and subbies from one pool, push the shifts to their phones and watch confirmations land live. Flights and rooms follow through templates and bulk uploads, so the crew and its logistics come together in hours.

Yes. Employees, labour hire and subcontractors sit in the same roster, each carrying their own compliance profile. Shutdown crews can be assembled from the whole pool, with shifts pushed to phones and confirmations tracked.

An indicative rollout runs about 11 weeks, phased so each step lands when the team is ready. Most businesses go live with the scheduler and mobile app first, then bring in timesheets, forms, fatigue and mobilisation. Humanz does the configuration and data setup with you.

Yes. Vehicles, plant and equipment are allocated on the same board as the crews who operate them, per job. A machine without an operator, or an operator without a machine, is visible while there is still time to fix it.

Yes. Credentials are held per worker with expiry dates, and bookings check them against what the job requires. Workers without the required ticket, induction or verification of competency are flagged before the shift is confirmed.

Subcontractors are managed in the same system as employees: their entities, insurances and licences on file, the same booking and confirmation flow, and the same compliance gates. One roster covers the whole blended crew.

Yes. Because timesheets are captured and approved against jobs, hours and labour costs accumulate per project as the work happens, with planned-versus-worked visible rather than discovered at month end.

Timesheets prefill from the roster, get submitted from phones on site and reach supervisors for same-week approval. Approved hours then flow to payroll without re-keying, including through the two-way Xero integration, and the same record drives job costing while the project is still running.

Yes. Site inductions, prestarts and incident reports are completed on mobile, timestamped and stored against the job, so the paperwork exists the moment the work does. When a principal contractor or auditor asks, the records are already in one place rather than in a ute's glovebox.

No. Humanz runs the workforce side: rostering, compliance, mobilisation, timesheets and the data payroll needs. It sits beside your project controls rather than replacing them.

Yes. The pool is filterable by availability, trade, tickets, hour limits and the specific client's site clearances, so a request is answered from workers who can genuinely take the placement. Open shifts can then be broadcast to all of them at once with one-tap responses.

Every worker's licences, tickets, inductions, medicals and VOCs are held with expiry dates and verification records. Alerts fire before anything lapses, and placements check the requirements of the client and site involved rather than a generic list.

New workers onboard from their own phones, with documents, tickets and licences uploaded once and held on their profile with expiry dates. From there they appear in the live pool with availability and credentials attached, ready to be filtered into the next placement.

Approval workflows are configurable, so hours can be approved by your coordinators or routed for host sign-off before they lock. Either way the approved record feeds payroll and invoicing from the same data.

It keeps the operational records licensing schemes and audits lean on: worker credentials with verification history, placement records, hours and approvals. The licence itself and its reporting stay with you, but the evidence stops being a quarterly assembly job.

Yes. Hours and fatigue are tracked across every placement a worker holds, and each client's site requirements are checked separately. A worker finishing nights with one host is flagged before being booked into a conflicting shift with another.

No. Humanz runs the on-hire side of the business: the live pool, credentials, placements, hours and the approved record feeding payroll and invoicing. Candidate sourcing and permanent placements stay with your CRM or ATS, and a desk doing only permanent placement is better served by one.

Not through a single national register, because none exists publicly. Verification means sighting the card, matching it to photo ID, and confirming the issuing details look legitimate. The WHS regulator in the issuing state can confirm cards it issued, and newer digital White Cards are significantly harder to forge than the old physical ones.

No. Building and trade licensing is state and territory based, so the search runs through the register where the work is performed, such as Service NSW, the VBA in Victoria or the QBCC in Queensland. High risk work licences are the partial exception, issued by states against national classes and valid everywhere.

No, a White Card carries no expiry date on paper. Most regulators treat it as lapsed, though, if the holder has been out of construction work for two years or more. So a 2011 card can still be valid, provided the holder has stayed on the tools, and asking when they last did construction work is a legitimate part of the check.

The date of the check, the register searched, the exact name searched, the result, the licence number and class, its expiry, and who performed the verification. Keep the evidence, a saved extract or screenshot, against the worker or entity it belongs to, so an auditor two years later gets an answer in minutes rather than a reconstruction.

At engagement, then on a cycle matched to risk, with annual re-verification a sensible floor for ongoing arrangements. Set alerts on every expiry date you capture, licences, insurances and inductions alike, because the register won't ring you when something lapses mid-project.

Yes, in the states that run labour hire licensing schemes. Victoria and Queensland both maintain public registers of licensed providers, and hosts in those states commit an offence by using an unlicensed one. South Australia and the ACT run schemes too. Check the provider's licence before you start on the individual tickets of the crew they send.

No. Licensing registers say nothing about public liability or workers compensation, which are separate documents with their own expiry dates. Request certificates of currency directly, check the insured entity name matches the contracting entity, and diarise the expiries alongside the licence dates.

A document portal is one central platform where business documents are stored, organised, accessed and managed. It replaces the patchwork of email attachments, shared drives, USB sticks and physical filing most field businesses rely on. Unlike a plain cloud folder, it controls who can see each document, tracks which version is current and watches expiry dates.

Cloud folders store files but don't manage them. A document portal adds role-based access controls, expiry date tracking, audit trails, version history, and integration with operational workflows. A folder tells you where a file is. A portal tells you who's accessed it, whether it's current, and what happens when it expires. For a field business with compliance obligations, that difference matters.

Any document with compliance, legal or operational significance: worker licences and certifications, insurance certificates, induction records, SWMS, site safety plans, employment contracts, contractor agreements, prestart check forms, incident reports, TFN declarations, and ATO-required payroll records. If you'd need to produce it for a Fair Work inspector, a WHS regulator or a principal contractor audit, it belongs in the portal.

In Humanz, yes. The document portal is fully accessible from the mobile app. Workers can view their compliance documents, access site safety documentation, complete and submit digital forms, and upload photos or files directly from their phone on site.

The expiry should flag a compliance issue in the roster, not just send a notification. Ideally the worker or contractor can't be scheduled again until the document is renewed. Alerts should also fire before the date arrives, so most expiries never bite at all.

Yes. In Humanz, subcontractors can be given controlled portal access to upload their insurance certificates, SWMS and licence copies directly, so a coordinator doesn't have to chase and manually file these documents. The coordinator reviews and approves, and the document is stored against the contractor's profile automatically.

Retention requirements vary by document type. Fair Work records must be kept for seven years. ATO business records for five years. WHS incident records are typically retained for at least five years, and longer if a claim is ongoing. A document portal that keeps records indefinitely, or with configurable retention periods, satisfies all of these obligations.

Their documents remain in the portal against their profile. This matters for post-employment compliance. A WHS investigation may require induction records for a worker who left the business two years ago. Deleting records when someone leaves creates risk. Retaining them in a structured portal with appropriate access controls is the correct approach.

Humanz stores documents in a secure, access-controlled environment. Personal information such as health declarations, emergency contacts and financial details is accessible only to authorised users. This aligns with obligations under the Privacy Act, which requires reasonable steps to protect personal information held about individuals. Access controls matter more than most people assume. The Office of the Australian Information Commissioner attributed 37% of the data breaches notified to it in the first half of 2025 to human error rather than attack, which is exactly the risk restricted access reduces.

There's no single figure in the Fair Work Act itself. The minimum rest between shifts comes from the applicable modern award, commonly 10 hours, and as low as eight under some construction and resources awards. Starting a new shift before the rest period has elapsed usually entitles the worker to overtime rates, and the fatigue it creates is a WHS risk the employer still has to manage.

Some do. Shift workers who are regularly rostered on Sundays and public holidays may be entitled to a fifth week of annual leave under the National Employment Standards, on top of the standard four. Check whether your rostering pattern triggers it before payroll assumes the default.

Rest period requirements depend on the applicable Modern Award, and many awards apply minimum rest requirements to casuals as well as permanent employees. The specific provisions vary by award. The casual loading (typically 25%) compensates for the absence of certain entitlements, but it doesn't waive WHS-related rest period obligations.

Under most Modern Awards, employees can be required to work public holidays with reasonable notice, but they must be paid at the applicable penalty rate (typically double time or double time and a half). Some awards allow substitution of another day in lieu. The specific provisions depend on the award and any enterprise agreement.

Generally no. The Fair Work Act applies to employees, not genuine independent contractors. Misclassify an employee as a contractor, though, and the Act applies retroactively, with serious penalty exposure. The Fair Work Ombudsman's guidance on contractor classification is worth reviewing for any business using subcontractors extensively.

Penalties for record-keeping breaches are set in Commonwealth penalty units, which are indexed periodically, so any dollar figure dates quickly. A body corporate faces a multiple of the individual maximum, higher tiers apply to serious contraventions, and in cases involving systemic underpayment penalties are multiplied by the number of affected workers. Check the current penalty unit value and the applicable multiplier with the Fair Work Ombudsman rather than working from a published dollar amount.

A Fair Work Inspector can investigate underpayment claims going back six years, and workers have six years from the date of underpayment to bring a claim. That's why record retention is set at seven years. It covers the full investigation window plus a buffer.

Long service leave in WA is governed by the Long Service Leave Act 1958 (WA). In the construction industry, portable long service leave schemes may apply for workers who move between employers. That's worth verifying with WorkSafe WA or a qualified employment advisor for your specific workforce.

A fatigue management plan is an operational document setting out how a business manages the safety risk of worker fatigue: the hour and rest limits, the controls at rostering time and during shifts, escalation steps when limits are approached, individual fitness-for-work assessment, and the records kept. It sits between a short fatigue policy and a full fatigue risk management system, and it's the document clients and regulators actually ask to see.

The model WHS laws don't name a specific document, but they require businesses to manage fatigue as a foreseeable risk, and a written plan is the practical evidence that you do. Mining and resources regulators expect documented fatigue management, and heavy vehicle operations are subject to prescriptive NHVR work and rest requirements. In practice, client prequalification makes a written plan effectively mandatory for most site businesses anyway.

They should come from your own risk assessment, but common starting points for Australian site work are a 12-hour maximum shift, a 10-hour minimum break, around 7 consecutive shifts with fewer for nights, and rolling caps on hours over 7 and 14 days. Count commute time in the daily total, and include a documented exception process; a limit that gets silently broken teaches crews the plan is optional.

Yes. A compliant 12-hour shift with a two-hour drive at each end is a 16-hour day, ending with the most dangerous drive of the week, and the roster can't see any of it unless the plan counts it. A door-to-door daily limit that includes the commute is the practical fix, alongside a journey rule so that past a set threshold the worker doesn't drive home.

A policy is one or two pages stating that the business recognises fatigue as a risk and commits to managing it. The plan is the working document underneath: the actual numbers, rostering controls, escalation triggers, fit-for-work checks and record-keeping. Most businesses have the policy; the gap that audits and incidents expose is almost always the plan.

For the structure, yes. The section headings transfer between businesses, and there's no prize for reinventing them. What a template can't supply is the content an auditor actually reads: your operation's real risks, limits your rosters can genuinely hold, and an escalation path naming people who exist. A downloaded plan with another industry's assumptions still inside it is arguably worse than no plan at all.

Annually at minimum, and immediately after any fatigue-related incident or near miss, any significant change to roster patterns or shift lengths, and any new client or site whose fatigue rules differ from yours. Reviews should look at actual hours, breaches, exceptions and TARP activations, not just re-read the document.

No single law mandates specific software. Australian WHS legislation does require employers to manage foreseeable fatigue risks, though, and a fatigue risk management system is one of the most effective ways to demonstrate compliance. In high-risk industries like mining and heavy transport, regulators increasingly expect documented evidence of systematic fatigue controls, and software provides the most reliable audit trail.

Focus on real-time roster integration rather than manual entry, mobile access for field workers, configurable alert thresholds that match your award and WHS obligations, audit-ready reporting, and ease of use for coordinators managing large crews under time pressure. A tool that's technically capable but too complex to use daily will be abandoned within a month.

Fatigue monitoring means tracking worker hours and rest periods. An FRMS is a broader framework of policies, controls and systems working together to manage fatigue as an organisational risk. Good software supports an FRMS but should be backed by solid workplace policies, worker education and supervisor training as well.

Yes. FIFO operations are one of the primary use cases. Extended rosters, remote sites, compressed swing patterns and travel time between home and site make automated workforce fatigue tracking essential. Manual spreadsheet tracking can't keep up with a large FIFO workforce.

It should. Fatigue doesn't care whose payroll a worker is on, and a subbie pulling shifts across your sites accumulates hours exactly like an employee. Look for a platform that applies the same fatigue policies and visibility to every worker type on the roster, contractors and labour hire included.

The best platforms, Humanz included, integrate fatigue monitoring directly with rostering and timesheets. Fatigue data flows automatically from your roster with no duplicate data entry, and payroll data can be cross-referenced to verify actual hours worked against scheduled hours.

Yes. Large mining and construction operations have the most complex fatigue management needs, but small and medium trades businesses benefit just as much. A two-person electrical contracting business running emergency callouts can rack up dangerous hours quickly, and a mobile-based worker fatigue app keeps that visible without needing a dedicated safety manager.

Modern FRMS software Australia platforms handle irregular shift patterns, rotating rosters and ad-hoc callouts as well as fixed weekly schedules. Humanz, for example, recalculates fatigue risk as roster changes are made, so a last-minute 12-hour callout is immediately assessed against the worker's recent hours and rest history.

If a supervisor overrides a fatigue alert and an incident occurs, the alert record becomes critical evidence in any WHS investigation. A documented alert that was ignored increases liability exposure considerably. Good fatigue management software makes it easier to act on alerts than dismiss them, by surfacing replacement workers, suggesting roster adjustments or escalating the issue to management.

We work with businesses across construction, mining services, trades and logistics Australia-wide.

Shift duration limits, minimum breaks between shifts, consecutive shift caps, rolling hours limits and night shift rotation rules. In Humanz that includes maximum shift length, earliest and latest start times, longer minimum breaks after night work, caps on consecutive days and nights, rolling hour maximums across 7 to 28 days and 3 months, and controls on permanent night work. Each policy applies at business, client or site level.

Yes. Set a policy at the client level and it applies to all of that client's sites. Set one at site level for individual sites. Anything without a specific policy falls back to your business default.

No. It flags the breach so the scheduler can make an informed call with assessment tools and internal processes. The decision stays with your team.

Fatigue warnings appear on the schedule page and are visible to planners and schedulers.

Every 3 days, via email, in-app alert, and push notification. They continue after expiry and stop automatically once the worker updates the item.

Yes. The same policies and alerts apply to subcontractors and labour hire workers scheduled through the platform, not just direct employees. That matters because audit questions about safe hours and current tickets don't distinguish between worker types, and neither should the system answering them.

Yes. When creating a policy you can start from a pre-populated template and adjust the limits to suit.

Software that turns fatigue rules (regulatory hours, internal policies, client requirements) into live rostering controls. Bookings are checked against accumulated hours with alerts as thresholds approach, and the records proving fatigue was managed build automatically.

A report tells you about a breach after the shift was worked. A gate checks the rule when the shift is being booked and stops the breach happening. Regulators and courts are considerably more interested in the second.

Humanz enforces the fatigue policies you configure, including daily, weekly and rolling-window limits, minimum rest between shifts and night-hour caps. Operators encode their standard, BFM or internal limits as policies and the roster gates against them. Accreditation obligations themselves remain with the operator.

More people than the driver. Under the HVNL's chain of responsibility provisions, schedulers, consignors and managers hold duties alongside drivers to ensure work demands don't induce fatigue breaches. A roster that pressures drivers into non-compliant hours implicates the business that built it, and subcontracted owner-drivers sit inside the chain too.

Yes. Hours count cumulatively across every shift type in the roster, which is exactly where manual systems fail. The Saturday depot shift quietly breaks Monday's driving limits.

Yes. Workers outside the HVNL's prescriptive hours, like depot crews, loaders and mechanics on irregular hours, still sit under the model WHS duty to manage fatigue as a foreseeable risk. Their hours also interact with driving limits when the same people do both, which is exactly the combination manual tracking misses.

Through the app. They get warnings when they're approaching limits, and can see rest requirements alongside their roster, so the conversation happens before shift acceptance rather than roadside.

Yes. Policies layer by business, client and site, so a WA mining contract's tighter limits can sit alongside standard rules for east-coast work, each enforced automatically for the relevant shifts.

Form builder software lets you create and customise your own digital forms (prestart checks, incident reports, inductions, approvals) without writing code. The better tools add conditional logic, photo and signature capture and mandatory fields, and store every submission with an audit trail so you can report on the data.

Paper and fillable PDFs don't enforce mandatory fields, capture photos at the source, link to the relevant job, or create a searchable record. Digital forms do all of that, reach the right person straight away, and let you analyse trends across submissions. None of that is practical on paper.

No, and you shouldn't accept a tool that requires one. A good form builder lets an admin assemble a prestart, incident report or approval from drag-and-drop fields and publish it in minutes. That matters beyond convenience, because the easier a form is to change, the more likely it stays current with how the work is actually done.

It should. Good mobile prestart checklist software lets workers complete forms offline and syncs automatically once they're back in range. Field operations regularly work in low-signal areas, so offline capability is essential rather than a nice-to-have.

Yes. There's no requirement for safety records to be on paper. What matters is that the form meets the content and sign-off expectations the regulator lays out for SWMS, and that submissions are stored with a clear audit trail, which digital handles better than paper.

The daily prestart. It's high volume and repetitive, so workers build the habit quickly and the payback shows up within days rather than months. Rebuild your existing form with its familiar wording and order first, then improve it once the crew trusts the new format.

Forms tie to jobs, shifts and individual workers, so a completed induction or sign-off can act as a compliance gate before someone is rostered to a task. This links your forms to credential tracking, onboarding and scheduling rather than leaving them as standalone documents.

In a single, searchable system with a timestamp and the submitter's name on every submission. That permanent audit trail is what lets you produce records on request and report on what your forms are telling you. Scattered emails and shared drives can't deliver it.

No. Forms in Humanz are designed, completed and reviewed by people. Your admins build them, your crews fill them in on the mobile app, and submissions are stored for tracking and reporting. There's no AI auto-filling or interpreting safety records today. That capability sits on our roadmap.

There is no single national maximum shift length that applies to all Australian workplaces. Maximum ordinary hours per shift are set by the relevant modern award or enterprise agreement, and typically sit at 8, 10 or 12 hours depending on the industry and shift arrangement. Separately, work health and safety law requires employers to manage fatigue risk regardless of what the award permits.

There's no single national cap on consecutive days worked. Some modern awards limit days worked before a break, particularly relevant on shutdowns and swing rosters, and the exact provision depends on the award covering the employee. On top of that sits the WHS duty to manage fatigue, which treats consecutive shifts and cumulative hours as risks regardless of what the award technically permits, and most large site owners impose tighter fatigue rules of their own.

Generally yes, where the applicable award or enterprise agreement permits it. Many awards allow ordinary shifts of up to 12 hours under specific shift arrangements, and even longer shifts aren't automatically unlawful. Legality isn't the whole question, though, because the employer's WHS duty to manage fatigue applies regardless, and a 12-hour shift at the end of a long run of them is a materially different risk even when every individual shift sits inside the award.

The minimum break between shifts is set by your award or agreement rather than by a single national rule. Ten hours is a common minimum in many modern awards, sometimes reducible to eight hours by agreement in defined circumstances. Because this is an award-level provision, the exact figure depends on which award covers the employee, so check the specific instrument rather than relying on a general figure.

The National Employment Standards allow an employer to request additional hours beyond 38 per week where those hours are reasonable. Reasonableness is assessed against factors including health and safety risk, the employee's personal circumstances and family responsibilities, operational requirements, whether extra compensation applies, the notice given, and the employee's level of responsibility. It is a balancing test, so the same number of hours can be reasonable in one situation and unreasonable in another.

Yes. Drivers of fatigue-regulated heavy vehicles are subject to the Heavy Vehicle National Law, which sets specific maximum work times and minimum rest times across multiple rolling periods, varying by accreditation tier and whether the driver operates solo or two-up. As an anchor, the NHVR's Standard Hours option caps a solo driver at 12 hours of work time in any 24-hour period and 72 hours in any seven days, with at least seven continuous hours of stationary rest. These limits apply in addition to award entitlements and work health and safety duties. Western Australia and the Northern Territory operate separate heavy vehicle fatigue arrangements.

Agreement does not remove an employer's work health and safety duty to manage fatigue risk, and it cannot override entitlements that an award or the National Employment Standards guarantee. Some award provisions, such as reducing a break between shifts, can be varied by agreement in defined circumstances, but the scope to do so is set by the award itself. Consent is never a substitute for a fatigue risk assessment.

It records every licence, ticket, induction and competency your workers hold, tracks expiry dates, and alerts the right people before anything lapses. Better systems also enforce credential requirements at the point of rostering, rather than just keeping a list.

Everything with an issuer and an expiry date. That means High Risk Work Licences, trade and occupational licences, driver and plant tickets, VOC records, White Cards, site and client inductions, medicals and drug-and-alcohol clearances, plus refresher-based training like first aid, working at heights and confined space. No two clients ask for exactly the same set, which is why the register has to map requirements to clients and sites rather than holding one flat list.

Expiry alerts watch each credential's date and notify the worker ahead of time by email, in-app message and push notification. Good systems repeat until the item is renewed, keep alerting after expiry, and stop automatically once the updated document is uploaded.

A check applied when a worker is assigned to a shift. If the worker is missing a required credential or holds an expired one, the system flags or blocks the assignment, catching non-compliant workers before they reach site.

Yes. A capable induction management software setup lets you map different credential and induction requirements to different clients and sites, so a worker compliant for one site isn't automatically treated as compliant for another.

At onboarding, before the worker is ever assigned a shift. Capturing licences, tickets and inductions as someone joins means expiry dates go in as the documents arrive and the alert clock starts immediately. It also prevents the most common failure mode, the worker who's been on the books for months with a gap nobody noticed.

A spreadsheet doesn't chase anyone, updates lag reality, documents end up scattered, and there's no link to the roster. As worker numbers and client requirements grow, the gaps multiply.

No. Humanz credential tracking is rules-based: you configure requirements and expiry settings, alerts fire on schedule, and compliance gates apply at rostering. AI is on the roadmap, but not part of how credential tracking works today.

A verification of competency, or VOC, is a practical assessment confirming that a worker can operate specific plant or perform a specific task to the required standard. An assessor observes the worker on the equipment, measures performance against the relevant unit of competency or standard, and records the outcome with a date and scope.

No law names the VOC itself. The legal driver is the WHS duty to ensure workers are competent for the work they perform, and a VOC is the accepted way to demonstrate that for plant operation. In practice most mining and many construction principals mandate VOCs through their site standards, which makes them contractually unavoidable even where legislation doesn't name them.

A high risk work licence is issued by a state WHS regulator for legislated classes of work, such as certain cranes and forklifts, and is valid across Australia. A VOC is not a licence. It's evidence of current competency on specific equipment, often demanded per site, and it applies equally to plant that needs no licence at all, like excavators and loaders.

For assessments that need to withstand client or regulator scrutiny, an assessor with current assessor qualifications and demonstrated currency on the plant, typically working through or with a registered training organisation. In-house checks by a competent senior operator are useful between formal cycles but usually won't satisfy a tier-one site standard that specifies independent or RTO-linked assessment.

There's no legislated expiry. Most businesses and sites work on one to two years for high-consequence plant, with earlier re-verification after incidents, long absences or a change of equipment type. The review date recorded on the VOC is what counts, and different sites are free to set different cycles.

The operator's name, the assessor's name with their qualifications and currency, the plant assessed down to make and model, the standard or unit of competency referenced, the assessment method, the outcome, and both the assessment date and a review date. The format matters far less than the fields. A one-page form that captures all of them beats a glossy booklet that misses the review date, because a VOC without an expiry quietly becomes permanent.

Often not. Many mining and construction principals require verification to their own site standard, so a VOC accepted at one operation can mean nothing at the next one up the road. Treat an incoming VOC as a claim rather than a fact, sight the actual record with its scope and dates, and budget for site-specific re-verification in the mobilisation timeline where the client's standard demands it.

No. Regulation 640 is entirely risk-based and contains no numbers, and the regulations as a whole set no maximum shift length, minimum break or cap on consecutive shifts. Numeric thresholds come from guidance like the Working hours code of practice, from awards and enterprise agreements, and from client site standards. The duty is to manage the risk and be able to demonstrate how.

It requires the mine operator, in complying with regulation 617, to manage risks to health and safety associated with worker fatigue, and that is the entire provision. There's no maximum shift length, no minimum break and no cap on consecutive nights anywhere in it. The numbers WA mining rosters actually run on come from the Working hours code of practice, awards and enterprise agreements, and client site standards, and the duty is to set safe limits for your own operation and prove you applied them.

Regulation 640 places the specific fatigue duty on the mine operator, but regulation 617 requires every business or undertaking at the mine to manage risks from mining operations, and section 19 of the WHS Act gives each employer a primary duty to its own workers. A contractor or labour hire provider holds duties at the same time as the operator. In practice the operator's safety management system and the contractor's plan are meant to work as one arrangement.

No, and it says so itself: a code does not have the same legal force as a regulation. It continues as a transitional code under the WHS Act, codes are admissible in court proceedings, and a court may use one as the standard when assessing the practices a business used instead. Ignoring it without a well-documented alternative is a poor position to defend.

Yes. Regulation 675B requires workers to be given information, training and instruction on the control measures that apply to their work, and names fatigue controls specifically. Unlike regulation 640 it carries its own penalty, so crews who have never been trained on your fatigue controls are a live compliance gap rather than a best-practice shortfall.

The documented fatigue limits and the plan they belong to, the roster as planned, the hours actually worked, and the record of allocations that were flagged against the limits along with what was done about them. Training records matter too, because regulation 675B requires workers to be given information, training and instruction on fatigue control measures. Records showing communication across shift changes round out the set.

Yes. Regulations 55A to 55D sit inside the WHS (Mines) Regulations and bind businesses at mines directly. The control measure factors in regulation 55D include the design of work, job demands, the systems of work and the condition of workers' accommodation, all of which a roster and camp arrangement directly shape. Roster design is a psychosocial control measure, not just a scheduling choice.

WHS compliance software helps a business meet its work health and safety duties by tracking credentials, inductions, site documents, hazard and incident records and safety forms in one system. The more capable products also apply those records as rules when work is allocated, rather than only storing them for reporting.

No, they're the same category of product under two names. Victoria never adopted the model WHS laws and still runs its own Occupational Health and Safety Act, so Victorian buyers say OHS where everyone else says WHS. What's worth checking isn't the label but whether the tool handles the framework your regulator enforces, since forms, duty-holder fields and exported reports should use the vocabulary your inspector does.

A register stores credentials and their expiry dates and can report on them. A gate applies that information at the moment work is allocated, preventing a worker being rostered onto a job they are not currently cleared for. A register tells you what happened; a gate changes what happens.

Whether the system can stop a worker being rostered onto a job their expired ticket doesn't cover, or whether it just sends someone an email. That single question separates a compliance gate from a compliance register, and it's the gap the whole category hides in. Follow up on site-specific inductions, subcontractor coverage, offline forms and what a single worker's audit export actually looks like.

Most jurisdictions have enacted the model WHS laws, but each does so through its own Act and regulator, and Victoria operates under separate occupational health and safety legislation. The core duties are broadly consistent, while specific regulations, codes of practice and notification requirements vary, so multi-state businesses need to check each jurisdiction they work in.

Yes. Work health and safety duties extend to workers a business directs or influences, not only direct employees. If subcontractor credentials sit outside the system used to allocate work, the compliance picture is incomplete precisely where blended crews make it hardest to keep track.

No. It removes the manual tracking that consumes a safety manager's week, such as chasing expiry dates and collecting paper forms, so the role can concentrate on risk assessment, consultation and site presence. The obligations remain with the business and its officers regardless of what software is used.

Not for most construction and trades use cases. Software-based asset tracking, where allocation and returns are logged in an app, covers most of what field businesses need. Hardware GPS trackers are useful for high-value mobile plant like excavators and trucks, but they aren't required for general tool tracking.

Fleet tracking usually means GPS-based tracking of vehicles. Asset tracking in a workforce context is broader. It covers all the tools and plant used by field workers, and focuses on allocation, availability and service schedules rather than live GPS positioning.

Yes. A proper asset register holds owned, leased and on-hire equipment in one list, with hire dates and return dates recorded against each item. Hired plant is where informal tracking costs the most, because gear with no recorded return date tends to stay on hire, and on the invoice, long after the job needed it.

Safe Work Australia requires that plant and equipment is maintained in a safe condition. Asset tracking software with service scheduling makes sure maintenance isn't missed and creates a documented record that the business met its duty. This matters most for powered plant and lifting equipment.

Yes, in platforms like Humanz. Workers see their allocated equipment as part of their shift details, which cuts the chance of arriving on site without the right tools or leaving equipment behind at the end of a job.

It comes out of the allocation pool, so it can't be assigned to a worker or shift until maintenance is done and the flag is cleared. That stops the familiar failure of a machine booked onto a job while it's sitting in the workshop. Once it's back in service, the asset returns to allocation with the work recorded in its service history.

A system with allocation records makes it immediately clear who had the asset, when they had it, and on which site. That information speeds up recovery and creates an accountable record if the asset is ultimately written off. Recovery matters more than it used to. Crime Statistics Agency Victoria figures reported by the RACV show 82,947 theft-from-vehicle offences in Victoria in the year to December 2025, up 9.5%, with power tools taken in 15,391 burglary incidents valued at $18,496,823.

There's no single best platform, because every product is strongest in the environment it grew up in. Deputy and Tanda suit fixed-location shift work, HR-led suites like Employment Hero suit businesses buying employment admin first, and field-heritage platforms like Humanz suit blended crews across construction, mining services and trades. Match the category to your operating model first and the shortlist mostly writes itself.

Pricing varies widely by platform and feature set. When we compared the published Australian price lists of eight vendors in September 2026, per-user list prices ran from about $6 to $15 per user per month, with minimum-spend floors, paid add-ons and quote-only tiers changing the real bill on most plans. Enterprise platforms are priced on a custom basis. Humanz pricing is quoted per business (every module enabled, shaped by workforce size) and is designed for the SME to mid-market construction and trades sector.

Yes, for most businesses managing more than 5–10 workers. The admin time saved on roster management, timesheet collection and compliance tracking usually exceeds the cost of the software within the first month, and you can test that claim against your own numbers with the free ROI and payback calculator. On top of that sits the reduced compliance risk, particularly around Fair Work record-keeping and WHS obligations, which is harder to quantify but real.

Three, drawn from the category that matches how your workforce operates. That's enough to compare properly and few enough to demo each one against your own messiest roster rather than the vendor's tidy sample data. Evaluating ten platforms usually means evaluating none of them well.

No, and you shouldn't. A platform that handles employees and subcontractors in the same system gives you full visibility across your labour. The key is making sure it supports contractor-specific compliance fields (ABN, insurance, trade licences) alongside standard employee profiles.

Most platforms integrate with the common Australian payroll systems, including Xero, MYOB, ADP and KeyPay, but the depth varies more than the marketing suggests and it is worth asking exactly which you are being offered. A file export is a snapshot: the moment an hour is corrected on either side, the two systems disagree until somebody reconciles them by hand. A two-way API integration keeps them in step in both directions. At absolute minimum you need a reliable export in a format your payroll system accepts. The ATO's STP reporting requirements make payroll accuracy a tax compliance matter as well as an operational one.

Payroll software processes payments. It calculates gross pay, applies tax and generates payslips. Workforce management software manages the inputs to that process: who worked, when, and for how long. The two are complementary and usually integrated. Workforce management sits upstream of payroll and provides the data that makes it accurate.

Start by sizing the gap. What records do you have, and how far back do they go? The Fair Work Ombudsman runs an anonymous inquiry line and provides guidance on voluntary disclosure. Implement a compliant system immediately and maintain it going forward. If the exposure is large, get advice from a qualified employment lawyer before approaching regulators.

Penalties scale with severity across three categories. Category 1 covers reckless or negligent conduct exposing someone to risk of death or serious injury, Category 2 a failure to comply with a duty that exposes someone to that risk, and Category 3 a failure to comply with a duty. Maximum fines for a body corporate run into the millions for the most serious category, and officers carry separate personal exposure that can include imprisonment. The model WHS Act is a template rather than the law itself: each state and territory enacts its own maximums, several index them annually, and Victoria sits outside the model scheme entirely, so check the current figure with the regulator for your jurisdiction rather than relying on a national number.

A site induction qualifies the person. It happens before a worker's first shift on that site and covers hazards, emergency procedures and site rules. A pre-start check clears the equipment, a daily documented inspection of plant before it's used. Both produce records an auditor will ask for.

Yes. Australian WHS regulators accept digital records, provided they're accurate, complete and accessible. Digital records are often more defensible than paper because they carry timestamps, user IDs and GPS data that paper can't provide.

It depends on the type of record. Fair Work Act timesheet records must be kept for seven years. WHS incident records generally need five years from the date of the incident, though this varies by jurisdiction. For induction records, the safe practice is the duration of the project plus seven years. When in doubt, retain longer.

Their ABN, trade licences and public liability insurance, all verified as current before any work commences, plus a completed site induction and a White Card. Expiry dates matter as much as the documents, because an insurance certificate that lapses mid-job is a gap nobody notices until a claim arrives. Tracking currency with automatic alerts is the practical fix.

Yes. The White Card (Construction Induction Card) is required for any person carrying out construction work in Australia, including subcontractors, labour hire workers and self-employed tradespeople. There's no exemption based on employment status.

Purpose-built field workforce platforms like Humanz are designed to consolidate forms, licences, timesheets, fatigue tracking and subcontractor management in one place. Generic HR platforms typically cover only part of the picture, which is why construction-specific tools are worth considering.

It's a platform that coordinates workers who operate outside a fixed office, covering rostering, compliance, timesheets, communication and documentation in one mobile-accessible system. The difference from standard workforce tools is the operating assumption: workers are spread across sites, live on their phones and work irregular patterns, so everything has to function fully from a mobile device.

Standard HR software is designed for office environments: fixed locations, stable patterns, desktop access. Field workforce management is built for dispersed, mobile workforces with complex compliance requirements and dynamic scheduling. The operational requirements are different enough that they usually warrant different tools.

Mining services, civil and commercial construction, mechanical and trade contracting, drilling and exploration, and field services such as utilities. What they share is dispersed crews, mixed workforces of employees and subcontractors, and compliance that has to be checked before every deployment. If your workers start their day at a site gate rather than an office door, the category applies to you.

The best platforms manage subcontractors and direct employees from the same interface, covering scheduling, compliance tracking and communication. That removes the parallel manual systems and puts subcontractors in the same compliance view as your own staff.

It should. A platform built for Australian field industries needs to function in low-connectivity environments and sync data when connection is restored. Humanz is designed with this in mind.

Yes. Small is the norm in these industries, not the exception. Master Builders Australia's industry figures show 98.6% of Australian construction businesses employ fewer than 20 people. A ten-person mechanical contracting team or a plumbing business with a handful of crews gets the same efficiency and compliance gains as a 200-person mining services contractor. The platform scales to your workforce size.

Humanz generates digital timesheets automatically from roster data, which feeds into payroll. Digital timesheets remove double data entry and the payroll errors that come with manual timesheet processing.

Paper-based onboarding for a field worker typically takes 1–3 days from offer acceptance to job-ready, assuming no delays in document collection. Digital onboarding through a platform like Humanz can bring that down to same-day or next-day in straightforward cases, because workers complete forms and upload documents from their phone before they arrive on site.

The day the offer is accepted, not the worker's first morning. Documents, licence uploads and induction modules can all be completed from the worker's phone before day one, so the start date is spent working rather than filling in forms. Waiting until they arrive on site is how a paid day becomes an admin day.

Yes. Under the model Work Health and Safety Act, adopted in most Australian states and territories, persons conducting a business or undertaking (PCBUs) must give workers the information, training and instruction they need to work safely. That includes a site-specific induction before work commences. Deploying a worker who hasn't been inducted creates direct WHS liability.

Yes. There's no legal requirement for onboarding documents to be paper-based. Digital documents, electronic signatures and online form submissions are all legally valid, and often more defensible than paper because they carry timestamps and user identification.

Only if the outstanding steps don't gate site entry. The site induction and licence verification must be complete before any work starts, because both are safety requirements rather than paperwork preferences. Payroll items can be chased afterwards at a pinch, though missing declarations turn into payroll errors that are expensive to unwind.

They shouldn't be deployed to site in any role that requires the licence. Under Australian WHS law, putting an unlicenced worker on licenced work creates serious liability for the business. A good onboarding and compliance system prevents it by flagging the gap before the worker can be scheduled.

The compliance elements are the same for both: White Card, trade licence, site induction and any site-specific requirements. The employment side differs, with an ABN and contractor agreement in place of a TFN declaration. A platform like Humanz runs both through the same workflow, with different fields for each worker type.

At minimum: the signed employment or contractor agreement, TFN declaration or ABN, White Card, any role-specific licences, site induction records (with a timestamp and the version of the induction form used), and superannuation choice. The ATO and Fair Work Ombudsman both publish new starter checklists worth bookmarking.

Each site typically has its own induction requirements. A good system stores the worker's base credentials (licences, White Card) centrally and lets site-specific inductions be completed separately for each site. The worker's profile then shows which sites they've been inducted at, so coordinators know where they can be deployed.

Messages sent through a workforce management platform like Humanz are stored on secure servers, not on workers' personal devices. Access is controlled by the platform. When a worker or contractor leaves the business, their access is revoked and they can no longer see job communications.

In Humanz, messaging is two-way. Workers can start conversations with supervisors, and supervisors can message individuals or broadcast to groups. The structure keeps job-related communication organised rather than siloed in one direction.

Make the app the only place work information is authoritative, then stop duplicating it anywhere else. Rosters, site changes and safety alerts go through the app from a set date, supervisors stop answering the old group, and workers follow the information. Running both channels in parallel for months is what kills these transitions, because everyone keeps watching the old one.

They can. A timestamped message with read receipts shows what was communicated, when, and who saw it, which is far stronger than anyone's memory of a verbal briefing. Messaging records complement formal induction and training documentation rather than replacing it, but they cover the ground where most disputes actually start: the day-to-day instructions between formal documents.

Most platforms, including Humanz, can send SMS notifications to workers who haven't yet installed or logged into the app. This is useful during onboarding and for casual workers who haven't been set up in the system yet.

For day-to-day field communications (site updates, shift changes, safety alerts) yes. In-app messaging beats email for field workers who are rarely at a desk. Formal documentation such as contracts and formal notices still warrants email or written correspondence.

Two-way radios are useful for real-time voice on a single site. In-app messaging does a different job. It covers asynchronous communication across multiple sites, with a written record, read receipts and a link to job context. They're complementary tools rather than alternatives.

Single sign-on lets people access an application using an existing account from a central identity provider, such as a Microsoft work account, instead of a separate username and password held by that application. The application never stores the password, and access is controlled in one place rather than app by app.

No, they are different controls that work well together. Multi-factor authentication proves identity using more than a password. Single sign-on determines where identity is checked. Using SSO means multi-factor authentication can be enforced once centrally and inherited by every connected application, and that inheritance carries weight. Microsoft's Digital Defense Report 2025 found MFA blocks over 99% of identity-based attacks.

Yes. Humanz supports Microsoft single sign-on across both the web app and the mobile app, which matters because in field businesses the mobile app is where most of the workforce actually signs in. Support on the web app alone would leave the majority of users outside the system.

With single sign-on, access depends on the central account being able to authenticate, so disabling that account removes the route into connected applications. Without it, each application holds its own credentials and has to be revoked separately, which is the step most commonly missed during offboarding.

It varies, and it's worth asking before you're deep into procurement. Some vendors include single sign-on on every plan, while others reserve it for enterprise tiers, where it surfaces as an unwelcome surprise late in the deal. Get the answer in writing alongside your other pricing questions, not after the contract is drafted.

Both, and the setup is small on each side. Your IT administrator approves the connection from the Microsoft side, the vendor enables it on theirs, and sign-in then runs through your existing directory. The ongoing work of adding and removing people stays where it already lives, in your Microsoft admin centre.

Not through your tenant, because they do not have an account in it. This is worth raising with any vendor early, since blended workforces are normal in field operations and a platform needs a sensible way to manage access for people who sit outside your directory.

HR platforms manage employment lifecycle, payroll, and leave. Onboarding software for mining and construction focuses on the pre-deployment stage: document collection, qualification verification, induction management, and mobilisation logistics. Humanz handles both onboarding and ongoing operational management in a single system.

Mining sites add principal contractor compliance packs, site-specific mandatory inductions that often need annual renewal, fit-for-work declarations covering fatigue and drug and alcohol status, and state mining regulator requirements around competency verification. FIFO rosters add fatigue declarations before each swing. Construction onboarding is demanding, but mining layers client and regulator requirements on top of it.

The day the role is confirmed, because several requirements have lead times you don't control. Site medicals, client induction modules and competency verifications all depend on third parties, and sites generally won't grant access until each item is in place. Start the document chase late and the crew flies a person short.

Entirely. Workers complete the whole process from their phone, uploading documents, completing induction modules and submitting declarations, without needing a computer.

Yes. Humanz provides separate onboarding tracks for employees and subcontractors, capturing the different documentation requirements for each. This counts double for businesses working with principal contractors who require evidence that all workers on their sites have been properly onboarded.

Humanz maintains a single worker profile that carries all qualifications and documents across sites. Site-specific inductions are added as the worker moves to new projects. They don't need to re-upload their white card each time, but they do complete a new site induction where required.

Humanz sends automatic alerts before expiry, to the coordinator and optionally to the worker, giving time to arrange renewal before the ticket lapses. If a ticket does expire, the system flags the worker as non-compliant for roles requiring that qualification, preventing them from being rostered until renewal is confirmed.

Yes. All records are stored with timestamps against the worker's profile and remain accessible even after the worker leaves the business. That matters for WHS investigations, where induction status at the time of an incident may be queried years later.

No. Humanz is a workforce management platform, not a project management tool. It handles the labour and people side of project delivery: rostering, timesheets, compliance and communication. It works alongside project management tools rather than replacing them. Humanz data on actual hours by project, shift fill rates and compliance status feeds into project financial and progress tracking.

Mobilisation failure, more often than anything else. Crews arrive short because confirmations were informal, a worker is turned away over an expired ticket, or a subcontractor's compliance wasn't verified before day one. A structured mobilisation workflow with confirmations and compliance checks completed before the start date is the cheapest schedule protection available.

Link every shift and timesheet to a project, so actual hours accumulate against the plan as they're worked rather than at reconciliation. A running planned-versus-actual figure shows an overrun developing while there's still time to change the roster, where a monthly report only tells you what it cost. Overtime deserves its own line, because it's the quietest way a labour budget disappears.

By generating accurate historical data on actual hours worked per project type, overtime incurred and fill rates, Humanz gives estimators a factual foundation for labour cost modelling. Over time the gap between estimated and actual labour costs shrinks, because estimates draw on real historical patterns rather than assumptions.

Yes. Multi-project management is a core use case for Humanz. Coordinators and operations managers see resource allocation across every active project in one view, so conflicts get spotted early and trade-off decisions are made with full information.

Fatigue alerts fire in Humanz at the point of scheduling, before a shift is confirmed. If a project schedule requires a crew to work a pattern that pushes workers into fatigue risk, coordinators see it before the roster is locked in. The project manager can adjust the schedule rather than react to a compliance issue or incident after the fact.

Subcontractors are managed in Humanz from the same scheduling interface as direct employees, with their compliance status, availability and booking history visible to project coordinators. When a subcontractor is booked onto a project job, they receive the same shift notifications and pass the same compliance checks as direct employees.

Humanz generates exportable reports on labour hours by project, compliance status and workforce utilisation. These can be formatted for client reporting, principal contractor compliance submissions or internal management presentations.

Yes. Humanz handles projects ranging from a two-person callout to a multi-site project with hundreds of workers. The scheduling, compliance and communication tools scale with the crew, and there's no minimum or maximum workforce requirement.

WFM stands for workforce management. WFM software is the category of tools a business uses to plan, deploy and manage its workforce, covering scheduling, time and attendance, compliance, communication, reporting and digital forms. The terms WFM system, WFM platform and workforce management software all describe the same category.

They overlap but aren't the same. HR software handles employment lifecycle, payroll, and performance management. WFM software focuses on operational scheduling, time tracking, and day-to-day workforce coordination. Many businesses use both, WFM for operations and HR for employment management. Humanz covers the operational and compliance dimensions of both.

A rostering app schedules shifts. A WFM system does that plus timesheets, compliance, communication, documentation, and analytics. For simple businesses with stable patterns, a rostering app may be enough. For field businesses with compliance-heavy operations, a full WFM system delivers far more value.

When the manual system starts creating operational failures rather than just admin work. The usual signs are a no-show caused by a missed roster update, a worker deployed with an expired ticket, payroll taking days to reconcile, and compliance questions you can't answer quickly. Any one of these occasionally is normal, but several of them regularly means the spreadsheet now costs more than software would.

Yes. A ten-person trade contracting business running callout work has just as much to gain from digital timesheets, licence tracking, and structured communication as a 200-person mining services contractor.

Published Australian prices mostly sit between $6 and $15 per user per month, with minimums and add-ons doing quiet work underneath, while compliance-heavy platforms including Humanz quote per business on workforce size and scope.

Generally no. WFM software generates the time and attendance data that feeds into payroll, but payroll processing (tax calculations, superannuation, pay slips) is handled by a dedicated payroll system. Humanz integrates with payroll systems to provide a clean, verified data feed.

Most Humanz customers are operationally live within days to a couple of weeks. The main tasks are importing worker data, setting up sites and projects, and configuring roster templates and compliance rules.

Start with shift fill rate, planned versus actual hours, and no-show rate by worker and site. Those three expose the most expensive problems in a field operation: unfilled shifts, quiet overtime and unreliable coverage. Fatigue alert frequency and override rates belong on the list next, once the basics are being watched.

In Humanz, analytics are generated automatically from the operational data your team creates. Rosters, timesheet submissions, compliance alerts, shift confirmations. There's no separate setup required to start generating data. Dashboards are available from day one and become more meaningful as data accumulates over weeks and months.

Even a small team using Humanz for a few weeks generates useful patterns. Shift fill rates and timesheet accuracy reports mean something from the first week. No-show patterns and overtime trends take a month or more to firm up. The longer you run the platform, the richer the historical context gets.

It means a safety control is being switched off shift by shift, and the reason is worth finding before an incident finds it for you. Either the thresholds don't match how the business actually works, or coordinators are under pressure to push workers through alerts. Both are fixable, but only if someone is measuring the override rate rather than assuming alerts get acted on.

Yes. All worker types tracked in Humanz contribute to the analytics layer. Shift fill rates, no-show data and compliance status can be filtered by worker type, so you can see the picture for direct employees and subcontractors separately or combined.

All operational data in Humanz is retained for the full period of your subscription and beyond, in line with Australian record-keeping requirements. Historical comparisons, month over month and year over year, become available as data accumulates.

Yes. Reports can be exported from Humanz in formats suitable for client reporting, principal contractor compliance submissions, and management presentations.

Humanz generates the labour cost data (actual hours by worker, overtime volumes, project allocations) that feeds into financial reporting and project cost reconciliation. For businesses using accounting platforms, this data can be exported straight into job costing or project financial tracking.

Your own data is the most relevant benchmark for your business. Comparing this month to last month tells you more than comparing your business to an industry average. That said, Safe Work Australia's data publications and Australian Bureau of Statistics workforce data provide industry-level context for metrics like injury rates, overtime prevalence and workforce mobility.

A rostering app schedules shifts. A workforce management app manages the full operational picture in a single platform: rostering, timesheets, compliance, communication, documentation, and assets. For field teams managing complex, compliance-heavy operations, a full workforce management platform delivers far more value.

Everything their working day requires: viewing and confirming shifts, clocking on and off, submitting timesheets, completing prestarts and other forms, reading job details and receiving change notifications. If any of those needs a browser or a desktop login, the app wasn't built for the field. The test is whether a worker's whole day runs from their pocket, from shift offer to approved timesheet.

The best platforms can. In Humanz, a subbie sits on the same roster, carries the same compliance profile and receives the same app notifications as a direct employee. One workflow for the whole crew. For trades and construction businesses that lean heavily on subcontract labour, that single view is often the deciding feature.

Field workforce management software should be designed for low-connectivity environments. The Humanz mobile app is built for use in areas with limited data access. Key functionality works offline and syncs when connectivity is restored.

In most field businesses, yes, and a well-designed app makes that workable. Workers shouldn't have to share personal phone numbers, the app has to behave on ordinary phones in poor coverage, and access should end cleanly when someone leaves the business. Businesses that prefer company-issued devices can run the same app on those instead.

Not automatically. But an Australian platform is far more likely to reflect local compliance requirements (Fair Work, WHS, state-specific licencing) in its design rather than requiring workarounds. Humanz was built for the Australian trades and resources sector from the ground up.

Pricing varies by platform and business size. Small crews get as much out of a field-ready app as large ones, a case we make in workforce management for startups and small businesses.

Published Australian prices mostly sit between $6 and $15 per user per month as at early September 2026, depending on vendor and tier. Minimum monthly spends, paid add-ons, GST treatment and how the vendor defines a billable user all move the real figure. The compliance-heavy end of the market doesn't publish prices at all and quotes per business instead.

Check for minimum monthly spends, paid add-on modules, per-message SMS charges and whether prices are in Australian dollars, since at least one major vendor bills in US dollars. Ask how a billable user is defined, because active-user billing and higher-of-contracted-or-active billing can hold the invoice at peak levels. Then ask what implementation involves and how many of your own admin hours it will consume.

Minimum monthly spends set a floor under the per-user price. Deputy applies a $30 monthly minimum, RosterElf wants at least 10 seats on annual billing, and foundU charges $400 a month for anything under 25 employees, so a 20-person crew pays the minimum rather than 20 times the sticker. Always work out your actual invoice at your actual headcount before comparing anything.

Setup effort varies widely between businesses once compliance is involved. Pay rules, credential and induction loads, subcontractor arrangements and payroll integration all differ, so vendors at that end scope the work before naming a figure. A quote is fair when the vendor can explain what about your business changes the price, and a warning sign when they can't.

Not on its own. Field and compliance platforms carry setup work that differs so much between businesses that one honest public number is hard to print. It becomes a red flag when the product is simple or the vendor can't say what specifically drives your price. Always get the total first-year cost in writing on your real headcount.

Yes, at the very small end. Connecteam publishes a free Small Business Plan covering up to 10 users, with its all-features claim qualified by a footnote, and it was the only genuinely free tier among the vendors we checked in September 2026. Free plans suit simple rostering for a handful of staff, but once compliance tracking, subcontractors or payroll integration matter, you're into paid territory.

Compare total monthly cost per rostered hour rather than the per-user sticker, then weigh the admin hours each tool removes and the operational failures it prevents. For field businesses, chased timesheets, no-shows and workers turned away over expired credentials usually cost more than any subscription. The cheaper tool wins on the price tag and often loses on that maths.

Software that manages everything between winning work and crews starting it. Assigning people, verifying site-specific compliance, booking travel, allocating equipment and confirming attendance, all in one live view connected to the roster.

Onboarding brings a worker into the business. Mobilisation gets a workforce ready for a specific site or project. They overlap heavily for new hires, which is why they work best in the same platform.

Five things per worker: confirmed availability for the dates, compliance current for the whole deployment window, travel and accommodation booked to match the roster, equipment allocated and serviceable, and paperwork acknowledged before day one. Every item needs an owner and a due date well ahead of departure. The checklist fails at whichever item nobody was watching, which is the argument for holding all five in one system.

With profiles current and templates set up, businesses routinely turn a client order into a confirmed, compliant, travel-booked crew inside a couple of days. The bottleneck becomes flights, not paperwork.

Yes. Subcontractors carry their own compliance profiles (insurances, licences, inductions) and are assigned, checked and confirmed through the same process as direct employees.

The gap shows on the mobilisation checklist and the worker is flagged at rostering, so the issue is fixed, or the worker swapped, before departure day rather than at the site gate.

Yes. Flights, drive days and accommodation appear in each worker's app schedule alongside shifts, with notifications when anything changes.

It should, because getting off site cleanly matters nearly as much as getting on. Demobilisation means equipment returned and condition-checked, travel home booked, and worker profiles updated so the next mobilisation starts from accurate records. Gear that was allocated and tracked at mobilisation is the gear that comes back at the end.

Software that manages an on-hire workforce end to end, covering worker compliance profiles, availability, placement rostering across client sites, attendance confirmation, and timesheets that feed both payroll and client billing.

It maintains the evidence licensing schemes ask for: right-to-work checks, qualification records, placement history, hours and pay records, all timestamped and exportable. The licence obligations remain yours. The software makes them provable.

It produces the approved hours both sides need rather than raising the invoices itself. Each timesheet is approved against the placement, so the same record drives what the worker is paid and what the host is billed, exported per client and site. Your accounting system still generates the actual invoice.

Yes. Employees, casuals and ABN subcontractors sit on the same roster, each with the compliance profile their engagement type needs. A subbie's record tracks insurances and licences rather than employment details, and placement gates apply to all of them equally.

No, it takes over after the hire. Candidate sourcing stays in your ATS. Humanz manages the placed workforce across compliance, rostering, confirmation, time capture and reporting.

Yes. Placements are scheduled per client and site, and safe-hours and fatigue checks run across the worker's whole week rather than per host, so combined hours stay compliant.

Through the mobile app. They see the site address, start time, host details and any placement notes, with push notifications when something changes and one-tap confirmation.

Reporting can be shared per client (fill rates, hours and compliance status for their sites) without exposing the rest of your pool.

It's software that plans and runs a mining or mining services workforce end to end: swing rosters, FIFO travel and accommodation, fatigue limits, site credentials, timesheets and reporting in one system. The distinguishing feature against generic rostering tools is that swings, sites, camps and blended crews are built into the data model rather than bolted on.

The common Australian patterns are 8/6, 2/1 (14 on, 7 off), even-time arrangements like 7/7 and 14/14 for residential crews, and longer 3/1 swings for some remote operations, plus shutdown surges that follow no pattern at all. The software should hold the pattern once and generate the forward roster, rather than requiring planners to place every shift.

Fatigue rules (maximum shift length, minimum breaks, consecutive-day caps and rolling hour limits) are configured as policies, often layered by client or site. The scheduler then checks every allocation against the applicable policy as it's made and flags breaches before the shift is confirmed, which is both safer and easier to evidence in an audit than after-the-fact reports.

Yes. Travel and accommodation attach to the shift itself, so booking a swing carries its flight and room requirements with it. Move the swing and the logistics move too, with the changes surfaced to whoever manages the bookings.

Each worker's profile holds their national units, licences, medicals, and company and site inductions with individual expiry dates. The roster then acts as a gate: a worker missing a required ticket or a current induction for that site can't be booked onto the job, and alerts fire before anything lapses.

Yes, and for shutdown-driven businesses it's close to mandatory. In Humanz, subcontractors and labour hire workers carry their own compliance profiles but sit on the same roster as employees, so planners crew a job from one view and every worker type passes the same credential and fatigue checks.

It has to. Workers confirm shifts, submit timesheets and read updates in the mobile app, and submissions made without coverage sync when connectivity returns. Coordinators in the office see live data the moment it lands.

Humanz was founded in Perth in 2019, and mining services businesses running crews across multiple sites and clients were among its earliest users. Swings, camp logistics, layered fatigue policies, site credentials and blended crews are core features rather than customisations. The short version of everything this guide covers is on the mining workforce management software page, and the broader platform lives on the workforce management software page.

Yes. Real-time, multi-site rostering is a core capability. You can build rotating morning, afternoon and night patterns, see all sites in one view, and adjust coverage live as availability and demand change.

Humanz holds each worker's qualifications, licences and inductions with their expiry dates, sends alerts ahead of time, and can apply compliance gates that prevent a worker being rostered onto a shift when a required credential, such as a registration, screening check, immunisation or first aid certificate, isn't current.

No. Humanz does not manage care plans, medications, resident records or any clinical workflow. It's a workforce management platform that handles the rostering, credential-tracking, timesheet and compliance layer that sits underneath those systems. Care providers run Humanz alongside their clinical software, not instead of it.

By showing you who's eligible before you start ringing. Coordinators filter the casual and agency pool by availability, qualification and induction, push the open shift to eligible staff through the app, and track responses in one place. Shift confirmation also surfaces unacknowledged shifts early, so gaps appear while there's still time to fill them.

Yes. Permanent, casual, agency and subcontracted workers can all sit on the one roster, each with their own qualifications and compliance profile, so you can offer open shifts only to people who are eligible and available.

Yes. Rosters, timesheets, credentials and documents live in one system, so you can show who worked each shift and that they held the required checks at the time. That evidence is generated as a by-product of running the roster rather than assembled under pressure before an inspection.

Humanz is not a payroll system and doesn't replace formal award interpretation. It helps you build rosters with award conditions like penalty rates and rest periods in mind, and digital timesheets feed cleaner data into your payroll system. For your obligations, check directly with the Ombudsman.

The rostering, credentialing, timesheet and mobile capabilities apply to both residential and community settings. Mobile access and digital timesheets are particularly useful for community care workers moving between client visits.

No. Humanz is built for field, operational and shift teams in construction, mechanical contracting, mining services, drilling and trades. It suits retail, hospitality and events teams whose main challenge is managing a variable, casual, multi-site shift workforce, but it doesn't include industry-specific features like POS-linked demand forecasting.

Yes. Shift confirmation tracking shows you who has acknowledged their shifts and who hasn't, so unconfirmed shifts surface early enough to chase or replace. Combined with mobile notifications, it closes the gap between publishing a roster and staff seeing it.

Yes. Licences sit on each worker's profile with expiry dates, and alerts flag anyone whose ticket will lapse before a rostered shift. That stops a casual working the bar on an expired RSA, and it applies the same way to RCG, security licences and first aid.

Yes, provided the trade goes through the system rather than the group chat. When a swap is handled in the app, the roster, the timesheet and the pay run all tell the same story, and the scheduler can see who actually worked. Sorting it by text leaves the record wrong in three places.

No. Humanz is a workforce management platform, not a payroll system, and it doesn't interpret awards for you. It gives you clear visibility of hours, sites and coverage so award and penalty-rate decisions are easier to make. Check the Ombudsman's pay guidance and the Fair Work Commission's award finder for the rules that apply.

Through fast onboarding, bulk scheduling, document distribution via the portal and instant mobile notifications. It's the same mobilisation tooling used to stand up field crews quickly, and expiry alerts flag any surge casual whose licence would lapse before the event.

Through the Humanz mobile app. Published rosters, last-minute changes, confirmations and messages all arrive on the worker's phone, so the schedule and the communication are the same thing rather than two separate steps.

Yes. Digital timesheets capture actual start, finish and break times from the mobile app, which can be approved against the roster and used for payroll. Workforce analytics then let you compare rostered and worked hours across sites.

No, not today. AI is on the Humanz roadmap but not part of the product yet. Rostering, filtering and confirmation are handled through real-time tools that schedulers control directly.

HR software looks after the employment lifecycle (contracts, leave, performance, payroll). Workforce management software runs the operational side: rostering, timesheets, compliance and real-time visibility of who's working where. For construction businesses, workforce management is usually the more pressing need, though many platforms now offer elements of both. The same operational priorities apply across other shift-heavy sectors.

No, and you shouldn't. A construction workforce platform that handles both worker types in one system gives you a complete picture of your labour across every job. Separate systems create version control problems and compliance gaps. The requirement that matters is support for different profile fields and compliance rules per worker type.

At minimum: Fair Work Act record-keeping (7-year timesheet retention), WHS Act requirements (induction records, incident reporting, fatigue management), and licence tracking for all workers and subcontractors. For businesses operating under specific Modern Awards, penalty rate and overtime calculations matter too. The Fair Work Ombudsman and Safe Work Australia both publish detailed guidance on what employers are required to maintain.

It's non-negotiable. Construction workers are not at desks. Any platform that requires desktop access for core functions (timesheet submission, roster viewing, form completion) won't be adopted by field workers. The mobile experience needs to match the desktop, and it needs to work offline.

Yes, for any business running long shifts, early starts or back-to-back rosters. Fatigue tracking built into the roster checks cumulative hours at the point of scheduling and flags a worker who hasn't had adequate rest before the shift is locked in. A separate fatigue tool that only reports after the fact leaves the gap exactly where the risk sits.

Yes, and it's one of the bigger wins. Pre-starts, inductions, incident reports and toolbox talk records completed on a phone carry timestamps that prove when they were done, and nothing has to be found, deciphered and re-entered later. Principal contractors increasingly expect that standard of evidence before anyone walks on site.

For a small-to-medium construction business (20–100 workers), implementing a platform like Humanz typically takes days to a few weeks, depending on how complex your roster setup is and how much historical data you want to migrate. Most businesses are running active rosters within a week.

Logistics workforce management software is a platform that helps transport and logistics operators roster, schedule and manage their people (drivers, depot crews and warehouse teams) alongside the compliance, timesheet and asset obligations that come with the industry. Unlike generic rostering tools, it's built for a mobile, multi-site workforce and the safety rules specific to freight, such as heavy-vehicle fatigue management.

Humanz monitors fatigue against the roster itself, tracking cumulative hours and flagging when a worker is approaching an unsafe threshold before a shift is published. It doesn't replace your obligations under the National Heavy Vehicle Regulator's framework, but it builds fatigue limits into the planning step and keeps the records that demonstrate work and rest hours were managed. Those obligations grew on 1 August 2026, when a National Heavy Vehicle Regulator rule took effect prohibiting driving any heavy vehicle over 4.5 tonnes GVM while impaired by fatigue.

Yes. A purpose-built platform like Humanz provides real-time, multi-site rostering so you can schedule drivers, depot crews and warehouse shifts across every location on a single live view. That makes it easy to spot coverage gaps and move people between sites.

Yes. Pre-starts, fitness-for-duty declarations, defect reports and incident records are captured as digital forms on the driver's phone, timestamped where the work happens. That produces the documented evidence a regulator expects without paper that gets lost in a glovebox.

Yes. Prime movers, trailers, forklifts and other equipment are assigned per shift at the same time the worker is scheduled, so there's always a record of who had what. Service due dates are monitored in the same place, instead of in a separate register.

Timesheets are pre-filled from the published roster, so the starting point reflects what was scheduled. Workers and supervisors capture and approve any variations, every change is logged in an audit trail, and the approved records are ready for export toward payroll, which cuts the re-keying errors common with paper timesheets.

Three areas. Fair Work record-keeping, through digital timesheets with audit trails. WHS fatigue management, through roster-integrated monitoring. And credential compliance, through expiry alerts and gates on licences, inductions and medicals. Because everything sits in one platform, producing records for an audit or investigation is straightforward.

Yes. Humanz is used by businesses of varying sizes across field-based industries. For a small-to-medium operator, implementation is typically quick, and the value is often immediate. A single live roster, confirmed shifts and digital timesheets replace several disconnected tools straight away.

Not yet. Automatic scheduling, including AI that would build a fatigue-compliant driver roster for you, is on the roadmap but not in the product today. For now, your planners build the runs manually, with Humanz supplying real-time visibility across depots, shift confirmation and compliance gates to keep unsafe or non-compliant rosters from going out.

It's a platform that handles the operational side of managing a production workforce in one system: rostering and shift scheduling, confirmation tracking, skills and licence matching, fatigue monitoring, timesheets and compliance. It differs from HR software, which focuses on the employment lifecycle (contracts, leave, performance). Manufacturers usually feel the workforce management need most acutely, because coverage and compliance directly affect whether the line runs.

Yes. Good manufacturing rostering software supports rolling, repeating shift patterns, including two- and three-shift operations and rotating panama or DuPont rosters, so you build the pattern once and reuse it rather than rebuilding each cycle. It should also let you reallocate people quickly when a machine goes down or demand shifts.

By bringing fatigue into the roster itself. The system tracks cumulative hours and consecutive shifts and warns before a worker crosses an unsafe threshold, helping you manage fatigue as the WHS control it is. Because the regulator treats work scheduling as a primary fatigue control, keeping that logic in the rostering tool rather than in someone's head is the practical way to meet the obligation.

Each worker has a credential profile with licences, tickets, competencies and inductions, plus their expiry dates. The system alerts you before anything lapses, and compliance gates can stop an uncredentialed or expired worker being rostered onto a restricted machine or task, so the control is enforced rather than relying on memory.

Yes. A flexible pool of casuals and labour hire can be onboarded and credentialed once, then held in the same system as your permanent crew. When you need to fill a shift, you draw from a known, pre-qualified group, and the same compliance rules apply to everyone, so a casual is never placed on a task they aren't cleared for.

Significantly. Timesheets prefilled from the roster start with the planned hours already captured, so supervisors confirm or adjust actuals rather than entering everything from scratch. That reduces transcription errors, creates an audit trail of approvals, and gives payroll clean, defensible records aligned to the relevant award.

Yes, through structured digital forms. The outgoing crew completes a handover form on a phone or tablet covering machine status, quality issues, outstanding maintenance and safety concerns, and the incoming crew sees it before they start. Every handover is timestamped and retained, so nothing critical gets lost between teams.

Yes. Because credentials and rosters live in the same system, reporting can show whether each critical station has enough certified operators or is relying on a single person. The same analytics surface chronic coverage gaps, no-show rates and overtime trends, which feed hiring and cross-training decisions.

Not today. Humanz does not currently have AI features in the product. Automated scheduling is on the roadmap rather than available now. What Humanz provides today is real-time manual rostering with confirmation tracking, compliance gates, fatigue monitoring and analytics, built specifically for Australian shift-based teams.

A good signal is when scheduling, timesheets or compliance start taking real time each week, or when a no-show or payroll error has already cost you. For most service businesses that's somewhere between five and 20 staff, or as soon as you're juggling more than one site, shift pattern or client at once.

Often, yes, because the biggest cost it removes is the owner's time. Even at a handful of staff, the hours saved on rostering and timesheet admin, plus fewer no-shows and billing errors, usually outweigh a modest subscription. The key is choosing a tool you won't outgrow.

Pricing depends on your team size and the features you need. The practical way to judge it is by return: time saved, no-shows reduced, and billing and payroll errors avoided.

Rostering software schedules shifts. A workforce management platform also handles shift confirmation, digital timesheets, subcontractor management, compliance and communication in one place. For a growing service business, the broader platform avoids stitching together several disconnected tools as you scale.

Yes. A capable platform schedules casuals and books subcontractors from the same interface, and tracks the qualifications and licences each job requires. That removes the separate phone-and-email process most small businesses run for subbies.

Yes, and for service businesses that's often the bigger win. Hours logged on site feed the same clean record that drives both the pay run and the invoice, so you stop under-billing clients or arguing about hours after the fact. When a client queries an invoice, there's a solid record to point to.

New starters come on through a digital portal rather than forms in the post. Details and documents are collected up front, licences go on file with expiry dates, and the worker is set up on the mobile app before their first shift. When you're hiring steadily, that repeatability matters more than any single feature.

It should. Look for multi-site visibility, repeatable digital onboarding and a mobile-first design from the start. Adopting a system early means scaling is more of the same workflow rather than a disruptive switch later on.

No. HR software (an HRIS) manages the employment relationship: pay, entitlements, performance, the employee lifecycle. Workforce management software manages the work: rostering, time, compliance and field coordination. They overlap on onboarding, documents, leave and credentials, but their core purposes are different.

Most field businesses eventually need both, but for different reasons. If the urgent problem is rostering across sites, tracking expiring tickets or chasing paper timesheets, that's a workforce management gap. If the problem is calculating pay, super and entitlements, that's an HR/payroll gap. They solve different things, so the better question is usually which you need first, not which one instead of the other.

Generally no, and Humanz doesn't try to. A WFM platform produces the verified time data that payroll consumes, but pay calculations, tax, super, STP reporting and entitlement accruals belong in a dedicated HR/payroll system. Humanz complements those systems rather than replacing them.

Both, in different ways. The HRIS owns the leave balance and accrual calculations. The WFM platform needs leave visibility so coordinators don't roster someone who's away. Humanz handles leave within rostering so your schedule stays accurate, while the entitlement maths stays in your HR system.

The record can sit in either, but the enforcement belongs in workforce management. An HRIS notes that a worker holds a ticket. A WFM platform blocks or flags the roster when that ticket has expired, which is what actually keeps an unqualified worker off a shift. A record without enforcement at the point of scheduling is just filing.

Time and attendance is captured in the WFM platform, then handed to payroll as a clean, verified feed. That avoids double-entry and reduces payroll errors. It also supports your record-keeping obligations, since the time records are timestamped and auditable.

Yes. Since 1 July 2026, super has to reach each worker's fund within 7 business days of payday, so payroll can only be as punctual as the time data arriving from the workforce management side. A slow timesheet chase-and-approve cycle now eats into a legislated deadline, which makes the handoff between the two systems a compliance boundary in its own right.

Yes. Humanz handles operational onboarding: inductions, qualification verification, document collection and getting workers app-ready. That's distinct from HR onboarding (contracts, tax, super setup), which stays in your HRIS. For field teams, the operational side is what decides whether someone can start on site.

Not yet. AI capability is on the Humanz roadmap, but the current platform is rule-based. We'd rather be upfront about that than claim functionality the product doesn't have today.

An 8/6 roster means eight consecutive days of work followed by six days off, repeating on a 14-day cycle. It is most common in Australian mining, drilling and resources contracting, usually on 12-hour shifts, and is typically flown as a fly-in fly-out swing.

On 12-hour shifts an 8/6 averages 48 hours a week across the cycle. Eight shifts of 12 hours is 96 hours per fortnight, which averages to 48 per week. That sits above a standard full-time week, which is why the pattern usually attracts shift and site allowances.

About 156 days at home per year, before travel. A 14-day cycle repeats about 26 times a year, and six days off each cycle gives roughly 156. Travel days at each end of the break reduce the usable portion, particularly on long commutes.

Either every cycle or never, depending on the start day. Because the 14-day cycle is exactly two weeks, the pattern falls on the same weekdays permanently. A break starting on a Monday or a Sunday never contains a full weekend, while any other start day contains one every cycle, which is about 26 a year.

It depends on what you are optimising. An 8/6 gives about 36 more days at home a year and a lower average week, at 48 hours against 56. It also requires 26 swings of travel a year rather than 17, so the extra home time arrives in smaller parcels with more commuting attached.

About 1.75 people per position, before any allowance for leave and absence. Divide the 14-day cycle by the eight days worked and you get the crew factor, so 20 continuously covered positions need about 35 people. That is a floor rather than an estimate, because it assumes nobody ever takes leave, gets sick or resigns, and real establishments carry a margin on top.

Yes. Some 4-panel operations run 8/6 timing instead of the more common 7/7, keeping the same four offset panels but lifting the average week from 42 hours to 48. That gets more hours from the same headcount without going back to a 2/1, which is exactly why the variant exists.

AI rostering software uses optimisation, machine learning and rules engines to generate, balance and check rosters automatically. Instead of building a schedule shift by shift, a coordinator gets a compliant draft to review, with conflicts, fatigue breaches and coverage gaps already flagged.

A normal online roster is a better digital grid. You still make every decision yourself. AI scheduling adds automation on top, generating drafts, optimising the whole schedule in one pass, predicting problems and enforcing compliance, so the coordinator reviews and refines instead of building from scratch.

It must. A credible tool treats Fair Work award conditions and WHS fatigue obligations as hard constraints, blocking non-compliant rosters rather than optimising around them. Be wary of any tool that can't demonstrate compliance enforcement at the scheduling step.

For most field businesses today, rules-based automation covers the work that costs real time: draft generation from templates, auto-fill from live availability and compliance checks before a roster is published. It is also more predictable than a machine-learning model, because the same inputs always produce the same result. AI adds value on top, in prediction and whole-schedule optimisation, but it depends on the same clean data foundations. Get the automation and the data right first.

Not yet. Humanz does not have AI features in the application today. AI-assisted scheduling is on our roadmap, and we're building it deliberately on the platform's compliance-first foundations, with a human in control throughout, because AI in rostering only adds value when it's done properly. We'd rather get it right than rush it out.

No. The most effective model is "AI proposes, human approves". Automation removes the repetitive assembly work and catches mistakes, while experienced coordinators still make the judgement calls on crew dynamics, client needs and the one-off requirements an algorithm can't see.

By learning from historical attendance patterns, AI can flag high-risk shifts before the day arrives, so coordinators confirm early or arrange backups. Combined with shift confirmation tracking, that turns no-show prevention from reactive to proactive.

It can. Models trained on historical rosters can quietly entrench old patterns, with the same people always copping the worst shifts. The safeguards are deliberate bias checks, transparency about why each person was rostered, and a human approving the final schedule. If a vendor cannot explain a rostering decision, workers won't trust it and you can't defend it when it's challenged.

Good platforms handle both. Humanz rosters direct employees and subcontractors in the same view, each with their own compliance profile, which any automation needs if it's going to produce a valid roster.

Data governance matters. Look for clear data handling, Australian-based support, and openness about how scheduling decisions are made, in line with Australia's AI Ethics Principles.

Auto-rostering is software building, filling and checking rosters with far less manual input than starting from a blank grid. You set the structure up once, as templates and recurring patterns, and the system generates the baseline, suggests available and qualified workers for gaps, and flags conflicts before publishing. The coordinator reviews and adjusts rather than assembling every shift by hand.

Auto-rostering applies fixed rules and templates, so the same inputs always produce the same result. AI scheduling uses optimisation and machine learning to generate and optimise drafts and predict problems. Rules-based automation is available today. AI scheduling is a separate, future direction, covered in our AI rostering guide.

The biggest saving comes from starting with a template-based baseline instead of an empty roster, then using auto-fill and bulk actions for changes. Coordinators move from building rosters by hand to reviewing and adjusting them, which removes most of the repetitive cross-checking that makes manual rostering slow.

It should treat compliance as hard rules, not suggestions. The strongest tools enforce WHS fatigue obligations and award conditions as gates at the point of scheduling, blocking non-compliant shifts rather than producing them. Safe Work Australia's fatigue guidance covers the WHS side, while Fair Work sets the award and hours obligations any automated roster must respect.

Yes. Recurring rosters aren't limited to a standard week, so swing patterns and day and night rotations can repeat on their own cycle and the baseline generates itself. The pattern is saved once and rolled forward, rather than copied and pasted each fortnight.

Yes. Templates and recurring patterns can be set up per site, crew or project and applied independently, so each part of the business keeps its own structure while the coordinator manages everything from a single live rostering board.

Data quality. Auto-fill, qualification matching and conflict detection are only as good as the live availability, qualification and booking data behind them. Keeping availability current, recording expiries accurately and holding every booking (subcontractors too) in one place is what makes automation reliable.

No. Automation removes the assembly and checking. Coordinators still make the judgement calls: crew dynamics, client preferences and one-off site needs that software can't see. The right model is the system doing the heavy lifting and a human approving the result.

Not yet. What Humanz runs today is deterministic: saved templates, recurring patterns, auto-fill from live availability and qualifications, plus conflict and compliance checks. AI-assisted scheduling is something we're working towards, but the speed you get right now comes from fixed rules doing the same checks every time, not from machine learning.

It depends on your work. Deputy and Tanda are strong, established platforms, particularly for fixed-location, shift-based industries. Humanz is purpose-built for Australian field, trades, mining and construction teams, with native subcontractor scheduling, FIFO logistics and compliance gates at the point of scheduling. If those are your priorities, Humanz is well worth shortlisting alongside them.

Many general tools originated in hospitality, retail or healthcare and excel at venue-based shift work. Humanz was built around dispersed field operations, meaning multiple sites, mixed crews of employees and subcontractors, swing rosters, travel and heavy compliance. Those capabilities are native rather than added on.

When your work is fixed-location and shift-based. Deputy and Tanda grew up serving hospitality, retail and healthcare, and they are strong, mature products for exactly that model: venue rosters, clock-in at a fixed site and predictable shift patterns. The case for switching only builds when field realities like mixed crews, swing rosters and compliance gates start generating workarounds.

Yes. You can book subbies and labour-hire alongside your own crew in the same roster and the same view, which removes the spreadsheets and separate systems many businesses use to track contractors.

Yes. Humanz supports swing rosters and lets you coordinate FIFO flights and accommodation against the schedule, so logistics stay tied to the roster rather than managed separately.

Humanz applies compliance gates at scheduling and provides expiry alerts for qualifications, licences and inductions, plus fatigue monitoring. For context on the underlying obligations, the Fair Work Ombudsman is a good place to start.

Trial each finalist with a genuine, messy week of your own work, not the vendor's demo data. Score every option against your non-negotiables, such as subcontractor scheduling, FIFO logistics and compliance gates at scheduling, rather than against its marketing. Local support and whether crews will adopt the mobile app matter as much as the feature checklist.

Plan for a real migration: export and map your data, run a parallel period for a pay cycle or two, phase the rollout by site or region, and lean on local support during cutover. Done in phases, most field teams move across with minimal disruption.

Yes. Humanz is Australian-built and Australia-supported, in use since 2019 by hundreds of businesses spanning construction, mechanical contracting, mining services, drilling and trades. The support team understands local awards, conditions and field realities rather than treating them as edge cases.

Because a work shift only happens if the worker can physically be on site for it, and the roster is the only place that can check both at once. When travel sits outside the roster the same three problems keep turning up: conflicts that surface only when someone misses a swing, double data entry across booking spreadsheets, and crews relying on a text from three weeks ago. Rostered travel means the scheduler and the worker both see the full picture in one place.

Yes. Flights and accommodation appear as shifts in the worker's mobile schedule, including the notes saved on the template.

Yes, if the travel is on the roster where fatigue rules can see it. Remote site travel is a recognised fatigue factor, and long travel days compress the rest window on either side of a swing. With flights on the same schedule as work shifts, fatigue checks run against what the worker is really doing rather than rostered work hours alone.

Both work. Templates speed up repeat routes, but you can create a flight or accommodation shift manually with custom details any time.

A spreadsheet template downloaded from Scheduler Settings. You fill in the rows (worker, date, times, shift type, notes) and upload it back. Humanz creates all the shifts at once.

Yes. Non-work shifts sit in the same scheduling data as work shifts, so they show up in exports and reports alongside everything else.

No. Any business that moves people around can use flights, accommodation and other non-work shift types, from remote construction to shutdown crews and regional service teams. The same scheduling approach extends to logistics and transport workforces, where drivers and field crews are constantly on the move.

FIFO runs on the swing, not the week, and most rostering tools are built around a Monday-to-Sunday grid. Swing patterns repeat over multi-week cycles with crews offset against each other, travel is part of the shift, and fatigue rules constrain consecutive shifts and total swing hours. A weekly-pattern scheduler forces you to rebuild all of that by hand every cycle, which is how the real roster ends up in a spreadsheet next to it.

Any repeating cycle (2/1, 8/6, even-time, rotating days and nights) plus one-off patterns for shutdowns and campaigns. In Humanz, patterns are saved as templates and applied to crews per cycle.

Fatigue rules such as maximum consecutive shifts, swing hours and rest windows are configured as policies and enforced when shifts are booked. A swing that would breach the policy is flagged or blocked before it's confirmed, not discovered in a report afterwards.

Yes. Flights and accommodation are roster items, so they appear in each worker's mobile schedule alongside shifts, with notes for terminals, check-in cut-offs and camp details.

Yes. Direct employees, labour hire and subcontractors are rostered in the same view, each with their own compliance profile, so crew coverage is checked across the whole workforce.

Through seen/unseen and confirmation tracking on every published swing. Each worker's status shows whether they have viewed and acknowledged the roster, so an unconfirmed swing surfaces a week out rather than at the airport. That early warning matters more in FIFO than anywhere else, because a no-show carries flight and camp logistics on top of the missed shift.

Live availability shows who else is qualified, compliant and not already rostered, so a replacement can be booked and notified through the app in minutes, with their travel updated in the same action.

No. The same swing logic serves remote construction, energy, drilling and any operation that moves crews to site for multi-day stints.

Covering one position continuously requires 168 hours of work per week. Measured in full-time equivalents at the Australian standard of 38 ordinary hours, that is 4.42 FTE before any allowance for absence, or about 5.3 FTE once roughly 19% is added for leave, public holidays, personal leave and training. Measured in crews on a 4-panel roster averaging 42 hours, the same coverage is 4 crews before relief and about 4.8 after. The two figures describe the same operation on different bases, so always state which one you are quoting.

A relief factor is a multiplier applied to base crew numbers to account for predictable absence. It is built from annual leave, public holidays, personal and carer's leave, and training time. On a continuous roster, where shift workers are often entitled to five weeks of annual leave rather than four, those total around 19% of the year, giving a relief factor of about 1.19. Applied to a 4-panel roster averaging 42 hours, that means four crews needs roughly 4.8 crews' worth of people to staff reliably.

Two 12-hour shifts cover a full 24-hour day, giving fourteen shifts across a seven-day week. Four crews rotating through those fourteen shifts each average 3.5 shifts, or 42 hours per week. Since 168 divided by 42 is exactly four, the pattern divides cleanly, which is why 4-panel rosters are common in continuous operations.

Five crews per position, at roughly 33.6 hours per person per week, against four crews on 12-hour shifts. Eight-hour shifts avoid the 42-hour average and the overtime question that comes with it, but you pay in changeovers: three handovers a day instead of two, which on complex work is a real cost in lost continuity.

Usually not. Understaffing does not remove the hours that need covering, it moves them from ordinary rates to overtime rates and from planned cost to unplanned cost. It also concentrates additional hours on whoever is available, which increases fatigue exposure and turnover, both of which carry their own costs.

Because 168 hours of weekly coverage divided across four crews is 42 hours each by definition. That sits four hours above the National Employment Standards ordinary week, so the arrangement has to be handled deliberately through overtime, an annualised salary arrangement, or an averaging provision in the applicable award or agreement.

Usually, yes. Under the National Employment Standards a shift worker regularly rostered on Sundays and public holidays may be entitled to five weeks of annual leave rather than four, and that describes most people on a continuous roster. Check the definition against your award and your actual roster, because the extra week is close to two points of relief factor and it compounds through every headcount number.

It depends on the shape of your workforce. For fixed-location shift businesses, several established platforms compete well. For field operations with blended crews, swing rosters and site-specific compliance, a field-built platform like Humanz is the stronger fit because those requirements are native rather than configured workarounds.

Employment Hero is an HR-led platform, and its strength is employment administration: contracts, onboarding paperwork and payroll. Businesses whose main challenge is operational rostering across sites, subcontractors and swing patterns usually find they need a workforce-management-first tool, sometimes running alongside an HR system.

Usually not, and that is about sizing rather than quality. Dayforce is a global enterprise HCM platform built for large organisations standardising thousands of employees onto one stack, with implementations priced and paced accordingly. A 60-person mining services contractor rarely has a six-month implementation team, and field-specific requirements can land in the customisation budget.

Yes, and for some businesses that is the right architecture. The HR-led platform keeps doing contracts, leave balances and payroll administration, while the field-built platform owns the roster, compliance gates, site logistics and timesheets. The seam that matters is payroll: the field platform hands approved, structured time data across to whatever runs the pay. The trap is the reverse arrangement, where a bundled rostering module gets pressed into field service because it came with the suite.

For a field business of 20 to 200 workers, a phased migration typically runs a few weeks from data export to full cutover, with at least one full pay cycle run in parallel on both systems. The crew-facing app usually lands within days. The office-side reconciliation is where the calendar time goes.

Not if the migration includes a parallel pay cycle. Running old and new systems side by side for a full cycle, and reconciling hours and pay between them before cutover, is the standard protection. Treat any migration plan without that step as incomplete.

You shouldn't. Worker records, qualifications and compliance documents should be exported and mapped into the new platform, and the old system can be kept read-only for reference. Time and wages records must be retained for seven years regardless of which system holds them, and the obligation is enforced. Fair Work inspectors issued 743 infringement notices for record-keeping or pay slip breaches in 2024-25, with $838,000 in penalties paid, so the records need to arrive in the new system intact.

It's a feature of workforce management software that lets one part of a business request people from another. A coordinator opens a shift for bookings, eligible staff accept or decline on their phones, and an acceptance places the worker on the roster automatically.

An open shift broadcast is one-directional. Workers claim it. A booking request is a managed loop. The coordinator sees pending, accepted and declined responses per person and controls who's confirmed onto the job, with requests targeted to specific teams or trades.

Yes. Requests are scoped by trade, and the platform holds each worker's tickets, inductions and qualifications, so the pool that receives the request is the pool that's eligible to work it.

No. Booking requests arrive as notifications in the mobile app, and accepting or declining is one tap from the My Bookings inbox, the same place workers already confirm shifts and submit timesheets.

The shift stays visibly unfilled with every decline recorded, so the coordinator knows early rather than on the morning of the job, and can escalate to other teams, adjust dates or bring in external labour with time to spare.

Yes, because open requests give everyone eligible the same shot at the work. Every accept and decline is recorded against the shift, so the question of why one person keeps getting the overtime is answered with data rather than memory. For growing businesses that transparency matters as much as the speed.

Watch four numbers. Response time from request sent to first accept should sit in minutes to hours, not days. Fill rate by trade shows where requests keep failing, which is a hiring case written in data. And the internal versus external ratio, how much work you resourced from your own bench before paying subcontractor margins, is the number that justifies the tool.

No, it complements it. Internal booking finds the people you already employ. A subcontractor process manages the labour you hire in. Running both through one platform means one roster and one compliance check, with a single timesheet trail across the whole crew.

Poor communication is the leading cause: workers who weren't clearly told the shift details, never got a confirmation request, or missed a last-minute update. The second most common cause is scheduling workers who weren't available, because nobody had live availability data.

No system eliminates no-shows completely. But a system with shift confirmations, automated reminders and fast replacement tools cuts their frequency and softens their impact when they do happen. The point is moving from reacting on the day to preventing in advance.

A traditional roster is a static schedule. It shows who is planned to work when, but not changes, confirmations or current availability. A real-time roster is live. It updates as confirmations come in, flags gaps, and gives coordinators a current view of workforce status at any point.

It depends on the role and the project stage, but a conservative estimate for a skilled trade no-show (counting direct labour cost, delay to dependent tasks and supervisor time) is $500–$2,000 per incident. The wage floor alone supports that range. The Australian Bureau of Statistics put construction full-time adult ordinary time earnings at $1,985.30 a week in May 2026, about $400 a day before on-costs. On a large project with frequent no-shows, the annual figure adds up fast.

Yes. A reminder the day before and again on the morning catches the worker who forgot, or who meant to call in and didn't, before the absence becomes a gap on site. Day-of check-ins go one step further, asking the worker to confirm they're on their way, which surfaces problems hours earlier than they'd otherwise show.

In Humanz, a cancellation triggers an immediate notification to the coordinator and can automatically surface available replacement workers. The coordinator can broadcast the open position to qualified, available workers from the same screen. No phone calls required.

Yes, in platforms like Humanz. Subcontractors use the same app as direct workers and the same shift confirmation workflow. Their availability is visible to coordinators too, so they can be included in open shift broadcasts alongside direct employees.

Under most Modern Awards, yes. Shift workers are generally entitled to minimum notice of roster changes, and businesses that handle no-shows and replacements informally can breach those obligations without realising. The Fair Work Commission's award finder confirms the notice requirements that apply to your workforce.

No single standard exists, because award requirements differ by industry. Any template you use should capture shift times, breaks, employment type, planned weekly hours and required qualifications. It's also worth checking roster-change notice rules for your award with the Fair Work Ombudsman.

Days down the side, one column per person, one week per tab. Enter times rather than just writing Day, total the planned-hours column before publishing so overtime is a decision rather than a surprise, and put an expiry date next to any ticket due within 90 days. When enforcing those three rules starts taking someone hours a week, you've outgrown the sheet.

Perfectly. The law cares about the outcomes (hours, breaks, records, entitlements), not the tool. The practical risk is that a spreadsheet can't warn you when a roster breaches rest rules or rosters an unqualified worker, so compliance depends entirely on the person driving.

The honest markers are more than one site or client, weekly roster changes, casual or subcontract labour in the mix, or any compliance requirement you're currently checking by eye. And casual-heavy is hardly rare. The Australian Bureau of Statistics counted 17% of employees, 2.1 million people, with no guaranteed minimum weekly hours in August 2025. If updating and re-sending the roster takes someone hours each week, the template has become a job.

Many awards require rosters to be displayed or communicated in advance, and some set specific notice for changes. Beyond the legal floor, field businesses that publish one to two weeks ahead, with a way for workers to confirm, see materially fewer no-shows.

There's no universal best. 4 on / 4 off is simplest to staff, 2-2-3 trades some complexity for better weekends, and FIFO swings are their own discipline. The right answer balances coverage, fatigue accumulation and what your workforce will accept.

It can draw one, and that's about where it stops. A swing is logistics as much as a grid, with flights, camp rooms and changeovers all hanging off the pattern, and a spreadsheet can't tell you who is qualified, rested and not already committed when Wednesday's sick call comes in. Swings are usually where a template graduates into rostering software earliest.

Yes. That's the point of the transition. Your patterns become repeating shift templates and your favourite views become saved layouts, so planners keep the mental model they already have. What the software takes over is the maintenance, the distribution and the checking.

A reason code is a label recorded against a shift you couldn't fill, such as no accommodation available, client cancellation or unable to supply. Coding those shifts preserves the story behind every gap, and after a quarter of consistent coding you can put numbers on how much work you turned away and why. That evidence is what carries a hiring case or a camp-bed negotiation.

Yes. The shifts report in Metrics can be filtered, and the CSV export lets you slice missed shifts by reason, client, site, trade, or period in a spreadsheet.

The top-left search matches the trade assigned to the job position. The Filters panel filters by the resource's own trade or profession.

No. Teams are a schedule-view grouping for planners only, with no link to clients, jobs, or trades.

Yes, a person can sit in multiple teams at once. Teams are a visual grouping for planners with no link to clients, jobs or trades, so someone can appear under both Leadership and A Panel without touching any operational data. You can drag to reorder members within a team, and drag teams to reorder them on the schedule page.

Straight after you add them in Business Ref Lists. Refresh your browser when you leave that page and the code is ready to use.

It's a record of whether each allocated shift has actually been displayed on the worker's phone. The Show Unseen button filters the whole schedule down to only the shifts workers haven't viewed, which turns follow-up from guesswork into a two-minute task. Every shift still showing is a call or message to make before it becomes a gap on site.

Treat it as a strong signal, not a guarantee. A shift must display for about 200 milliseconds to register, so very fast scrolling can leave a viewed shift marked unseen. When in doubt, follow up.

The seen status is a scheduler-side view. Workers use the app as normal, and the schedule records whether allocated shifts have been displayed on their device.

Check their last login. The My Organisation page shows each user's last login date and time, which catches the workers who haven't opened the app at all rather than just missed one shift. Those are the people to ring rather than message, and the ones to sort out before a roster with a long lead time.

Any combination of individual users, roles, and teams. Membership updates with your org, so if the rostered supervisor changes, the role-based chat still reaches whoever holds it.

No. They sit alongside it as global chats for defined scenarios, so workers always have a guaranteed-monitored channel for time-critical issues.

No. It only controls which internal users, roles, or teams receive business notifications. Worker notifications are unchanged.

A 2/1 roster is two weeks on site followed by one week off, on a 21-day cycle, also written 14/7. At 12-hour shifts it averages 56 hours a week and gives roughly 120 days at home per year. It's Australia's most common FIFO production roster: flight-efficient, with a break long enough to be worth flying home for.

Even time means the days off equal the days on: 7/7, 14/14 or two weeks on, two weeks off. Workers spend half the year at home and average 42 hours a week on 12-hour shifts. It costs more to staff than compressed swings, so it's used where retention pressure justifies the extra headcount.

The Panama (also called 2-2-3) is a 14-day cycle of 2 on, 2 off, 3 on, 2 off, 2 on, 3 off, worked in 12-hour shifts by four crews. It averages 42 hours a week, never rosters more than three consecutive shifts, and delivers a three-day weekend every second week. It suits residential 24/7 operations such as processing plants and control rooms rather than FIFO.

The DuPont is a 28-day, four-crew rotation mixing day and night blocks, typically four nights, three off, three days, one off, three nights, three off, four days, then seven days off. It averages 42 hours a week across the cycle, and the full week off every month is its whole appeal. The price is one week in the cycle containing six shifts, a 72-hour week, plus day-night flips with as little as 24 hours' turnaround.

Put five numbers side by side: average weekly hours, days at home per year counted after travel, full weekends off per year, fatigue exposure and headcount required. For fatigue, test the worst window in the cycle rather than the average, meaning the longest run of consecutive shifts, the longest run of nights and the worst rolling 7-day hour total. The average is what hides exactly the stretch fatigue rules are written to catch.

Divide 168 (the hours in a week) by the pattern's average weekly hours. Even-time and Panama-style patterns at 42 hours need exactly 4 crews; a 2/1 swing at 56 hours needs 3. Real operations then add a relief allowance for leave, public holidays, sick leave and training, which on a continuous roster runs to about 19% once the fifth week of shift-worker annual leave is counted, so a 24/7 even-time site plans around 4.8 people per seat.

Yes, provided the arrangement meets award or agreement terms and the employer manages fatigue as required under WHS law. Ordinary hours of 38 a week can be averaged over a roster cycle, which is how compressed swings like 2/1 operate lawfully. Most sites also apply numeric fatigue standards (maximum shift length, minimum breaks, caps on consecutive shifts and rolling hours) that constrain how 12-hour patterns are built.

It's rostering functionality that lets shifts change hands through the system instead of around it. A swap or open shift becomes a request, the software checks the incoming worker's qualifications, hours and breaks, a coordinator approves, and the roster, notifications and audit trail all update automatically.

Yes. Because the system knows both workers' rostered and worked hours, it can flag a swap that would break the minimum gap between shifts, exceed consecutive-day limits or push a rolling-hours cap before the booking is confirmed. The warning appears at approval time, when the swap can still be declined or adjusted.

Yes. Time and wages records must reflect who actually worked, and they must be kept for seven years. A swap that lives only in a group chat leaves the official record wrong on both counts. And the rules get enforced. The Fair Work Ombudsman issued 743 infringement notices for record-keeping or pay slip breaches in 2024-25, with $838,000 in penalties paid. Routing swaps through the roster keeps records accurate and produces an audit trail of who approved the change and when.

A swap is worker-to-worker: someone can't make a shift they own and a specific teammate takes it. An open shift is coordinator-to-many: a gap is broadcast to every eligible worker at once, first-in or coordinator's pick. A good platform runs both through the same qualification, hours and break gates, so the only real difference is who starts the conversation.

The healthiest model keeps approval with a coordinator while automating everything around it. Workers initiate and accept in the app, the system runs the eligibility, hours and break checks, and the coordinator gets a one-look approval with the results in front of them. That preserves oversight without the ring-around.

Make the app the only door that opens, and the fastest one. The policy is one sentence, a swap isn't a swap until it's in the system, and supervisors hold that line by declining chat-arranged changes for the first month. If requesting a swap takes ten seconds in the app, it wins on laziness alone. Most crews make the transition in a few weeks.

A clopen is a closing shift followed by an opening shift the next morning, with too little rest in between. It commonly breaches the minimum break requirements in modern awards and is a known fatigue risk. Swap approvals are where clopens usually sneak in, which is why the break check has to run on the new pairing rather than the original roster.

The category, not the feature list. Cafe and retail shift tools are built around one location with employees only, HR suites treat compliance as records rather than gates, and field-built platforms make the multi-site live view the default, roster employees and subbies together, and check fatigue and licence currency at booking time. FIFO swings and travel are handled natively rather than bent out of a weekly grid. None of the three is bad at its own job, but buying one category and expecting the behaviour of another is where it goes wrong.

Five steps: audit what you roster today including the unwritten rules, turn your recurring patterns into templates, load workers and compliance rules, publish to phones, and measure fill rates and confirmation lag from the first month. Keep the thinking rather than the file, because the spreadsheet encodes years of crew and coverage decisions that map straight into templates. Then set a cutover date and honour it. Two pay cycles in parallel is prudence, six months is a second job.

Yes. Good rostering software handles every employment type (permanent full-time, part-time, casual, labour hire) with the right availability patterns and entitlements for each. Humanz handles all of these, plus subcontractors, in one platform.

Coordinators make the change from desktop or mobile and instant notifications go to the workers affected. Live availability data means a replacement for a no-show can be found and contacted within minutes, not through a chain of phone calls.

Yes. Humanz lets you build roster templates for repeating patterns (weekly rotations, FIFO swings, standard crew configurations) and apply them to new periods without rebuilding from scratch. A good template captures the pattern, the crew mix and the compliance rules together, so applying it produces a roster that is already checked.

In Humanz, workers see their full roster through the mobile app, including upcoming shifts, recent changes and details like site address and job brief. Shift confirmation is submitted through the app too.

By tracking cumulative hours across the pay period and flagging when an extra shift would tip a worker into overtime. That makes the cost visible before the decision is made, which matters under Award conditions that apply overtime rates past certain daily or weekly hours.

The roster is the planned schedule, the shifts workers are assigned to. The timesheet records the time they worked. In Humanz, timesheets are generated automatically from roster data and adjusted for actual attendance, closing the gap between what was planned and what gets paid.

Humanz supports state-based compliance configurations, so a business operating across several states can manage different award conditions in a single platform.

Project management software tracks tasks and timelines. Contractor management software tracks the people doing the work, covering compliance status, availability, scheduling and documentation. They serve different purposes. Humanz focuses on workforce and contractor management and sits comfortably alongside project management tools.

Contractor management software runs the subbies and contractor businesses you engage directly, while labour hire software runs an agency's pool of on-hire workers supplied to host clients. The machinery overlaps heavily: profiles, compliance tracking, scheduling and timesheets. Humanz handles both models on one platform, so a business that engages subbies and also supplies labour to clients doesn't need two systems.

Yes, and it's one of the core advantages of Humanz. Direct employees and subcontractors appear in the same scheduling view, with the right compliance requirements tracked for each. There's no need for separate systems.

Yes. Some Humanz customers have a workforce that is mostly or entirely subcontractors, and the platform is built for that model, with contractor-specific workflows covering onboarding through to compliance tracking.

By keeping clear records of how each contractor is classified and engaged, plus their work history, the software builds an audit trail that supports genuine independent contracting arrangements. The enforcement behind that is not theoretical. The Fair Work Ombudsman's 2024-25 annual report puts recoveries at $358 million for more than 249,000 underpaid workers, with a record $23.7 million in court penalties across 73 new litigations, and clear documentation is the best protection when that attention lands on you.

Yes. Contractors complete onboarding from their phones, and licences, insurance certificates and other compliance documents load straight into their profile. When a document approaches expiry, the alert goes to the contractor as well as the coordinator, so chasing the renewed certificate doesn't fall entirely on your office.

Humanz sends automatic alerts before expiry, so it rarely gets that far. If a lapse does occur, the system flags the contractor as non-compliant and blocks further scheduling until the renewed certificate is uploaded.

Yes. A contractor business in Humanz can have multiple individual workers managed under its profile, each with their own qualifications, licences and induction records. That's essential for subbies who supply a crew rather than a single worker.

Victoria, Queensland, South Australia and the ACT run labour hire licensing schemes, and in each one a host must only use licensed providers. NSW, WA, Tasmania and the NT have no scheme, though NSW says it is working with the Commonwealth and other states on a nationally consistent framework. Safety duties to labour hire workers apply in every state and territory regardless.

No. In every scheme state the licence sits with the provider, and no Australian jurisdiction requires a host to hold one. The host's job is to use only licensed providers, confirmed against the state register before work starts, and to meet the WHS duties owed to on-hire workers once they are on site.

For 2026-27, Victoria's Labour Hire Authority publishes maximums of $167,280 for an individual and $669,120 for a corporation, and Queensland's figures based on the 1 July 2026 penalty unit are $518,100 for a corporation and $178,571.80 or three years imprisonment for an individual. South Australia's maximums are $140,000 for an individual and $400,000 for a body corporate, and they apply equally to hosts. The ACT publishes no current host-side figure but confirms financial penalties can apply.

Yes. Both the labour hire agency and the host are PCBUs, both owe the worker a health and safety duty, and neither can contract out of that duty or transfer it. As the PCBU at the workplace, the host must provide facilities, first aid access and an emergency plan, and must work with the agency on induction, training and supervision.

Keep the licence number, the name of the register searched, the date of the search and the person who ran it, together with the licence expiry. Re-check on a schedule rather than once, because a licence can be suspended or lapse partway through an engagement. Holding those records with the provider's file, beside each worker's induction and qualification records, is what turns an audit into a short email.

It is a Fair Work Commission order requiring labour hire employees working for a host to be paid no less than they would receive under the host's enterprise agreement or other relevant workplace instrument, called the protected pay rate. Employees, unions and the host itself can apply, while labour hire employers cannot. Exclusions cover small business hosts, genuine services rather than labour, training arrangements and short-term engagements of usually three months or less.

The rules of the state where the work is performed, not where your head office sits. Each scheme is a separate law with its own register, so a licence is proof only in the state that issued it. When crews work across borders, search each relevant state's register and keep each result on file.

It's software that runs the workforce side of a planned shutdown or turnaround end to end: building a credentialed worker pool, crewing shifts from it, checking tickets and inductions before booking, and capturing hours through the event. The distinguishing feature is that employees, labour hire and subcontractors are managed on one roster with per-worker compliance checks, because shutdown crews are always blended.

Crewing should start as soon as the scope is firm enough to estimate trades and headcount per shift, which is typically months before the window. Credential gaps are the reason: renewing licences, booking medicals and completing site inductions all have lead times that can't be compressed in the final week. The day-one queue at the gate is where late mobilisation becomes visible, but the failure happened weeks earlier.

Yes, and for shutdown work it's close to mandatory, because the crew is blended from the start. In Humanz, subcontractors carry their own compliance profiles, including entity-level insurances and licences, and sit on the same roster as employees, so every worker type passes the same checks before being booked. Planners see one crew rather than three separate lists.

By checking hour limits and break rules when each shift is allocated, not after the event. A shutdown combines 12-hour shifts, consecutive days and night work, which Safe Work Australia names among the main contributors to fatigue, and PCBUs must minimise that risk so far as is reasonably practicable. If an incident occurs, the roster is the first document an investigator asks for, so the controls have to live in it from the start.

Yes. A high risk work licence is recognised in every Australian state and territory, so a ticket issued in Queensland works on a Pilbara shutdown. The checks that still matter are whether the licence class matches the task, whether it stays current for every rostered day of the window, and whether anyone verified it before the worker got on the plane.

If it's only discovered mid-window, the worker is stood down until the credential is renewed, which can idle a whole crew that depends on them. The fix is to check expiry dates against every rostered day of the window at booking time, rather than day one alone. That surfaces the problem weeks early, with time to renew the ticket or roster someone else.

Volume and turnover. Hundreds of long shifts are worked by people who may only be engaged for a couple of weeks, and by the time hours are queried, many have left site. Prefilling timesheets from the roster, capturing confirmation on workers' phones and approving daily keeps the record intact while the people who can verify it are still standing in front of you.

When keeping it current has become someone's job and things still slip through. The usual signs are a licence expiry nobody caught, a subbie double-booked across two jobs, or an invoice that doesn't match any recorded hours. A spreadsheet only works while someone remembers to check it, and a growing subbie count is exactly what makes them stop.

Yes, in platforms like Humanz. Subcontractors log in to the app, view their scheduled jobs, submit timesheets, complete forms and message the coordinating business, all within the platform. That removes the overhead of a coordinator manually relaying information.

At minimum: ABN, insurance certificate of currency, trade licences, White Card, induction records per site, and timesheet or hours records. Keep them for at least seven years for Fair Work purposes, and for the duration of any applicable warranty or defect period for WHS incident purposes.

By creating the hours record before the invoice arrives. Subbies submit timesheets from their phones, pre-filled from the roster, and a supervisor approves them as the work happens. When the invoice lands, it's reconciled against approved hours in minutes rather than argued about from memory weeks later.

The distinction matters because it affects entitlements, tax obligations and liability. The Fair Work Ombudsman provides guidance on the difference. Key factors include whether the worker is engaged for a specific outcome, uses their own tools, sets their own hours and carries their own insurance. Misclassifying an employee as a contractor creates serious legal exposure.

Ask for a Certificate of Currency from their insurer, noting the policy number, coverage amount and expiry date. A good subcontractor management system stores this against the contractor's profile and alerts you when renewal is approaching. The standard for construction in Australia is a minimum of $10–20 million public liability cover, though principal contractors often require higher.

A system like Humanz maintains one contractor profile that applies across all jobs. Compliance credentials are tracked centrally, so a renewed licence updates everywhere. Hours are tracked per job, which means you can see their total engagement across your business at any point.

The core set is an ABN verified against the register, the legal entity name, any trade or contractor licence the scope requires, White Cards and high risk work licences for the people coming to site, a public liability certificate of currency, workers compensation or personal accident cover, a SWMS for any high risk construction work, induction records, and a signed subcontract or purchase order.

Not on anything the missing documents cover. A SWMS must exist before any high risk construction work starts, and letting someone on site before licences and insurances are checked hands you exactly the risk the file exists to control. If the start date can't move, narrow the day-one scope to work the completed parts of the file support.

A purchase order referencing your standard terms is the workable minimum for smaller scopes. Whichever form you use, it needs to cover scope, rates, required insurances, safety obligations and what happens on variation. For larger or higher-risk packages a signed subcontract is worth the effort, because agreeing what delays and variations cost is far cheaper before the job than mid-argument.

Sometimes, yes. Under the superannuation guarantee rules, a contractor paid wholly or principally for their labour is treated as an employee for super purposes regardless of holding an ABN or issuing invoices. Single-person, labour-only, hourly-paid arrangements are exactly the pattern the rule captures, so get advice before assuming the ABN settles it.

Generally a sole trader cannot cover themselves under a workers compensation policy, since those policies cover a business's workers rather than its owner. That is why many principal contractors require sole traders to hold personal accident and income protection insurance instead, and why the distinction between a sole trader and a subbie company with employees matters when collecting certificates.

Every document with an expiry date needs re-checking at or before that date: insurances annually at renewal, licences and tickets on their own cycles, and inductions when a site or client requires refreshers. A file that was complete at onboarding decays from that day forward, which is why expiry tracking matters more than the initial collection. The entity itself deserves the same schedule. The Australian Bureau of Statistics' Counts of Australian Businesses puts the annual business exit rate at 13.8%, with 375,331 of 2,814,778 businesses exiting in the latest count, so the ABN you verified at onboarding belongs to a population where roughly one business in seven leaves each year.

Onboarding a subcontractor means verifying a business: its entity, licences, insurances and safety documentation. Onboarding an employee means setting up a person: tax and super details, inductions, training and their profile in your systems. The two produce different files and different obligations, and blurring them is how sham contracting problems start.

Yes. The Fair Work Act doesn't specify a format for records, only that they're accurate, complete and kept for 7 years. A digital timesheet from a mobile app satisfies those requirements, and it's generally more defensible than a handwritten paper record.

Significantly. If Fair Work investigates a wage underpayment claim, you need to produce accurate time records going back up to 6 years. A digital system with complete, timestamped records is far easier to audit than boxes of paper timesheets, assuming the paper still exists.

For most small-to-medium trades businesses, initial setup in a platform like Humanz takes a few hours to a couple of days. Workers adapt fast. Clocking on with a phone beats filling out a paper form.

Yes. When workers clock on against a job, hours roll up per worker per job in real time, so you can see where labour costs sit against budget while the work is still running. Paper timesheets only give you that picture weeks later, if the sheets survive.

Most platforms, Humanz included, let supervisors adjust timesheets manually and send workers a reminder when a clock-off is missing. The app flags the anomaly rather than silently recording wrong hours.

No. Platforms that use location generally capture it at clock-on and clock-off, as proof the worker was on site, rather than tracking anyone through the day. That gives you an accountable record without being intrusive about it.

With the right app, yes. Humanz and several other mobile timesheet apps support offline mode. Timesheets save locally on the device and sync once coverage returns.

Employee records must be kept for seven years. This applies to both current and former employees, so records for someone who left the business several years ago must still be retained until the seven-year period expires. Records must remain legible, in English, and readily accessible to a Fair Work Inspector throughout that period.

Required records cover general employment details, pay, hours worked where overtime or penalty rates apply, leave taken and balances, superannuation contributions including the fund and why it was chosen, individual flexibility arrangements, guarantees of annual earnings, and termination details. Each category has specified contents rather than being satisfied by general paperwork.

Beyond penalties for the record-keeping breach itself, failing to meet record-keeping or pay slip obligations can reverse the usual burden of proof in a court claim about an employee's pay or entitlements. Instead of the employee proving the claim, the employer may have to disprove it. Without records, that is very difficult, which is why missing hours records tend to be far more costly than the record-keeping penalty alone.

Yes, and the hours requirement is stricter for casuals than for most permanents. For a casual paid a loading or penalty rates you must record the hours actually worked, while a salaried full-timer on ordinary hours needs no minute-by-minute record. In field and site businesses that asymmetry covers most of the workforce most of the time.

A pay slip must be given to each employee within one working day of being paid, including employees who are on leave at the time. It can be provided electronically or on paper. Required contents include employer and employee names, employer ABN, pay period, payment date, gross and net pay, entitlements such as loadings and penalty rates, deductions, and superannuation contributions.

No. A roster is a plan that shows what you intended, and records have to show what actually happened. On any operation where shifts get extended, swapped or cut short, the gap between the two is exactly the territory a dispute will fight over, so worked hours need their own record captured at the time.

A spreadsheet can hold the required information, but it can struggle with two requirements: records must not be altered except to correct an error, and they must be readily accessible for seven years. A shared file that any user can edit without leaving a history makes it difficult to demonstrate that a figure was not changed after the fact, which is the distinction the rules rely on.

Hours recorded from memory rather than at the time. A worker filling in a paper sheet at the end of the week is reconstructing shifts, and every manual re-entry after that, by a supervisor or by payroll staff, adds another chance for a number to change. Small individual errors then compound across the workforce and land in the pay run.

They remove the guesswork. When a timesheet is generated from roster data, the expected hours are already in place, so the worker confirms or corrects a known plan instead of rebuilding the week from memory. Supervisors can then focus their attention on the entries that differ from what was rostered.

Leave management software is a system for requesting, approving and recording employee leave. For shift and field-based teams, the most useful versions connect leave directly to rostering so that approved time off is visible when shifts are built, reducing double-booking and uncovered gaps.

Prioritise roster integration, a mobile-first request and approval flow, a retrievable audit trail, multi-site visibility, roster-cycle awareness for FIFO and shift patterns, and alignment with your payroll system as the source of truth for accruals.

Leave and rostering are two views of the same problem. When approved leave appears on the roster, the person building shifts can immediately see who's unavailable, plan coverage in advance and avoid scheduling someone who already has time off.

Because every absence has an operational cost. When a shift worker takes leave, their roster slot has to be covered. If leave approvals and the roster live in separate systems, managers approve time off without seeing the impact, which leads to gaps and no-shows.

The National Employment Standards set minimums including annual leave, personal/carer's leave, compassionate leave, parental leave and unpaid family and domestic violence leave. Long service leave is set by state and territory law. The Ombudsman publishes the authoritative detail for each leave type.

Only if it understands roster cycles. A worker on a two-and-one swing doesn't take leave against a calendar week, so a request has to be assessed for where it lands in the cycle and what it does to flights and accommodation. A standalone leave app that thinks in Monday-to-Friday terms will happily approve time off that breaks a swing or strands a crew.

Australian employers must keep accurate records of leave taken and leave balances, and be able to produce them. In practice that means a time-stamped trail of every request, approval and rejection, showing who decided it and when. Leave that moves by text message and a verbal nod leaves none of that behind.

Yes. With Humanz, workers submit leave requests through the mobile app from anywhere, managers approve or decline them, and approved leave becomes visible in rostering, with no paper forms and no chasing requests by text.

Humanz handles leave through requests, approvals and roster visibility. Accrual and entitlement calculations should align with your payroll system, which remains the source of truth for balances. The value Humanz adds is making approved leave visible directly in rostering.

Payday super applies to qualifying earnings paid from 1 July 2026. Earnings paid up to 30 June 2026 stay under the old quarterly super guarantee rules, so the 2026-27 year is the first fully on the new system.

Super guarantee contributions must be received by the employee's fund, with the information needed to allocate them, within 7 business days of the day qualifying earnings are paid. Business days exclude weekends and any public holiday that applies to a whole state or territory. Time taken by a clearing house counts against the window.

A contribution that lands after the deadline exposes the employer to the super guarantee charge, which includes the shortfall, an interest component and an administrative charge. Because the obligation now attaches to every pay run rather than every quarter, a recurring delay compounds with each payroll cycle.

Because the pay run can only happen once hours are approved, and the super clock starts at the pay run. Slow timesheet collection and approval now consume the same seven business days that the super payment needs to clear. Fast digital capture and same-week approvals are what keep the window workable.

It can. The super guarantee has never been limited to employees, and a contractor engaged under a contract wholly or principally for their labour can be owed super, now on the same per-payment clock as everyone else. If your subbie arrangements assume an ABN settles the question, it's worth getting specific advice, because the question now recurs every pay cycle instead of every quarter.

Yes. Every payment of qualifying earnings is its own qualifying earnings day, so a December bonus run, a resolved back pay claim or a termination payment each starts a fresh 7 business day window for the super riding with it. Off-cycle payments handled outside the normal payroll pipeline are where the likeliest breaches sit.

No. The rate and the earnings base are unchanged by the reform. What changes is timing, super moves with each payment of qualifying earnings instead of accumulating for a quarterly payment, and the compliance consequences of running late.

By removing manual re-entry between systems. When approved time data flows straight from your workforce management platform into payroll, you cut out the transposition and omission errors that come from retyping hours. Approvals and audit trails add a further check before anything reaches the pay run.

Start with data accuracy at the source, a clear approval step before data moves, a complete audit trail, and clean mapping to your pay categories. Automated approaches such as letting the system build the roster for you can strengthen the upstream data, but accuracy and approvals come first.

An export is a snapshot, a file generated at one moment and uploaded into payroll. Correct an hour on either side afterwards and the two systems quietly disagree until somebody reconciles them by hand. A two-way integration connects the systems directly, so corrections flow through and both sides stay in step between pay runs.

No. Humanz isn't a payroll engine. It produces accurate, approved time data that feeds into your existing payroll system, with timesheets pre-filled from rosters and reviewed against actual attendance. This keeps responsibilities clear and cuts the manual re-keying that causes errors.

A payroll system calculates gross and net pay, tax and superannuation. The timesheet to payroll step is about getting accurate worked hours and allowances into that system. Workforce management software handles the time data, and payroll software handles the calculation and payment.

Penalty rates, overtime and allowances are calculated from when and how hours were worked. If start and finish times or shift types are inaccurate, the award is applied to the wrong inputs and pay comes out wrong, even with a correctly configured payroll system.

STP requires you to report pay information to the ATO each pay run, so errors surface quickly. That raises the bar for accurate Single Touch Payroll timesheets. Clean, approved time data with a clear audit trail makes each STP report consistent and defensible.

Yes. Accurate, approved time records per worker, subcontractors included, give you a consistent basis for payment and reconciliation. Keeping employee and subcontractor records structured the same way makes downstream processing far simpler.

You still get most of the benefit, because most of the value sits upstream of the connection. Accurate, approved time data with an audit trail can be handed to any payroll system in a structured form, which beats re-keying from paper regardless of how the last step travels. Where a specific connection matters enough, a custom integration can be scoped and built.

Time and attendance software records when employees actually start, take breaks and finish work, captured at the time rather than reconstructed later. For Australian employers its real job is making Fair Work record-keeping a by-product of running the business, with hours stored in a form that is accurate, retrievable and not altered after the fact.

Time and wage records are. Employers must keep records of hours worked (particularly for casuals and employees paid by the hour), overtime, and pay for seven years. Timesheets are how most businesses generate those records. The obligation is that the records exist, are accurate and aren't altered after the fact.

Capture time digitally at the point of work, connect it to the roster so planned-vs-worked is visible, approve with a recorded trail, and store centrally with search. The audit answer is then an export, not a reconstruction.

A roster is the plan and time and attendance is the record of what actually happened. The two earn their keep when connected, because timesheets generated from rostered shifts let supervisors review exceptions rather than every line, with planned versus worked visible per shift. That gap between planned and worked is exactly the data an award-compliance check needs.

No, it feeds it. Time and attendance produces approved, award-relevant hours. Payroll applies rates and pays. The integration removes the re-keying step where errors breed.

An app records when the entry was made as well as what it claims, and supervisors approve against the rostered shift. Compared with a Friday-afternoon paper timesheet, the honesty gradient runs strongly in your favour.

Supervisor-entered time on behalf of a worker is supported. It's still timestamped against the roster and still auditable. In practice smartphone coverage on Australian field crews is near-universal.

It's the structured path a timesheet follows from submission to payroll. The timesheet lands in an approval queue, an authorised approver reviews it against the roster and approves or rejects it with an audit trail, and approved hours flow to payroll. The workflow also surfaces what hasn't been submitted, so chasing happens early instead of in a payday scramble.

The person who knows whether the hours are real, which is usually the site supervisor or coordinator who managed the shift. A supervisor-scoped portal means each approver only sees their own crews, and payroll receives hours that have already passed the person closest to the work.

The variance from the roster, not every line. When timesheets prefill from the roster, entries that match plan need only a scan, and attention goes to edited entries, which carry a warning marker, and to any missing signatures or attachments. Approving against the roster is what catches the 11.5 claimed hours that were rostered as 10.

Yes, and they should be. When timesheets prefill from the roster, the majority match plan and can be selected and approved together, leaving individual attention for the entries flagged as edited or unusual.

A team outstanding view lists every worked shift with no timesheet against the responsible worker. Coordinators chase from that list during the week, by in-app message rather than phone calls, so the pay run isn't held hostage by two missing sheets on Friday afternoon.

Employers must keep time and wages records for seven years under the Fair Work system. A digital approval workflow satisfies this naturally: submission, edits, approver, approval time and any signatures are stored against each timesheet and can be produced on request.

Yes. Client sign-offs, dockets and photos travel with the timesheet itself rather than in a separate email thread, and a timesheet can be resent when a counter-signature is missing. When the client or an auditor wants the pack, it downloads to PDF without anything being re-keyed.

Yes. Subcontractor hours can run through the same submission and approval queues, which is how you avoid the "two systems, two chases" problem.

No. Xero Payroll calculates gross to net, superannuation and leave balances and reports to the ATO each pay run, but it doesn't plan shifts, know who is on which site or check whether a ticket is current. Rostering happens upstream in workforce management software, which then hands Xero the approved hours.

An export produces a file that you upload, capturing the hours at the moment you generated it. A two-way API integration connects the systems directly and keeps them in step in both directions, so a correction after the transfer does not leave the two quietly disagreeing until someone reconciles by hand.

No. Humanz produces accurate, approved time data and hands it to payroll. Xero Payroll does the calculation, the superannuation, the payslips and the Single Touch Payroll reporting to the ATO. The two do different jobs and most field businesses need both.

Three ways. A payroll admin can type them straight in, the worker can enter and submit them through the Xero Me app, or a connected system can write the whole timesheet through Xero's payroll API, lines and rates included. The first two paths mean someone is re-creating numbers the roster already holds, and every keystroke is a fresh chance to transpose a figure.

Because penalty rates, overtime thresholds and many allowances depend on when work happened, not only how much of it there was. A shift recorded as a flat total cannot be interpreted correctly by any payroll system, so the award gets applied to the wrong inputs and the pay comes out wrong.

It raises the cost of getting it wrong. You report to the ATO every pay run, so errors surface immediately and corrections mean an amended submission. Accurate hours, an approval before the pay run and a clear audit trail are what make each report defensible.

Yes, and it should. The same job often produces employee hours that become a pay run and subcontractor hours that become an invoice. Keeping both on one platform means one approved record of who worked, with two different destinations downstream, rather than two systems to reconcile.