When a Return Customer's Measurements Are Nowhere to Be Found
The customer calls on a Wednesday afternoon. She wants an Ankara jumpsuit for a weekend event. She was in the shop eight months ago for a skirt and blouse, and she wants the same fit. You pull out the notebook. The entry from eight months ago is there, somewhere, written in a different pen, partially illegible because someone rested a cup on the page. The hip measurement reads either 40 or 46 — you can't be certain. You call her back to come in for a remeasure, and she's annoyed, because she thought the whole point of going to the same tailor twice was that you had her measurements.
That lost ten minutes — the apology, the remeasure, the rescheduled pickup — is the cost of not having structured records. At thirty customers a month, the accumulated friction is significant. At a hundred active customers across a full year, the notebook system is completely unmanageable.
What the Measurement Sections Actually Cover
The template is organized by garment type, not by measurement point. That's the right architecture for a Nigerian fashion tailoring business, because a customer who orders an Agbada, a Senator wear set, and a plain shirt in the same month needs measurements tracked per style — and the measurements diverge in ways that matter.
For Senator wear, the critical cascade is Chest through Trouser tip: Chest, Top Shoulder, Neck, Top Length (primary and alternate), Sleeve Length for both long and short, round sleeve circumference, then the full trouser dimension sequence — Hip, Waist, Length, Half Length, Laps, Kneel, and Down. The distinction between Top Length and Top Length 2 matters because many Senator style tops have a facing or split hemline that requires a secondary length reference. A customer who specifies a back-longer-than-front finish needs both numbers in the record.
The Agbada section sits separately with just two fields: Full Length and Agbada Sleeve. That's correct — Agbada construction starts from the full drop length, and the sleeve on an Agbada robe is measured differently than a fitted top sleeve. The fields don't need to be elaborate. They need to be accurate and separate from the Senator measurements so the cutter is never pulling the wrong reference.
Skirt and Blouse has the highest field count, reflecting the actual complexity of fitting that garment category. Burst, Shoulder, Blouse Length, Blouse Waist, and Sleeve establish the top; Hip, Waist, Length, Half Length, Skirt Band, and Blouse Band close out the bottom. The Burst-Burst and Shoulder-Burst measurements capture the cup spacing and shoulder slope variables that determine whether a blouse pulls across the chest or sits correctly. These are the measurements that amateur tailors skip and experienced ones never do.
The Long Customer File and What It Tells You at 100 Entries
At 100 customer records, the measurement database is a complete intelligence layer on your active clientele. Filtering female customers by Gown Length field values — specifically customers who order full-length gowns versus mid-length — tells you fabric requirement patterns before you make purchasing decisions at the market. Customers with Jumpsuit Laps measurements above 24 inches need wider trouser blocks, which affects cutting efficiency on fabric.
The CAP section — just Head circumference for cap size — exists because Senator wear often includes a matching cap, and a cap that doesn't fit the customer's head size is a rework. One measurement, entered once, prevents that problem indefinitely.
The Last Updated date field tracks when the record was last refreshed. Bodies change. A customer who was last measured eighteen months ago and has explicitly mentioned weight change gets a remeasure before cutting — not because you're guessing, but because the field tells you the data is stale.