How do you delegate event decisions beyond the founder?

You're trying to confirm tomorrow's programme, but your phone keeps filling with questions. Can production approve the extra delivery charge? Can the ticket team correct a booking? Can the sponsor manager promise a different position for the sponsor's stand?

You've hired people to handle those jobs. Somehow, you're still making every decision inside them.

The way out is to agree what each person can decide before the questions arrive. Name an owner for each recurring decision, describe their limits, and tell everyone which changes need somebody else's agreement. Give them a reachable backup when that owner is unavailable. Then let them use the authority you've given them.

An event decision authority matrix is simply a record of those permissions. It connects a specific decision with a named person, the conditions they must check and the point where they need to refer it. You can keep it in a spreadsheet or shared document. What matters is whether someone can read it and know what they're allowed to do.

For a paid event, this protects more than your diary. A rushed decision can add an unplanned supplier commitment, change what buyers receive or promise something you can't deliver to a sponsor. The useful balance is to let your team handle ordinary work while keeping consequential changes with the people equipped to judge them.

Start with the questions people already bring you

The first thing you want to do is look at your recent messages. Find the decisions that repeatedly wait for you, including the ones you answer almost without thinking. Those are good candidates for clearer instructions or delegated authority.

Be specific. "Production" is a department. "Approve an additional delivery charge for equipment already in the agreed production specification" is a decision. You can define conditions for the second one. The first could mean anything from ordering batteries to replacing the stage.

Ask your leads where they get stuck. Sometimes they're waiting for your permission. Sometimes they're waiting for information that only you have, such as an unrecorded promise to an artist. Delegation won't fix missing information. Put the promise into the working plan and resolve any conflict before expecting a lead to act on it.

You may also discover that people ask because earlier decisions were reversed. If a production manager was told to choose a supplier and then criticised for choosing the one you wouldn't have chosen, asking you next time is a reasonable response. The written permission needs to agree with how you behave afterwards.

Make your first list manageable. Include repeated purchasing decisions, ticket exceptions, programme adjustments and sponsor delivery changes where they genuinely create delays. Leave out tasks that already follow a clear instruction. Someone printing an approved sign doesn't need a separate decision record unless they're also choosing its wording, cost or location.

For each candidate, describe what could go wrong if the answer is late, incorrect or made without the right information. A late stationery order and a changed admission arrangement have different consequences. They shouldn't receive identical permission merely because both cost less than your purchasing limit.

You aren't trying to eliminate every question. A lead raising an unfamiliar risk is doing something useful. The goal is to stop requiring the founder's attention for decisions another qualified person can make within conditions the business has already accepted.

Separate doing the work from choosing what happens

A responsibility list tells you who prepares the programme, contacts suppliers or runs admission. It may still leave nobody authorised to choose between two options. That's why a team can look well organised and continue forwarding every unresolved question to its founder.

Take a speaker cancellation. Your programme coordinator can contact potential replacements, gather availability and update the draft running order. That doesn't necessarily give them permission to replace the advertised headline session or agree a new fee. Name the person who makes that decision and the information they need.

You can use a formal management method if your team already knows one. Bain's explanation of decision roles distinguishes recommending an action, contributing information, providing required agreement, deciding and carrying it out. The useful idea is that these are different jobs, even when a small team combines some of them.

For most event teams, plain words are enough. Write "Maya recommends the replacement, Sam approves the commercial change, and Maya instructs the supplier." Add whose agreement is required before that approval becomes usable. If the venue must accept a changed installation, Sam's spending permission doesn't settle the venue's requirements.

Be careful with the word "consult". A person whose advice should be considered is different from someone whose approval is a condition of proceeding. If the technical lead hasn't accepted a proposed equipment substitution, you can't treat their silence as agreement because the purchase owner wants to move quickly.

A lead can own the final business choice while other people retain authority over matters within their responsibilities. That isn't a contradiction. The business may choose whether to purchase an additional screen. A competent technical team and the venue still determine whether the proposed installation is acceptable under the agreed arrangements.

Our guide to dividing work between an agency and your team covers the wider delivery split. Use your decision record to resolve the smaller questions inside that split, especially who can commit money or change an instruction without returning to the founder.

Write permissions around a recognisable decision

A useful entry should survive being read by someone who missed the planning meeting. They need to understand the permission without knowing what you meant when you said, "Use your judgement."

Record the decision in ordinary language, followed by the person who holds it now. A role can help identify their responsibility, but include a name and contact route for the actual event. "Ask operations" becomes frustrating when several people are wearing operations badges and none thinks they own the answer.

