Out Friday, Back Sunday, Clean by Wednesday: Event Rental Turnaround

Out Friday, Back Sunday, Clean by Wednesday: Event Rental Turnaround

It's Monday morning. The vans came in late Sunday night, 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, and two chairs have bent legs that nobody can match to a job.

The phone is already ringing about next weekend. The honest answer to "do you have 600 ivory linens?" is "we own 600, and I'll know how many are usable on Wednesday."

Between Sunday's collection and Friday's load, event rental turnaround gives you five days to count, clean, fix and stage the same chairs, tables, linens and glassware. Our event rental software guide explains why availability has to be answered by date rather than by count; this post is the weekly routine that keeps those dates true.

The Weekly Cycle

In wedding season, every Saturday wedding takes the same week:

  • Friday - load out. Vans loaded from each job's pull list and on the road by mid-morning, with set-ups running into the afternoon.
  • Saturday - the event. Everything is out and nothing is coming back.
  • 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. Each event's crates are counted against that event's pull list. Breakages and shortages show up here, and Monday is the last day you can still say which client they belong to.
  • Tuesday and Wednesday - cleaning and repairs. Linens go to the laundry, glassware gets washed and racked, tables and chairs get wiped and checked, and anything damaged goes to the repair bay.
  • Thursday - staging. Next weekend's pull lists are picked, crated and labeled by job.
  • Friday - load out again.

Catering crew setting out glassware on a table before an outdoor event

Skip Monday's count and you find the gaps on Thursday instead, when the staging crew comes up 40 glasses short for a job that loads tomorrow.

Each item type also runs the loop at its own speed. Chairs can be back on the shelf Monday afternoon, linens Wednesday at the earliest, and glassware somewhere in between. Whoever quotes next Saturday has to know which is which.

A shared sheet holds up until two people edit it on the same Saturday, one of them on a phone at a venue. In a peak month, Monday's count runs into Tuesday, the laundry comes back Thursday, and Friday's load gets built from what's on the shelf instead of what was promised. Tape each item's turn time next to the phone, or put it in the system, so whoever answers on Monday knows linens aren't back until Wednesday.

When collections run late

When the crew gets back at midnight, nothing comes off the van until Monday, and the week starts a day behind. The cleaning clock starts when the crates are unloaded, not when the event ended.

Stock that hasn't come back yet should stay off the board. In EquipDash a delivery booking reads Delivered on the way out and Collected on the way back, and a late one shows a Not collected yet banner with the time it was due.

Until someone marks it collected, that gear keeps counting as out. If the crew forgets to tap Collected, the worst case is a quote you turned down for tables that were sitting on the dock. Say you own 46 tables and 8 are still at Sunday's venue: availability shows 38, not 46, on your booking page, in POS and in Quick Book.

Cleaning as Blocked Downtime

Friday shortages usually start with stock that was back but not clean. Say the 60 ivory linens from Saturday's wedding come back Sunday night, and a system that only knows "returned" makes them available Monday morning.

Someone quotes them to a reception the following Saturday. On Thursday the laundry calls: it's a heavy week, and the load will be ready Friday afternoon, after the van has left.

Cleaning has to sit on the calendar like a booking. When an item type comes back, it stays off the board for a cleaning window you set once per item type. These are example windows, counted from a Sunday-night check-in:

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
Dishes and flatware Washed, recounted 1 day Monday evening
Chairs and tables Wiped, checked for damage Same day Monday afternoon
Dance floor sections Wiped, edges checked, restacked Same day, next day if it came back wet Monday or Tuesday
Tent tops and sidewalls Dried, cleaned, inspected, rolled 2 to 4 days depending on weather Tuesday to Thursday

Treat those day counts as a starting point. Put a strip of masking tape with the check-in date on one peak-season laundry bag and one wet tent, then write down the day each is actually ready to go out. Whatever the laundry quoted, the tape gives you the real day.

Setting the block in EquipDash

