Field operations · Inspections, audits, permits, logs

The work gets done.
The record comes with it.

Every check is built around the way you already run it — the conditions, the thresholds, the order things happen in. Your crew runs it on a phone, with the photos, signatures and timestamps attached.

A plant floor drawn in one terracotta line: pipework, a spill and warning placards, an inspector photographing an extinguisher, a worker carrying a box, and in the foreground a hand holding a phone with the first item on a checklist ticked.

Used across construction, manufacturing, agriculture and industrial operations.

Early access is open — tell us what you run and we'll be in touch.

Free foreverUnlimited usersNo contract
No rollout

One is a fine place to start.
You get a system anyway.

The next one can wait until you feel like it — nothing has to move across before this is useful, and anyone can fill one in the first time they see it.

One template.Five.Twenty.

You've replaced a clipboard.

One place to look, and one set of permissions.

Everything your operation runs, on record — and you never rolled anything out.

A worker in a hard hat carrying a single box, drawn in one terracotta line.
A worker pushing a hand truck stacked with boxes, drawn in one terracotta line.
A worker driving a forklift with a full pallet load, drawn in one terracotta line.
In the field

Filled in on the spot. Nothing gets in the way.

Your crew will fill a check in on the spot when the app doesn't fight them. Most apps do — they want signal, or they ask for the site name a third time, or they freeze on a progress bar. So we took those reasons away.

Works with no signal.

Start it, work through it, submit it — in a basement, a tank, or forty miles from the nearest tower. It syncs itself when the phone finds a connection. Nobody has to think about it.

Submit and walk away.

A two-hundred-item audit doesn't keep anyone waiting on a spinner. The phone goes back in the pocket and the work carries on.

A photo beats a description.

Especially in gloves. High resolution, attached to the exact item, timestamped where it was taken.

A factory drawn in one coral line and cut away to show two floors. Below ground, a worker in a hard hat fills in a check on a phone beside a crossed-out wi-fi symbol, with racking and pallets behind them. Clouds and a small plane sit in the sky above.

iPhone, Android, any tablet, or just a browser. Including the Windows tablets already on your floor.

One permit, two views

The template knows the procedure.

Your process isn't a list. It has conditions, thresholds, and things that have to happen before other things are allowed to. All of it is set in the template once — what an answer makes appear, what gets raised when something fails, what has to be filled in alongside it, and who it goes to. Nobody in the field decides any of that on the day.

Combustibles cleared within 35 ft?No

The inspector answers honestly.

Permit proceeds normally
No
Combustibles clearedNo
Photo of the areaRequired
What is still presentRequired

The item turns red. A photo and a description become required before the check will move on.

Fire watch assignedNew
Extinguisher within 10 mNew
Fire blanket in placeNew
Post-work watch, 60 minNew

Four items appear that weren't there a second ago — the ones that only matter while combustibles are still present.

Fire watch assignedEmpty
Extinguisher within 10 m
The permit cannot be issued.

Nothing downstream unlocks.

The same permit, from the desk

Numbers you can act on.

That permit came back as Not issued — not as 87%. Because 87% wouldn't have told you the fire watch was missing, and Not issued tells the crew they can't start.

A site board drawn in one terracotta line: a list of percentages on the left, a worker on a ladder hammering, and a second worker celebrating under '100% Completed!'.

Weighted, so the number is honest.

A missing extinguisher tag and an unlabelled spray bottle aren't the same finding. Scored the same, a site with one catastrophic gap comes back at 95% and looks fine.

One critical failure can fail the whole thing.

That's how audits work — one critical finding fails the audit regardless of the other hundred and ninety items. A flat percentage can't say that.

On a schedule

It goes out without you.

You shouldn't have to be the reason the Monday inspection happens. Assigned once, it keeps arriving — at the right site, in front of the right person, on whatever cadence the regulation asks for.

Assign to the role, not the person.

A check assigned to whoever holds the Hot Work Supervisor role at Site B survives someone leaving. One assigned to a single name doesn't.

Anchored to sites, users or machines.

The same monthly inspection across three sites is three separate records. The forklift pre-op belongs to that forklift, with its own history.

Whatever the cadence actually is.

Daily at seven with a two-hour window. Monthly, any time that month. Once, by a due date. Or on demand.

