How do you manage coat check and bag storage at a paid event?

Your closing speaker has finished, people are checking train times, and the cloakroom suddenly has a longer queue than registration did that morning. Someone has lost their token. Someone else needs a laptop from a bag already stored behind the counter. The next venue booking starts soon, and your team still has a room full of coats.

Plan your event cloakroom around that collection rush before you promise storage to ticket buyers. Agree exactly what you can accept, use a reliable item and receipt system, and test how quickly the actual team can return belongings. You also need a named person responsible for exceptions and anything left after closing.

A coat check can be a useful service at a paid conference, concert or exhibition. It lets people take part without carrying everything they brought. But the service includes keeping track of those belongings and returning them properly, even when the programme overruns or the person collecting has a problem. Here's how to make those arrangements practical, affordable and clear to everyone working the event.

Decide what storage you are actually offering

Start with the audience's day. A local evening audience may mainly bring coats. Conference guests checking out of hotels may arrive with luggage. Exhibitors may have sample cases, while performers have equipment that belongs under a separate backstage arrangement. Calling all of this "bag storage" doesn't tell you what the room needs to hold.

Look at travel information, previous event enquiries and the season. Ask the venue what guests at comparable bookings actually bring, while recognising that your audience may behave differently. If you ask ticket holders about likely use, explain that a reply is an estimate unless you are deliberately taking reservations. Interest in storage and a confirmed booking need different records.

Choose between a staffed cloakroom, self-service lockers and an unattended coat area. Each involves a different customer experience and different responsibilities. If guests choose a hook and keep control of their belongings, don't describe the area as a staffed coat check. If staff accept an item, they need a way to identify it and record its return.

Our guide to festival locker rentals covers the separate decisions about hired locker equipment, rental periods and access failures. A staffed counter needs its own arrangements for tagging, searching, handovers and collection. You can't assume that a locker booking process will also explain who may collect a coat from a member of staff.

Define a service people can understand. You might accept ordinary coats and small bags, exclude wheeled luggage, and provide a separate access contact for questions about essential equipment. Alternatively, you might offer luggage storage in an approved room with suitable handling arrangements. Either offer can work when the venue supports it and buyers know the limits before travelling.

A useful real example is the British Museum's visitor information. It publishes cloakroom restrictions, collection arrangements and a capacity limit. Those are that museum's conditions, rather than a standard for your event. The useful lesson is how much practical information "we have a cloakroom" leaves unanswered.

Agree responsibility with the venue and operator

The first thing you want to settle is who takes responsibility when an attendee hands something over. Your business, the venue or a specialist cloakroom company might operate the service. Confirm which organisation provides the service, which terms apply and who handles complaints. A uniformed person behind a venue counter doesn't answer those questions on its own.

Ask whether the venue's existing cloakroom is included in your hire. Check staffing hours, usable capacity, equipment, payment collection and access after the audience leaves. A room appearing on the venue plan doesn't establish that someone will operate it. Nor does access to a room mean your team has permission to store every type of item there.

Put the agreement into your event paperwork. Name the operating lead and deputy, identify who can authorise an exception, and say who will keep uncollected property. Establish the contact route during the event and afterwards. The event venue contract guide can help you place these commitments alongside access hours and other venue services.

Review insurance and customer terms with the people responsible for them. Ask specifically about property in the operator's care, any applicable limits or exclusions, subcontracted services and the claims process. Don't assume general event insurance covers every coat, device or bag. A sign saying belongings are left at the owner's risk doesn't settle your responsibilities or replace checking the actual cover.

The agreement also needs to address changes. Who can stop accepting items when the store is full? Who pays for staff if a delayed programme extends collection? Can the venue transfer belongings elsewhere, and who tells the customer? Resolve those questions while you can still change the service or its price.

Keep staff responsibilities workable. The cloakroom lead should have authority to pause intake and call the agreed support. They shouldn't need to find the event director for every unreadable token. Equally, a temporary employee shouldn't be expected to decide a disputed ownership claim or negotiate compensation while everyone else waits.

Count usable places for each type of item

Storage capacity begins with the actual equipment and approved layout. Check rail loading, stability, shelving, access aisles and the space staff need to retrieve things. Use the equipment supplier's instructions and the venue's assessment. A rail looking partly empty doesn't prove it can safely take more weight or that another rail fits beside it.

