How to divide work between an event agency and your own team

You've hired an event agency to take work off your team. A month later, your marketing manager is still chasing speakers, the agency is waiting for ticket prices, and two people have asked the same venue for the same quote. Everyone is busy. You're paying for some of that work twice.

The useful division starts with decisions. Your team should retain control over the event's commercial offer, budget and promises to buyers. The agency should own the agreed delivery work, with enough authority to finish it. For every task that crosses between you, name the person doing the work, the person approving it, the input they need and the deadline for that input.

That sounds straightforward until someone writes "marketing: shared" in a plan. Shared can mean collaboration. It can also mean nobody knows who sends the email.

Here's how to make the split work for a paid conference, festival, workshop series or other ticketed event, including the awkward cases that tend to surface after the agency starts.

Keep the business decisions with the people carrying the risk

Start by listing what your event business is promising and what it can afford. Who is the event for? What will a ticket buy? Which costs are already committed? What would make you cancel, reduce the production or change the programme?

Your agency can help answer those questions. It can challenge a weak budget, recommend a different venue and show you the cost of a decision. But somebody inside your business needs to approve the answer, because your business will live with it after the agency contract ends.

Suppose you're producing a paid industry conference. The agency suggests a more expensive venue with better production facilities. That's useful advice. Whether the improvement justifies a higher ticket price is your commercial decision. The agency can prepare the comparison and negotiate the venue terms after you choose. It shouldn't have to guess how much loss you're prepared to accept.

Keep a named internal owner for the event budget, ticket offer, sponsor promises and decisions about material changes. That can be the founder in a small event business. In a larger team it might be the event director, supported by finance and marketing. The title matters less than their authority and availability.

This isn't an argument for approving every operational detail. An agency that must ask permission to move a crew call by a few minutes cannot manage delivery effectively. Keep approval of the commercial conditions and delegate the work inside those conditions. Be specific about the exceptions that require another decision.

If you're still deciding which services you need, our guide to event services and on-site execution explains the different jobs. Once you've hired the agency, the next question is who actually owns each one for your event.

Divide complete jobs before dividing individual tasks

An agency can manage venue sourcing, production, speaker logistics, registration support or a broader programme of delivery. None of those labels tells you exactly what you're buying. "Speaker management" might mean travel bookings, or it might include invitations, contracts, presentation collection and rehearsals.

Ask the agency to describe the finished work. Then ask what it needs from you to produce that result. If the answer is a supplier-ready programme, your inputs might include confirmed sessions, speaker agreements and the latest approved timing. If the agency also books travel, identify who approves the cost and handles a speaker who changes their plans.

Try to keep connected tasks together when the same person has the knowledge to complete them. Giving the agency venue logistics while your team separately negotiates every delivery slot creates avoidable coordination. Let the agency manage the slots within venue rules, and tell suppliers whose instructions to follow.

There will be good reasons to retain parts of a job. Your founder may have the relationship needed to secure a headline speaker. That's fine. Write that the founder confirms the booking and hands over the signed agreement, technical requirements and direct contact. The agency then manages the agreed logistics. Put a date on that transfer.

Avoid an arrangement where both sides keep doing the whole job "just in case". If your team checks every supplier response, rebuilds the schedule and independently calls every speaker, the agency hasn't removed much work. Decide which checks you need to protect the event and which repeat delivery you're already paying for.

The UK Government Commercial Function's guidance for people managing supplier contracts calls for clear delivery responsibilities, understood obligations and agreed performance measures. It's public-sector guidance, but that practical discipline is useful when you're buying event services too.

Write responsibilities so another person could follow them

A responsibility list works when a colleague can use it without knowing the conversations behind it. "Client to provide content" fails that test. What content? In what form? Who decides it is complete?

Use a short entry for every important deliverable. Record the person preparing it, the person accepting it, the inputs needed, the due date and what counts as finished. Add who covers an absence and where the current file or decision lives.

For a conference registration page, that could read as follows. Your marketing manager supplies the approved ticket description, prices, refund wording and programme highlights. The agency builds and checks the page if that work is in its contract. Your event director approves the buyer-facing offer before publication. The marketing manager tests the live purchase journey and confirms that the page matches the approved information.

That's a suggested division, rather than a rule that the agency must build your page. Your own team may already run ticketing well. In that case, keep page setup internally and give the agency the access or reports it needs for its work. Paying the agency to recreate a working internal process needs a reason.

For a sponsor deliverable, write who confirms the sold entitlement, who collects the artwork and who checks that it appeared in the promised location. "Agency handles sponsors" leaves open whether the agency is selling packages, fulfilling them or merely placing logos.

