Keep one roster per wedding party, with a row for every person showing measurements, order status, pickup date and return date, and calculate every deadline backwards from the event date. AI can draft the reminders (measure now, collect, return, overdue) from those rows; a person approves them, and the sheet or your software decides when each one is due.
The dedicated-software market has shifted under shop owners' feet. BBL Systems' own site says its ProfitSystem products, used by bridal, prom and tuxedo shops for more than two decades, have moved into maintenance mode, so ask the vendor what that means for support and new sign-ups before relying on them. Newer systems exist, and a spreadsheet plus a form does the job for a shop with a modest number of parties in the diary. The same rows move into software later.
One event, many garments, four dates that drive everything
Formalwear hire is not like renting a single tool for a weekend. One event can bring a whole wedding party, half a dozen people or more, each needing a fitted outfit, and every outfit has to be measured, ordered or reserved, collected and returned around a date nobody can move. The unit you track is therefore the party, with one record per person underneath it, and four dates fall out of the event date.
- Measure-by date. The last day a person's measurements or fitting can be accepted. It is set by your supplier lead times, plus time for a remake.
- Order lock. After this date sizes are final and garments are ordered or allocated from stock. Changes after it cost money or risk the event.
- Pickup date. Usually a day or two before the event, with a try-on so that problems surface while there is still time to swap a size.
- Return due date. Usually a day or two after the event, with a short grace period before fees start.
The offsets below are an example, not a standard. Take yours from your supplier lead times and your own habits, and put them in a settings tab so that a change recalculates every party at once.
| Setting (illustrative) | Value | Settings cell |
|---|---|---|
| Grace days after the return due date | 1 | B2 |
| Late fee per outfit per day | $15 | B3 |
| Fee cap (the outfit's replacement cost) | $210 | B4 |
| Measure-by: days before the event | 42 | B5 |
| Order lock: days before the event | 28 | B6 |
| Pickup: days before the event | 2 | B7 |
| Return due: days after the event | 2 | B8 |
| Minimum days between reminders to one person | 3 | B9 |
| Clean-and-press buffer between hires of one item | 2 | B10 |
The party roster: one row per person, dates built backwards
The roster tab has one row per person and one line of dates that are all formulas. Nothing is typed twice: the event date lives on a Parties tab, and each roster row looks it up. These are the columns, with the letters the formulas below rely on.
Roster tab
A Party ID (matches the Parties tab)
B Person (role and name: groom, best man, groomsman...; contact details stay in your customer list)
C Measurements (Not measured / Measured / To verify)
D Order status (Not placed / Placed / Ready / Out / Returned)
E Event date =INDEX(Parties!$B:$B,MATCH($A2,Parties!$A:$A,0))
F Measure-by =E2-Settings!$B$5
G Order lock =E2-Settings!$B$6
H Pickup =E2-Settings!$B$7
I Return due =E2+Settings!$B$8
J Returned on (typed when the outfit comes back)
K Late fee so far =IF(OR(D2="Out",D2="Returned"),MIN(Settings!$B$4,MAX(0,IF(J2="",TODAY(),J2)-I2-Settings!$B$2)*Settings!$B$3),0)
L Last reminder sent (date, typed or pasted)Here is the roster for one illustrative party, seven people, on a day 44 days before the event. The measure-by date is two days away, so the sheet shows exactly who needs a nudge.
| Role | Measurements | How taken | Order status | What the sheet says to do |
|---|---|---|---|---|
| Groom | Measured | In shop | Not placed | Nothing until the order lock, 16 days from now |
| Best man | Measured | In shop | Not placed | Nothing yet |
| Groomsman 1 | Measured | In shop | Not placed | Nothing yet |
| Groomsman 2 | Not measured | None | Not placed | Measure nudge now; deadline in 2 days |
| Groomsman 3 | Not measured | None | Not placed | Measure nudge now |
| Groomsman 4 | To verify | Self-reported on the form | Not placed | Verify at a fitting or by video before the order lock |
| Father of the groom | Not measured | None | Not placed | Measure nudge now; consider a phone call |
Three people need a nudge, one needs a check, and three need nothing. A shop running ten parties at once would find that list nearly impossible to hold in its head and easy to produce from this sheet. Notice too that each person has their own status, because the party is only ready when the slowest member is. The tutorial on ski rental software with sizing forms, bookings and returns covers a close cousin of this problem, with the same pattern of sizes collected in advance and kit returned on a date.
Measurement forms that cut remeasures, and an AI outlier check
Most remakes start with a number typed wrongly or a measurement taken in the wrong place. A form helps in two ways: it asks the same questions every time, and it can reject nonsense before it reaches the roster. Build the form from your suppliers' size charts and no wider.
| Field | Why it is there | Rule to add |
|---|---|---|
| Party ID and role | Links the answer to the right roster row | Drop-down, not free text |
| Height and weight | Used by most size charts as a cross-check | Number between plausible limits |
| Chest, waist, sleeve, inseam, neck | The measurements the supplier chart needs | Number, one unit throughout |
| Shoe size | For hire shoes, where offered | Drop-down of sizes |
| Measured by and date | Shows whether the figures came from staff or the customer | Staff initials, or "self" |
| Consent to text reminders | A written yes before the first message | Yes or no, with an opt-out note |
Self-reported figures are the main source of error, which is why the roster has a "To verify" status. An assistant can also act as a second pair of eyes on a batch of entries, before you place an order. Strip the names, paste the numbers and ask for oddities, with the instruction not to correct anything.
Below are measurements for one wedding party, in inches and pounds. Find any row where a value looks implausible or inconsistent with the others in that row (for example a chest figure far outside the others, a sleeve far short for the height, or a height that looks like a typing slip). Do not correct anything. For each flagged row give: row number, the value, why it looks wrong, and what to ask the person.
role | height | weight | chest | waist | sleeve | inseam | neck
[paste rows]Run on an illustrative batch, a good answer is short.
Row 4 (groomsman 2): chest 83. Far outside the other rows and implausible as a chest measurement; the digits may be swapped (38). Ask: please re-measure your chest.
Row 5 (groomsman 3): sleeve 28 with height 74. Sleeve looks short for this height and for the rest of the party. Ask: please re-measure from the centre back of the neck, over the shoulder, to the wrist bone.
Row 6 (groomsman 4): height 62 with inseam 31. Possibly 6 feet 2 inches entered as 62. Ask: please confirm your height.Those three flags are the sort of error that would otherwise surface at the pickup try-on, two days before the wedding, when a remake is no longer possible. The assistant guesses and you check: it cannot know the real height, only that 62 does not fit with the rest of the row. Treat every flag as a question for the person, never as a correction. Because measurements and contact details are personal data, collect only what the size chart needs, keep the sheet restricted to the staff who use it, and delete records after the season in line with your own retention rule.
Availability: stopping one jacket going to two weddings
If you own stock, you need to know that a given jacket is free for a given pair of dates. If your garments come from a supplier per order, you need an order status per person instead, and the roster already has it. For owned stock, add a Garments tab with one row per booking: item code, pickup date, return date and party ID.
The only subtle part is the clean-and-press time between hires. A jacket returned on the 16th is not ready for pickup until the buffer has passed. The formula below counts existing bookings of the same item that overlap a new request once the buffer is allowed for. A result of zero means free and anything above zero means a clash.
Clash check for a new booking (item code in B2, new pickup in B3, new return in B4):
=COUNTIFS(Garments!$A:$A,B2,Garments!$B:$B,"<"&(B4+Settings!$B$10),Garments!$C:$C,">"&(B3-Settings!$B$10))Test it with dates before you trust it. Take an existing booking with pickup on the 12th and return on the 16th, and a two-day buffer. A new request for the 17th to the 21st clashes, because the jacket is still being cleaned. A request starting on the 18th is free, since the jacket is back and pressed by then. A request from the 8th to the 11th clashes too, because the jacket must be ready for the 12th, while the 8th to the 10th is fine. An assistant can write this formula for you if you describe the rule, and you should run those four test dates against whatever it produces. For the general logic of availability in a hire business, event rental inventory software for tents, tables and chairs covers the same problem at larger scale.
Late-return fees: write the rule once, then calculate it
A late fee is easy to charge and hard to collect if the customer first hears of it afterwards. Formalwear retailers commonly publish late-return charges in their rental FAQs, so customers expect to see them stated in advance. Decide the rule once, write it on the booking confirmation and in the settings tab, and let the sheet apply it.
The example policy used here is a fee of $15 per outfit per day after one day of grace, capped at the outfit's replacement cost of $210. Column K in the roster already holds the formula. Here is what it gives for an outfit due back on a Monday.
| Returned | Days after due date | Billable days | Fee |
|---|---|---|---|
| On the due date | 0 | 0 | $0 |
| The next day | 1 | 0 | $0 (grace) |
| Friday | 4 | 3 | $45 |
| Twelve days late | 12 | 11 | $165 |
| Twenty days late | 20 | 19 | $210 (capped; $285 uncapped) |
The sheet only shows what the policy produces. Whether to charge it is your decision: a long-standing customer returning a jacket a day after the wedding party flew home is a different case from an outfit that has not been seen for three weeks. Keep the human decision and let the assistant help with wording once you have made it. The tutorial on chasing late payments with AI reminders that sound human has wording patterns that carry over from invoices to fees. Have the fee clause in your terms read by a qualified adviser, since whether a fee is enforceable can depend on how and when it was disclosed.
At the counter: the pickup try-on and the return check-in
Reminders get people to the counter, and what happens there decides whether the dates mean anything. Pickup is the last chance to change a size, and the return is the moment the fee clock stops, so each deserves a fixed routine short enough to run with a queue behind the customer.
At pickup, open the party's roster row and take each person through the same short list. The order status says Ready, the balance is settled, and every piece is tried on and checked against the roster measurements: shoulders, sleeve length, trouser waist and length, shirt neck. Note any alteration and decide on the spot whether it is done today or needs a swap. Count the pieces and any accessories aloud, agree the return time, repeat the late-fee rule from the confirmation, then change the status to Out and record the pickup.
At return, count the pieces against the roster, check for stains or damage, and photograph anything doubtful before the garment goes anywhere else. Then enter the returned-on date straight away, because that entry stops the fee formula in column K. Send the pieces for cleaning and pressing, which the availability tab already keeps blocked for the buffer days.
The realistic slip here is a forgotten date. A staff member takes a jacket back in the rush before closing and never types the return, so the sheet keeps counting days and the overdue filter proposes a fee notice for an outfit that is already hanging on the rack. Two habits prevent it. The return check-in is the only place where the status changes to Returned, and a person reads every name on the overdue list before anything is sent. The checks catch what the formula cannot know, which is that the garment is already back.
The reminder sequence: seven messages, and which ones AI should draft
A reminder is cheap compared with a late return or a remake, and the wording is the same every time, which makes it ideal for an assistant. The sequence below follows the four dates. The "when" column is the rule the sheet tests, and the "AI drafts" column says what the assistant is allowed to produce.
| # | When | Purpose | Channel | AI drafts? |
|---|---|---|---|---|
| 1 | On booking | Confirm roles, the four dates and the fee rule | Yes, from your template and policy lines | |
| 2 | 7 days before the measure-by date | Ask anyone unmeasured to book a fitting or use the form | Text and email | Yes |
| 3 | On the measure-by date | Last call; explain what happens after it | Text, then a phone call | Text yes; the call is a person |
| 4 | 3 days before pickup | Outfit ready, collection window, balance due | Text and email | Yes |
| 5 | The day before the return is due | Return time and the late-fee rule | Text | Yes |
| 6 | After the grace period | Overdue notice with the fee so far | Text and email | Yes, with the fee copied from the sheet |
| 7 | 4 days after the due date | Final notice before a replacement charge is discussed | Email, then a call | The email only; the decision is yours |
Give the assistant your policy lines and two or three real messages you have sent in your own voice, then ask for the five text messages. The prompt matters more than the model, and the most important sentence in it is the one about fees.
Write five text messages for a formalwear hire shop, one for each of these triggers: measure nudge, final measurement call, pickup ready, return reminder tomorrow, overdue notice. Rules:
- Each message under 140 characters including placeholders, straight apostrophes only, no emoji.
- Use placeholders in square brackets: [first name], [groom], [shop], [day], [date], [time], [link], [fee], [fee so far].
- Mention a fee only if it is in the policy lines below, and copy the numbers exactly.
- Tone: friendly and brisk, like the sample messages.
POLICY: Late fee $[fee] per outfit per day after [grace] day of grace.
SAMPLE MESSAGES: [paste two or three of yours]A usable set looks like this. Each draft is under 140 characters with its placeholders, which leaves room for a shop name and a short link.
Measure nudge:
Hi [first name], [shop] here. We still need your measurements for [groom]'s wedding. Book a fitting or use this form: [link]. Due [date].
Final measurement call:
Hi [first name], your measurements are due today so your outfit arrives in time. Book a fitting or send them here: [link]
Pickup ready:
Hi [first name], your outfit is ready. Collect it [day], [time] to [time], at [shop]. Reply here if that time doesn't suit.
Return reminder:
Hi [first name], please return your outfit to [shop] by [time] tomorrow. Late returns cost $[fee] a day after [date]. Thank you!
Overdue notice:
Hi [first name], your outfit was due back [date]. Late fees so far: $[fee so far], rising $[fee] a day. Please return it today or call us.Two limits are worth knowing before you automate any of this. First, text providers split anything longer than 160 characters into several billed segments, and a single emoji or curly apostrophe can lower that limit to 70 characters, according to Twilio's guidance, so use straight apostrophes and keep the messages short. Second, a first draft sometimes adds a promise you never made. A typical slip is "no charge if you return it within a week", which invents a grace period, or "free alterations if it doesn't fit", which invents a service. Strike any sentence that is not in your policy lines. Send texts only to people who agreed to them, include a way to opt out and keep the content about their booking. The tutorial on reducing no-shows with AI reminders and automatic rebooking covers channel choice and timing in more depth.
Who gets a reminder today: filters that survive a missed day
The weak design is a rule such as "send on exactly 42 days before the event". Miss a day and the reminder is never sent. A stronger design is to describe the state and the window: anyone still unmeasured with a deadline inside seven days, anyone with an outfit out and a return due within a day, anyone overdue. These lists stay on the screen until the state changes. The "last reminder sent" column and the minimum gap in the settings stop the same person being nudged every day.
Measure nudges (unmeasured, deadline within 7 days, not nudged in the last 3 days):
=FILTER(Roster!A2:B200,(Roster!C2:C200="Not measured")*(Roster!F2:F200-TODAY()<=7)*(TODAY()-Roster!L2:L200>=Settings!B9),"None today")
Pickup reminders (order ready, pickup within 3 days):
=FILTER(Roster!A2:B200,(Roster!D2:D200="Ready")*(Roster!H2:H200-TODAY()<=3)*(Roster!H2:H200>=TODAY()),"None today")
Return reminders (outfit out, due today or tomorrow):
=FILTER(Roster!A2:B200,(Roster!D2:D200="Out")*(Roster!I2:I200-TODAY()>=0)*(Roster!I2:I200-TODAY()<=1),"None today")
Overdue (outfit out, past the grace period):
=FILTER(Roster!A2:B200,(Roster!D2:D200="Out")*(TODAY()-Roster!I2:I200>Settings!B2),"None today")FILTER works in current Excel and in Google Sheets. In an older version of Excel, filter the roster by the status column instead and sort by the date. Each morning someone opens the tab, sends the drafted message for each name listed, and types today's date in the last-reminder column. Messages are drafted by the assistant and reviewed by that person, which keeps both the speed and the accountability. If you later automate sending, put a simple approval step in front of anything that mentions a fee.
Spreadsheet, form and AI, or dedicated formalwear software
A sheet, a form and an assistant suit a shop whose parties are few enough that one person can follow them. They begin to strain when you own a lot of stock, several staff update the same roster, or you want try-on appointments, payments and inventory in one place. Dedicated systems exist for exactly that, and the picture, as of October 2026, is below. Prices and features change, so check each vendor's page before deciding.
| Option | What its own site says | What to check |
|---|---|---|
| Sheet, form and AI assistant | Nothing to buy beyond an assistant plan; you build the rules in this tutorial | Whether one person can keep the roster current for every party at once |
| SleekSync POS | Describes itself as a browser-based, rental-first system for formalwear shops covering measurements, party members, payments, pickups and returns; its pricing page listed Starter at $99 a month, Pro at $199 and Multi-Store at $299 when checked, with two months free on annual billing and a 4-day free trial | Confirm current prices and plan limits; ask about vendor size, support and data export, and test its measurement and AI features during the trial |
| BridalLive rentals | Rental orders, inventory reservations, pickups, laundry and returns for owned rental stock, with each item tracked by serial number | No price on the rentals page; ask which plan includes rentals and for a quote |
| BBL Systems ProfitSystem | Moved into maintenance mode, according to the vendor's home page | If you already run it, ask what maintenance mode covers (fixes, support and for how long) and plan a migration, starting with a full data export |
That last row is a useful warning about any vendor. A product you build a shop around can be put into maintenance mode, and your data has to leave in a usable form. A demo is the moment to test five things: whether an item can be blocked by date with a prep buffer; whether the party roster shows each person's status and roles; whether measurements are stored as fields with a history; whether the reminders can be edited in your own wording, with consent recorded; and whether you can export everything, including customers and measurements, as a file you can open yourself.
Whichever route you choose, the rules in this tutorial transfer. The offsets, the late-fee policy and the reminder wording are yours, not the software's, and an export from a system can be pasted into the same prompts. If the bridal side of the shop is where more of the work sits, can AI run bridal shop appointments? replies, fittings and limits covers fittings from the other direction. And if a suit is being altered rather than hired, AI for tailors: one wedding-suit job from quote to final fitting shows the equivalent sequence for a made-to-measure job.
Questions formalwear hire shops ask about reminders and tracking
How far ahead should the wedding party be measured?
Set the deadline from your suppliers' lead times, then add a buffer for remakes and for party members who live far away. The example here uses six weeks before the event, but yours may differ. Put the number in one settings cell so every roster date recalculates, and tell customers the deadline when they book.
Should reminders go by text or email?
Use both for the two that matter most, the measure-by date and pickup. Use text for short day-before nudges, and email for anything with detail or fees. Ask for consent to send texts at booking, include a way to opt out, and keep every message about the booking itself.
Can AI decide whether to waive a late fee?
It should not. A waiver is a decision about money and a customer relationship. Let your sheet show the fee your policy produces, then decide yourself. Once you have decided, the assistant can draft either the fee notice or the waiver message in your voice, without changing any amount.
What should a measurement form collect?
Whatever your suppliers' size charts need, usually height, weight, chest, waist, sleeve, inseam, neck and shoe size, plus the party and event date. Record who took each measurement and when, ask for one unit throughout, and collect nothing you will not use, because measurements are personal data.
Further reads
- Party Rental Booking Software: Quote and Availability Tools With AI — Compare availability and quote tools built for party hire
- Party Rental Contract: Damage, Weather and Deposit Terms With AI — Draft damage and deposit terms that sit behind a late fee
- Bridal Shop Marketing: Appointment Slots and Real-Bride Posts With AI — Fill fitting appointments with bridal-shop marketing ideas
- How Wedding Suppliers Can Reply to Enquiries in Minutes With AI — Reply to wedding enquiries in minutes with AI drafts
- Music Store POS System: Serial Numbers, Rentals, Repairs and AI — Another shop tracking serial-numbered rentals alongside sales
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: SleekSync POS pricing and product pages, BridalLive's rentals page and help centre, and BBL Systems' home page on ProfitSystem (all checked October 2026); Twilio's guidance on SMS segment length. Rosters, fees and sample messages are invented for illustration.