How to agree a workable neighbourhood plan for a paid outdoor event

You've found a site that makes the event feel possible. The stage fits, the audience can get there, and the budget looks workable. Then you walk down the lane behind it and notice the flats above the loading gate. Your cheapest delivery slot is early on Saturday. Your cheapest collection slot is straight after the final set.

Those neighbours are going to experience a much longer event than the people buying tickets.

A workable event neighbourhood agreement starts with that whole experience. Talk to the people affected while you can still change the operation, then record what you'll do, who will do it and how you'll check. Cover access, deliveries, sound, departure, cleaning and a contact who can reach someone with authority. Be honest about the disruption that remains.

Some residents will still dislike the event. You can make it easier for someone to get home, run their business or raise a concern without spending the afternoon chasing your team. For a commercial organiser hoping to use the site again, those are production decisions with a budget attached.

This guide explains how to develop that plan, including a worked example and wording you can adapt. The agreement here is a practical record of commitments. Its legal status, and any formal agreement you need, depend on the location and the parties involved.

Establish what you can actually agree

The first thing you want to do is separate your responsibilities from decisions that belong to someone else. You can instruct your supplier when to arrive. You may need another body's permission to change the route they use. You can move your steward to a gate. That doesn't give the steward authority to close a public road.

Ask the landowner and relevant authorities which permissions, conditions and consultation procedures apply to the proposed paid event. Describe the audience, entertainment, structures, traffic and full occupation period. Include the hours before opening and after closing. Our outdoor event permits guide helps you organise those checks before commitments become expensive.

Keep the confirmed requirements in a separate section of the working plan. Record the document, relevant condition, responsible person and drawing version. If a proposed neighbour arrangement conflicts with a condition, resolve that through the proper approval route. Don't circulate a friendlier version and expect your operations team to choose between them later.

The Department for Transport's guidance on temporary traffic restrictions for special events illustrates the distinction in its framework for local traffic authorities. It calls for appropriate consultation and notification where measures affect property access or parking. It also says the time needed varies with the event. Your resident meeting doesn't replace the authority's process, and a deadline borrowed from another event may be wrong for yours.

Be equally clear about who speaks for whom. A residents' association can raise valuable concerns without representing every household. A landlord may manage the building without knowing a tenant's working hours. Record the people and organisations you consulted, the issues they raised and any remaining disagreement. Don't describe a neighbourhood as having approved the event because a few people attended a meeting.

Where you need a contract, access permission or other binding document, have the appropriate local adviser prepare or review it. Avoid asking residents to sign away complaints as the price of discussing practical arrangements. The useful question is whether the operation can work beside their homes, with the permissions and responsibilities properly established.

Map the disruption beyond your fence

Take your site plan outside the event boundary. Walk the streets people will use to arrive, work and leave. Visit at the times that matter where possible. A service lane that looks empty during a weekday site visit may be busy with restaurant deliveries on Saturday morning.

Mark homes, shops, care facilities, entrances, loading points, transport stops and the routes affected by your proposal. Include people who could experience an indirect change. Moving the audience pickup point away from the nearest flats may send vehicles past another row of homes. Solving one complaint by exporting the same problem around the corner isn't much of a plan.

Then map the event by phase. There is the build, soundcheck, audience arrival, programme, departure, removal and restoration. For each phase, ask what someone nearby might hear, find blocked or need explained. A resident who works nights may care more about Friday's build than Saturday's music. A shop may care about access during its busiest trading hour.

Consider a fictional event called Marsh Yard Sessions, a ticketed outdoor music afternoon beside homes and small businesses. All details and figures in this example are invented to show the planning decisions. They aren't recommended hours, staffing levels or cost benchmarks. The organiser plans for up to 600 ticket holders, with actual capacity and access arrangements determined separately by the responsible team.

The proposed public opening is Saturday at 2pm, with performances ending at 9pm. The first supplier arrives on Friday, and some equipment remains until Sunday. One neighbour's concern is a Saturday pharmacy delivery. Another is a residential entrance beside the proposed rideshare collection point. Neither issue appears on the poster.

On the marked plan, the organiser records the pharmacy entrance, residential door, service gate and collection route separately. That lets the traffic and safety leads assess actual movements rather than approve a general promise to maintain access. The people delivering the event can see exactly which location each commitment concerns.