Then describe the permitted scope. A production lead might approve equivalent consumables for the existing installation. That doesn't include changing the installation, adding a new supplier agreement or accepting unfamiliar cancellation terms. Scope should describe the work and commitments, rather than relying on a loose word such as "minor".

Use the following fields as a starting point:

• Decision: the specific question this permission answers.

• Current decision owner: their name, role and agreed contact route.

• Allowed action: what they can approve or change without further commercial approval.

• Conditions: the specification, policy, contract or other requirements that must remain satisfied.

• Spending limits: the complete cost per request and any cumulative allowance.

• Required agreement: whose explicit acceptance is needed and for which part of the decision.

• Referral conditions: what takes the request outside this permission.

• Backup: who acts during an agreed absence and how that cover starts and ends.

• Record and notification: where the decision goes and who needs the resulting instruction.

• Validity: the event, phase, version and dates covered by the permission.

You don't need a long paragraph in every field. "No change to the advertised programme" is a clear condition. "No significant programme changes" leaves the lead deciding what significant means at the exact moment you're hoping to avoid confusion.

Write the limits with the owner, rather than giving them a finished document to sign. They may spot a missing delivery charge, a supplier approval condition or a decision they're not trained to make. You need that information before issuing the permission to other teams.

For decisions that affect contractors, check the arrangement against their contracts and confirm who can instruct them. An internal record doesn't automatically change an existing supplier agreement or establish a person's authority to bind the business in every situation. Resolve that with the appropriate commercial or legal advice where needed.

When the entry is ready, ask the owner to explain a permitted decision and an exception in their own words. If they still need you to interpret both, the wording needs another pass. This is a useful understanding check, without turning a simple working document into a training course.

Make spending limits work against the full commitment

"You can spend up to $500" leaves several unanswered questions. Is that per invoice, per supplier or across the event? Does it include delivery and tax? Can the person use it for any purpose? What happens after somebody else has used part of the same allowance?

Define the limit against the total commitment you are approving. If equipment costs $300 and the required delivery costs $90, the request is $390. A later invoice for delivery doesn't create a second, unrelated decision. If the quote leaves an important cost open, get it clarified before treating the request as within a known limit.

Also decide how related requests accumulate. A lead with a $500 limit could approve several individually small orders and create a much larger bill. Set a cumulative allowance for the relevant event and scope, and show how much is already committed. Don't wait for invoices to arrive before reducing the available balance.

The Charity Commission's financial control guidance calls for written authority limits for orders and payments, agreed budgets and checks against what was ordered and received. That guidance applies to charities in England and Wales. The same practical distinctions are useful when designing controls for a commercial event, without treating charity rules as your business's legal requirements.

Approval to order and authority to release payment should be clear separately. Your producer might approve a purchase within their allowance, while finance checks the supplier details and pays under the business's banking arrangements. A company card in someone's pocket doesn't settle whether they're allowed to make a particular commitment.

Choose limits from your event's budget, available cash and risks. There is no useful universal dollar threshold for an event lead. A sum your larger series can absorb may undermine the margin on a small workshop, and a cheap change can still breach a venue condition or a sponsor agreement.

The cumulative allowance also needs a defined source. If production can use $1,200 of a $3,000 extra-cost reserve, that $1,200 is part of the $3,000. It isn't additional money. Other departments need to see the shared reserve reducing as commitments are approved, even if their own delegated allowance hasn't changed.

Keep cash timing visible. A purchase can fit the remaining cost budget and still require payment before the event has enough cleared funds. Decide who confirms affordability and what information the decision owner can rely on. Expected ticket sales aren't money already available in the bank.

Where the underlying forecast changes, update the information available to leads. A delegated permission based on yesterday's reserve can become misleading after a major supplier increase. Our guide to reviewing event spending against budget explains how to include agreed work and expected remaining costs in that review.

A worked decision record for a paid conference

Let's use a fictional event business producing Northbank Forum on 20 November 2026. All names, permissions, times and USD figures below are invented to explain the method. They're not recommended staffing levels, spending benchmarks or customer results. The example covers selected decisions, rather than the event's complete operating or emergency plan.

Leila is the founder. Sam is the event director, Maya leads production, Jo leads attendee support and Omar handles finance. Nia can cover Sam's director responsibilities during an expressly agreed handover. The venue and specialist teams retain their separate responsibilities under the event's arrangements.

