Describe the crane, the worksite, and the checks your operators must complete before use. Makeform turns your instructions into a mobile-friendly crane inspection checklist with equipment identification, visual and operational checks, defect details, photos, and a clear release-or-remove decision for every shift.
Send inspection records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose the closest crane scenario, adjust the prompt, or send it to the Makeform builder. Each sample is a starting structure to adapt to your instructions and procedure.
Prompt ready4 formats
Audience
Operators inspecting a mobile crane before the first lift
Format
Shift checklist with condition status and photos
Prompt size
519 chars
Brief qualitySends to builder
Example checklist structure
Shift checklist with condition status and photos
Prompt exampleEditable in builder
Crane ID, site, shift, and configuration
Short answerFirst ask
2
Outriggers, carrier, boom, rope, and hook condition
Multiple choice
3
Controls, brakes, indicators, alarms, and limit devices
Multiple choice
4
Describe and photograph each defect
File upload
5
Ready for use or removed from service?
Multiple choice
Suggested routing tags
Suggested
Ready for use
Defect review
Removed from service
Ask for a separate status for every inspection point: satisfactory, defect found, not applicable, or not checked. A single overall checkbox hides the exact item that stopped the crane from being used.
Step 1
Identify
crane, operator, site, shift, and configuration
Step 2
Inspect
visual condition and no-load operating checks
Step 3
Decide
ready, review required, or removed from service
Step 4
Route
defect evidence and notification reach the right person
Inspection records that lead to action
Turn the walk-around into a usable shift decision.
A generic tick sheet records that someone visited the crane. A purpose-built checklist records which crane and configuration they saw, what they tested, exactly what failed, and whether use stopped before the next lift.
One result per inspection point
Give every component its own satisfactory, defect found, not applicable, or not checked result. Required explanations for skipped items keep an incomplete inspection from looking complete at a glance.
Defect questions appear when needed
Conditional fields open only after a defect result, asking for the observation, location, photo, immediate control, equipment status, tag reference, and person notified without slowing routine entries.
The final status drives routing
Separate ready-for-use records from items needing review or removal from service. Notifications can give supervisors and maintenance the defect context instead of a vague message that a check failed.
Adapt it to the crane
The useful checks change with the equipment.
Begin with the crane type your crews actually operate. Then replace generic labels with your asset names, site terminology, manufacturer inspection points, and internal escalation path.
Mobile hydraulic cranes
Capture carrier condition, tires, outriggers, boom configuration, hydraulic leaks, rope and hook condition, cab controls, safety devices, and the setup that applies to that shift.
Tower cranes
Organize access, base, visible structure, ties, jib, trolley, hoist, cab, communications, brakes, alarms, and operational devices into sections that suit the operator's route.
Overhead and gantry cranes
Focus a concise pre-start check on the hook, rope or chain, block, controller, emergency stop, brakes, limits, bridge and trolley travel, and anything unusual during the no-load test.
Portable cranes and hoists
Record assembly, pins and braces, wheels or casters, floor conditions, hoist mounting, capacity markings, recent reconfiguration, and the status for the planned maintenance task.
Build the workflow
From a plain-language brief to a field-ready checklist.
Start with the inspection your operator already performs, make every decision explicit, and test the form on the device and route crews will use at the start of a shift.
State whether this is a pre-use, shift, post-assembly, or other internal check. Include the crane type, identifiers, typical configuration changes, work environment, operator role, and the procedure or manufacturer list you want reflected.
02
Edit checks and decision choices
Review every generated item with people familiar with the equipment. Split combined questions, add not-applicable and not-checked choices, mark essential identifiers required, and use your own language for equipment status and escalation.
03
Build the defect branch
When an operator finds a problem, reveal targeted questions for component, observation, location, severity used by your team, photos, immediate action, tag number, notification recipient, and whether the crane remained unavailable.
04
Test and route the completed record
Run one clean inspection and one defect scenario from a phone. Confirm required fields behave correctly, photos are readable, the final status cannot be missed, and defect notifications reach the designated supervisor or maintenance queue.
Choose the right record
Why a generated checklist works better than a generic sheet.
The format should help the operator make and communicate a specific pre-use decision. Compare what each approach captures after the walk-around is over.
Approach
What it records
Where it fits
ApproachPaper tick sheet
What it recordsFast marks and a signature, with photos and follow-up often stored somewhere else.
Where it fitsA familiar backup where the completed sheet can be routed and retained reliably.
ApproachGeneric digital inspection form
What it recordsSearchable answers, but broad equipment questions may miss crane configuration and device-specific checks.
Where it fitsA shared program covering many assets when each asset does not need tailored branching.
Approach
Generated crane checklist
What it recordsCrane identity, component results, functional checks, conditional defect evidence, final status, and notification in one submission.
Where it fitsRepeatable pre-use documentation adapted to a crane type, site process, and escalation route.
Field guide
Six sections for a practical crane inspection checklist.
Use these sections as an editing guide after generation. The final contents should follow the equipment manufacturer's instructions, the crane's configuration, and the inspection process established for your workplace.
Identity and context
Tie the result to the exact crane and shift.
Asset identity prevents a satisfactory result from being attached to the wrong machine. Ask for the site, work area, date and time, shift, operator, crane ID, make or model, capacity reference, hour meter when relevant, and any configuration detail that changes which checks apply.
Use an asset dropdown or scanned identifier when crews inspect several cranes.
Record boom, jib, counterweight, outrigger, controller, hoist, or attachment details that distinguish the setup.
Include handover notes or recent reconfiguration prompts when they affect the inspection route.
Visual condition
Give major components separate, observable checks.
Avoid one question asking whether the whole crane looks good. Divide the walk-around into the carrier or base, structure, boom or bridge, outriggers or supports, fluid leaks, electrical condition, guards, access points, markings, and surrounding travel or swing area as applicable.
Phrase items around what the operator can observe rather than an unexplained yes or no.
Offer satisfactory, defect found, not applicable, and not checked choices consistently.
Require a reason whenever an expected item was not checked.
Load path components
Separate rope, chain, hook, block, and reeving results.
The load path deserves component-level responses. Depending on the equipment, include wire rope or chain condition, reeving, drum, sheaves, lower block, hook, throat area, latch, swivels, and visible attachment points. Keep inspection wording aligned with the terms crews know.
Do not hide several components behind one combined pass box.
Let operators identify the component and location of any observed damage.
Add a photo field that can capture both context and a close view of the issue.
Operational checks
Record what happened during the no-load test.
Create distinct results for controls, emergency stop, brakes, hoist, swing or bridge travel, trolley movement, warning devices, indicators, communications, and operational limiting devices that apply. A notes field should capture unusual sound, delay, vibration, or movement without forcing it into the wrong category.
Name each direction or function when that detail matters to troubleshooting.
Keep visual checks separate from functional test results.
Provide not-applicable logic for equipment that lacks a listed function.
Defect and control
Make every failed item produce an actionable record.
A defect branch should collect more than a comment. Ask what was found, its component and location, photos, the immediate step taken, whether a tag or barricade was used, whether operation stopped, and who received the report. Use the severity and status terms already defined by your organization.
Require details only when a defect or incomplete check is selected.
Capture tag or work-order references so related records can be matched later.
Do not let a free-text note replace the explicit equipment-status decision.
Status and handoff
End with ownership, notification, and the next step.
The submission should finish with a clear status such as ready for use, review required, or removed from service, using your workplace's approved wording. Collect operator confirmation, the time of the decision, who was notified, and any supervisor or maintenance follow-up field your process needs.
Show the final status prominently in confirmation messages and exports.
Route defect records to a named role or queue rather than relying on the operator to forward them.
Keep repair completion or return-to-service authorization in its own controlled follow-up process.
Related tools
Connect inspections to equipment follow-up.
Build companion forms for general equipment checks, safety observations, maintenance requests, and other inspection programs while keeping the crane checklist focused on the operator's pre-use decision.
Practical answers for safety managers and operators moving pre-use documentation from paper to an online form.
What should a crane inspection checklist include?
Start with crane ID, site, date and time, shift, operator, and configuration. Then organize relevant visual checks, load path components, controls, brakes, warnings, indicators, communications, and functional devices. Add a conditional defect section for descriptions, location, photos, immediate action, tag or work-order reference, operation status, and notification. Finish with an explicit ready, review-required, or removed-from-service decision. Adapt the items to the crane, its manufacturer information, and your workplace procedure.
Can I create different checklists for mobile, tower, and overhead cranes?
Yes. Generate a separate form for each crane family or use branching after an equipment-type selection. A mobile crane may need carrier, tire, outrigger, boom, and hydraulic questions; a tower crane may need access, base, ties, jib, trolley, hoist, and communications; an overhead crane may emphasize bridge travel, trolley, pendant or radio controls, hook, rope or chain, brakes, and limit functions. Separate forms are often easier when inspection routes differ substantially.
How should the form handle a defect found before use?
Use conditional logic so defect found opens required fields for the component, observation, location, photo, immediate control, equipment status, tag reference, and person notified. Keep the final operational decision separate from the defect description. This lets the record show both what the operator saw and what happened next. Define the decision options and escalation route from your own process, and keep repair or return-to-service approval as a distinct follow-up record when needed.
Can operators complete the crane checklist on a phone?
Yes. Publish the checklist as a link operators can open on a phone or tablet. Keep question labels short, group checks by the physical inspection route, use consistent response choices, and reveal detailed defect questions only after a problem is selected. Test both a clean result and a defect result on the devices used at the site. If connectivity is uncertain, decide on a documented backup process before replacing the paper copy.
Can operators attach photos of damage or unusual conditions?
Yes. Add file-upload fields inside the defect branch. Ask for one image that shows where the issue is on the crane and another close image when detail matters. Pair every upload with text fields for the component, location, and observation because a photo alone may be hard to interpret later. You can also request an assembly or overall-condition photo for specific workflows without making every routine inspection unnecessarily long.
Is this crane inspection checklist generator free?
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect crane inspection submissions without a response cap. The paid tier removes the Makeform badge. Review the generated checklist with people familiar with the crane and replace sample language with the equipment checks, status choices, and notification rules used at your workplace before putting it into service.
Where do completed inspection records go?
Submissions are collected in Makeform, where the inspection answers, final status, comments, and uploaded files remain together. You can send data to Google Sheets, notify a channel in Slack, or connect workflows through Zapier. Plan the destination around who needs to see normal results, who must receive defect records, how asset IDs will be searched, and how a related maintenance request or tag reference will be matched to the original inspection.
Does a generated form replace the manufacturer's inspection instructions?
No. The generator helps turn your requirements into a structured online checklist; it does not determine the correct inspection scope for a particular crane or configuration. Build the form from the manufacturer information and inspection process applicable to your equipment and workplace, have the contents reviewed by the responsible people in your organization, and update it when the crane, attachments, configuration, site process, or internal escalation path changes.
Make every pre-use decision clear.
Generate a crane inspection checklist your operators can complete at the equipment.
Unlimited free forms and responsesConditional defect details and photosClear status and notification handoff
