Crane Inspection Software: What OSHA Requires You to Document

Crane inspection software has one job that matters more than any feature on the demo. When someone asks for the last twelve months of inspection records on a specific machine, the software produces them in under a minute, complete, signed, and dated. Everything past that is convenience.

Most crane companies do not get written up because their cranes are unsafe. They get written up because the record proving the crane was inspected is in a binder in a truck, or in a photo on somebody phone, or was filled out correctly in the field and then never filed anywhere. The equipment was fine. The paper trail was not.

This post covers what 29 CFR 1926 Subpart CC actually requires you to document, which inspections carry a retention obligation and which do not, what crane inspection software has to do beyond storing forms, and the questions worth asking a vendor before you sign anything.

What OSHA requires you to document, and what it does not

This is the part most owners have never read straight through, and it changes how you evaluate crane inspection software. The inspection requirements for cranes in construction live in 29 CFR 1926.1412, inside the broader Subpart CC framework. Three of those inspections drive almost all of the recordkeeping burden.

• Shift inspection, 1926.1412(d). A competent person visually inspects the equipment each shift the equipment is used. The inspection is required. The standard does not require you to document it.
• Monthly inspection, 1926.1412(e). Same scope as the shift inspection, but this one is documented. The record has to include the items checked, the results, and the name and signature of the person who performed it, along with the date. It is retained for a minimum of 12 months.
• Annual comprehensive inspection, 1926.1412(f). At least every 12 months a qualified person inspects the equipment. Documented, same required fields, retained for a minimum of 12 months.

Wire rope carries a parallel schedule of its own under 1926.1413, and 1926.1412 adds inspections after modification, after repair or adjustment, after assembly, for equipment in severe service, and for equipment that has been idle. Every one of those is a record somebody has to produce later.

Two practical points fall out of this. First, the shift inspection is where the real safety value sits and where the least paperwork is legally required, which is exactly why it gets skipped in practice. Second, plenty of crane companies document the shift inspection anyway. That is a business decision, not a legal one, and it is usually the right decision. A daily record is what defends you when a GC claims damage happened on your pick, and it is the earliest signal that a machine is drifting toward a failure.

Why the binder keeps failing

It is not because operators are careless. The binder fails because the record gets created where the crane is and gets needed where the office is, and nothing reliable connects the two.

There are four separate places the process breaks. Capture, when the form is filled out on a clipboard in the rain or not at all. Transfer, when the paper rides in the truck for a week. Filing, when it lands on a desk and gets scanned eventually, or does not. Retrieval, when you need one specific record for one specific machine from eight months ago and the search is physical.

There is a fifth failure that costs more than the other four combined, and it is invisible. Paper cannot tell you what is coming due. An annual inspection date sitting in a binder does not raise its hand at 60 days out. Nobody notices until the machine is scheduled on a job and someone happens to check. That is how a crane ends up on a jobsite it should not be on, and it is a scheduling failure caused by a records problem. We wrote about that overlap in our breakdown of crane compliance software.

What crane inspection software actually has to do

Digitizing the form is the easy 20 percent. Six jobs separate a real system from a PDF with boxes.

1. Capture in the field, without a signal. Yards, rural sites, and structures kill connectivity. If the app requires a live connection to save a shift inspection, it will get skipped and backfilled from memory, which is worse than no record at all.
2. Enforce the required fields. Items checked, results, name and signature, date. If the form can be submitted incomplete, it will be, and an incomplete record does not satisfy a documented inspection requirement.
3. Bind the record to the specific machine. Not the model, not the size class. Serial number or unit number, so that pulling twelve months of history on one crane is one action.
4. Turn a deficiency into a work order automatically. More on this below, because it is the failure point.
5. Watch the calendar and warn early. Annual inspections, wire rope inspections, and scheduled service should surface 60 and 30 days out without anyone querying anything.
6. Produce the packet on demand. One machine, a date range, every record with signatures, exported in one file. If that takes an afternoon of clicking, the software did not solve the problem you bought it for.

The deficiency loop is where most tools quit

Inspections exist to find problems. So the interesting question is not what the software does when everything passes. It is what happens when something fails.

Under 1926.1412, a deficiency that affects safe operation has to be corrected before the equipment is used again. A tool that records a failed item and stops there has done something genuinely dangerous. It has created a dated, signed, written record that your company knew about a defect, with no matching record that anything was done about it. A documented deficiency with no documented correction is worse evidence than no record at all.