Count coats and bags separately. Hanging places don't automatically become suitcase places, and a floor corner isn't approved overflow because it is temporarily clear. Wet coats, bulky winter clothing and several items attached to one hanger can change the practical space needed. Make the acceptance policy match the capacity you have checked.

For a fictional winter conference, suppose the agreed setup provides 160 usable coat places and 50 small-bag places. The organiser forecasts 140 coats and 40 small bags, each handled as a separate checked item. There are 180 expected items and 210 places in total, but the remaining capacity is 20 coats and ten bags. Thirty additional bags would still exceed the bag provision.

These are invented planning quantities, not equipment ratings or a recommended allowance per attendee. Your usable capacity has to come from the proposed setup. Review the forecast when travel plans, weather or the audience mix changes, and decide how you will limit intake before the remaining places disappear.

Keep an accurate count by item category during operation. Update it when an item is accepted, returned or moved to another authorised location. If your chosen system already maintains these counts, use that record and check it against the physical store. Avoid asking staff to maintain several competing totals that disagree during the busiest period.

An overflow location needs the same planning as the main room. It needs permission, security, a location reference and a retrieval route. Tell staff how an item transferred there remains connected to its original receipt. If you have no approved overflow, the correct response to reaching capacity is to stop accepting the affected items and explain the available options.

Put the counter where queues can work

Walk the route from the entrance to the counter and from the counter to the event spaces. Then walk the departure route. Look for crossings with ticket checks, toilets, catering and the main exit. A convenient counter can become a serious obstruction when people stop to unpack bags or wait for friends beside it.

Allow space for the service as it actually happens. Guests need somewhere to remove coats, find payment and put a returned bag on their shoulder. Staff need room to move between the counter and store. Design the queue around those activities, rather than drawing a thin line up to a desk and assuming everyone keeps moving.

The Health and Safety Executive's crowd control guidance, for Great Britain, says queues should not block emergency access and people need a safe way to leave them. Review your cloakroom position with the venue and crowd-management team, including where a growing queue will go. Local requirements and the event's assessment determine the arrangement you can use.

Decide where security screening happens relative to storage. If a prohibited bag cannot pass the entrance search, an inside cloakroom cannot solve that problem. Agree the policy and any separate approved storage with security before advertising it. Cloakroom staff shouldn't inherit rejected items simply because someone at the door wants to keep the entry line moving.

Make the counter usable for people who cannot stand in a long queue, lift a bag onto a high surface or hear a number called across a noisy foyer. Agree assistance with the access lead and tell guests how to request it. Keep the method available when the usual staff member takes a break. A QR code alone is a poor instruction for someone whose phone is in storage.

Separate the place for difficult enquiries from routine collection where space permits. It should remain accessible and allow a private conversation without giving guests access to stored belongings. The supervisor can resolve a lost-token case there while the team continues ordinary returns. Moving the conversation only helps if someone actually takes responsibility for it.

Use one reference that follows the item

Choose a receipt method that connects the accepted item, its storage location and the person entitled to collect it. Numbered physical tags can work for a small service. A purpose-built cloakroom system may be useful at greater scale. Test the method with your staff and equipment, including how they record a completed return.

Admission tickets and cloakroom receipts do different jobs. An admission ticket establishes an event entitlement. It doesn't identify which of several similar coats someone deposited. Avoid treating a ticket barcode as a cloakroom solution unless the system you are using explicitly supports the storage workflow and you have tested the connection.

For numbered tags, use matching references on the customer's receipt and the stored item. Make the storage location clear enough that another trained employee can find it. A number such as C047 might refer to a labelled coat position, while B012 identifies a bag position. Those are example labels. Choose a method that remains readable under the actual lighting and doesn't depend on one employee remembering every location.

Decide what happens when one customer deposits several things. Either give each item its own reference or use a system that clearly records all the items under one receipt. Make the number of items visible to both sides. Don't let an umbrella, scarf or second bag become an unrecorded extra that someone later expects you to find.

Avoid references that repeat across separate counters, dates or shifts without another clear identifier. If two cloakrooms both issue number 47, staff need to distinguish them immediately. When equipment or receipts carry previous event labels, remove or reconcile those before opening. A rehearsal with deliberately similar numbers will show how easily staff can confuse them.

