Crane Field Ticket Software: How to Turn a Signed Ticket Into a Paid Invoice Without the Two-Week Detour

Crane field ticket software is the difference between a pick that gets paid in two weeks and a pick that gets paid in two months. The lift is the easy part. The money is the part that goes sideways, and it almost always goes sideways in the twelve inches between the operator writing a ticket and the office turning that ticket into an invoice a general contractor will actually process.

Most crane companies still run this on paper. A three-part carbonless pad rides in the truck. The operator fills out a ticket at the end of the shift, gets a signature from whoever happens to be standing there, and the yellow copy lives in a door pocket until Thursday. By the time it reaches the office, the hours are approximate, the signature belongs to somebody nobody can identify, and the standby time is a number the customer is going to argue about. That argument costs more than the standby time ever did.

This post covers what belongs on a crane field ticket, what the federal payment clock actually says about invoices, what crane field ticket software has to do to be worth installing, and how to roll it out so your operators do not quietly go back to the paper pad in week three.

What a crane field ticket actually is

A field ticket is the record of what your crane and crew did on a job, signed by somebody with authority to confirm it. It is not a timesheet, though it carries time. It is not an invoice, though the invoice is built from it. It is evidence.

That word matters. Everything downstream of the pick depends on the ticket holding up. Payroll pays the operator from it. The invoice is priced from it. When the customer disputes four hours of standby, the ticket is the only thing standing between you and eating those hours. When the job goes to a claim, the ticket is the contemporaneous record of who was on site, what crane was there, and what it did.

A ticket that is legible, complete, signed, and delivered the same day is a strong piece of evidence. A ticket that shows up nine days later with a scrawl in the signature box is a negotiating position, and not a good one.

The three places paper field tickets leak money

The delay between signature and office. Every day a signed ticket spends in a truck is a day your invoice is not out and your cash is not moving. Crane companies routinely lose a week here without noticing, because the week is invisible. Nobody logs it. The operator does not think of himself as holding up billing. He thinks of himself as driving home.

The dispute you cannot win. Standby, travel, extra rigging, a second pick that was not on the original scope, waiting on the concrete, waiting on the steel that did not show. These are the line items customers push back on, and paper tickets almost never carry enough detail to defend them. A ticket that says "standby 3.5 hrs" loses. A ticket that says standby began at 10:15 when the steel delivery was late, was authorized on site by a named superintendent, and ended at 13:45 when the first piece landed, wins.

The invoice that gets returned as improper. This one is the most expensive and the least understood, because most owners have never read what the payment clock is attached to.

What a proper invoice requires, and why the field ticket decides it

If you touch federal construction work, the payment terms are not a matter of opinion. FAR 52.232-27, Prompt Payment for Construction Contracts, sets the clock. Progress payments are due 14 days after the designated billing office receives a proper payment request. Final payments are due 30 days after receipt of a proper invoice, or 30 days after acceptance of the work, whichever is later.

Read that phrase again: a proper payment request. If the invoice is not proper, the billing office returns it within 7 days with the reasons why, and your 14-day clock restarts when you resubmit. The clause then lists exactly what makes an invoice proper. Eleven items, including the contract number or other authorization for the work performed with order number and line item number, a description of the work or services performed, delivery and payment terms, substantiation of the amounts requested, and any other information or documentation required by the contract.

Look at that list from the seat of a crane operator. Description of the work performed comes from the field. Substantiation of the amounts requested comes from the field. If your ticket does not carry a clean description tied to the right job authorization, your invoice is not proper, and nothing about the payment clock protects you.

The same clause is why the money often stops one tier above you. Under paragraph (c)(1), the prime contractor must include a clause obligating it to pay the subcontractor for satisfactory performance not later than 7 days from receipt of payment from the government. Seven days. If you are waiting sixty, the delay is usually not the prime sitting on funds. It is that your paperwork has not cleared far enough up the chain for the prime to get paid in the first place.

Private commercial work is not governed by FAR, but most GC subcontracts mirror the same structure: pay-when-paid language, a monthly billing cutoff, and a requirement that backup documentation accompany the pay application. Miss the cutoff by one day because a ticket was in a truck and you have just added a full billing cycle to your own cash conversion.

What belongs on a crane field ticket, field by field

Most tickets fail because they were designed by a print shop, not by somebody who has argued with a customer about hours. Here is the field list that survives a dispute.

• Job identity. Customer, job name, site address, and the purchase order or contract authorization number. Without the authorization reference, the invoice cannot be matched on the other end.
• Equipment. Crane unit number, make and model, capacity, and serial number. Serial number matters because it is what ties this ticket to the inspection and maintenance record for that machine.
• Crew. Operator, oiler, riggers, and signal person by name, with certification identifiers where the job requires them.
• The clock, broken out. Departure from yard, arrival on site, setup start, first pick, last pick, teardown complete, departure from site, return to yard. One lump "hours worked" number is a dispute waiting to happen.
• Standby, with cause and authorization. Start time, end time, the reason, and the name and title of the person on site who authorized it.
• Mobilization and travel. Miles, permits, escorts, and any assist equipment.
• Rigging and accessories. Slings, shackles, spreader bars, jib or fly sections installed, counterweight configuration, and matting.
• Description of work performed. Plain language, specific. What was picked, from where, to where, how many times.
• Signature block that means something. Signature, printed name, title, company, and a timestamp. A signature with no printed name is close to worthless six weeks later.
• Photos. Setup, ground conditions, matting, the load, and anything unusual. Photos end more disputes than paperwork does.