You can use a responsibility table if it helps. Avoid spending the kickoff meeting teaching everyone a set of initials. Plain words such as "prepares", "approves" and "needs input from" usually reveal the problem faster. The table is useful because the work is clear, not because the headings sound formal.

Make the client inputs part of the schedule

Agency deadlines depend on your deadlines. If your team confirms the programme late, the agency may be unable to finish the production schedule on time. Calling the agency's task overdue doesn't fix the missing information.

Build the schedule backwards from the point when a decision becomes expensive to change. Printing, equipment bookings, speaker travel and venue access all have their own constraints. Ask the agency to show which inputs must arrive before those commitments, then agree internal owners who can actually provide them.

For example, the agency needs the final session order before it can prepare speaker calls and technical cues. Your programme lead needs speaker confirmations before approving that order. The confirmation deadline belongs in the same plan as the agency's delivery deadline. Otherwise you see the final delay without seeing what caused it.

Check what "approved" means at each stage. A programme may be approved for ticket sales while individual presentation files are still outstanding. A sponsor logo may be approved for the event page but unsuitable for a large printed sign. Name the use and the version, so somebody doesn't treat an early approval as permission for every later output.

Be honest about your team's capacity. A marketing manager who already has a full campaign workload may not be able to review a long supplier pack that afternoon. Agree a review window before booking the delivery date, and tell the agency when the approver is unavailable.

If an input slips, the owner should report the consequence while there are still choices. The agency might proceed with a previously approved layout, delay printing or quote for an urgent revision. Decide which response is acceptable. Silence should trigger a follow-up to the named backup, rather than an invented assumption about what the client wanted.

Separate creative feedback from permission to proceed

An agency can receive plenty of feedback and still have no approval. Your founder likes the concept, sales wants more sponsor space, and marketing says the copy needs another pass. The agency now has comments from everyone and a decision from nobody.

Choose one internal person to collect that feedback and send a resolved response. Other people can contribute their expertise, but the agency shouldn't have to negotiate your internal disagreements through separate messages. Where two requirements conflict, the internal owner decides which has priority or takes the decision to the person with authority.

Be clear about what the agency is being asked to do next. "Looks good" can mean the direction is right, the copy is approved, or the artwork is ready to print. Use the actual instruction. If printing can begin, say so and identify the version. If the ticket price is still provisional, say that too.

For consequential approvals, ask for the information needed to decide. A venue recommendation should show the cost, important exclusions and relevant operating restrictions. An extra production element should explain why it's needed and what happens if you decline. You shouldn't have to approve a vague idea and discover its cost later.

Some decisions can be delegated in advance. You might allow the agency to make equivalent substitutions within an approved specification and spending limit. Define what equivalent means for the work concerned. A different cable supplier is a different decision from a different sound system or an inaccessible replacement room.

Keep decisions in the agreed shared record even when the conversation happens on a call. A short note naming the approver, decision and version is enough for many operational matters. Match any formal approval requirements in the contract. The aim is to make tomorrow's work follow today's actual decision.

Decide who directs suppliers and who pays them

Supplier relationships get confusing when the client signs the contract but the agency manages the work. A venue coordinator hears one instruction from your operations lead and another from the agency producer. Both believe they're helping. The crew gets two plans.

Tell each supplier who gives day-to-day instructions, who can approve a change and who is responsible for payment. These can be different people. The agency can coordinate delivery under a contract your business holds, provided the supplier and your internal team understand that arrangement.

If the agency contracts suppliers itself, ask how the charges appear in your budget. Check whether the agency fee includes sourcing and management, whether supplier costs carry a markup, and how cancellations or substitutions are handled. You need to understand the agreed charging method before deciding whether another supplier task is extra.

Don't assume your internal team can request additional work directly because it holds the budget. A sponsor manager asking the production supplier for extra signage may create cost and installation work that the agency doesn't know about. Route the request through the agreed delivery lead and approval process.

Equally, don't make an agency responsible for a supplier you keep instructing independently. If your venue relationship is particularly sensitive, retain a named internal contact for commercial discussions and let the agency coordinate the agreed operations. Explain where those responsibilities meet and how disagreements will be resolved.

Our event production brief template helps describe what technical suppliers need to deliver. Use the same clarity in your agency arrangement. The brief describes the required event; the responsibility record tells people who supplies the information, checks the work and authorizes a change.

Agree extra work before it becomes an invoice

An event changes as you plan it. A sponsor buys a late package, a speaker needs a different setup, or you decide to add another ticketed session. The problem is rarely that a change exists. It's that the people requesting it don't know whether it changes the agency's fee.

Agree how the agency identifies additional work and what it must provide before starting. A useful change request describes the requested result, the reason, the extra fee or saving, any supplier cost and the effect on deadlines. Your authorized internal person then approves, declines or asks for another option.