Have a fallback for the parts of the system that can fail. If you use digital receipts, ask what happens when a phone is flat, reception drops or a scanner stops working. If you use paper, keep replacement materials and an approved way to record damaged tags. The fallback must preserve unique references and completed returns, so recovery doesn't create duplicate claims later.

Make deposit and return a repeatable routine

At deposit, confirm the item is within the agreed policy before accepting it. Explain the charge, if there is one, and when collection closes. Attach the tag using a method that won't damage the item, place it in the recorded location, and give the customer the matching receipt. Only mark the deposit complete once those steps agree.

Ask people to keep the receipt somewhere they can access. A paper token put into the bag you have just accepted creates an avoidable exception. If essential information or a transport ticket is stored on a phone, the guest may want to keep that phone with them. Make the reminder helpful without turning staff into inspectors of everyone's belongings.

At collection, check the receipt against the item reference before bringing the item to the customer. Confirm the number of pieces and let them identify an obvious mismatch before they leave. Record the return and deal with the receipt in the way your system requires. Leaving a used token active makes a second attempted collection harder to identify.

Don't hand out several similar black coats and invite people to choose. Staff should retrieve the matched reference from the controlled store. If something appears wrong, pause that transaction and involve the lead. A faster handover that returns the wrong item creates two problems and another person who has to be contacted.

Agree how temporary access works. A guest retrieving a laptop and leaving the bag again may need a fresh acceptance record or a defined update to the existing one. The physical item, reference and storage location must remain connected. Avoid allowing customers to walk behind the counter to get things themselves, even when they seem familiar to the team.

Use the same discipline at shift change. The incoming staff should understand the numbering, outstanding exceptions, remaining spaces and any moved items. Check unresolved differences while the outgoing lead is still available. Record the handover so the next person knows who accepted responsibility, rather than relying on a quick "everything's fine" as the previous team heads home.

Test collection at the busiest moment

The rate at which you accept coats in the morning tells you little about the final collection rush. Morning arrivals may be spread across registration and coffee. Departure can begin when one speaker finishes, with people already watching the clock. Forecast the likely collection pattern separately and test returns with the actual room arrangement.

Measure the whole return transaction. That includes receiving the reference, locating the item, bringing it to the counter, checking the match and completing the record. A test where someone hands over a coat already waiting beside them leaves out the retrieval work. Run repeated trials across different positions, including the furthest bag shelf.

Here's a deliberately simple calculation for the fictional conference. Suppose 120 customers, each collecting one item, reach collection during the first 15 minutes after the programme. You test three independent return positions, each completing one ordinary transaction every 45 seconds. Each position can complete 20 transactions in 15 minutes, giving 60 across the three positions if work is available throughout and there are no interruptions.

That leaves 60 of those customers unserved at the end of the interval. It doesn't mean everyone waits 15 minutes. Individual waits depend on when people join and which position serves them. If more customers arrive during the next interval, those arrivals add to the work still outstanding. Our event queue calculation guide explains how to follow those intervals and distinguish individual waiting from the time needed to clear a backlog.

The arithmetic describes an idealised test, not a staffing benchmark or a safe queue capacity. The positions must really operate independently. If three counters share one runner, a narrow aisle or a single device, adding counters may barely change completed returns. Include those shared constraints when you test your proposed service.

Try a useful change and measure again. Better location labels may reduce searching. Moving ordinary enquiries away from collection may remove interruptions. Extra trained retrieval staff may help when the store, rather than the counter, is slow. Don't claim a benefit until the revised arrangement has been tested, and keep time for exceptions rather than planning every position at its ideal rate throughout the rush.

Agree an action point with the crowd-management team. Staff need to know whom to contact when the queue reaches the approved limit or starts affecting another route. The response may involve pausing deposits, directing people to a planned waiting area or adding the agreed trained support. It should not depend on abandoning ownership checks to make the line look shorter.

Staff the service through final collection

List the jobs before choosing a headcount. Someone receives and returns items at the counter, someone retrieves them, someone watches the queue where needed, and a lead handles exceptions and decisions. The same person can cover compatible duties during quieter periods. At the departure peak, check whether those duties compete for their attention.

Build a rota across setup, briefing, public service, breaks, closing and handover. The service may accept its first coat before the main programme and return its last one after it ends. Paying only for the advertised conference hours leaves work outside the rota. Include a deputy and planned relief so the store remains controlled when someone needs a break.