The business has set aside a $3,000 reserve for approved additional event costs. For this simplified example, that amount is available in cleared cash after all other recorded commitments, and the cost forecast supports using it. Every request below includes its required tax, delivery and labour. No separate fee is waiting to be added later.

Leila approves the initial permissions on 19 November. Sam can approve an eligible additional delivery request up to $1,000, subject to the remaining shared reserve and the other conditions below. He cannot use that power to change the advertised event offer or override specialist requirements. Requests outside his permission go to Leila or the person separately authorised for the matter.

Production purchases

Maya can approve additional consumables or delivery needed for the already agreed production specification. Her limit is $500 for one complete request and $1,200 cumulatively for this event. She checks the current commitments record before approving, and Omar records the commitment against the reserve.

The permission excludes equipment substitutions that change the agreed technical specification, new contractual terms, changes to venue access or installation, and alterations affecting the programme or attendee arrangements. Those need the relevant review and commercial approval. Maya doesn't make them eligible by fitting the price below $500.

When a request would exceed her cumulative allowance, Sam can consider a specific exception within his own authority. His approval must name the request and the revised authorised total. It doesn't automatically increase Maya's standing allowance for every future purchase.

Attendee support

Jo can apply the business's documented ticket-correction procedure to verified bookings. She can also authorise eligible goodwill gestures up to $150 per case and $400 in total for the event, recorded against the same reserve. These gestures are discretionary measures within an agreed policy, not a limit on a buyer's legal rights or contractual entitlements.

Jo refers requests outside that procedure, changes to admission conditions and proposed compensation beyond her permission. Relevant legal obligations and ticket terms still apply. A customer with an urgent access need receives the appropriate support route rather than a debate about whether Jo has unused goodwill money.

Changes to the event offer

Leila retains approval of cancellation, postponement and changes to the advertised core offer in this example. Sam gathers the relevant delivery, financial and buyer information and presents a recommendation. The business obtains professional advice when the proposed decision needs it.

Leila also retains changes to sponsor exclusivity and new sponsor promises outside the signed package. The sponsor manager can coordinate existing deliverables, but can't sell a conflicting entitlement because the proposed activation costs nothing to install. Contractual commitments matter independently of production spend.

Information and payment

Omar maintains the shared commitment balance and checks payment details under the business's payment procedure. He doesn't become the approver of every operational choice because he records it. If a request fails the affordability check, the decision owner must resolve it before ordering.

Maya, Jo and Sam each record their decisions in the same agreed location. For the people actually doing the work, the final instruction identifies the decision, approved scope and current version. Nobody has to infer approval from an enthusiastic message in a separate group chat.

See what happens when three requests arrive

At 09:10 on 19 November, Maya receives a $390 request for additional consumables and their delivery. The items support the existing specification, all required conditions remain satisfied, and no prior additional production spend has been committed. Maya approves the request within her permission and tells the supplier to proceed.

Omar records $390 against the $1,200 production allowance and the shared $3,000 reserve. Production has $810 left under Maya's cumulative permission. The shared reserve has $2,610 left. These balances answer different questions about the same commitment, so nobody adds the two deductions together as though the business spent $780.

At 10:00, another eligible request arrives for $440. Maya checks the live balance and approves it. The production total becomes $830. That leaves $370 under her cumulative permission and $2,170 in the shared reserve. Both requests were individually below $500, and their combined cost remains below $1,200.

A third request at 10:35 is $460. It covers eligible additional delivery for the same agreed production, but would bring the production total to $1,290. Maya can't approve it herself. The price is below her individual limit, yet the cumulative total would exceed her allowance by $90.

She sends Sam the complete request, the current $830 commitment, the proposed $1,290 total and the remaining reserve. She explains the operational reason, the supplier's actual decision deadline and the consequence of declining. Omar confirms the current affordability information. No work on the third request has been instructed yet.

Sam considers it under his separate permission. At 10:50 he approves this specific $460 request, after confirming the required conditions remain satisfied. His note authorises a $1,290 production total for the listed requests. Maya then instructs the supplier, and Omar updates the shared reserve to $1,710.

The example doesn't assume savings, reimbursement or new ticket revenue. It simply shows an approved additional commitment. When the invoice arrives, finance matches it to the approval rather than deducting the same $460 from the reserve again.

Maya's next purchase still needs a fresh check. Sam has authorised these listed requests to total $1,290, not given her another $1,200 to use. Further production requests require Sam's approval under the current arrangement unless the business explicitly issues a new delegation. Splitting a connected request into smaller orders wouldn't change that.

