Field inspection form template
Record the state of a machine, a vehicle, or a structure on site, with photos and a signature.
10 fields. Free to start. No card.
Who uses it
Plant operators, fleet supervisors, lift technicians, and asset managers. Common in mining, construction, logistics, utilities, and heavy manufacturing on every continent.
The problem it solves
An inspection on a paper pad is invisible until somebody drives it back to the depot. By then the machine has moved and the operator who saw the crack has finished their roster.
How this handles it
Each block draws itself on a phone, so the operator answers yes, no, or not applicable with a thumb, and the photo field opens the rear camera and shrinks each image before it leaves the handset. The finished sheet becomes a PDF the moment it is sent, so the depot inbox has it before the operator walks back to the ute.
Machine and shift
Walk around
Up to six photos. Take one wide shot and one close shot of each fault.
API
Submit this form over the API
The template is published as JSON at
/templates/field-inspection.json.
Read it for every field id, then post values keyed by those ids.
A field id is stable. A label is not.
{
"values": {
"insp_asset": "ex_11_excavator_5t",
"insp_operator": "Full name",
"insp_date": "2026-09-09",
"insp_shift": "day",
"insp_fluids": "yes"
},
"idempotency_key": "field-inspection-2026-09-09-001",
"agent": {
"name": "your-agent"
}
}Authorization: Bearer ifk_submit_…, or connect over MCP at /mcp.Questions about field inspection forms
Can an operator finish an inspection with no signal?
The form loads once and holds the answers in the browser while the operator works. It sends when the handset finds a bar of signal again. Photos are shrunk on the phone first, so the upload is small enough to clear a weak tower.
How many photos can one inspection carry?
Twelve is the ceiling for a photo field, and six is the sensible default for a walk around. Each file is capped at three megabytes after the phone resizes it, which is plenty for a crack or a leak.
Does the signature prove who did the walk around?
The drawn signature is stored as an image against the submission, next to the operator name, the timestamp, and the asset. It is evidence of who signed, not a cryptographic identity, so pair it with an API key when the audit matters.
What happens to a failed check?
Nothing routes automatically on its own. Point a webhook at your maintenance system and it fires on every submission with the answers keyed by field id, so a no on the guard check can raise a work order in your own tooling.
Create this form in your own workspace.
It loads as a draft. Change every field, or send it as it stands.
Create this form