Three settings hold stock off the board while it's being cleaned:

  • Clean between rentals, per product. Turn it on in the product's settings under Rentals > Products. When a booking is marked returned or collected, the quantity that came back goes into a Cleaning workshop job, and only that quantity: 60 cloths back means 60 held, while the rest of the product stays bookable. Those units return to stock when someone completes the cleaning job.
  • Buffer time, per product. In the same settings, turn on Buffer time and set the time after each booking in minutes, hours or days. The buffer holds that booking's quantity, not the whole product, from the booking's end time, so a booking taken weeks ahead can't land in the cleaning gap.
  • The workshop, for one batch. When a load runs long, open the product's Inventory tab and send that quantity to the workshop with the reason Cleaning and an expected completion date. That date is when the units count as available again: a booking that starts after it can take them, whether or not the job has been signed off. Turn on Automatically remove when done and the job also closes itself on that date.

With the windows set, Monday's board shows only what can actually go out. Say last weekend was quiet and only one wedding took ivory linens, 60 of the 600 you own. A corporate client calls Monday wanting 600 for a Tuesday dinner, and the board shows 540 until those 60 clear the laundry, so you quote 540 and sub-rent 60 instead of promising 600 and hoping the laundry is early.

Chart of 600 ivory linens owned and 540 bookable while 60 are in the laundry

If your collections run a day late most weekends, set the buffer a day longer than the laundry takes.

If four glasses are missing, hold the whole line until it's counted. Don't guess that the other 236 are fine. The four might be broken, or in a crate that went back on the wrong van, and the warehouse total won't tell you which until someone counts.

What slows each item down

Tents set the longest windows because nothing gets rolled wet. Wet material should be dried within 24 to 48 hours to keep mold off it, so a tent that came down in the rain gets spread out until it is fully air dry before anyone packs it. That takes floor space, and the web belts and straps need drying room too, not only the vinyl.

Whoever unrolls a wet tent pushes its workshop job's expected completion date back that morning.

Linens slow down when the stains sit. Pull the wine- and wax-marked cloths out of the bags Sunday night and send them to the laundry flagged, because a stain over 24 hours old is much harder to get out than a fresh one.

Commercial laundry worker loading white linens from a cart into the washers

Wax comes off with an ice cube and the edge of a card before the cloth goes in the bag, and a cloth with a burn hole goes to the damage pile, not the laundry.

Glassware is the fastest turn if it goes through a commercial dish machine, yours or a caterer's. A high-temperature machine's final rinse runs at about 180°F (82°C) on most machine types, so a rack comes out sanitized and dries fast. Most of the time goes into polishing and recounting.

Counting Back Against the Event

Every item that goes out on Friday goes out on a pull list for one event. Every item that comes back on Sunday gets 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. Once the crates from three weddings are merged into one pile on the warehouse floor, that record is gone.

The count-back is one pass with four columns per line: out, back, broken, missing. It settles three things at once:

  • A stock adjustment. 240 glasses went out; 236 came back intact, two broken and two missing. Stock is now 236, or 238 if the two broken ones can be repaired, and next weekend's availability works from that number.
  • A damage and loss charge. The two broken and two missing glasses go on that wedding's booking on Monday, while the deposit is still there to take them from.
  • A cleaning block. The 236 intact glasses go into the one-day wash and are back on the board Monday evening.

Dock count sheet for one wedding with glasses out, back, broken and missing

Count "everything that came back this weekend" against "everything that went out" and nobody can say whose four glasses are missing, so they come out of your margin instead of the client's deposit.

Our guide to reconciling bulk event stock covers the count sheet in more depth and how to track shrinkage across a season.

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 gets counted first, not 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 out quantities are already on the sheet. In EquipDash, a booking's Gear tab lists what to pull and how many, and exports to PDF or CSV, so the crew only writes in back, broken and missing.
  • Anything that can't be counted Sunday night stays in the van or in a marked holding zone and gets counted first thing Monday. It does not go on the shelf.

Attributing Breakages

A cracked table leg logged against Saturday's wedding on Monday is a charge against that deposit. The same cracked leg found in the warehouse three weeks later is a cost of doing business, because nobody can say whose event it came off.

A card hold puts its own clock on it. Stripe says holds on online card payments usually last 7 days and some in-person holds only 2, so raise the charge on Monday. A cash or bank-transfer bond doesn't expire, but settle it before the crates are merged too.