Check decisions that cost nothing today

A financial limit is only one part of delegation. Some of your most consequential requests arrive with no extra invoice attached. Moving a sponsor stand, admitting additional guests or removing a session can change the event even when the person asking calls it free.

Suppose Northbank Forum's sponsor manager asks to move a contracted stand into a different position. The existing display can be moved without an additional supplier charge. That settles the immediate price, but leaves the actual decision open. Does the position match the sponsor's contract? Does it affect another sponsor's entitlement? Has the venue accepted the proposed use of that area?

The sponsor manager should gather those answers before promising the position. Maya checks the installation implications with the appropriate people, and the venue reviews the matters it controls. The person holding commercial authority then decides whether the business can offer the change. If it changes exclusivity or creates a promise outside the signed package, Leila retains that decision under this example's permissions.

Until those conditions are resolved, the response to the sponsor should describe a proposal being checked. Don't say the move is confirmed and leave production to explain later why it cannot happen. An agreeable conversation with the sponsor manager is different from a deliverable the business has approved.

The same reasoning applies to guest admission. A colleague may say that another guest costs nothing because the event has empty seats. But the team still needs to consider the authorised attendance arrangements, ticket inventory, eligibility and any promised services. An empty-looking room isn't permission to create an admission entitlement.

You can delegate a routine guest-list process with appropriate limits and checks. The person administering it should know who can authorise an addition and how the resulting entry is recorded. That permission doesn't expand approved capacity or allow them to disregard access and security arrangements. Those conditions remain with the people responsible for them.

For programme changes, describe the difference between coordinating an existing plan and altering what was advertised. A programme lead can contact a speaker about the confirmed arrival time. A request to remove their session raises a different business decision, even if no cancellation fee applies. Consider the buyer promise and the relevant agreements before deciding who can authorise it.

This is where a vague instruction to escalate only expensive changes fails. Add observable referral conditions for non-financial consequences, such as a new sponsor entitlement, changed admission conditions or an alteration to an advertised core session. Your team can then spot the boundary without guessing what the founder considers important.

Use a short record when you need an exception

Keep the exception request short enough that people will use it during a busy planning day. It should still contain enough information for the approver to decide without restarting the investigation. For the third production request, Maya's entry could read as follows.

Request awaiting approval, 19 November at 10:35

Decision requested: approve the complete additional delivery request for $460 under the existing production specification. Current additional production commitments total $830. Approval would increase that total to $1,290 and leave $1,710 of the shared event reserve.

Reason for referral: the request exceeds Maya's $1,200 cumulative permission, although it is below her $500 individual limit. Omar has confirmed the current balance and affordability information. Required operational checks are complete and the specification and venue access conditions remain unchanged.

Recommendation: approve the listed request. The supplier needs an answer by 11:15 to retain the agreed delivery slot for 20 November. If declined, that slot is lost and Maya must obtain a costed, acceptable collection alternative before treating transport as resolved. Maya has not instructed the work and will release it only after the authorised decision.

Decision recorded at 10:50

Sam approves the specific $460 request under his director permission. The authorised production total is $1,290 for the listed requests. Maya communicates the approval to the supplier, and Omar records the additional commitment once. Further production purchases require a new approval under the current arrangement.

This record supports the purchase approval. Keep any separate contractual acceptance, supplier acknowledgment and payment evidence the business requires. If the scope or total price changes afterwards, return the changed request to the appropriate owner before proceeding on the assumption that this approval covers it.

Escalate with a recommendation and a real deadline

When a request falls outside someone's permission, make the next conversation useful. "Can we spend more on production?" sends the investigation back to the founder. Explain what needs deciding and what will happen under the available options.

A practical referral includes the requested action, complete cost, current commitment, relevant deadline and reason it exceeds the existing permission. Add the people whose agreement is required and whether they've provided it. Finish with the owner's recommendation and the consequence of waiting or declining.

For the $460 request, Maya might explain that the additional delivery is needed to move the already approved equipment within the confirmed access window. In our example, the supplier's dispatch allocation closes at 11:15. That time comes from the fictional supplier's schedule, not a standard response window. If declined, the team must establish another acceptable arrangement before treating delivery as resolved.

That detail matters more than attaching an arbitrary "urgent" label. Ask the supplier which part of the deadline is fixed and what alternative remains. You may still need a fast answer, but at least the approver knows what the timing is based on. Don't invent a countdown to force a decision.