A production line drawn in one terracotta line. A worker loads a jumble of paperwork — question marks, a warning triangle, crossed boxes — onto a conveyor. It runs through a machine, and out the right comes a neat stack of records, while three workers each look at a phone that has just pinged.
Closing the loop

Finding it is the easy part.

An open finding you wrote down and never closed is worse than never having looked. That's the one that gets cited.

Nothing found in the field ends its life as a note in someone's phone.

A corrective action is a whole template, not a text box.

It carries its own items — a photo of the repaired guard, a re-reading, a signature. Proof, not an assertion.

The fix is assigned from inside the check.

By whoever is standing in front of the problem. No admin rights needed; the template already granted the authority.

Both people have the context.

Whoever receives it sees the photo, the reading, the failed item. Whoever found it sees the fix land.

The chain holds.

Every fix links back to the check it came from, the exact item, and who raised it.

A four-panel comic drawn in one coral line. A ladder snapped in two with a phone lighting up beneath it. A hand holding that phone, an exclamation on screen, beside a hard hat. A worker arriving with a replacement ladder on a cart. A person at a desk giving a thumbs up as a notification bell appears.

The same finding block 5 produced — raised, assigned, fixed, and closed back to whoever found it.

Ask anything

You don't pick a report. You ask a question.

There's no menu of twelve reports you'll outgrow in a month. You build the question — what you're measuring, how it's grouped, over what period — and save it.

Five shapes, not five reports. Ask any of them of the whole workspace, or of a single item on a single form. The last two, most tools can't ask at all.

Which single item fails most often, and where?Item level · 90 days
ItemTemplateFailedWhere
Hydraulic leaksForklift Pre-Op9 of 62Yard B
Combustibles cleared, 35 ftHot Work Permit6 of 41Site B
Guard interlock testedMachine Guarding4 of 55Site A
Eyewash flushedEyewash Check2 of 90Site C
Truck 4 accounts for seven of the nine — one item, on one machine, the same pre-op your operator filled in with no signal.

And the ones you'd rather not ask. Who's marking half their items not applicable? Which schedule has quietly stopped being serviced? Nothing gets edited quietly: a submitted record can't be altered, and a correction is its own record.

It comes to you

Save it once. It keeps answering.

Your inbox

On whatever cadence you set — Monday morning, month end, quarter close. One question feeds several schedules, and the answer arrives as a spreadsheet.

Mon 07:00 Repeat offenders — last 90 days .xlsx
1 Oct 06:00 Repeat offenders — Q3 .xlsx
A colleague

They run it themselves, against what they're allowed to see. If they can't see all of it, it tells them — nobody ever gets a smaller number under the same title.

Runs as Site Manager · Site A
Nine sites. Your role can see three. It won't run under this title with the other six missing.
The file itself

Which version produced it, and what changed since. Edit the question and it warns you three schedules are using it.

“Repeat offenders — 90 days” · version 4 · run 24 Aug 07:00
One item deleted 12 Jul — earlier counts aren't comparable.
Pricing

You pay for the work, not for the people.

The person who sees a near-miss first is the one who reports it. Everyone closest to the work has an account, because you pay for the work that gets done — never for the number of people doing it.

Everyone's on it.
Every crew member, every sub, every temp. Unlimited users on every plan, including the free one.
You pay for what gets done.
Submitted work — not headcount, not sites. A quiet month costs less than a busy one. Reading your own records is always free.
Free forever, and not a crippled version.
Every feature, unlimited users, and the same spreadsheet export as a paid plan. Roughly thirty inspections a month — more if yours are short, fewer if they're long.
Free keeps three months.
On the free plan, records and reports are kept for three months — enough to run on, not enough to be your archive. Paid is how you keep years; a 300 log has to survive five of them. Export any time, on either plan.
To start
Nothing to sign, and no card.
Setup
No setup fee, and no implementation package.
To leave
Everything exports, and not just on the way out. Whatever we're holding is yours to take, any time.
Start

One template, one crew, no rollout.

A template of ours, changed to fit, in front of the people who'll run it.

Early access is open — tell us what you run and we'll be in touch.

Free foreverUnlimited usersNo contract

Get early access

Leave your email and we'll be in touch. Tell us what your crew runs and we can come back with something you can start working with.