Enterprise DNA

Instead of Humanz

Stop renting Humanz. Own your FIFO roster.

We build your version around your sites, your clients' gate requirements and your fatigue plan, bring your Humanz people, credentials and roster across, and run it for you. Your crews keep confirming shifts and sending hours the way they do now.

Humanz publishes no price. Its pricing page says each business is quoted on the size of the workforce it rosters, employees and subcontractors together, so the bill grows every time you add a crew.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

You pay by the head for screens over your own roster

Humanz quotes each business privately. Here is what the quote is built from, and which parts are really the front end.

groups

A quote sized by headcount

Humanz says the quote reflects the size of the workforce you roster, counting employees and subcontractors together. A bigger shutdown crew means a bigger number.

calendar_month

A scheduler over dated shifts

Swing templates, panels and the planning view are a grid over one record per person per day. The pattern is arithmetic; the grid is the front end.

badge

Credential gates

Inductions, medicals, high risk work licences and VOCs with expiry dates, checked against what each client and site requires before a booking is confirmed.

bedtime

Fatigue rules

Shift caps, minimum breaks and days in a row at business, client and site level, with the strictest applied. Each rule is a number and a comparison.

flight

Mobilisation

Flights and camp rooms scheduled beside each swing. Under the screen, a booking is a date, a flight number and a reference next to a person.

schedule

An eleven week rollout

Humanz describes an indicative rollout of about 11 weeks, phased module by module. The time goes on configuring someone else's system around your crews.

Your own crew office

Start with what the crew coordinator is asked every day

Gates

Nobody booked who will be stopped at the gate

Every client's and site's requirements, and the ticket each trade needs on each job, checked against every booked shift.

  • check A booking refused when an induction, medical or ticket is missing, unless someone overrides it with a reason and their name
  • check Credentials that lapse partway through a swing that is already booked, weeks before the gate
  • check The rigger whose rigging licence runs out on day four of the shutdown
  • check Labour hire firms supplying a Queensland site with no Queensland licence on file

Roster

Swings, panels and the gaps between them

Book a swing pattern once and the shifts roll forward. Declines, leave and cover all land in the same records.

  • check Days each job is short of a trade, collapsed into runs, not a wall of red
  • check Who can fill a gap: cleared for the site, free on those days, not on R&R, inside the days-in-a-row limit
  • check A changeover list for any day: who flies in, who flies out, on which flight
  • check Every override and decline on an audit trail with who and why

Fatigue

The strictest limit, counted across every site

Your fatigue plan, each client's standard and each site's rule, applied shift by shift with the real hours.

  • check Shift length, rest between shifts, days in a row and hours in any 14 days
  • check Counted across jobs, so a shutdown followed by a mill swing is one run
  • check A night-to-day swap with eight hours' rest found the day it happens
  • check Timesheets that break a limit flagged as they are entered

Hours

From the timesheet to the invoice and the pay run

Hours entered from a photo, a text or the supervisor's sheet, approved by name, then billed and paid exactly once.

  • check Rostered shifts with no hours recorded, before the pay run, not after
  • check Approved hours not yet invoiced, by job and trade, at each client's rate
  • check Employee hours handed to your payroll system as a file, never sent twice
  • check Planned against worked by job, site and client

Make it yours

Design your own Humanz replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Humanz. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Humanz replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Humanz data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from fictional demo records for a Perth mining services contractor. Your team asks the question and checks the records behind the answer.

forum

FIFO Crew Rostering for Claude Code

Connected to your own database

Who can fill the two fitter gaps on the Bowen Range shutdown?

Fitter for J-203 Bowen Range dragline shutdown, 2026-11-06 to 2026-11-15 (2 short)

W15

Name
Ana Lopes
Type
labour-hire
Supplied by
Fortitude Labour Hire
From
BNE
Can they go
ready

W17

Name
Chris Doran
Type
labour-hire
Supplied by
Fortitude Labour Hire
From
BNE
Can they go
ready

W16

Name
Pete Walsh
Type
employee
From
PER
Can they go
S11 none on file

W01

Name
Tom Harding
Type
employee
From
PER
Can they go
busy 5 of 10 days (J-201); IND-BRC none on file; S11 none on file; ...

W03

Name
Kelly Brooks
Type
employee
From
PER
Can they go
busy 5 of 10 days (J-201); would work 19 days in a row, limit 14; I...

W02

Name
Raj Patel
Type
employee
From
PER
Can they go
busy 10 of 10 days (J-201); IND-BRC none on file; MED expires 2026-...

Ask it anything

Questions answered from your crew records

Real questions the free version answers today on its demo data. They are not a claim that Humanz cannot produce a custom report.

