Paper LEM books
Carbon copies. Coffee rings. A day’s work left on a dashboard.
From the first hour on site to the final invoice.
Field tickets, client approvals, and the office.
Finally, working together.

Labour. Equipment. Materials.
You did the work. Paid the crew. Ran the equipment.
A forgotten ticket shouldn’t be the reason you don’t bill for it.
Carbon copies. Coffee rings. A day’s work left on a dashboard.
Another version of LEM_tracker_FINAL.xlsx. Still no clear status.
The approval you need, buried somewhere in the replies.
A rate in a group chat. A photo that never made it to the office.
Yesterday’s work, erased before anyone recorded it.
Trying to remember what happened when it’s time to bill.
The billable value of one ticket, before tax.
Work that would otherwise go unsubmitted and unbilled.
Adjust the portion you expect to submit, get approved and collect.
Same crew. Same equipment. Work you already did, brought back into the billing process.
RECOVERED STILL AT RISK
Illustrative estimate using your inputs, held constant each month. Assumes the selected share of missed work is submitted, approved and paid. Gross billing before costs, tax and software fees—not profit or guaranteed savings.
See how a ticket makes it to the invoiceLabour, equipment and materials on one ticket, coded to the PO number and its major and minor codes.
Sign the work and check that submission succeeded.
Give the client the work and supporting record to review.
Bring approved tickets and their backup into the invoice.
A ticket shouldn’t be a dead end.
See how one day in the field becomes
one clear record in the office.
This is a sample project. Try the controls.
No account. No real data. Just the flow.
Drag to change the hours. Watch the ticket update.
The hazards, controls, and crew acknowledgement stay with the day’s work. Open the sample, then add yourself to the crew.
Review the exclusion zone, spotter, and radio check before the shift.
Review access routes and confirm the walking surface has been treated.
Stop and reassess with the supervisor when the work or conditions change.
Illustrative risk scores: before → after controls, on a 1–5 scale.
Emergency arrangements are reviewed with the crew at the briefing.
Example only. No attendance or safety record is created.
Illustrative rates. Demo actions never send an email or create real records.
Good work gets lost in the handoff.
Give the field, the office, and the client
one connected place to move it forward.
Capture labour, equipment and materials while the work is fresh, coded to the PO, AFE and major and minor codes. Text it to the field rep with a secure link to sign: no app, no account. Give the office a ticket they can actually use.
See it for your teamHours on site. Details in place.
FOR THE OFFICE
Every approved ticket posts against its PO the moment it’s approved — not at month-end. Clients watch commitment build in real time, catch overruns before they happen, and never again learn about a blown PO from an invoice.
Contractors see the same numbers. One shared ledger means the month-end reconciliation call simply stops happening.
Explore Control for your teamSee the limit coming.Haul road maintenance is at 96%. Review the remaining authorization before approving more work.
Sample purchase orders. No live account data.
Connect field work to purchase orders and rate sheets, so the right context starts with the ticket.
Bring approved field tickets into invoicing. Keep the supporting record close to the amount being billed.
Go further with equipment economics, margin visibility, and field safety tools in Pro.
Hands check in at the site and log their own hours on free Operator accounts. The crew foreman approves, and approved hours land on the labour ticket.
See what every rented unit has burned, what it adds to the PO, and get an email before it renews.
Set each crew's days on, days off and shift. Tickets put today's crew first, and nobody is reminded on a day off.
SECURITY & RELIABILITY
These tickets are money and legal record. The platform treats them that way.
Every signed ticket is hashed (SHA-256). Changing a signed ticket means voiding the signature first, and it must be signed again — keeping the approved record tied to what your client signed.
Ticket status moves through the API. Approvals run in atomic transactions with the PO drawdown, so concurrent approvals don’t overwrite the PO balance.
Contractors see their own work. Clients see only the connections they’re party to. The server enforces role and company access; database rules block direct browser reads and writes.
Rate changes, PO amendments, approvals and invoice generation create audit events recording who acted and when, with before/after details where applicable.
Staff access requires explicit staff privileges and a server-side email allowlist. Sessions expire; invite tokens are single-use and time-boxed.
Infrastructure providers encrypt data in transit and at rest. Content-security policies restrict the resources the app can load. Ask us about backup and retention.
Contractors and operators in geotechnical drilling, mining, oil and gas, and heavy civil work. If your day runs on crews, equipment, field tickets, and client approvals, we’d like to show you the fit.
Yes. Client approval is part of the workflow, so your client can review the field record before it moves into invoicing. Client approvers are free.
Operations connects field tickets, approvals, and invoicing. Pro adds margin and equipment economics, plus field hazard assessments with QR crew sign-on. Control is built for client-side cost oversight. Compare the current plans and pricing ↗
No. This page uses a sample project and illustrative rates. You can explore the workflow without creating records or sending anything. To see your own operation in Pit & Rig, get in touch ↗.
Your crew has a job to do.
Give the paperwork a better way home.