What crane field ticket software has to do

Software that only digitizes the paper form is not worth the rollout friction. Crane field ticket software earns its place when it does these things.

It works with no signal

Your crews work in basements, in steel structures, on rural sites, and in the middle of plants with no coverage. If the app requires a connection to save a ticket, your operators will stop using it the first week and you will never get them back. Offline capture with a sync when service returns is not a feature. It is the entry requirement.

It prefills from the dispatched job

The operator should not be typing the customer, the address, the purchase order, the crane, or his own name. All of that already exists in the dispatch record. Every field the office already knows is a field the operator should not have to fill in, because every field he fills in by hand is a field he can fill in wrong.

It captures the signature with its context

A signature is only useful with a printed name, a title, a company, and a timestamp attached to it. Software should require those, then stamp the record so nobody can quietly adjust it later.

It becomes the invoice without rekeying

This is where the money is. A signed ticket should turn into a draft invoice with the rate structure already applied, minimums enforced, standby priced correctly, and the description of work carried straight through to the invoice line. If somebody in the office is retyping ticket data into accounting software, you have bought a digital ticket and kept the two-week delay.

It keeps the ticket attached to everything else

The ticket belongs to a job, a crane, an operator, and eventually an invoice. When a claim comes back eight months later and asks what happened on that pick, you want one search to produce the ticket, the photos, the lift plan, the operator certification that was current that day, and the inspection record for that machine.

That last piece is where field documentation and compliance documentation stop being separate systems. Under 29 CFR 1926.1412, monthly inspection documentation must record the items checked, the results, and the name and signature of the person who conducted it, and must be retained for a minimum of three months. Annual inspection documentation carries the same content requirement and must be retained for a minimum of twelve months. If your tickets live in one place and your inspection records live in a binder in a different building, you are maintaining two archives of the same crane and the same day.

Rolling it out without the crew going back to paper

Field software fails on adoption, not on features. Four rules keep a rollout alive.

Start with one crew, not the whole yard. Pick the operator most likely to tell you the truth about what is annoying, run two weeks, and fix what he flags before anyone else touches it.

Make day one faster than paper, not more thorough than paper. The temptation is to add every field you ever wanted. Do not. Ship a ticket the operator can complete faster than he could write one, then add fields once the habit exists.

Give the operator something he wants. Accurate time capture means accurate overtime. Say that out loud. A crew that believes the ticket protects their pay will fill it out.

Close the back door. Keep the paper pad as a backup for thirty days, then remove it. As long as paper is an option, paper wins on a bad day, and one bad day resets the habit.

The part that actually changes your week

Field tickets are not paperwork. They are the moment your work becomes money, and every hour the ticket sits unfinished is an hour your business is carrying somebody else. Crane field ticket software collapses that gap from days to minutes, and it does it without asking your operators to become clerks.

Frequently asked questions

What is a crane field ticket?

A crane field ticket is the signed record of what a crane and crew did on a job. It carries the customer and job authorization, the crane and crew identities, the full time breakdown including standby and travel, the rigging used, a description of the work performed, and a signature from a person on site with authority to confirm it. Payroll, invoicing, and any later dispute all run off it.

How fast should a field ticket reach the office?

The same day, ideally within minutes of signature. On federal construction work the payment clock under FAR 52.232-27 does not start until the billing office receives a proper payment request, and on private work most subcontracts have a monthly billing cutoff. Every day a signed ticket spends in a truck is a day of float you are giving away for free.

Can we just use general field service software for crane tickets?

You can, and many companies try. The gap shows up in crane-specific data: configuration and counterweight, jib and fly sections, load charts, standby with authorization, mobilization and permits, operator certification currency, and the inspection record tied to the machine serial number. Generic field service tools model a technician and a work order. A crane company needs a machine, a configuration, a crew, and a compliance file, and retrofitting that into a generic tool usually costs more than it saves.

Do digital signatures hold up on a field ticket?

A captured signature holds up far better than a paper one when it carries context: the printed name and title of the signer, the company they represent, a timestamp, and a record that cannot be edited after the fact. The weakness in most disputes is not the signature itself. It is that nobody can establish who signed or when.

How long should we keep field tickets?

Longer than you think. Tie the retention to your contract terms, your insurance requirements, and your state statute of limitations for construction claims, which commonly runs for years. Separately, OSHA sets its own minimums for inspection documentation under 29 CFR 1926.1412: three months for monthly inspections and twelve months for annual inspections. Those are floors for a different record, not a ceiling for yours.

What is the fastest way to cut days off our billing cycle?

Attack the handoff, not the office. Most crane companies assume billing is slow because the office is slow. Time it honestly and you usually find the delay is between signature and office, and that a same-day digital ticket removes more days than any process change inside the office ever will.

See it on your own jobs

CraneOp keeps field tickets with the dispatched job, the crane, the operator certification record, the inspection log, and the invoice they turn into, so a signed ticket becomes billable work the same day instead of the following week. If you want to see what one of your own picks looks like inside it, book a walkthrough at craneop.net. Thirty minutes, your real jobs, no slide deck.