An SLA per stage
Each stage carries its own expected hours. A stage running over is visible while there is still time to move work, not at handover.
Home · Lifecycle
The flowEvery order carries its own stage list. Each stage has an owner, a start time, a completion time and an SLA — so a delay is visible on the day it happens, not at delivery.
The client, the garment and the measurements are captured at the counter. This is the only stage where a mistake is cheap — a wrong measurement here becomes an alteration in week four, so it is taken by someone whose job it is.
Owner or MasterThe design is agreed, the costing is set line by line, and the advance is recorded against the order. Nothing is cut before this point, which is what makes a cancellation at this stage cost nothing but time.
Owner or counter staffDesign references and fabric are checked together before anyone commits. The reference is recorded with its source — boutique catalogue, a previous garment, a customer sketch, a Pinterest screenshot — because "the one she showed me on her phone" is not a specification.
Designer or ownerThe longest stage, and the one that hides the most: pattern drafting, cutting, embroidery, then stitching. On embroidered pieces the Maggam run sits in the middle and usually sets the delivery date on its own. Each specialist picks the job off their own queue and marks it done, so the order's position is known without asking anyone.
Pattern, Cutting, Maggam, StitchingThe QC Staff inspects the finished garment against the measurement ledger it was supposed to be made from. A fail here returns the piece to the floor with a reason attached — which, over a few months, tells you which stage actually generates your alterations.
QC StaffPressed, packed and photographed from every angle — front, back, sleeve, dupatta, close-up detail. The balance is settled here. The photographs are held until you publish them, because a half-uploaded gallery is not what you want the customer looking at.
Pressing Staff, ownerCourier and tracking number recorded against the order, or marked for counter pickup. The customer's tracking link updates on its own — no separate message needed to say it has left.
DispatchClosed, with the whole history kept against the client: what was made, who made it, what it cost, how long each stage took, and what the QC found. That record is what makes her second order faster than her first.
Closed"In progress" is not information. The reason each stage names an owner and starts a clock is that delays are almost never spread evenly — they sit in one stage, with one person, for a reason you can usually fix once you can see it.
Each stage carries its own expected hours. A stage running over is visible while there is still time to move work, not at handover.
Who should have done it and who actually did are recorded separately — the gap between them is where your real capacity lives.
Time in stage accumulates automatically. After a season you know what a lehenga really takes, rather than what you tell customers it takes.