SHIFTLEDGER / VALUE / FICTIONAL DATA

One record.
Every department
reads it differently.

Crews, supervisors, dispatch, payroll, safety, maintenance and the data van all touch the same shift. ShiftLedger is the shared record between them, not another system to replace.

The reason it exists is personal: after a handover went wrong and two technicians were written up because nobody could show who did what, Matthew wanted a record that protects the people who did their jobs right.

Every chart below is drawn live from the tested code with fictional people. Nothing here is a measured result from a real company. Where the tool falls short, the page says so.

Try crew time →Try the stage console →

01 / Who it is for

Nine roles.
One shift record.

02 / Where finance connects

Hours in.
Clean files out.

Finance does not need another place to type. It needs approved hours, split the way the company counts them, with a trail behind every number. The hand-off is a file the company’s own payroll or accounting system already knows how to import.

How hours reach financeCrew submit time, a supervisor approves it, back office reviews overtime and holiday hours, then exports files for the company payroll or accounting system.
Where ShiftLedger stops: pay rates, deductions, tax and general-ledger coding stay in the company’s own finance system.
One crew member’s weekly hours across a 14 on, 7 off hitch

What finance receives

The weekly summary, produced by the same code as the download in Crew Time. First rows from the example:

  • Approved hours by person, date, location and shift.
  • Regular, overtime and holiday hours by week, from settings the company controls.
  • The audit trail: who entered, who approved, who changed what and why.
  • Missing-time and scheduled-versus-actual lists before the payroll cutoff.


03 / Scheduling and coverage
14 on, 7 off.
Who covers the gap?
Day and night coverage over six weeks, two crews against three


04 / Test it on your numbers
A calculator,
not a promise.
Enter your own figures. The reduction is an assumption to test in a pilot, so it starts at zero. Nothing here is a measured result.


05 / How it compares
Where it wins.
Where it does not.
Marks come only from what each product’s public pages say. A hollow mark means the pages I read do not document it, not that it is missing. ShiftLedger is a demonstration and loses plainly on maturity.
Sources read: Corva’s frac optimization page, NexTier’s IntelliStim page, FieldPro Software’s public site, Innovapptive’s Maximo mobile page. Frac design tools such as FracPro were not assessed beyond a job posting naming them.


06 / Prove it
A four-week pilot
with numbers set in advance.


What this is not
These are demonstrations with fictional data. They are not a payroll, legal, or safety system, they have no sign-in or security review, and they are not connected to any company system. Overtime and holiday settings are the company’s to set. A real pilot needs privacy review for employee time data and agreement with any labor representatives.
Back to ShiftLedger →Contact Matthew →