Sort out the terms and the photos before the gear leaves the dock. Once a cloth comes back with a burn hole, you're arguing by email about what the client agreed to.

  1. The rental agreement names the charges. Per-item replacement and cleaning fees go on the agreement the client signs, with deposit terms that say breakage and loss come out of it. Once you switch on the rental agreement in EquipDash settings and write your terms, it is emailed when the booking is made and signed from the email, the confirmation page or the counter, and the signed PDF stays on the booking. What the deposit covers and how to set it on the quote is in our post on quoting event rentals and holding the date with a deposit.
  2. Condition is documented at hand-over. Photograph the linens and the glassware crates at delivery and keep the photos with the job. A timestamped photo ends the "it was already like that" conversation. For item-tracked pieces, EquipDash records a condition and up to five photos per item at pickup and at return, and at return an item marked Poor or Damaged needs at least one photo.
  3. The charge comes from Monday's count. On the booking's return screen in EquipDash, Settle up shows the deposit you're holding. Keep some lets you type in the breakage amount, keeps that and gives the rest back. If there's no deposit, or the damage is more than it covers, enter the amount on the item's condition report and choose Send charge, which emails the client a payment link and a page with the photos.

Put both sides of the wear line in the agreement in plain words. A tablecloth that comes back with wine and grass marks gets cleaned, and that cost is already in the rental price. A tablecloth with candle wax burned through it is charged at its replacement price.

Give the count sheet a column for it too, "cleaned" or "charged," so Monday's charge matches what the client signed.

Repairs

Most rental sheets have an "out" column and an "in" column, and broken stock ends up in the back with a sticky note while the sheet counts it as in. A round table with a bent leg is in the warehouse, counted and clean, and it still can't be sold.

If the board doesn't know that, the table goes out on Friday to a client who finds out when the cake goes on it.

Repairs need a block like cleaning does, but you can't set it once. Washing takes the same days every week. A bent table leg might be fixed Tuesday, wait a week for a part, or never go out again.

A repair loop that works for an event rental shop:

  • The dock count flags the unit. Two broken glasses are a write-off and a stock adjustment. A bent table leg, a torn tent panel or a chair with a loose back is a repair job, raised from the same count that raised the charge.
  • Red-tag it and put it in the repair bay, out of the pick path, so Thursday's staging crew doesn't grab it for a pull list.
  • Write down the part, what it costs and who is fixing it. Set that against the breakage charge the client paid, and you can see whether you're recovering repair costs or eating them.
  • It goes back on the board, with its next available date, when someone logs the repair done. Not before.

A torn tent panel needs more care than a loose chair back. Patch or replace panels with fabric certified to NFPA 701, the flame propagation test for textiles, and keep the paperwork with the tent's repair job.

Fire officials can ask for that proof, and some sites write the rule down, such as the National Park Service for tents on the National Mall. Check what your local fire marshal wants.

Holding a repair off the board in EquipDash

If returns run on a clipboard and a red tag today, this is the screen that replaces both. Mark a tracked item Damaged in the return window and EquipDash sends it to the workshop with the reason Returned Damaged, notes and photos attached, and takes it out of availability straight away. It stays under Rentals > Workshop until someone clicks Mark complete & return to stock.

On a workshop checklist, a critical item marked as failed stops the job from being closed unless someone overrides it, which suits a tent frame or a dance floor panel that needs an inspection before it goes out again. Every job is logged, so each unit builds a repair history over the season.

For serialized items such as dance floor sections, generators, tent frames and specialty furniture, that repair history is also the maintenance history, and it tells you when a unit has stopped being worth fixing. The operations features page shows the workshop, and the party rental software page shows how returned stock stays off the board until it's ready.

For bulk items such as chairs, linens and glassware, the return window takes one condition for the whole line, not a count of broken units. To hold the 2 chairs that broke, send 2 to the workshop from the product's Inventory tab, and take anything that will never come back out of stock by hand.

Sizing Stock to the Cycle

If you own 720 linens because the biggest Saturday of the year needs 720, the extra 120 sit on the shelf most weekends.

Owning 600 and turning them every week covers every Saturday that needs 600 or fewer. For the few that need more you sub-rent, and you've skipped buying, storing and laundering 120 cloths. Whether that pays comes down to what your supplier charges per sub-rented cloth against what a cloth costs you to own; our post on selling out tables and chairs and sub-renting the gap covers what sub-renting costs and when to buy instead.

