Home/Blog/Crane Work Order Software: How to Build a System Your Operators Will Actually Use
2026-05-21  ·  13 min read  ·  Written by LaSean Pickens  ·  Updated May 2026

Crane Work Order Software: How to Build a System Your Operators Will Actually Use

Crane work order software exists to close one gap: the distance between what the office dispatched and what actually happened on the jobsite. If your operators ignore the work order, rebuild it from memory at the end of the day, or never see it until the carrier is already rolling, you do not have a work order system. You have paperwork. This is a working guide to building a crane work order system your operators will actually use, and to deciding whether you need crane work order software to run it.

We will cover what a crane work order has to contain, why paper and generic field service tools fail in a crane yard, the design choices that decide whether an operator opens the work order or ignores it, and how the work order connects to the field ticket and the invoice so the job pays you on time instead of chasing you for three months.

Work Order or Field Ticket: Know the Difference

A work order is the instruction. It is what the office sends to the field so the operator, the rigger, and the signal person know the job before the carrier leaves the yard. A field ticket is the record. It is what the field sends back to the office to prove what was done so the job can be billed. Same job, two documents, two directions.

Most crane companies blur the two, and the blur is where money and compliance leak out. An operator who never got a clear work order improvises on site. A dispatcher who never gets a clean field ticket back guesses at the invoice. Both ends of that job are now soft, and a soft job is a slow-paying job. We covered the back end in the field ticket to invoice workflow. This guide is the front end: the work order.

What Every Crane Work Order Must Contain

A crane work order that an operator can actually run a job from carries more than an address and a time. Thin work orders are the reason operators call the office four times before lunch. Here is the field set a complete crane work order needs.

  • The job basics. Customer, general contractor, site address, gate or laydown instructions, site contact name and phone, date, and the scheduled start time. Half the morning calls to dispatch are an operator looking for a gate code that was never written down.
  • The scope of the lift. What is being picked, the load weight, the pick radius, the height, and the number of picks expected. An operator who knows the heaviest pick and the working radius before leaving the yard can confirm the crane and the counterweight are right for the job.
  • The crane and configuration. Which crane by unit number, boom and jib configuration, counterweight, and whether the job runs on outriggers or on rubber. The work order is where the office and the field agree on the machine before it is on a truck.
  • The crew. The assigned operator, the rigger, the signal person, and the lift director if the job calls for one. Naming the crew on the work order is also the first checkpoint that every person on the job holds a current credential for the role.
  • The compliance checkpoints. A line for the pre-shift inspection, the lift plan reference, and any site-specific requirements. The work order should remind the operator what has to be documented, not assume he remembers.
  • The billing terms. The quoted rate, minimum hours, travel time, and overtime terms. When the billing terms ride on the work order, the field ticket that comes back can be checked against them in seconds.
  • Notes and known risks. Power lines near the radius, soft ground, a tight swing, difficult access. The work order is the cheapest place to move a hazard out of one person's head and onto the page.

Miss two or three of these and the operator fills the gap with a phone call or a guess. Neither one is free.

Why Paper and Generic Work Order Software Fail on a Crane Jobsite

Paper work orders fail in the obvious ways. They live in a truck. They get coffee on them. They cannot be updated when the general contractor moves the start time, so the operator drives to a 7 AM that became a 10 AM. And a paper work order produces no record the office can search, which means at the end of the month the only proof of what was dispatched is whatever made it back on the field ticket.

Generic work order software fails in quieter ways. Field service tools built for plumbing, HVAC, or general contracting do not know what a crane is. They have no field for boom configuration, no field for counterweight, no concept of a load chart, no place for a pick radius, and no idea that the person assigned to the job needs a current certification for that specific crane type. You end up bending a tool built for service trucks into a shape it was never cut for, and the operators feel it. When the software does not speak the work, the crew stops trusting it, and a work order system the crew does not trust is back to being paperwork.

Crane work order software is different because it is built around the lift. It knows a crane has a unit number and a configuration. It knows a job has a radius and a load weight. It knows the operator assigned to a 90-ton crane needs a certification that covers that crane type. The difference is not cosmetic. It decides whether the work order is the thing the job runs on or the thing the job ignores.

How to Build a Crane Work Order Operators Will Actually Use

The hard part is not the data fields. It is adoption. A work order system only works if the operator opens it. Four design choices decide that.

It has to live on a phone. Operators are not at a desk. The work order has to be in the same pocket as the truck keys, readable in sunlight, and usable with work gloves on. If checking the job means calling the office, the office is still the system.

It has to stay current. Jobs move. The general contractor pushes the start time, the laydown area changes, a second pick gets added. When the office changes the work order, the operator's screen changes with it. A work order that is accurate only at 5 AM is wrong by 9.

It has to be faster than the phone call. If an operator can get an answer faster by calling dispatch than by opening the work order, he will call dispatch. The work order has to put the gate code, the site contact, and the scope one tap away. Speed is what earns adoption.

It has to flow straight into the field ticket. The operator should never retype the job. The crew, the crane, the customer, and the scope carry from the work order into the field ticket, and the operator only adds what actually happened: hours, picks, delays, a photo of the load. When the work order and the field ticket are one connected record, the operator does the job once instead of documenting it twice.

Connect the Work Order to the Field Ticket and the Invoice