Brief staff on the actual acceptance policy and give them the authority to apply it. They need a usable answer when a customer asks to store a large suitcase, a wet item or equipment outside the agreed offer. "Ask someone" is incomplete unless they know whom to ask, how to contact them and what to do while waiting.

Consider the handling work as well as the customer-facing work. The HSE's manual handling guidance, for Great Britain, describes avoiding hazardous handling, assessing work that cannot be avoided and reducing injury risks. It also makes clear that the law doesn't set a single weight limit. Your bag policy should reflect the actual task and assessment, rather than an invented universal safe weight.

Use suitable equipment and arrange storage to reduce difficult lifting and repeated reaching. Have the responsible people assess heavy or awkward items, floor-level storage and long retrieval routes. Staff need to know when to seek help or refuse an item outside the service. Don't rely on a quick lifting demonstration to make an unsuitable setup acceptable.

Keep security and specialist concerns within the agreed event procedures. ProtectUK's unattended and suspicious item guidance calls for a documented local plan and trained staff. A suspicious item shouldn't be carried into the cloakroom as ordinary storage. Brief the team on reporting through the event's security arrangements, without expecting a cloakroom worker to improvise an assessment or handle something potentially dangerous.

Work out whether to include storage or charge

A charge can help pay for the service, but begin with the costs you will actually incur. Include labour across the full rota, equipment hire, tags, payment costs, secure storage, closing work and any agreed additional insurance. Check which costs are already included in the venue hire so you don't count them twice.

For an invented budget, suppose the fictional conference needs four core staff for ten paid hours each and two additional peak staff for two paid hours each. That is 44 paid hours. At an assumed all-in labour cost of $25 per hour, labour is $1,100. Add $180 equipment hire, $40 supplies and $80 for an agreed after-event transfer and follow-up allowance. These selected delivery costs total $1,400.

The amounts are hypothetical US dollars, not supplier quotes or recommended pay rates. This is not a complete event budget. It also assumes those staffing hours have been checked against the actual duties, breaks and collection test. If that review changes the rota, change the cost before choosing a price.

At an assumed $5 per item and 180 paid item deposits, gross cloakroom income would be $900. That is $500 below the selected $1,400 cost, before any additional payment charges, taxes or other omitted costs. Charging doesn't make the service profitable under those assumptions. You would be choosing to fund part of it from the wider event budget.

You might decide that is worthwhile. Included or partly funded storage can support the experience you sold, particularly when your venue requires coats or bags to be left outside the event space. Alternatively, a genuinely optional service may suit a separate charge. Assess the customer promise and applicable requirements before turning essential access support into a paid extra.

Explain the unit of charge. Is it per item, per person or per deposit? Can someone retrieve an item temporarily, and does depositing it again create another charge? State the complete payable price and relevant conditions where people decide to use the service. Keep the wording consistent at purchase, in attendee information and at the counter.

If you collect money onsite, use the approved payment and reconciliation process. Staff need a way to distinguish a payment failure from an item that has already been accepted. Avoid launching an improvised storage sales flow on the morning of the event. The retrieval record must still work even when a payment query needs separate attention.

Tell guests what to expect before they travel

Publish the storage offer early enough to influence what people bring. Include accepted item types, any size restrictions, price, location, hours and whether availability is limited. Say plainly if there is no luggage storage. A bag policy revealed at the entrance leaves an attendee choosing between missing your event and finding somewhere else to put their belongings.

Keep the information close to the relevant arrival instructions. Explain whether guests pass security before reaching the cloakroom and whether they must collect before leaving the site. Give an access contact for anyone who needs help using the service or has a question about essential equipment. Don't invite sensitive medical details in a public comment thread.

For the fictional conference, a short message could read as follows. "Coat check is beside reception and accepts ordinary coats and small bags. Wheeled luggage isn't accepted. Storage costs $5 per item and is subject to remaining space. Deposits open at 9am and finish at 3pm. Collection remains open until 6pm, after the programme finishes at 5pm. Keep your receipt available. Please contact the event access team before travelling if you need help using the service."

That wording is a worked example, not a complete set of customer terms. Its hours and limits need to match the actual venue agreement. If you use it, add the real access contact, directions and any restrictions the guest must understand. Check whether someone who has never visited can find the counter without asking several staff members.