That only works if the turn is reliable, and one wet weekend or a backed-up laundry can throw it off for days. On a three-day laundry block, linens back Sunday are clean Wednesday and load Friday. On a five-day block they land Friday afternoon, after the van has gone, so each set misses the next weekend and you're back to needing two sets.

Linen stock sizing with a three day and a five day laundry turn across the week

Work it out per item type, with your own numbers in place of these examples:

  1. Peak weekend demand. The most units committed on the busiest Saturday of the season, from last year's bookings. Say 720 linens.
  2. Turnaround in days. The realistic block from return to back on the board, not the best case. Say 3 days for linens.
  3. Weekend length. How many days the stock is out per event, including load and collection. Say 3 days (Friday to Sunday).
  4. Does one set cover back-to-back weekends? Add the turnaround to the days out. A 3-day turn plus 3 days out is 6 days, which fits inside a week, so the same cloths come round every Saturday and one set covers every weekend up to the number you own.
  5. What if the turn is slower? A 5-day turn plus 3 days out is 8 days, so Saturday's cloths miss the next Saturday and that weekend needs its own set. Two 600-cloth Saturdays in a row then need 1,200, and a 600 followed by a 300 needs 900.
  6. Sub-rent threshold. Buy for a normal busy Saturday and sub-rent the gap on the few weekends above it. If a normal busy Saturday takes 600 and the peak takes 720, owning 720 leaves 120 cloths on the shelf every weekend but the peak, so price sub-renting 120 once against buying and laundering 120.

Tents add weather to that arithmetic. Our tent rental software guide covers the build and strike days that make a tent booking run most of a week.

What to do this week

If you run the loop on a spreadsheet and a calendar today, first find out who logs returns. If it's three people with three habits, settle on one way before anything else. Then:

  1. Run the masking-tape test from the cleaning section on one laundry bag and one wet tent.
  2. Count one weekend's returns per event at the dock, with the out quantities already on the sheet.
  3. Use those two ready dates to decide which products get Clean between rentals and how long each buffer runs.

If you'd rather the board track this than a sheet, the workshop in this post (cleaning and repair jobs, checklists and repair history) comes with the Growth plan, $55 a month in USD billed annually. Delivery tracking with Delivered and Collected is on Pro, and the pricing page compares every plan.

The event rental software guide covers the rest of the operating model: date-based availability, same-day quoting, packages that track their parts, and crew on the same schedule as the gear. For couples' orders that change three times before the date, see the wedding rental software guide.

FAQ

What is event rental turnaround?

Turnaround is the time between stock coming back from one event and being ready for 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 still inside that loop is in the warehouse but not available to sell, and the turnaround decides how much stock you need to own.

How long should a linen cleaning schedule block stock for?

A 3-day block is a reasonable starting point for tablecloths, napkins and runners going through a commercial laundry, back Sunday and ready Wednesday, with chair covers around two days, glassware, dishes and flatware one day, and chairs and tables the same day. Tent canvas can take two to four days, depending on whether it came back wet. Time your own laundry in peak season, not in a quiet week, then set that window as a buffer after each booking so bookings made ahead leave room for it, and hold each returned batch in a cleaning job until it is actually ready.

Why should returns be counted per event instead of per weekend?

Because each event's pull list is the only record of what that client had, and counting its crates against it (out, back, broken, missing) lets you charge that client's deposit on Monday while 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 deposit terms that say breakage and loss come out of it, and photograph condition at hand-over. Raise the charge from Monday's count-back, while the deposit or card hold is still there, rather than in a phone call three weeks later. Treat normal wear as cleaning, which is priced into the rental, and damage such as a burn hole as a replacement charge.

How much event rental stock should you own?

Buy for a normal busy Saturday, not the biggest Saturday of the year, and check it against the turnaround: take a normal busy Saturday's demand for the item type, the realistic turnaround in days, and the days the stock is out per event. If turnaround plus the out period fits inside seven days, one set covers every weekend up to the number you own, so sub-rent for the one or two weekends that need more. If the turn is slower, you need closer to two sets in rotation, which is why a reliable three-day linen block is worth more than a shelf of extra linens bought for the peak.

Does ChatGPT send customers to you?
See who AI recommends when people in your town ask. Free, in about a minute.
Manage your business
in one place
Start your free 21-day trial and see how EquipDash's AI-native platform (with Dash AI and Dash Bots) simplifies your operations.
EquipDash Dashboard