A work order that dead-ends is a wasted document. The point of getting the front end right is that it makes the back end automatic. When the work order carries the customer, the crew, the crane, the scope, and the billing terms, the field ticket signed at the end of the pick is already most of the way filled in. The operator confirms the hours, captures the signature, adds a photo, and the office has a billable record the same day, not the same week.

That connection is where the cash-flow math lives. Construction subcontractors routinely wait two to three months to get paid, and every day the invoice sits unsent is a day added to that wait. When the work order flows into the field ticket and the field ticket flows into the invoice, the billing clock starts the day of the lift instead of the week the paperwork finally gets rebuilt. The work order is not just a dispatch tool. It is the first link in the chain that decides how fast the job pays you.

The Compliance Records a Good Work Order Produces

OSHA does not mandate a document called a work order. It mandates the records a good work order naturally produces, and that is the quiet reason to get the work order right.

OSHA's crane standard, 29 CFR 1926.1400 Subpart CC, sets the rules for cranes used in construction. Section 1926.1412 requires documented shift, monthly, and annual inspections. Section 1926.1427 requires operators to be certified for the equipment they run and requires the employer to evaluate and document operator competency. When the work order names the crane, names the crew, and carries a checkpoint for the pre-shift inspection, it becomes the moment those obligations get confirmed instead of assumed.

The cost of getting it wrong is set by the OSHA penalty schedule. Under the adjustment effective January 2025 and carried into 2026, a serious violation carries a maximum of $16,550 and a willful or repeated violation carries a maximum of $165,514, each per violation. An operator dispatched to a crane he is not certified for, or a pick run with no documented pre-shift inspection, is citable. A work order system that checks credentials before it lets the dispatch happen turns that exposure into a routine step nobody has to remember.

What Crane Work Order Software Should Do

Pull the threads together and the job of crane work order software is clear. It should let the office build a complete work order in minutes, with crane fields, not bent service-truck fields. It should put that work order on every crew member's phone and keep it current when the job moves. It should check that the operator, rigger, and signal person hold current credentials for the role before the dispatch is allowed to stand. And it should carry the work order straight into the field ticket and the invoice so the job is documented once and billed the same day.

CraneOp does this on one screen. The office builds the work order, assigns the crane by unit number and the crew by name, and the system confirms every credential before the job locks. The operator opens the job on a phone, runs the pick, and signs the field ticket that was already populated from the work order. The invoice generates from that ticket. The owner stops being the relay between dispatch and the field, and stops spending the evening rebuilding work orders other people half-finished. That is the outcome: the work order does the job, so the people do not have to do the work order twice.

Frequently Asked Questions

What is the difference between a crane work order and a field ticket?

A work order is the instruction the office sends to the field before the job: the customer, the site, the scope, the crane, and the crew. A field ticket is the record the field sends back after the job: the hours worked, the picks made, the signatures, and the proof needed to bill. The work order starts the job. The field ticket closes it. In a connected system the field ticket is built from the work order, so the crew does not retype the job in the field.

Does OSHA require a crane work order?

OSHA does not require a document specifically called a work order. It does require records that a complete work order helps produce, including documented inspections under 1926.1412 and operator certification and evaluation under 1926.1427. A work order that names the crane, names the crew, and prompts the pre-shift inspection makes those requirements part of every dispatch instead of an afterthought.

Can I run crane work orders on generic field service software?

You can, but the fit is poor. Field service tools built for trades like HVAC or plumbing have no field for boom configuration, counterweight, pick radius, or load weight, and no concept of crane-type certification. Crews tend to stop trusting a tool that does not speak the work, and a work order system the crew does not trust gets ignored. Crane work order software is built around the lift, so the work order matches the job.

What should a crane work order include?

At a minimum: the customer and general contractor, the site address and access details, the scheduled date and time, the scope of the lift including load weight and radius, the crane by unit number and configuration, the assigned crew, a pre-shift inspection checkpoint, the billing terms, and any known site hazards. Anything missing becomes a phone call to dispatch or a guess on site.

How does crane work order software help cash flow?

The work order carries the customer, the crew, the crane, the scope, and the billing terms. When it flows into the field ticket, the ticket is mostly filled in the moment the pick ends, and the invoice can go out the same day. Construction subcontractors often wait two to three months to get paid, and every day an invoice sits unsent adds to that wait. Starting the billing clock on the day of the lift is the single biggest cash-flow gain a work order system gives you.

Conclusion

A crane work order system is not about adding paperwork. It is about making the work order the thing the job runs on, not the thing the operator ignores. Get the fields right so the crew is never guessing. Put it on a phone so it travels with the truck. Keep it current so it is still true at 9 AM. Connect it to the field ticket and the invoice so the job is documented once and paid fast. Whether you run that on a spreadsheet, on paper, or on crane work order software, the test is the same: does the operator actually use it.

If your work orders today live on paper in a truck cab or in a generic tool that does not know what a crane is, CraneOp brings dispatch, work orders, field tickets, credential checks, and invoicing onto one screen built for crane companies. Start a free trial at craneop.net or book a demo to see the work order flow from dispatch to invoice.

Written by LaSean Pickens, founder of CraneOp.

Written by LaSean Pickens, founder of CraneOp. Built CraneOp after seeing crane companies run their entire operations on spreadsheets and group texts.
Ready to run a tighter operation?

Book a Walkthrough

Dispatch, fleet, OSHA compliance, field tickets, and invoicing in one platform. 20-minute walkthrough. Custom quote inside one business day.

Book a Demo