Don't collect private information simply because it makes the map feel complete. You usually need to know that an essential visit requires an access arrangement, rather than someone's diagnosis. Keep sensitive details out of the version shared with suppliers. Give the responsible person enough information to make the arrangement work, using an appropriate private channel where needed.

Consult while the important choices can still change

There is a big difference between asking for views and announcing a finished plan. If the stage position, service hours and transport arrangements are already fixed, say so. Calling that consultation invites people to spend time suggesting changes you have no intention or ability to consider.

Start with an outline that shows what is proposed, what is confirmed and what remains open. Explain why you want to use the site and what kind of paid event you're producing. Neighbours shouldn't have to decode a marketing campaign to find out whether the proposal involves amplified music, food deliveries or a late departure.

Ask practical questions. Which entrances must remain usable? Are there regular deliveries or collections your plan conflicts with? Where do vehicles already queue? Is there an activity nearby that makes a proposed soundcheck particularly difficult? Ask about the effect rather than requiring people to design your solution.

Offer more than one way to respond. A meeting suits some people. Others need a telephone conversation, written response or an accessible version of the information. Use the channels required locally and those likely to reach the affected occupants. A post in a community group can help, but it doesn't establish that everyone who needs the information has received it.

Keep the conversation specific when people disagree. One resident may prefer an earlier music finish, while a nearby restaurant values evening customers. Record both positions and assess them against the requirements and workable production choices. Counting favourable comments won't tell you whether a blocked entrance has been resolved.

At Marsh Yard, the organiser initially proposes putting the collection point beside the residential door because it's easy to describe to customers. Residents explain that cars already wait there for food deliveries. The transport lead checks an alternative with the relevant parties and revises the collection arrangement. The team also changes its signs and customer travel information. The conversation has altered something people will experience.

Close the loop with a short response explaining what changed, what stayed and why. If you cannot meet a request, explain the actual constraint and any alternative being considered. Avoid saying you'll keep disruption to a minimum when you already know the requested delivery window is impossible. A clear unresolved issue is more useful than reassurance that hides it.

Build time for that response into the programme. The sequence should allow consultation, technical review, necessary approvals, supplier confirmation and final notification before the relevant work begins. Set dates backwards from your own authority's requirements and purchasing deadlines. There is no universal number of weeks that makes an inadequate conversation adequate.

Turn concerns into commitments someone can carry out

A concern becomes useful production information when the team knows what to do about it. Write each commitment around a place, activity, responsible person and check. Include the condition that triggers further action and who can authorise that action. Keep it short enough for the duty team to use.

"Respect local residents" doesn't help the driver who arrives early. "Supplier vehicles must use the service gate during the booked delivery window, with early arrivals held at the approved offsite location" gives the logistics lead something to brief. The holding arrangement itself must be permitted, safe and available. You can't solve early arrivals by telling trucks to wait on the nearest residential road.

For each commitment, keep the reason behind it. That helps someone understand why an apparently convenient change needs review. If the delivery window protects the pharmacy's access, an unbriefed replacement driver should be able to find that out before reversing into the wrong space.

Use a simple working record with these fields:

• The issue and exact location, described without unnecessary personal details.

• The agreed action, operating period and any approval it depends on.

• The person responsible, their deputy and the supplier instruction required.

• The check, its timing and where the result will be recorded.

• What happens if the action fails, including who can change or pause the activity.

• The current status, date and relevant plan version.

At Marsh Yard, the pharmacy access concern becomes a delivery commitment rather than a promise of goodwill. The logistics lead coordinates the approved supplier timetable with the pharmacy's confirmed delivery needs. A steward checks the agreed route during the relevant period and reports obstructions to event control. Any change goes through the people responsible for safe access and traffic arrangements.

The organiser doesn't promise that every outside delivery will run perfectly. The commitment describes what the event team controls and how it responds when something goes wrong. If a third party is needed to deliver the arrangement, record their confirmation. "The council will handle it" isn't a completed action until you've established what the council has actually agreed to do.

Make the distinction between a target and a requirement explicit. A hotline acknowledgement target can help you staff the role. It doesn't extend a deadline imposed by an approval or justify leaving an urgent safety problem waiting in a queue. The responsible team needs to understand which instructions require immediate action.

Review commitments together before circulating them. A quieter collection time may require overnight equipment storage, which needs security and site permission. A revised walking route may affect accessibility or emergency arrangements. Get the relevant leads to check the combined operation, so the neighbourhood plan describes an event your team can actually deliver.