Loopyah's attendee email tools can send event updates to the relevant ticket holders, so storage instructions can reach the people attending. Keep the message focused on their visit. The cloakroom operator still needs to manage physical item references, capacity and collection. Emailing the policy doesn't establish that those operating arrangements exist.

Show the same information onsite with readable signs and brief the reception team. A change to the location or opening hours needs an owner who updates every affected channel. If the service fills, replace any unconditional invitation to use it and tell the entrance staff promptly. Guests shouldn't be sent through several queues before learning you have stopped accepting bags.

Handle missing tokens without guessing

A guest who loses a receipt needs help, and the person holding the next receipt still expects the queue to move. Give staff a separate route for the exception. They should explain who will review it, keep the item secure and continue routine collection where the team can do so safely.

Start by asking the claimant to describe the deposited item and the circumstances of the deposit. Compare their account privately with the records. Don't display several bags or reveal distinguishing details before asking what belongs to them. A token number overheard in the queue or a valid admission ticket is insufficient by itself to establish the claim.

Have the lead decide what supporting information is appropriate. A deposit time, existing photograph, receipt record or distinctive feature may help, depending on the item and the available system. A wallet or identity document might be inside the checked bag, so demanding that same document before reviewing anything can make the process impossible. Agree an alternative rather than leaving staff to make exceptions inconsistently.

Minimise the personal information you collect. The UK's Information Commissioner's Office describes information being adequate, relevant and limited to the purpose in its data minimisation guidance. That guidance is under review following UK legislation changes. Check the rules applicable to your service, and define what you need for a claim instead of routinely copying identity documents or photographing private bag contents.

Record the decision and who authorised the release, using the approved restricted record. Give access only to the people who need it to operate the service or resolve the case. Set a review and retention arrangement for these records with your privacy lead, including how outstanding complaints affect deletion. Closing the event is not a reason to keep every claimant's details indefinitely. If the evidence doesn't establish a match, explain the next review step. Don't release an item because a guest is persuasive, recognises the brand or says they are in a hurry. Equally, don't describe someone as dishonest because they have lost a small paper receipt.

Collection by another person needs an agreed authorisation process. Being on the same group booking doesn't automatically entitle someone to everyone else's belongings. Explain what the owner and collector need to provide through a private route. Keep disputed claims with the lead and relevant security support, rather than letting an argument continue across the public counter.

Keep complaints and uncollected items assigned

If a customer reports that a stored item is missing, start with the deposit record and last known location. Ask the lead to check the relevant positions, transfers and completed returns. Preserve the record of what staff actually did. Don't quietly change a location or mark something collected to make the count agree with the shelf.

Tell the attendee who is handling the case and when they will hear from that person. Separate what is confirmed from what you are checking. "The deposit is recorded and we're checking the return history" is more useful than an unsupported promise that the coat must be somewhere. Follow the agreed security, insurer and complaint routes where relevant, without promising a settlement you aren't authorised to make.

A damaged item needs the same care. Record the reported damage, available observations and the customer's account without deciding the cause at the counter. Refer the claim to the responsible organisation. Staff should know how to make an incident record and get assistance while continuing to protect the remaining property.

Plan the final collection period with the venue. In the fictional timetable, public collection finishes at 6pm and core staff remain until 6:30pm for the count and handover. That requires approved access to the counter and store until the handover is complete. If a delay prevents completion, the lead uses the agreed extension or transfer arrangement. The schedule doesn't authorise anyone to abandon the remaining items at 6:30pm.

Keep checked but uncollected belongings connected to their original deposit references. They shouldn't become anonymous found property when the public counter closes. Agree a secure destination, receiving person and record of transfer. Publish the after-event enquiry route and confirm who will answer it after your temporary team has dispersed.

Our event lost property procedure explains the separate work of receiving found belongings, assessing claims and arranging later collection. Your cloakroom can connect to that service through an agreed handover, while retaining its deposit history. Check the applicable rules before setting retention, disposal or delivery conditions. Don't invent a right to discard a bag because its owner missed the event's collection deadline.

Turn the decisions into a short operating brief

Write a brief the team can use at the counter. Start with the decisions already agreed, then add names, locations and the contact method. Keep detailed insurance and customer terms available separately. The operating brief should tell a worker what to do when the next person arrives with a coat, rather than make them interpret the venue contract.

For the fictional conference, the completed brief could contain these entries:

