The hem was agreed; now it needs confirmation again
A customer returns with different shoes and asks for the dress to be “a little shorter”. The previous record contains an agreed hem marking. Do you delete that note, keep the alteration or treat the change as approved? In this guide’s exercise, the professional explicitly puts the hem on hold pending another fitting. The earlier note remains in the history; no new length is authorised.
We propose testing a text assistant on comparing notes between clothing fittings. Its draft should distinguish the earlier agreement, the instruction now on hold and the new request. You will find a fictional case, a manually prepared answer key and an instruction to try. We are not reporting a completed AI test or promising an outcome.
One record per garment, one note per fitting
In an alterations workshop, “the sleeves too” needs a garment and confirmation. Having a jacket in the same order is insufficient. For this pilot, we suggest identifying each piece, numbering fitting notes and preserving the original wording before summarising it.
Taller Cleo describes a second fitting where the alteration requires one. Modista Moda explains that assessment depends on the garment and that the intended footwear is part of checking its length. These are descriptions from those workshops, not universal turnaround rules or AI results. Our record adds an administrative change history; the professional still assesses and marks each alteration.
- Garment: a stable code, type and enough description to distinguish it; avoid just “the dress” if there are two.
- Fitting: an identifier, the sequence of notes and the person responsible for reviewing them. Keep previous versions.
- Change: the affected area, the literal request and its supporting note. Do not derive centimetres from “shorter”.
- Confirmation: distinguish a request, a recorded agreement, an instruction on hold and completed work. None automatically establishes the others.
Fictional case: a dress, a jacket and an ambiguous message
All these notes are invented. P1, first fitting: “V-01, navy dress. Professional and customer agree hem marking A.” P2, same order: “J-02, cream jacket. Agreed to leave the sleeves unchanged.” P3, second fitting: “V-01. The customer brings different footwear and requests a shorter hem. The professional states: do not carry out marking A; another fitting with the final footwear is pending. No new marking has been agreed.” P4, later message: “The sleeves too, please.” It identifies no garment and provides no workshop confirmation.
Before asking the assistant, write down what needs clarification. This table is our human answer key, not observed model output. A identifies a fictional marking; it is not a measurement or cutting instruction.
| Piece or message | What to preserve | What remains open |
|---|---|---|
| V-01 · hem · P1 and P3 | P1 stays in the history; P3 puts execution of A on hold | Another fitting and a confirmed new marking; no new length agreed |
| J-02 · sleeves · P2 | Leave sleeves unchanged as recorded in P2 | P4 does not establish a new alteration to this garment |
| P4 · “The sleeves too” | A request without an identified garment | Ask which piece and what change; then assess and confirm |
Ask for a comparison without delegating tailoring decisions
Copy this instruction and add all four fictional notes: “Compare P1–P4 in their sequence. Prepare an administrative draft showing garment, area, previous agreement, requested change, instruction explicitly put on hold, open question and source note. Preserve the history. Link every statement to a passage in the notes. Do not assign an ambiguous message to a garment because they appear near each other. Do not invent measurements, markings, feasibility, prices, dates or approvals. Do not mark work completed or garments ready. If unrecorded, write not recorded. Notes: [paste P1–P4].”
Save the first response and compare it with AR-01. The dress has no newly authorised hem, and A must not appear as the current instruction to carry out: P3 explicitly says to wait. The jacket sleeves retain the instruction recorded in P2; P4 stays unassigned. Check the quotations as well: a correct note identifier can accompany a wrong interpretation.
Anthropic’s documentation on incorrect responses recommends allowing uncertainty and checking support for statements. It does not establish that this exercise works in a workshop. The assistant’s usefulness here is a hypothesis to assess; its draft replaces neither the garment fitting nor agreement between the parties.
What changes when a new confirmation arrives?
For a second fictional round, add P5: “V-01. New fitting completed with the final footwear. Professional and customer confirm marking B, replacing A for the hem. The alteration has not yet been carried out.” P5 supports recording B as the confirmed marking in this exercise, keeping A in the history and closing that confirmation question. It does not support marking the work completed.
Do not turn this example into a rule that “the latest message always wins”. A later question does not automatically cancel an agreement. P3 explicitly says to wait, and P5 records a confirmed replacement. If your actual notes do not establish who confirmed what, ask before changing the record. Technical decisions, measurements and acceptance remain with the responsible people.
Test cases that could contradict the summary
Prepare the answer keys for AR-01 and the round with P5 by hand. Add two more fictional cases: two similar dresses with different codes, and a note saying “same as the previous fitting” without a reference. For each, preserve the input, first response, corrections and the entire preparation and review time.
Count confused garments, reactivated old instructions, requests turned into agreements and work marked completed without support separately. Before testing, agree that any such error requires correction and another review of the record. Compare against preparing the record manually to decide whether to continue, change the format or abandon the trial. Assume no time savings or accuracy.
Start with invented notes, without real names, contact details, fitting photographs or people’s measurements. Do not enter personal or commercial information without authorisation and suitable conditions for use, access and retention. This exercise needs neither body photographs nor conversation recordings.
A manual record, workshop software or a scoped integration
For the manual test, you copy fictional notes into an authorised tool and check its response. There is no connection to workshop software or automatic change. If a manual record solves the problem, you can keep it. Before commissioning software, also check what your current tool supports.
GTG Arreglos describes garment management and notes per piece; SuitTracker documents individual garment instructions and statuses within an order. That information helps compare organisational options. We have not verified their operation, their suitability for your workshop or an Adaris connection to either program.
If the pilot justifies considering integration, an initial scope could be limited to reading an authorised notes export and preparing a comparison awaiting review. The existence of that export would need checking, with permissions, versions, recovery and acceptance criteria agreed. Automatic measurement changes, message sending, invoicing and releasing work would remain outside this scope.
Adaris considers custom software, CRM and automation with AI case by case. A record of changes between fittings would be a proposal requiring assessment and a quote, not an available proprietary tailoring program. Commercial communication is in Spanish.
Related services
Sources
Do agreements change between fittings?
Tell us in Spanish how you record fittings and who confirms each change. With fictional notes, we can assess a scoped record or integration, with scope and quote to be agreed.