Keep the agreed original work available for comparison. If the contract includes presentation collection, collecting those presentations is part of delivery. If you add a new stage with a separate speaker programme, the agency may reasonably need more staff time. Look at what changed in the required result before arguing about how many messages somebody sent.

Ask the agency to flag likely changes early. A task that is repeatedly being handled as a favour can become a dispute when pressure rises. Your team also needs to stop issuing casual requests that look small individually but collectively require another person.

The Government Commercial Function's contract and supplier management guidance includes controlling contract changes, reporting and managing risk. For your event, turn that into an agreed way to record a change and obtain approval while the choice still exists.

Set a separate rule for urgent on-site spending. Define who can authorize it, the limit and how the decision is recorded afterwards. Keep the event's safety procedures separate from routine commercial approval. A person responding to a dangerous situation shouldn't be waiting for a purchase-order conversation before following the emergency plan.

Keep ticketing accounts and buyer access under control

Your agency may need ticket-sales information to plan staffing, prepare badges or judge whether a campaign needs attention. That doesn't mean everyone involved needs the same account access. Start with the job each person needs to perform and grant access appropriate to that job.

Keep your business in control of the main organizer account and the people authorized to manage it. Agree who can change prices, issue complimentary tickets, process refunds and publish buyer communications. If the agency is doing any of those jobs, record the limits and the internal person who approves exceptions.

With Loopyah's event team access, you can add admins and door staff without sharing your login. Door staff can receive check-in access. That gives you a practical way to separate scanning tickets from broader event administration, instead of passing the organizer's password around before doors open.

Check your platform's actual permissions before assuming you can restrict individual actions. If a task requires broader access than you'd like, decide whether an internal person should do it, whether supervision is appropriate or whether the task can be handled differently. A responsibility list cannot create a permission the software doesn't provide.

Buyer data needs the same attention. An agency preparing registration materials may need names and ticket information. A production supplier generally doesn't need your complete buyer history. Agree the purpose of access, the necessary fields, how files can be shared and what happens when the job ends.

For UK operations, the ICO explains that controller and processor roles depend on the decisions organizations actually make about personal data. Don't assign those legal roles simply from the words "client" and "agency". Identify the processing involved and get the appropriate agreement reviewed for the jurisdictions where you operate.

Give attendee communication a named sender and approver

A programme change can require updates to the event page, a message to ticket holders and instructions for customer support. If the agency handles the operational change while your team handles marketing, the communication can be missed between them.

Decide who notices that a buyer needs an update, who writes it and who can send it. Include the deadline and the information needed to make the message accurate. A changed room may need an accessibility check. A delayed opening needs a confirmed time and instructions for people already travelling.

Keep routine messages separate from material changes to what people bought. You can approve a standard arrival email in advance and let the agreed operator send it when the details are confirmed. A cancellation message, changed ticket entitlement or refund announcement needs the appropriate internal decision before anyone improvises the wording.

Choose one contact route for attendee questions and make sure the people covering it have current information. Otherwise the agency tells buyers one thing at the registration desk while an internal support person repeats yesterday's policy by email. Record who updates the answer when a decision changes.

Where an agency processes buyer data on your behalf, the ICO's guidance on controller and processor contracts explains the written contractual requirements under UK GDPR. The practical responsibility discussion should include instructions, access and what happens to personal data when the work finishes. Apply the requirements relevant to your operation.

Don't let approval become a reason for silence when attendees need information. Agree a backup approver and prepare likely messages before the event. The person at the registration desk should know whom to call and what they can tell a buyer while the final decision is being made.

Set the on-site authority before anyone arrives

During planning, an unclear responsibility can wait for the next meeting. During load-in, it can leave a truck outside the venue while the crew waits to find out who is allowed to change the unloading order.

Name the person coordinating the site and tell your internal staff to route operational requests through that person. If the agency produces the event, its on-site lead needs a clear remit. Your team should still have a named person available for commercial or programme decisions beyond that remit.

Great Britain's Health and Safety Executive says organizers must coordinate work and manage overall event safety. It also distinguishes that coordination from responsibility for each contractor's specialist technical work. Hiring an agency doesn't justify treating every safety matter as someone else's concern. Confirm the actual duties with competent people for your event and location.

Agree who runs the site briefing, checks that contractors received the current plan and records changes during the day. Include setup and breakdown. Your internal team may focus on ticket holders, but the agency and suppliers will still be working after the audience leaves.

Make emergency responsibilities explicit. The HSE's event incident and emergency planning guidance calls for clear roles and staff who understand what to do. Your plan should identify who communicates with venue management and emergency services, who directs staff and how public information is handled.

