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 checkpoint the vehicle cannot pass until every SLA item is verified on the record, including inspection, condition report, keys, and target state of charge. The difference shows when someone is busy. A checklist degrades quietly across shifts, yards, and new hires. A gate does not, 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 | |
|---|---|---|
| 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 depends on attention. On a normal shift with an experienced crew, a checklist works, which is why the failure is easy to miss. It degrades at volume, on a short-staffed Saturday, with a new hire, or at a site running a variant the last lead taught. Nobody decides to skip a step. Steps get skipped anyway, and it stays invisible until a client disputes damage and the photos that would settle 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.
A signature does not establish whether the photos were captured or the box was ticked from memory at shift end, whether the EV reached the program's target charge or just whatever it hit, whether the tech who signed was the tech who looked, or whether the vendor invoice matches the work done. A signed checklist is a claim. A gate is a proof. The unit cannot advance through the vehicle lifecycle until each SLA item exists as a record: photo captured, timestamp present, charge verified against target, and 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 one object at every site, not one document interpreted at each. 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 setup where the process repeats, the evidence has commercial value, and more than one party relies on the result. For low-stakes or one-off procedures, a checklist is lighter and appropriate. Gating everything adds friction with no payoff. The test: if skipping the step could cost you money or a client, and you would want proof it was followed, it belongs in a gate. If not, leave it on paper.
Frequently asked questions
A readiness gate is a rule-based checkpoint a vehicle must clear before it can advance through the vehicle lifecycle. 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 take one of your vehicles through every gate in the live product.