So the loop has to close inside one system. Failed item opens a corrective action. Corrective action holds the machine out of service or flags it, gets assigned to somebody, gets a completion record with a name and a date, and links back to the inspection that found it. Then the next inspection on that machine shows the history. If your inspection tool and your maintenance tracking are separate products that do not talk, that loop is being closed by a human remembering, which means sometimes it is not closed at all. Our post on crane maintenance tracking software covers the service side of this in more detail.

What the paperwork gap actually costs

For 2026, OSHA maximum civil penalties are $16,550 per serious violation and $165,514 per willful or repeat violation, with failure to abate running up to $16,550 per day past the abatement date. Those figures carried over from 2025 rather than rising, because the Bureau of Labor Statistics did not publish the October 2025 CPI-U data needed to calculate an adjustment. OSHA documented that in its 2026 annual adjustment memo, and the current amounts are listed on the OSHA penalties page.

Citations are the visible cost and usually not the largest one. The quieter costs are a machine pulled off a job because its annual lapsed, an insurance renewal priced off a thin documentation history, and a damage claim you cannot rebut because the shift inspection from that morning does not exist. One of those in a year clears the cost of the software several times over. That is the honest math on this category.

What to ask a vendor before you buy

Every product in this space will show you a clean inspection form. Push past the form.

• Does the app save a completed inspection with no connectivity, and what happens to it when the truck gets back in range?
• Can an inspection be submitted with blank items, or does the form block it?
• Show me twelve months of monthly and annual records for one specific crane, exported as one file, right now.
• What happens the moment an operator marks an item as failed? Show the corrective action it creates, not a description of it.
• Where does the signature live, and can it be traced to a specific person rather than a typed name?
• What warns me that an annual inspection is due, how far out, and who receives it?
• Does the inspection record connect to the schedule, so a machine that is out of service cannot be booked on a job?

That last one is the difference between a records tool and an operating system. Storing the inspection is table stakes. Having the inspection change what the business is allowed to do is the actual value.

Frequently asked questions

Does OSHA require crane inspections to be electronic?

No. The standard specifies what has to be inspected, who is qualified to inspect it, what the documentation has to contain, and how long it has to be kept. It does not specify paper or software. Crane inspection software is a way of meeting the requirement reliably, not the requirement itself. A crane company with a disciplined paper system is compliant. The difficulty is that disciplined paper systems depend on one person never getting sick, quitting, or falling behind.

How long do we have to keep crane inspection records?

Monthly inspection documentation and annual comprehensive inspection documentation are each retained for a minimum of 12 months under 1926.1412. The shift inspection is required but is not required to be documented, so no retention period attaches to a record you are not obligated to create. Most companies keep everything considerably longer than the minimum, because inspection history is what defends against damage claims and supports the resale value of the machine.

Who is allowed to perform each inspection?

The shift and monthly inspections are performed by a competent person. The annual comprehensive inspection is performed by a qualified person. Those are defined terms in the standard, not job titles you assign, and the distinction matters when you are configuring software. If the tool lets any user sign any inspection type, then your records can look complete while being performed by someone the standard does not authorize for that inspection.

Can we use general field service or maintenance software instead?

You can store forms in almost anything. What horizontal tools generally lack is the crane-specific structure: inspection types tied to the correct interval and the correct qualification level, wire rope handled on its own schedule, deficiencies that hold a machine out of service, and an export that reproduces a defensible record set for one serialized machine. We compared that gap directly in crane company software versus field service software.

What is the fastest way to get current if our records are a mess?

Start with the annual inspections, because those have hard dates and the highest exposure. Get every machine current on its annual and get that documentation into one place. Then turn on monthly inspections going forward and stop trying to reconstruct the past. Backfilling records from memory produces documents that are wrong and signed, which is a worse position than a gap you can explain. Fix the forward-looking process first, then the history fills itself in twelve months.

The point of all of this

Nobody got into the crane business because they enjoy documentation. The reason to move inspections off paper is not that software is modern. It is that the annual never sneaks up on you, that a failed item cannot quietly go nowhere, and that the day someone asks for records is a five minute day instead of a two week scramble through truck cabs and filing cabinets.

CraneOp runs inspections, fleet and equipment records, operator certifications, maintenance, scheduling, dispatch, field tickets, and invoicing in one platform built specifically for crane companies. If you want to see what your inspection records look like inside one system, book a walkthrough at craneop.net. Thirty minutes, your real machines, no pitch deck.