• Service and stock. Staffed storage beside reception, with 160 approved coat places and 50 approved small-bag places. Track the two categories separately. Accept only the item types and bag sizes shown in the agreed customer policy. No wheeled luggage or unapproved overflow. Stop accepting the affected category when its remaining capacity reaches zero.

• Hours and team. Core staff are paid from 8:30am until 6:30pm. Deposits run from 9am until 3pm; collection runs until 6pm. Three core employees can each complete ordinary returns, including their own retrieval, and the fourth is the lead. Two extra staff work from 4:30pm until 6:30pm, covering the queue and relief. Confirm breaks and any shared retrieval constraints in rehearsal.

• Receipts and charging. Each separate item has one unique matching reference on the item and customer receipt. Record its actual storage position and completed return. The assumed charge is $5 per item deposit. Any temporary access or new deposit follows the agreed receipt and charging policy, which staff can explain before accepting the item.

• Exceptions. The lead handles missing receipts, unmatched items and collection by another person at the enquiry position. Keep items in the controlled store while checking a claim. Security and urgent welfare concerns use their respective event procedures. The brief names the lead, deputy, control contact and access contact, with a working way to reach each.

• Closing. At 6pm, stop public collection and reconcile the remaining items with the records. The lead and venue receiving person acknowledge any agreed transfer, keeping the original references and outstanding cases. Tell affected guests the after-event contact route. Arrange an extension through the duty manager if the agreed handover cannot be completed by 6:30pm.

This brief still needs the real names and approved policy details before anyone uses it. Its six-person peak team is an example allocation, not a guarantee that three independent returns can happen every 45 seconds. If the rehearsal shows a shared bottleneck, change the allocation, layout or service promise and recalculate the budget.

Give essential belongings an explicit route as well. A cloakroom is not automatically suitable for medication, mobility equipment or something a guest needs urgently throughout the day. Ask the event's access and medical leads what can be provided, how someone obtains assistance and what staff should say. Don't promise temperature control, charging or specialist care unless the approved service actually provides it. Explain the arrangement before accepting an item that ordinary storage cannot support.

Rehearse the awkward cases before opening

Run a practical rehearsal with the people operating the service. Start with ordinary deposits and returns, then add similar coats, multiple items and a request for temporary access. Use the actual receipts, labels, counter and storage positions. Ask someone unfamiliar with the layout to retrieve items using only the records and briefing.

Time ordinary returns across different parts of the store. Then introduce a missing token while other people continue collecting. Watch whether the supervisor can take the exception without leaving the store uncontrolled or stopping every position. Record what caused delays so you can change the task, layout or staffing before guests arrive.

Try reaching the bag limit while coat places remain available. Does the intake count show the right restriction? Can reception explain it? If the team is using a digital system, test the agreed failure method and recovery. Check that temporary records don't reuse a live reference or make an item appear available for a second return.

Include the final handover. Give the outgoing lead an uncollected item, a claim under review and a mismatch between a location record and the physical store. Ask the receiving person to explain what they would accept, what they would check and whom they would contact. Resolve missing instructions while both organisations can still amend the agreement.

Connect the rehearsal to the emergency plan too. Staff and guests need to follow the event's evacuation instructions without returning for belongings. Agree who communicates later collection information once the responsible authorities and venue permit it. The cloakroom team should not promise immediate access to a closed area because someone's keys are inside.

Before opening, confirm the approved capacity, staffed hours, working receipt method and escalation contact. If a material problem remains, change what you offer and tell attendees. It's better to provide a smaller service your team can deliver than accept belongings into an arrangement that hasn't passed its own rehearsal.

Use the results to plan the next event

After collection and transfer are complete, compare the service with your plan. Count accepted items by category, actual paid hours, completed returns during the departure peak, exceptions and unresolved claims. Separate gross charges from the costs you paid. A busy cloakroom can still require a substantial contribution from the event budget.

Ask where the work slowed. Searching, payment, inaccessible instructions, poor labels and insufficient retrieval space require different changes. Buying more rails won't fix a token process that repeatedly sends the wrong person to the wrong shelf. Use observations from the team and guest complaints to identify the task you need to improve.

Keep each remaining case assigned until the responsible organisation confirms its next step. Then use the findings to revise the next venue brief and customer information. Before offering storage again, resolve the specific problems the team recorded, including any staffing or access commitments that the venue needs to confirm.