Checking records against the rules before sign-off is a job for software.
Inspection, maintenance and quality records, checked against the rules your team already writes down. Software checks every record; your people see only the ones that need a decision.
If sign-off means reading every sheet…
You read the inspection sheet, check the reading is inside its limit, check someone signed it, and file it.
Most sheets are fine. The one that is not is the one that matters.
A reading outside its limit, a missing signature, a task overdue: these are written rules, and software can check every record against them. Your people decide what to do about the ones it finds.
See what reaches your people.
Five of twenty invented inspection records, checked against house rules. Clear records pass; a person gets the ones that break a rule, with the reason.
Records
| Asset | Category | Due | Signed off | Check |
|---|---|---|---|---|
| AF-0101 | Point machine | Due in 11 days | L-02 | Cleared |
| AF-0102 | Point machine | 18 days overdue | L-02 | Exception · R1 |
| AF-0103 | Signal relay cabinet | Due in 17 days | Not recorded | Exception · R2 |
| AF-0104 | Track circuit | Due in 4 days | L-02 | Cleared |
| AF-0105 | Level crossing barrier | Due in 3 days | L-02 | Exception · R4 |
Sent to your team
Rail and power inspection records here are invented illustrations, not customers.
What the 30 days look like.
A Proof shows you on your own data: one workflow, run for 30 days beside your current process, for a fixed price. Nothing you run today is switched off.
Pick the workflow.
We scope one workflow with you and agree in writing, on day 5, what it has to get right for you to keep it.
Test it on your own data.
Up to three candidate AI models and one leading hosted model do the same checking on your past inspection and maintenance records, on your systems, which we can read but never change. Limits, dates and sign-offs are rules; a model is only used for things like free-text notes. If a simple rule does the job, we'll use a rule.
Take the evidence to your leadership.
You get a working workflow, a comparison you can rerun, and a pack showing how it meets the rules in one country or region.
You keep what we built either way.
The data, the rules, the tests and the documents stay yours. The exact terms are at the bottom of this page.
Straight answers.
- "Our inspections are on paper. Where do you start?"
- With what is already captured: registers, spreadsheets, scanned sheets. In a Proof we read those and never change them. If the records exist only on paper, the first job is getting them into a form software can read, and we'll tell you on the first call whether that fits in 30 days.
- "We don't want AI. Just automate this."
- We'll take that brief. If a simple rule does the job, we'll use a rule and tell you so. Checking a reading against its limit is a rule. A model only reads what rules cannot, such as a written note, and your team reviews what it flags.
- "Will my inspectors and planners push back?"
- They stay the ones who decide. They stop re-checking the clean records and get only the exceptions, each with the rule it broke. They switch when they trust it, and the old way keeps running until they choose otherwise.
- "Does it change our maintenance system?"
- No. In a Proof it reads your records and never changes them. Every exception goes to a named person, and the record shows who decided.
Bring us the records you check by hand.
A 30-minute call and six questions. You get green, amber or red, and if it's red we say so and tell you why.
From $30K, fixed scope. Live in 30 days, or you don't pay the balance. 30% at kickoff, 70% only if the bar we agree on day 5 is hit. Terms are set out in each statement of work. You own the data, the rules, the tests and the documents; nothing is locked to us. Exact terms