Walk through realistic situations together. A speaker is late. A buyer disputes an entitlement. A supplier asks for overtime. A weather warning affects part of the site. These are different decisions with different owners. Testing them in advance shows whether the responsibility record works when people need an answer quickly.

Check that the split actually removes work

Before the first major delivery deadline, ask your internal leads what they're still doing. Compare the answer with what the agency is delivering. You may find a sensible quality check, a missing task or an entire job being done twice.

If marketing still rebuilds the agency's attendee email, understand why. Perhaps the agency lacks approved information. Perhaps the brief didn't explain your voice. Perhaps your manager doesn't trust the output. Each problem needs a different response. Quietly repeating the work leaves the fee unchanged and the cause unresolved.

Use the kickoff to review your recurring meetings too. The agency may need a short operational discussion with your event lead. It probably doesn't need every internal department in every supplier call. Invite people because they have an input or decision, and send the rest the outcome they need.

Review the split again when the event changes materially. Adding another venue or a second ticketed day can create work that no original assignment covers. Check whether the same people still have enough time and authority, rather than assuming the first plan will stretch indefinitely.

At the end, compare the agency's completed deliverables with the agreed scope and approved changes. Review internal effort as well as the invoice. An agency can be more expensive on paper while saving your team substantial work; it can also be reasonably priced while leaving your people to finish the job. You need both views to judge the arrangement.

Work through a real assignment together

Imagine you're hiring an agency for a paid weekend conference. Your own team has a programme lead, a marketing manager and a founder who approves spending. The agency has a producer and an event coordinator. This is a hypothetical example, but the questions apply to much smaller teams too.

Start with the programme. Your programme lead decides the sessions and secures speakers. The agency coordinator collects travel requirements and presentation files after receiving confirmed contacts. The producer checks whether the proposed timing works operationally. Your programme lead approves any change that affects what ticket holders were promised. Now everyone can explain their contribution without calling the whole job shared.

For sponsor signage, your marketing manager confirms the entitlement and obtains approved artwork. The agency prepares placement and production instructions. Your marketing manager checks the sponsor information, while the producer checks practical delivery with the venue. Identify the person authorized to release the files for production. A sponsor saying its logo is correct doesn't answer whether the proposed location is permitted.

Next, test a request arriving after approval. The founder wants an additional sponsor panel beside the stage. The agency checks venue restrictions, the supplier cost and any impact on installation time. The founder sees the complete proposal and decides whether to proceed. The producer then gives the supplier the instruction. Your marketing manager shouldn't also order the panel through another contact.

Finally, test absence. If the programme lead is travelling when a speaker withdraws, who can approve a replacement? Does the agency have the current attendee message and a contact who can authorize it? If nobody can answer, the original assignment needs a backup before the event, regardless of how complete the task list looks.

Notice when the agency needs a different brief

Sometimes a poor division of work is really a mismatch between what you bought and what you need. You hire coordination support, then expect the agency to redesign the programme and lead the commercial strategy. Or you pay for a senior producer while your own team continues to direct every supplier. Neither arrangement makes good use of the people involved.

Discuss the mismatch openly. Ask the agency which decisions it needs from you and which work it believes you still expect it to lead. Compare that with your team's understanding. Use a specific unfinished job to explain the problem, rather than a general complaint that the agency should be more proactive.

You may decide to expand the scope, remove a duplicated service or retain more work internally. Make that a deliberate change with a revised fee and delivery plan where needed. Don't keep the contract untouched while informally moving responsibilities until neither side recognizes the arrangement.

If the problem is capability, reallocating tasks on paper won't solve it. A coordinator who has never managed a technical build doesn't become a competent production lead because their name appears in the right column. Ask for the appropriate person or buy the specialist service separately, then connect their work to the overall plan.

Keep a separate note of assumptions you haven't confirmed. A venue may have offered access, or the agency may have priced staffing around a programme that is still changing. Assign someone to verify each assumption before the related commitment. Otherwise an agreed responsibility can depend on information neither side has checked. When confirmation changes the job, update the affected assignments and tell the people doing the work. They need the revised instruction before they start, especially where supplier bookings or buyer communications depend on it.

Finish with a handover your team can use

The agency's final report should help you run the next event. Agree the handover before the contract ends, including final supplier costs, outstanding commitments, editable files, approved materials and the operational lessons your team needs. Identify who accepts the handover and resolves missing items.

Close outstanding attendee and sponsor work explicitly. A completed event doesn't mean every refund query, promised report or supplier invoice has been dealt with. Assign each remaining task to a person and a date. Remove temporary access when the relevant work is complete, following your agreed retention and data-handling requirements.

For your next kickoff, bring the actual scope and walk through a ticket sale, a supplier change and an on-site problem. Ask who does the work, who decides and what information they need. Wherever the answer is "both of us", keep talking until each person can explain their own part.