Readiness gates vs. checklists - enforced rules vs. remembered process
A checklist or written SOP is a description of a process. A readiness gate is an enforcement of it: a rule-based checkpoint the vehicle cannot pass until every SLA item is verified on the record - inspection complete, condition report captured, keys accounted for, target state of charge reached. The practical difference is what happens when someone is busy. A checklist degrades quietly across shifts, yards, and new hires. A gate does not degrade, because the unit simply does not advance. Releases rarely stall because the work was not done; they stall because nobody can prove it was.
| Checklists | Parq.ai | |
|---|---|---|
| Nature | A description of the process | An enforcement of the process |
| Lives in | A binder, a wiki, or someone's memory | Rules attached to the VIN |
| Consistency across yards | Varies by site and shift | Identical everywhere by construction |
| What happens if a step is skipped | Discovered later, if at all | The unit cannot advance |
| Evidence produced | A signature, at best | Timestamped photos, timers, and sign-offs |
| Configurable per client or program | In theory | Yes, without a software release |
| Surfaces blocked units | Someone has to notice | Exception queue, the moment it blocks |
| Survives staff turnover | No | Yes |
| Defensible in a damage dispute | Weakly | Yes - full chain of custody on the record |
Where the line actually falls
A checklist describes a process. A readiness gate enforces one. That is the entire difference, and it only becomes visible under load.
With a written SOP, compliance is a function of attention. On a normal shift with an experienced crew, a checklist works fine - which is why the failure is so easy to miss. It degrades quietly: at volume, on a short-staffed Saturday, with a new hire, at a site that runs a slightly different variant because that is how the previous site lead did it. Nobody decides to skip a step. Steps get skipped anyway, and the skipping is invisible until a client disputes damage and the photos that would have settled it were never taken.
A scenario, because this is where it gets concrete
The check-in sheet for a unit is signed and complete. Every box ticked.
What the signature does not establish: whether the condition report photos were actually captured or the box was ticked from memory at the end of a shift, whether the EV was charged to the program's target state of charge or to whatever it happened to reach, whether the tech who signed was the tech who looked, and whether the vendor invoice attached to that work order matches work that was done. A signed checklist is a claim. A gate is a proof - the unit cannot advance to the next phase until each SLA item exists as a record: photo captured, timestamp present, SOC verified against the program target, signature bound to a named user.
The practical consequence is that a gate turns "we follow our SOP" into something you can hand to a client. When damage is disputed sixty days later, the difference between a ticked box and forty-eight timestamped photos is the difference between eating the cost and not.
Why this changes at multi-site scale
One site with one shift lead can run on a checklist and a strong culture. Six sites cannot, because a checklist has no mechanism for consistency - each site drifts toward its own interpretation, and you find out at audit. Gates are configured centrally per client, program, or market and applied identically everywhere, so the SOP is the same object at every hub rather than the same document interpreted at every hub. When a client changes a requirement, you change the gate, not twelve laminated sheets.
It also changes what a bad shift costs. A missed checklist step produces a problem discovered later, usually by the client. A failed gate produces an exception in a queue, discovered immediately, with an owner attached.
Where a checklist is the better answer
Gates are worth the configuration effort where the process is repeated, the evidence has commercial value, and more than one party relies on the result. For genuinely low-stakes or one-off procedures, a checklist is lighter and entirely appropriate - encoding everything as an enforced gate creates friction with no payoff. The test is simple: if failing to follow the step could cost you money or a client relationship, and you would want proof it was followed, it belongs in a gate. If not, leave it on paper.
Questions people actually ask
A readiness gate is a rule-based checkpoint a vehicle must clear before it can advance to the next phase. The gate verifies every SLA item, including inspection completion, condition report capture, and target EV state of charge, and blocks release until each item is proven.
Yes. Gates, SLA items, cost rules, and escalation paths are configured per client, program, or market without a software release.
IMS plans self-onboard using your existing SOP and data sources. Full Suite customers go live with a dedicated onboarding specialist who sets the timeline against your sites and programs.
Terms used on this page are defined in the fleet operations glossary, including readiness gate, dwell time, chain of custody, and cost-per-vehicle-per-day.
Thirty minutes, screen-shared. We walk a vehicle through every gate with the proof attached at each step - no slideware.