Agree a route if the owner doesn't respond in time. That could mean contacting the named deputy, using a tested alternative communication method or referring to a higher commercial approver. The route depends on the event and issue. Silence isn't approval to create a new commitment.

Keep ordinary commercial referrals separate from emergency actions. Staff facing immediate danger must follow the agreed emergency procedures, including raising the alarm and summoning urgent assistance as appropriate. They shouldn't wait for the founder to answer a spending question before taking those actions.

Great Britain's Health and Safety Executive says event emergency plans should define responsibilities and staff should understand what to do and who gives instructions. Have the people responsible for your event's emergency arrangements define that authority. A commercial decision record should reference those arrangements and preserve them.

The founder also needs a workable standard for accepting referrals. If a lead supplies the agreed information and a recommendation, respond with a decision or a specific missing condition. Asking everyone else what they think, without naming whose answer settles the matter, recreates the original delay at a higher level.

Treat an absence as a transfer of responsibility

Naming a deputy isn't enough if nobody knows when the deputy becomes the decision owner. Sam and Nia can both be available and still leave Maya wondering whose approval to seek.

For Northbank Forum, Sam plans to be unavailable from 11:00 to 12:30 on 19 November. Before leaving, he gives Nia the current permissions, commitments and unresolved requests. At 10:55, Nia confirms she accepts the specified cover. Sam tells the affected leads when it starts and which contact route to use.

Nia receives Sam's defined director authority for that period. She doesn't receive Leila's retained powers, and she doesn't gain an unused version of the reserve. The shared reserve remains $1,710 after the three production requests. Existing commitments and specific approvals continue to count during the handover.

If a new request arrives, Nia checks the same conditions and records her decision as the current owner. Sam doesn't approve it independently through a private message while Nia is considering it. If he unexpectedly intervenes, they reconcile who is acting and tell the team before issuing conflicting instructions.

At the return, Nia briefs Sam on decisions made, open requests and any changed balance. Sam explicitly accepts responsibility again, and the affected leads hear that the cover has ended. The handover should also state what happens if he doesn't return at the expected time, rather than leaving authority to expire silently.

Use the same principle for breaks and changing event phases. The person covering a show-period decision may not have authority to approve later equipment removal or venue handback. Identify those responsibilities in advance and keep the transfer clear to the people who rely on it.

Match software access to the job you've delegated

A person can have authority on paper and still be unable to do the job because the only usable account belongs to the founder. The reverse also happens. Someone receives broad account access for one task and assumes they can change everything the account allows.

Check both sides. The decision record says what the business authorises. The software account determines which actions the person can technically perform. Where permissions are broad, make the operational limits explicit and use appropriate checks. Don't describe a written policy as though it creates a restriction the software doesn't enforce.

For ticket operations, Loopyah lets you add event admins and door staff without sharing your login. Door staff can have check-in-only access and scan QR tickets from their own phones. That gives a scanner a practical way to carry out their assignment while keeping wider administration separate.

Your ticket-exception policy still needs a decision owner. A successful ticket scan doesn't answer whether someone should receive a discretionary remedy, whether a booking can be corrected under your policy or whether an unusual admission request is acceptable. Brief the team on the action they can take and where unresolved cases go.

The same applies to attendee updates. With Loopyah's attendee email tools, a teammate can build and send campaigns without using your login, and send a test before the audience receives the message. Decide separately who approves a consequential programme change and its wording before the teammate sends it.

Confirm access before the event, using the accounts and devices people will actually work with. Check the appropriate process for removing access when someone's assignment ends. A former contractor shouldn't remain your accidental backup because nobody reviewed who could still enter the account.

Keep supplier instructions consistent with the approval

A supplier needs to know who can authorise extra work and whose instruction releases it. If everyone can request changes directly, your internal matrix won't stop an enthusiastic colleague from creating a confusing conversation or disputed charge.

Tell suppliers the agreed arrangement at the start. For Northbank Forum, Maya coordinates production instructions. She can authorise requests within her written permission; requests outside it need the appropriate approval before she releases the work. Omar handles payment checks. Leila's attendance at the venue doesn't turn every passing comment into a production instruction.

For an approved change, identify the deliverable, complete price, relevant timing and any conditions still preventing work from starting. "Budget approved, subject to venue acceptance" means the commercial part is approved. It doesn't mean the supplier should start installing while everyone waits for the venue.

Great Britain's HSE event management guidance distinguishes coordinating the overall work from taking responsibility for every specialist task. It also calls for competent people and suitable supervision. Keep those distinctions intact when assigning authority. A spending approver doesn't become the person qualified to accept technical work merely by authorising its cost.