Make access work for ordinary life

Start with the people who need to use the area without attending your event. Residents, carers, customers, tradespeople and delivery drivers may need different arrangements. Agree those with the relevant property interests and authorities, then test how the frontline team will recognise and handle each situation.

Don't use an event ticket as a shortcut for legitimate access. A resident going home is making a different journey from a customer entering the paid audience area. Keep that distinction visible in the plan and staff briefing. Our ticketed neighbourhood street festival guide explores the wider admission and boundary choices when an event occupies a working street.

Walk the proposed route as it will operate. Add the barriers, signs, queues, equipment and steward positions to the discussion. A doorway can be technically outside your footprint while a customer queue makes it difficult to reach. A route that works before opening can stop working when the first performance finishes.

Have the access and safety leads assess alternatives for people whose usual route changes. Be precise in the information you publish. "Access maintained" could mean a longer walk, a different entrance or an arrangement requiring assistance. People need those details to plan a journey. Don't describe a route as accessible solely because it is available on the drawing.

Ask what happens when someone arrives without the evidence staff expected. There should be a private way to resolve a query without arguing at the public queue or collecting more personal information than necessary. Name the supervisor who handles exceptions and make sure they can be reached during the whole affected period.

At Marsh Yard, the residential door remains outside the customer collection area in the revised plan. Signs direct ticket holders to the confirmed pickup location, and the departure team knows where to send a vehicle that stops incorrectly. The organiser also checks that suppliers aren't using the space while waiting to leave. Otherwise the same obstruction returns under a different description.

Test the awkward combination, too. What happens if the pharmacy delivery arrives while customers are leaving a performance and a resident needs assistance? Ask the responsible leads to explain the sequence and where people wait safely. If the answer depends on everyone arriving at the right moment, the plan needs more work before you promise it publicly.

Explain sound, working hours and the finish honestly

Neighbours need the schedule they will experience. Show the first deliveries, build activity, rehearsals, soundcheck, programme, audience departure and removal separately. "The event ends at 9pm" is misleading if you've arranged for trucks to collect equipment beside homes at 11pm and haven't explained that work.

For Marsh Yard, the team develops a permitted Friday build window, Saturday operating schedule and Sunday removal window with the relevant parties. It distinguishes the performance finish from the expected departure period. Those are fictional arrangements for this example. Your own hours need confirmation for your site, activities and approvals.

Sound needs a proper technical plan. Bath and North East Somerset Council's advice on preventing noise nuisance at events recommends informing neighbours, taking their views into account and providing a direct telephone number for concerns. Its practical advice also includes checks outside the venue boundary. Use the locally applicable requirements and competent advice for your production, rather than promising a universal sound level in a resident letter.

Our outdoor event noise management guide covers the technical assessment, measurements and response. Here, the neighbourhood plan should explain which activities are expected, who takes reports and how those reports reach the person responsible. Residents shouldn't need to identify the equipment or produce a sound reading before someone listens.

Be careful with claims about permission. Defra's noise nuisance guidance for England explains that councils can investigate statutory nuisance at any time of day or night. Finishing before a particular evening hour doesn't establish that everything earlier is acceptable. Check the corresponding framework where your event takes place.

Agree the response to delays with production before the show. If an artist starts late, who decides what changes so the event meets its requirements? If removal cannot happen as planned, who can approve a safe alternative and fund the additional work? Include the neighbourhood contact in relevant updates, so they don't keep repeating a schedule the production team has already abandoned.

Put the cost in the event budget

Neighbour arrangements need the same costing discipline as sound, staging or ticketing. Include preparation, staffing, printing, translation where needed, contact cover, approved traffic arrangements, additional cleaning and any effect on supplier hours. Check what is already included before adding a separate allowance. A production manager's existing paid hours shouldn't appear twice because you've given their work another name.

The useful question is what the event costs with the required and agreed arrangements in place. Don't build the sales case around a cheaper operation you cannot responsibly deliver. If the revised cost makes the site unworkable, change the scope, find funding or reconsider the site before making promises to customers and neighbours.

Take an illustrative budget for Marsh Yard in USD. Here, operating profit means event revenue less delivery costs, before business income tax. The event initially shows $6,500 before four additional neighbourhood costs, each covering different work. Allow $900 for liaison and contact cover, $600 for additional approved access stewarding, $450 for the agreed surrounding-area clean and $350 for overnight equipment arrangements. Assume those are the full additional charges, including any applicable tax, with no tax recovery in this simplified example.

