Out Friday, Back Sunday, Clean by Wednesday: Event Rental Turnaround
Out Friday, Back Sunday, Clean by Wednesday: Event Rental Turnaround
Every event rental operator knows the Monday feeling. The vans are back, the warehouse is full, and none of it is ready. Linens are in bags that smell like a wedding. Glassware is in crates with a few empty slots. Two chairs have bent legs and nobody is sure which job they came off. Meanwhile the phone is ringing with Saturday inquiries, and the honest answer to "do you have 600 ivory linens?" is "we own 600, and I will know how many are usable on Wednesday."
That gap - between what the warehouse holds and what the board can sell - is the whole subject of this guide. Event rental is not a stock business; it is a turnaround business. The same chairs, tables, linens, and glassware go out every weekend, and the money is made or lost in the five days between collection and the next load. This is a follow-up to our event rental software guide, which covered why availability has to be answered by date rather than by count. Here we go one layer down into the weekly cycle itself: cleaning as blocked downtime, counting returns back against the event, attributing breakages, repairs, and sizing stock to the turn rather than to the biggest Saturday of the year.
The Weekly Cycle
Wedding-season event rental runs on a seven-day loop, and every operator's loop looks roughly the same:
- Friday - load out. Vans loaded from the pull list, crew on the road by mid-morning, set-ups through the afternoon.
- Saturday - the event. Everything is out. Nothing is coming back. This is the day availability is truest and least useful.
- Sunday - collection. Strike and collect, often late. Stock arrives back dirty, unsorted, in whatever crates the crew could find at 11pm.
- Monday - count and reconcile. Everything gets counted back against the pull list per event. This is where breakages and shortages are found, and it is the only day they can still be attributed to a client.
- Tuesday and Wednesday - cleaning and repairs. Linens at the laundry, glassware washed and racked, tables and chairs wiped and checked, damaged units pulled for repair.
- Thursday - staging. Next weekend's pull lists picked, crated, and labeled by job.
- Friday - load out again.
Two things about the loop matter for how you run it. First, the days are not interchangeable. Skipping Monday's count does not save a day; it moves the count to Thursday's staging, when the crew finds out they are 40 glasses short for a job that loads tomorrow. Second, the loop is per item type, not per warehouse. Chairs are back on the board Monday afternoon. Linens are back Wednesday at the earliest. Glassware is somewhere between. The board that sells Saturday has to know the difference.
An operator running the loop from memory and a spreadsheet can hold it together at 20 events a month. At 40, the week starts eating itself: Monday's count runs into Tuesday, Wednesday's laundry comes back Thursday, and Friday's load is built from what is on the shelf rather than what was promised. The fix is not a bigger warehouse. It is treating the turnaround as a schedule the software enforces rather than a routine the team remembers.
Cleaning as Blocked Downtime
The single most expensive mistake in event rental is selling stock that is back but not ready. The Ashcroft wedding's 60 ivory linens come back Sunday night. A system that marks them "returned" makes them available Monday morning, and someone quotes them to the Delgado reception on Saturday. On Thursday the laundry calls to say the load will be ready Friday afternoon, after the van has left.
Cleaning has to be a block on the calendar, the same as a booking. When an item type comes back, the system applies a downtime window before it goes back on the board, and the length of that window is set once, per item type, in the item setup:
| Item type | Return process | Downtime block | Back on the board |
|---|---|---|---|
| Linens (tablecloths, napkins, runners) | Bagged, sent to commercial laundry, pressed, folded | 3 days | Wednesday |
| Chair covers and sashes | Laundry, pressed | 2 days | Tuesday |
| Glassware | Washed, polished, racked, recounted | 1 day | Monday evening |
| Crockery and cutlery | Washed, recounted | 1 day | Monday evening |
| Chairs and tables | Wiped, checked for damage | Same day | Monday afternoon |
| Dance floor sections | Cleaned, edges checked, restacked | 1 day | Tuesday |
| Marquee and tent canvas | Dried, cleaned, inspected, rolled | 2 to 4 days depending on weather | Wednesday or later |
The point of the table is not the specific numbers - yours will differ - but that the numbers exist and live in the system rather than in someone's head. Once they do, Monday morning's availability board for Saturday already shows the linens as blocked until Wednesday. A quote for 600 linens on Saturday is answered against 540 (the ones that stayed in), not 600, and the operator can offer 540 plus a sub-hire line instead of promising 600 and hoping the laundry is early.
The gap between the warehouse count and the bookable count is widest on Monday morning, and Monday morning is exactly when next weekend's quotes are being built. That is not a coincidence; it is why turnaround discipline and quote accuracy are the same problem. An operator whose software models the block can quote from a true number on Monday at 9am. One whose software does not will find out on Thursday.
Three rules that keep the block honest:
- The block starts on return, not on collection. If the crew collects Sunday night but does not unload until Monday, the clock starts Monday. Set the return time when the crates are actually checked in.
- Weather extends the block for anything that dries. Wet marquee canvas rolled up for three days grows mold. The block for canvas should be set by the person who unrolls it, not by a default.
- A partial return blocks the whole line until it is counted. If 236 of 240 glasses are back, the line is not "236 available." It is "0 available until counted," because the count is what tells you whether the other four are broken, missing, or in a crate that went back on the wrong van.
Counting Back Against the Event
Every item that goes out on Friday goes out on a pull list for a specific event. Every item that comes back on Sunday should be counted against that same list, per event, before anything is cleaned, restacked, or put back on the shelf. The pull list is the only record of what the client had, and once the crates from three weddings are merged into one pile on the warehouse floor, that record is gone.
The count-back is a single pass with four columns per line: out, back, broken, missing. It produces three outcomes at once:
- A stock adjustment. 240 glasses went out; 236 came back intact; two came back broken; two did not come back. Stock is now 238 (236 plus two repairable, if they are) or 236. Saturday's availability updates from that number, not from the number the warehouse thought it had.
- A damage and loss charge. The two broken and two missing glasses are a line on the Ashcroft invoice, charged against the deposit that was taken to hold the date. Not a phone call three weeks later; a line on Monday.
- A cleaning block. The 236 intact glasses enter the one-day wash block and are back on the board Monday evening.
The count-back only works if it happens per event and before merging. Operators who count "everything that came back this weekend" against "everything that went out this weekend" get a warehouse total that is roughly right and a client attribution that is impossible. Three weddings, four missing glasses, and no way to say whose. The four glasses become a cost of doing business, and so do the twelve next weekend and the twenty after that.
Practical ways to keep the count per event when the crew is unloading at 11pm on Sunday:
- Crates are labeled by job on the way out and stay labeled on the way back. A crate that comes back unlabeled is the first thing that gets counted, not the last.
- The count happens at the dock, before the crate crosses into the warehouse. Once it is on the shelf, it is stock, not a return.
- The pull list is on a phone or tablet at the dock, with the out quantities already filled in. The crew enters back, broken, and missing; the system does the arithmetic and the charge.
- Anything that cannot be counted Sunday night is left in the van or in a marked holding zone and counted first thing Monday. It does not go on the shelf.
Attributing Breakages
A cracked table leg logged against the Ashcroft wedding on Monday is a charge against that deposit. The same cracked table leg found in the warehouse three weeks later is a cost of doing business. The difference is not the damage. It is whether anyone can still say whose event it came off.
Attribution has a very short window - it is open at the count-back and closed the moment the stock is merged - and it is where most event rental businesses leak money without noticing. A mid-size operator running 30 weddings a month through peak season can easily lose $400 to $900 of breakage per weekend across glassware, crockery, linens (wine, candle wax, burn marks), chairs, and tables. Attributed and charged, that is a line item the client signed for when they accepted the deposit terms. Unattributed, it is margin that disappears into the replacement budget.
Making attribution stick needs three things in place before the event, not after:
- The rental agreement names the charges. Per-item replacement and cleaning fees are on the agreement the client signs, with the deposit terms stating that breakage and loss are deducted from it. A charge the client agreed to in advance is collected; a charge they hear about for the first time on Monday is argued.
- Condition is documented at hand-over. A photo of the linens and the glassware crates at delivery, timestamped and stored against the event, closes the "it was already like that" conversation. The crew takes it as part of the set-up checklist, not as a favor.
- The charge is raised from the count-back, in the same step. When the dock count records two broken glasses, the system raises the charge against the event, applies the rate from the agreement, and deducts it from the deposit. Nobody has to remember on Wednesday to go back and bill Monday's breakages.
One distinction worth holding: normal wear is not a breakage. A tablecloth that comes back with the kind of marks a wedding leaves gets cleaned, and cleaning is priced into the hire. A tablecloth that comes back with candle wax burned through it is a replacement. The agreement should draw that line clearly, and the count-back should have a way to record it - "cleaned" versus "charged" - so the client is billed for the second and not the first.
Repairs
Damaged stock is the third state between "out" and "available," and it is the one most spreadsheets do not have a column for. A round table with a bent leg is physically in the warehouse, counted, and clean. It is also not sellable, and if the board does not know that, it goes out on Friday to a client who finds out when the cake goes on it.
Repairs need the same treatment as cleaning: a block on the unit that holds it off the board until the work is logged as done. The difference is that cleaning blocks are predictable and set per item type, while repair blocks are per unit and open-ended. The table might be fixed Tuesday; it might wait for a part until the following week; it might be written off. The system has to hold the unit off the board for as long as the repair is open, and release it only when someone closes the job.
For an event rental operator, a workable repair loop looks like this:
- The count-back flags the unit. Two broken glasses are a write-off and a stock adjustment. A bent table leg, a torn marquee panel, or a chair with a loose back is a repair ticket, raised from the same dock count that raised the charge.
- The unit is physically separated. A repair bay, a marked shelf, a red tag - anything that keeps the unit out of the pick path so Thursday's staging crew does not grab it for a pull list.
- The ticket carries the parts and the cost. What is needed, what it costs, who is doing it. That cost is set against the breakage charge the client paid, so the business can see whether it is actually recovering repair costs or subsidizing them.
- Closing the ticket releases the unit. Not a verbal "it's fixed" - a logged closure that puts the unit back on the board with its next available date.
For serialized items - dance floor sections, generators, marquee frames, specialty furniture - the repair history per unit is also the maintenance history, and it is what tells you when a unit has stopped being worth fixing. EquipDash's maintenance tracking, on the operations features page, keeps a per-unit log of every repair, its cost, and its downtime, and the per-item-type cleaning blocks and repair holds described here are the same mechanism the party rental software page describes for keeping returned stock off the board until it is ready. Bulk items - chairs, linens, glassware - are handled as counts with a repairable and written-off quantity rather than per-unit tickets.
Sizing Stock to the Cycle
The reason the turnaround matters so much to the P&L is that it decides how much stock you need to own. An operator who owns 1,000 linens because the biggest Saturday of the year needs 1,000 is carrying stock that sits idle 45 weekends a year. An operator who owns 600 and turns them every week can serve every Saturday that needs 600 or fewer, sub-hire the two Saturdays that need more, and carry 40% less capital in linens.
That only works if the turn is reliable. Six hundred linens on a three-day laundry block are available every Saturday. Six hundred linens on a five-day block - because the laundry is slow, the count runs late, or the returns come in on Tuesday - are available every second Saturday, and the operator is back to needing 1,000.
The arithmetic for any item type is short:
- Peak weekend demand. The most units committed on the busiest Saturday of the season, from last year's bookings. Say 720 linens.
- Turnaround in days. The realistic block from return to on-the-board, not the best case. Say 3 days for linens.
- Weekend length. How many days the stock is out per event, including load and collection. Say 3 days (Friday to Sunday).
- Stock needed for back-to-back weekends. If the turn plus the out period fits inside seven days, one set covers consecutive weekends and you size to peak demand: 720. If it does not - a 5-day turn plus a 3-day out period is 8 days - you need enough for two weekends in rotation, and the number is closer to peak demand times two, less whatever overlap the calendar allows.
- Sub-hire threshold. Decide which peak weekends are cheaper to sub-hire than to own for. Owning 720 to serve one Saturday a year at 720 rarely beats owning 600 and sub-hiring 120 once.
The operators who get this right are not the ones with the most stock. They are the ones whose Monday count, cleaning blocks, and repair holds are reliable enough that the board on Monday morning is a true statement of what will be clean, counted, and ready by Friday's load. The turnaround is the asset; the linens are just what it turns.
Plans for event rental businesses start at $23/month on annual billing - see pricing for current tiers. For the rest of the operating model - date-based availability, same-day quoting, packages that track components, crew on the same schedule as the gear - go back to the event rental software guide.
FAQ
What is event rental turnaround?
Turnaround is the time between stock coming back from one event and being ready to go out to the next: collection, count-back, cleaning, repairs, and staging. In wedding season it runs as a seven-day loop - out Friday, back Sunday, counted Monday, cleaned and repaired through Wednesday, staged Thursday, out again Friday. Stock that is physically in the warehouse but still inside that loop is not available to sell, and the turnaround is what decides how much stock an operator needs to own.
How long should a linen cleaning schedule block stock for?
Three days is a typical block for tablecloths, napkins, and runners going through a commercial laundry - back Sunday, ready Wednesday. Chair covers and sashes are usually two days, glassware and crockery one day, chairs and tables the same day they are wiped and checked. Marquee canvas can be two to four days depending on whether it came back wet. Set the block per item type in the system so it applies automatically on return and the availability board shows the true ready date.
Why should returns be counted per event instead of per weekend?
Because the pull list per event is the only record of what a client had. Counting each event's crates back against its own pull list - out, back, broken, missing - lets you charge that client's deposit for breakage and loss on Monday, when the terms they signed still apply. Once three events' crates are merged on the warehouse floor, the four missing glasses belong to nobody and become a cost of doing business. Count at the dock, per event, before anything goes on the shelf.
How do you charge clients for breakages in event rental?
Put per-item replacement and cleaning fees on the rental agreement the client signs before the event, with the deposit terms stating that breakage and loss are deducted from it. Document condition at hand-over with timestamped photos stored against the event. Then raise the charge from the count-back on return, in the same step that adjusts stock, so the deduction is on Monday's invoice rather than in a phone call three weeks later. Distinguish normal wear (cleaned, priced into the hire) from damage (charged as a replacement).
How much event rental stock should you own?
Size stock to the turnaround, not to the biggest Saturday of the year. Take peak weekend demand for the item type, the realistic turnaround in days, and the days the stock is out per event. If turnaround plus out period fits inside seven days, one set covers back-to-back weekends and you size to peak demand, then decide which one or two peak weekends are cheaper to sub-hire for than to own for. If the turn is slower than that, you need closer to two sets in rotation - which is why a reliable three-day linen block is worth more than 400 extra linens.
in one place