chat_bubble Who is on site today without a current site requirement, and who let them through?
chat_bubble Whose induction, medical or ticket lapses before the end of a swing they are already booked on?
chat_bubble Which booked rigger has a high risk work licence that runs out partway through the job?
chat_bubble Who can fill this gap: cleared for this site, free on these days, not on a declined day and inside the days-in-a-row limit?
chat_bubble Who goes over the strictest fatigue limit of the business, the client and the site, counted across every job?
chat_bubble Which labour hire firm is supplying people to a Queensland site with no Queensland licence on file?
chat_bubble Which swings in the next two weeks have no flight in, no flight home or no camp room?
chat_bubble Which rostered shifts have no hours recorded?
chat_bubble How many approved hours are not yet invoiced, by job and trade, at each client's rate?
chat_bubble Which overrides have no reason or no name on them?

Switching

How to switch from Humanz

The move involves exporting your workers, credentials and roster, matching your records to the new system, then checking the results against Humanz before you switch.

  1. 1

    Get your records out

    Ask Humanz for exports of your workers, their credentials with numbers and expiry dates, and your roster with timesheets. Humanz can export reports, but it does not publish the export layout. Ask what your account allows and check with Humanz if you are unsure which reports to request. The replacement can bring these records in from CSV exports.

  2. 2

    Load the records

    Set up your sites, requirements, fatigue limits and jobs, then bring in the worker, credential and roster records. Start with a test run for each import so you can see what it will bring in before the records are loaded. The columns in Humanz exports need to be matched to the fields in the new system, so do not assume the layouts will line up automatically.

  3. 3

    Review what the import flags

    Check the import results and resolve anything they flag before relying on the new roster. Confirm that workers, credential numbers and expiry dates, shifts and timesheets have come across as expected. Pay attention to records that need field mapping or clarification. The test run lets you review the import before loading, and running an import twice does not duplicate the records.

  4. 4

    Compare both systems

    Run the new roster alongside Humanz for four weeks. Compare the new system's board with the Humanz scheduler and check that the people, shifts and requirements agree. Use this period to find records or rules that need correcting before you depend on the new system. Keep Humanz available while you check the comparison, rather than treating the first import as proof that the move is complete.

  5. 5

    Switch off Humanz

    Once you have checked the four-week comparison and corrected any issues, make the new system your working roster and switch off Humanz. Confirm that the records you need are in place before ending your Humanz use, including the roster and timesheets you chose to bring across. Keep approved hours in your payroll process, since payroll stays in your payroll system.

construction

Where the real effort goes

The main work is usually matching Humanz's export columns to your records, setting up your own sites, requirements and fatigue rules, and deciding how much history to bring across. Humanz does not publish its export layout, so these details need review. If Enterprise DNA installs and runs the system for you, it handles this migration work as part of that service.

Not ready for a call?

Get your Humanz switch plan by email

We will send you the step-by-step plan for moving your business off Humanz, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Start with the free version or have your version built

Open source

Do it yourself

Free code

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Enter your sites, their requirements, your fatigue limits and your jobs by asking for them.
  4. 4 Export workers, credentials and the roster from Humanz to CSV and run each import with --dry-run first.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your swing patterns, trades, client gate requirements and fatigue plan
  • check Your Humanz people, credentials and roster brought across and checked against four weeks of the scheduler
  • check A phone screen for workers to confirm shifts and send hours, if your crews want one
  • check Approved hours connected to your payroll and invoicing, scoped for how you work
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Access for the crew coordinator, supervisors, travel and payroll
  • check Backups, restore checks and updates looked after
  • check The Monday review and every changeover checked for you to approve
Book a call with Sam

Questions

Instead of Humanz, answered

Our workers confirm shifts and send timesheets on the Humanz app. What happens to that? expand_more

In the free version workers confirm by text or a call and send hours as a photo of the timesheet or the supervisor's sheet, and the office enters them by asking. Nothing is guessed: if a time or a date is unclear, it asks. If your crews need a phone screen, we build that into your version.

How do our people and roster come across from Humanz? expand_more

Humanz onboards from spreadsheets and can export reports, so ask for three exports: your workers, their credentials with numbers and expiry dates, and the roster with timesheets. Each comes in with a test run first, and running it twice does not double anything. Humanz does not publish its export layout, so matching the columns is part of what we do on the paid paths.

Will it stop someone being booked who should not be? expand_more

Yes. A booking is refused when a requirement is missing or lapses before the last day, when the person is already booked or declined those days, or when it would break the days-in-a-row limit. Someone can override it, but only with a reason and their name, and every override stays on the audit trail.

Does it cover our fatigue and safety obligations? expand_more

It checks your roster against nine rules, from site requirements and high risk work licences to four fatigue limits, hours records and Queensland labour hire licensing, and names the source of each. It does not replace your fatigue management plan, your safety adviser or the client's contractor management plan. It makes sure the evidence is there when the client's auditor asks.

What do we pay Enterprise DNA? expand_more

The code is free. A version built and run for your business has one setup fee, then a retainer. It does not grow with your headcount. Sam looks at your Humanz quote, your sites and how your crews mobilise before agreeing the scope.

Own the records behind your next changeover

Take 30 minutes with Sam to go through your Humanz quote, how a swing moves from booking to the gate to the timesheet, and how you invoice. We map your sites and agree what your version needs before you change anything.

FIFO Crew Rostering for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Humanz?

Get your version built