The extra cost is $2,300, leaving forecast operating profit of $4,200. That is the figure the organiser should use when deciding whether to proceed. The earlier $6,500 depended on missing work. It wasn't money the business had already earned and then lost to a difficult neighbour.

If the organiser's minimum acceptable forecast profit is $4,000, only $200 remains above that target. Another $250 charge would take the forecast to $3,950. The response needs a funded decision, such as removing an unrelated optional expense, changing the proposal or rejecting the site. It cannot be an instruction to skip an access commitment while continuing to describe it as agreed.

Check payment dates separately. A cost included in the profit forecast may still be due before ticket receipts are available to spend. Confirm deposits, balances and any site restoration requirements. Keep the available money for delivery and potential customer obligations visible when deciding whether an additional commitment is affordable.

Complimentary tickets or a local offer can be a welcome benefit where appropriate. They don't fix a blocked driveway, remove noise or buy agreement from someone who doesn't want to attend. Keep those offers separate from resolving the operational issue. If you make a financial or trading arrangement with a local business, document its terms properly rather than leaving it inside a friendly conversation about community support.

Send a resident notice people can use

The final notice should tell someone what changes around them, when it changes and how to get help. Keep the promotional introduction brief. A person reading it at their front door is looking for the delivery time or contact number, not your event's brand story.

Use a clearly dated version and identify the organising business. Give the event name, exact location and dates, followed by the full period of relevant activity. Explain access and traffic changes in plain words, supported by a readable map where needed. State which arrangements are confirmed and what will happen if something material changes.

Include a contact before the event and a staffed route during the affected work. Say when each is monitored. If one number covers the whole period, arrange shifts and handovers accordingly. The public contact should not be the private mobile of a person who will be onstage, driving a truck or unable to answer.

Here's sample wording for the fictional Marsh Yard event, after its arrangements have been checked and approved where required. Add the organising business name, actual calendar dates, tested contact details and the confirmed map before using it.

"Marsh Yard Sessions is a paid outdoor music event at the yard beside the service lane. The event opens to ticket holders on Saturday at 2pm, with performances ending at 9pm. Managed audience departure is planned to finish by 10pm.

"Our working schedule also includes the Friday build between 9am and 5pm, Saturday setup between 9am and noon, and Sunday equipment removal between 10am and 2pm. Soundcheck is planned for Saturday between noon and 1pm. These activities may be audible nearby.

"The attached current access map shows the service gate, residential entrance, pharmacy route and customer collection point. Residential access does not require an event ticket. Supplier deliveries will follow the confirmed access arrangement. Please contact the liaison team if you need to discuss an affected journey or delivery.

"The neighbourhood telephone line is staffed Friday from 9am to 5pm, Saturday from 9am to 11pm and Sunday from 9am to 3pm. Use the listed number for event concerns during those periods and the listed email for questions in advance. The line is not an emergency service. We will investigate reports, explain the action taken and update people affected by material changes."

Your actual notice may need additional information or a different format under local requirements. Have the relevant leads check it against the same current plan before distribution. Ask someone unfamiliar with the event to explain the access arrangement back to you. If they misunderstand the entrance or believe the hotline handles emergencies, fix that wording before sending it.

Give the team one version of the plan

A resident notice can be beautifully clear while the supplier order still instructs the opposite. Before distribution, compare the plan with contracts, delivery bookings, crew calls, steward briefings, customer information and the production schedule. Identify the person responsible for each correction and confirm completion.

Ask contractors to acknowledge the parts affecting their work. A company accepting a removal window doesn't prove the driver assigned on Sunday has seen it. Confirm how instructions reach replacement staff and subcontractors. Include a route for questions before anyone arrives at the wrong gate.

In Great Britain, HSE's guidance on managing an event stresses coordination across the event's phases and relevant information for contractors. It also recommends checking that agreed controls work and reviewing the event afterwards. Apply the requirements and competent advice relevant to your location. The practical point for this plan is to connect each public commitment with the people carrying it out.

At Marsh Yard, the Sunday collection window changes the equipment order and the site handover. Overnight storage creates security and access work that must also be covered. Confirm who handles issues while the public contact line is closed and how responsibility transfers when that line reopens. The resident notice, logistics schedule and supplier instructions all need to describe the same arrangement. If the organiser changes one document, they check the others before considering the change complete.

