How it works
Plan. Do. Study. Act.
That’s the loop W. Edwards Deming taught Toyota and half of postwar manufacturing. It’s also what centerleap runs in the background of your shop — quietly, on every job your crew finishes.
You don’t fill out forms. You don’t run meetings. The platform watches what actually happens. When it spots a pattern, it suggests the fix. You approve or you ignore.
P · Plan
You name what the job should look like.
How centerleap does it · Job templates
Every recurring kind of work has a template — kitchen sink slow drain, AC tune-up, residential rewire, weekly route cleaning. The template knows the steps, the parts, the time budget, and the customer-facing ETA. You don’t write the template in some separate tool; the platform builds it from the work you’re already doing.
What that feels like in the shop
Day one, your templates look like a list of the jobs your shop ran last month. By day thirty, each one carries the lessons your crew learned along the way.
D · Do
Your crew does the work.
How centerleap does it · The job record
When the tech taps on the way, the customer gets a real ETA from live traffic data. When the tech taps arrived, the clock starts. Notes, photos, parts used, time intervals — all append to the job’s record as it happens. Nothing to fill in after the fact.
What that feels like in the shop
The tech’s phone is the only thing they touch. You see the truck on the map, the job timer running, and the customer’s confirmation that the SMS landed. The dispatcher is a coordinator now, not a phone-tag operator.
S · Study
The system reads what actually happened.
How centerleap does it · The outcome, distinct from status
Every job closes with two fields. Status is whether the work is finished. Outcome is whether it went the way you planned. Most jobs close done · completed cleanly. The interesting ones are done · completed with issues, done · customer not home, done · parts on order. Those are the rows that teach.
What that feels like in the shop
centerleap looks at the outcome field across hundreds of jobs and finds the patterns you’d need a full-time analyst to find by hand. Three of the last twelve drain calls hit the same rusted access panel? You’ll know on Wednesday.
A · Act
One tap to change the next job.
How centerleap does it · Suggestions you approve
When the system spots a pattern, it proposes an edit to the affected template. Add “bring impact driver” to the kitchen-sink slow-drain checklist.You approve, you ignore, or you write back “not quite — try this instead.” Either way, the next time that job runs, your crew has the right setup.
What that feels like in the shop
You stay in the seat. The platform never edits a template without your say-so. Most owners say yes to about a third of the suggestions. The rest gets filtered out as noise — which is also useful, because the system learns what your shop considers signal.
The lineage
We didn’t invent this. We just put it on your phone.
The Plan-Do-Study-Act cycle came from Walter Shewhart at Bell Labs in the 1930s. W. Edwards Deming carried it to Japan after the war. Toyota built a manufacturing empire on it. Healthcare systems use it. Software teams call it “continuous integration” and stop one step short.
The reason most field-service shops don’t run it: the paperwork. Capturing what actually happened on every job, then sitting down once a month to find patterns, is a job nobody has time for. So the cycle gets skipped and the same problems show up next week.
centerleap closes that gap. The capture happens in the iOS app as your crew works. The pattern-finding happens server-side, on a schedule. The act-on-it suggestion lands in your inbox with one tap to accept. The loop runs whether or not you remember to run it.