Cavor Desk — first module ready · for technical maintenance and service companies
PlatformModulesSecurityWhy CAVORStoriesContact
← Back to list
// Case #01

The strip that covered five days of work

Estimated Leak Cost
~4,800 PLN · 3 people × 5 days × 8 h × 40 PLN/h (example)

01Situation

Subfloor finishing for linoleum flooring on a large project in Scandinavia. Three-person crew, supervision: overall project manager plus flooring contractor. Standard job, clear scope — theoretically. Days 1–3: crew lays wood-based panels, assuming a reasonable joint tolerance of ~4 mm. Nobody specified on entry that for this material the tolerance must be a maximum of 2 mm. The requirement existed — it didn't trickle down before anyone touched the material. Three days of three people's work goes to rework. Days 4–5: second attempt — precise, under correct joints so the flooring lies without grooves. Heavy, precise work. After the fact: PM together with flooring contractor decide that in these places a metal strip will run along the entire length anyway. The strip covers exactly what the crew struggled with for the last two days. The decision invalidating the work is made after it's done, not before.
StageWorkStatus after Decision
Days 1–33 people × 3 days layingrework (tolerance not specified at entry)
Days 4–53 people × 2 days precise workcovered by strip — redundant work

02Where Margin Escaped

Not in material. Not in crew skills. In information that arrived too late. Up to ~15 man-days burdened by coordination error, not execution — borne by the contractor, generated higher up.

03Root Cause

Both losses have the same source: decision made after the work instead of before. The 2 mm tolerance existed as a requirement — it wasn't communicated before the first panel. The strip was a sensible solution — decided two days too late.

!How the Loop Closes It

Task does not move to execution without complete specs — tolerance is a required field, not a verbal 'I think it was in the project'. Design change enters the system with date and time, collided with work status: the system shows the cost of a late decision before it's made. The strip gets locked in on day 3, not after day 5.
See the modules that close this loop