Make audience instructions part of that check. Tell ticket holders the confirmed arrival and collection points before they travel, then reinforce the message with signs and staff. Loopyah's attendee email tools support sending event updates to ticket holders. Use that for the information your team has confirmed, such as the correct collection point. Neighbour consultation still needs its own contact and distribution arrangements.

Give the duty manager and deputy access to the current working plan if mobile reception fails. Keep the public summary separate from private contact details and technical documents. Staff should be able to find their instruction without opening a resident's confidential correspondence or searching an old group chat.

Rehearse a change as well as the original plan. A supplier calls to say its collection vehicle has been replaced. Ask who checks the revised vehicle and route, whether approvals or staffing need review, and who tells affected people. Having a person authorised to accept a phone call is different from giving them authority to approve any arrangement the supplier suggests.

Run the contact line as an operational role

The person receiving concerns needs time, a working phone and a route to event control. Treat that as a staffed responsibility. If you assign it to the person also solving every ticket query, you need enough cover for both jobs when the event gets busy.

Train them to capture the useful detail without making callers prove they deserve attention. Ask what happened, where and when, whether it is continuing, and how to follow up if they want a response. Distinguish a report from a confirmed cause. A resident may accurately describe a noise while being mistaken about which piece of equipment creates it.

Use a shared log accessible to the authorised duty team. Give reports a reference, record the time received and name the person handling the action. Track investigation, changes, checks and the next update. An acknowledgement is helpful, but "passed to production" shouldn't be the final status of a problem that remains unresolved.

At Marsh Yard, a resident reports a vehicle waiting across the agreed access route. The contact person records the location and passes it immediately to the responsible operational lead under the agreed procedure. The lead checks the situation and arranges a safe response. Once the obstruction is resolved, the log records the time and action, with follow-up to the caller where appropriate.

If the report reveals an urgent threat to safety, use the event's emergency arrangements immediately and direct callers to emergency services where appropriate. The neighbourhood line must not delay that response. Keep the difference clear in the public information and the briefing for whoever answers.

Give ordinary concerns a realistic update process too. You may not be able to promise a fixed resolution time for every issue. You can explain what will happen next, who is investigating and when an update should be expected. If the target is missed, the next shift needs to see the outstanding commitment.

Avoid debating motives on the phone. Someone can dislike the event and still report a real obstruction. Someone can enjoy the music and still need a promised route kept clear. Handle the factual issue, record abusive or threatening behaviour through the appropriate procedure, and keep staff support available. Courtesy shouldn't depend on whether the caller sounds like a potential customer.

Handle changes without quietly rewriting the agreement

A plan needs a change process because real events change. That process should identify who can approve an adjustment, what must be checked and who must be told. It shouldn't allow the organiser to remove an inconvenient commitment simply by updating the file after a complaint.

Consider a delay to the Saturday programme at Marsh Yard. The stage manager knows the performance finish, the noise lead knows the applicable conditions, and the event manager coordinates the authorised response. The neighbourhood contact needs the resulting information, but shouldn't negotiate a new finish time with individual callers. Any necessary approvals remain with the appropriate bodies.

For a significant planned change before the event, check which neighbours it affects and how. A new generator position, longer occupation period or revised vehicle route may affect people who weren't included in the original discussion. Update the relevant technical assessments and seek approvals where needed, then issue a clear correction through the required and appropriate channels.

Say what changed and which previous information it replaces. Don't send a whole new notice with the revised time hidden in the middle. A neighbour who already made arrangements needs to understand the difference quickly. Record when the correction was distributed and by whom, while being honest that delivery doesn't prove it was read.

If an arrangement fails during the event, tell the relevant person what happened, the action being taken and any remaining uncertainty. Avoid promising compensation or a particular remedy unless the authorised person has checked the facts and applicable obligations. Record commitments that need follow-up so they survive the shift change.

Keep public responses proportionate. Where several people report the same transport issue, a general update may help. Remove personal details and confirm the facts before posting. There is little value in declaring the neighbourhood satisfied while unresolved access reports are still waiting in the log.

Protect the information people share with you

Neighbour liaison can gather more personal information than the team expects. Someone explaining an access concern may mention a medical appointment, care visit or personal difficulty. You need a workable arrangement, but that doesn't mean every detail belongs in a supplier briefing.