Protect payment checks even when a request appears to come from the founder. The FBI's business email compromise guidance advises verifying payment requests and changes to account details through a separate, trusted contact route. An urgent message with Leila's name on it shouldn't bypass Omar's verification procedure.

After approval, confirm that the instruction reached the people doing the work. The decision owner confirms what was authorised, the supplier acknowledges the instruction, and the relevant lead checks delivery. If the supplier reports a different price or scope, resolve that difference before treating the original approval as covering the new arrangement.

Rehearse the awkward decisions before doors open

You don't discover whether a delegation works by asking everyone if they've read it. Use a few situations that resemble the questions your team actually receives. Ask the person holding the decision to explain what they would do, who they need and what they would record.

Start with an ordinary request inside the limit. Then change one condition. The price stays the same, but the equipment is a different specification. Or the purchase fits the per-request limit, but earlier commitments have used most of the cumulative allowance. Can the lead explain why the answer changes?

Try a disagreement between functions. A sponsor wants to move a stand, the sponsor manager sees a relationship problem, and production sees an installation problem. The right outcome is a named business decision after required checks, not whichever person reaches the founder first.

Also test an unavailable owner. The team should be able to find the current deputy, verify the scope of their cover and contact them. If everyone reaches for an old screenshot of a phone list, update the working source and remove the ambiguity before the shift begins.

Put the confirmed instructions into your event team briefing. Most crew members don't need every department's purchasing conditions. They need their own permitted actions, the situations they must report and the names of the people deciding those matters today.

Keep the full record available to leads, and give suppliers the permissions and contact details relevant to their work. If you amend a permission after the briefing, identify what changed, when it takes effect and who acknowledged it. A new version sitting in a folder doesn't establish that the person currently giving instructions has seen it.

The founder has to honour the arrangement too

Once you delegate a decision, let the named person make it within the conditions you've agreed. If the answer must still be exactly what you would have chosen, you haven't delegated much. You've asked someone to predict your preferences before asking for approval.

You can review the reasoning without taking every choice back. Ask whether the lead used current information, stayed inside the permission and recorded the commitment. A decision can satisfy those tests even if you prefer another supplier or would have chosen a different eligible option.

When new information makes a decision unsuitable, explain what changed and update the instruction. Don't quietly message the supplier with the opposite answer. That teaches everyone that the written owner isn't the real owner and encourages them to keep going directly to you.

Founders also create exceptions by promising favours. An extra sponsor entitlement agreed over lunch may affect exclusivity, staffing or inventory. Record it through the same process, with the relevant checks, before the team treats it as something it must deliver. Personal enthusiasm doesn't reveal the operational consequences.

If someone asks you about a decision that belongs to Maya, send the question to Maya and let her answer. Stay involved where you're the required approver or where the situation exceeds her permission. Otherwise, repeated rescue messages make the bypass more attractive than the agreed route.

There's an equally important responsibility on the other side. People need to raise a genuine uncertainty rather than conceal it to appear independent. Make it acceptable to say that a condition isn't met or that a decision falls outside their competence. Confidence is useful when it's backed by the right information and authority.

Review the exceptions and change the next delegation

After the event, compare the written permissions with the decisions people actually made. Look at requests that waited, decisions reversed, commitments discovered late and occasions when the founder intervened. Use the records to understand what happened before deciding the team needs tighter control.

Some referrals were appropriate. A material programme change may always deserve a senior business decision. Others reveal an incomplete permission. If Maya repeatedly sought approval for ordinary delivery charges within a stable specification, you may be able to define that scope more clearly next time.

Check the workload created by delegation as well. A lead covering production, attendee support and every exception may become a new source of delay. Reassign complete decision areas where the knowledge and availability support it. Adding another approver to every request isn't the only response.

For a small event business, you can begin with the founder and one capable event lead. Delegate a limited set of recurring decisions, keep meaningful review and payment checks, and name a realistic backup. Don't invent several job titles to make a tiny team look like a larger organisation. The people must actually be available to do the work.

Use the next event's budget and conditions to issue fresh permissions. A successful allowance at Northbank Forum doesn't prove that the same dollar amount, supplier scope or deputy arrangement fits a different venue or ticket offer. Preserve what you learned, then check what has changed.

Before your next planning meeting, choose one question that still comes to you unnecessarily. Sit down with the person best placed to decide it and write the allowed action, conditions and referral point together. Confirm the information and access they need, tell the affected team, and let that person handle the next request within the agreement.