Decide what information the role needs, who can see it and how long it should be retained under your applicable obligations. Tell people how their information will be used and provide an appropriate private contact route. Keep public summaries about the issue and response, with confidential details in restricted records only where needed.

The UK's Information Commissioner's Office explains data protection principles for small organisations, including limiting collection to the purpose, keeping information secure and retaining it only as long as needed. The page is under review following legislative changes. Check the current rules that apply to your operation, particularly if people share health information or other sensitive details.

Don't add residents to ticket marketing because they contacted the liaison team. They supplied information for a different reason. Any marketing use needs its own appropriate basis and handling. A community contact list isn't automatically an audience list for your next on-sale announcement.

For repeat events, retain the operational learning without copying unnecessary personal history into each new edition. "Confirm the pharmacy delivery arrangement before supplier bookings" helps the next organiser. An old narrative about the person who complained may add little and create an avoidable privacy problem. Review what you keep rather than treating the entire mailbox as permanent production documentation.

Review what happened before booking the next date

Close the neighbourhood work after removal and restoration, not when the music stops. Check the agreed surrounding areas, access routes and cleaning with the relevant parties. Record unresolved damage or service issues and assign follow-up. Keep the contact arrangement available for the period you promised, including work after the audience has gone.

Compare delivery against individual commitments. Was the access route available during the agreed period? Did the supplier use the correct gate? Did the contact line have cover through removal? Did reports reach someone who acted? The answers are more useful than a broad statement that the event had good community engagement.

Read complaint numbers carefully. Few calls may mean the event worked well, or that people couldn't find the number. Repeated calls may concern one unresolved problem rather than separate incidents. Keep those distinctions in your review and don't claim a causal improvement from a small, inconsistent comparison.

At Marsh Yard, suppose the pharmacy route worked, but the departure signs were difficult to see after dark. The correction needs an owner, a revised sign specification and confirmation in the next budget. "Improve communication" leaves the next team to rediscover the actual problem. Ask affected people whether the proposed correction addresses what they experienced.

Use the post-event report guide to connect that operational review with the event's actual costs and result. Keep forecasts separate from what was paid. If the neighbourhood arrangements cost more than expected, establish whether the scope changed, a supplier quote omitted something or the original allowance was unrealistic.

Send a brief factual follow-up where appropriate or required. Thank people for specific input, state the changes made and explain unresolved actions with their expected next step. Avoid turning it into a claim that the event benefited every local business. You would need evidence to make that claim, and a good relationship doesn't require pretending everyone experienced the same afternoon.

Before taking another booking, check what has changed around the site. New occupants, construction, transport changes or a different programme may make last year's arrangements unsuitable. Use the previous record to ask better questions. Then have the people responsible confirm the plan for the event you're actually going to run.

Prepare a short agreement summary

Keep the detailed plan, correspondence and approvals behind a concise summary that the organiser, landowner and affected people can understand. Use the form required locally where one exists. Otherwise, the following structure gives your discussion a practical starting point without pretending to be a legal contract.

Begin with the organising business, named liaison lead, event location and dates. State the complete occupation period and identify the current site plan. Explain that the summary records operational commitments alongside the separate permissions and conditions that apply. If someone is being asked to sign, make the intended meaning clear and obtain appropriate advice about the document.

Next describe the people and areas consulted, the methods used and the issues still open. Keep the record accurate about participation. "Comments received from nearby residents and businesses" is safer and more informative than "approved by the community" when there was no process establishing that claim.

List the confirmed arrangements by activity. For deliveries, give the route, window and owner. For access, identify the confirmed procedure and person handling exceptions. For sound, point to the approved technical plan and explain the public contact. For departure and cleaning, describe the affected area, operating period and check. Identify any action that still needs another party's confirmation so nobody mistakes a proposal for an arrangement that is ready.

Finish with the contact hours, who handles an unresolved concern, the change procedure and post-event follow-up. Identify the deputy and the point at which responsibility transfers during removal. Keep emergency instructions distinct. Add a version date so a resident, contractor or duty manager can tell whether they are looking at the current information.

Before the notice goes out, ask your duty manager to work through it using an actual concern raised during consultation. They should be able to identify who acts, find the current instruction and explain what happens next. If they can't, fix that missing part while the site is still quiet and your neighbours are still being asked to trust the plan.