HourTab

Blog › ICP guides

Event planner retainer: how to track and communicate the hours behind client event planning

July 12, 2026 · ~11 min read

Event planning has the most compressed visibility problem in professional services. The client attends the event, which is one day. What they do not see is the ten to fourteen weeks that preceded it: the initial venue research that reviewed fifteen properties to shortlist three, the site visits, the vendor vetting calls with five AV companies before selecting one, the forty-page logistics manual that no attendee will ever read, the three timeline revisions when the keynote speaker changed, the contingency planning for catering failures or weather issues, and the coordination emails that consumed forty-five minutes every time a vendor needed to confirm a setup window.

For event planners who work project-by-project with a flat fee, this invisibility is baked into the pricing model: the client pays for the outcome, and the planner prices to cover the hours whether they appear obvious or not. But for event planners on retainer — particularly those serving corporate clients with recurring events, monthly advisory needs, or complex multi-event annual programs — the billing model is hourly, which means the client is paying for work they cannot see. When the invoice arrives, the hours need to be legible.

This guide covers how event planners on retainer should structure their billing, what to track and log during a planning cycle, how to communicate hours so clients understand what they are paying for, and the most common tracking mistakes that create friction on event planning invoices.

Retainer vs. project: why the billing model changes the tracking requirement

The distinction between project billing and retainer billing in event planning determines everything about how hours need to be tracked.

In project billing, the planner quotes a flat fee for a specific event: a 150-person corporate dinner at a hotel, for example, might be quoted at $8,000 all-in. The client pays for the outcome, and the planner manages their time internally. If the planner spends 120 hours or 90 hours, the client pays the same amount. Tracking is a planning and profitability tool for the planner; the client never needs to see it.

In retainer billing, the client pays for the planner’s time: a monthly fee covering a defined hours cap for ongoing planning, advisory, and coordination work across one or more events. The client is paying for the time investment, which means the client has a legitimate interest in how that time is being spent. A retainer invoice for 35 hours of planning work without a work log is asking the client to trust a number they have no basis to verify.

This is particularly important in multi-event corporate retainers, where a planner might be simultaneously in early planning for a Q3 conference, mid-planning for a client dinner series, and close-out for a product launch event. The client may not know where in the planning cycle each event sits, and without a log, there is no way for them to understand why March consumed 42 hours and April consumed 18.

The phases of an event planning retainer and their hours profiles

Event planning work follows a predictable phase structure, and each phase has a distinct hours profile. Understanding these phases — and communicating them to the client before planning begins — prevents the invoice surprises that generate billing disputes.

Kickoff and discovery (weeks 10–16 before event)

The kickoff phase covers needs assessment, event scope definition, and initial research. Work includes structured discovery conversations with the client to understand event objectives, guest experience goals, logistical constraints, and budget parameters; initial venue research to identify the shortlist of properties that meet the criteria; and an early timeline that maps major planning milestones to the event date.

Hours in this phase: 15–25 per month. Most of this is research and coordination that produces no visible output until the venue shortlist is ready. Clients who see hours in this range before a single vendor has been contracted sometimes question whether the work has started yet. A work log that documents the scope-definition conversations, the venue research criteria, and the properties reviewed makes the kickoff phase legible.

Active planning (weeks 6–10 before event)

Active planning is the most hours-intensive phase that is not the event itself. Work includes site visits to shortlisted venues, vendor sourcing and vetting (catering, AV, photography, entertainment, florals, signage), contract negotiation and review, guest management and RSVP logistics, run-of-show development, and ongoing client communication. This is also the phase where scope changes are most likely to occur: the guest count increases by 30%, the venue changes, the keynote speaker cancels, or the client adds a reception that was not in the original brief.

Hours in this phase: 25–45 per month. The variance is high because scope changes and vendor coordination complexity are unpredictable. A month that involves a major vendor substitution (re-sourcing and re-contracting an AV company six weeks before the event) can spike to 50+ hours.

Pre-event logistics (weeks 2–6 before event)

The pre-event phase is coordination-intensive. Work includes logistics confirmation calls with every vendor, final venue walkthrough, run-of-show finalization, attendee communication (confirmations, directions, special accommodations), vendor briefing documents, contingency plan development, and the comprehensive event manual that documents every moving part. This phase feels administrative but is the most complex risk-management work in the entire planning cycle.

Hours in this phase: 30–55 per month. Contingency planning alone — documenting what happens if each vendor fails, if key speakers are delayed, if venue conditions change — typically takes 4 to 8 hours that never appear in any visible deliverable until something goes wrong.

Day-of execution

Day-of execution is the only phase the client directly observes. Work includes on-site coordination from setup through strike: vendor check-ins, setup supervision, guest registration management, run-of-show execution, issue resolution, and vendor close-out. A full-day conference (setup at 7 AM, dinner ends at 10 PM) is a 16-hour day; a half-day executive meeting is 8 to 10 hours including setup and close-out.

Day-of hours are highly visible by definition, but they should still be logged with a debrief summary: setup timing, any issues resolved, vendor performance notes. This documentation serves both the current invoice and future planning for repeat events.

Post-event close-out

Close-out work is consistently underestimated: reviewing final vendor invoices against contracted terms, resolving discrepancies, coordinating final payments, gathering attendee feedback, documenting lessons learned, and preparing a post-event report. For events with 100+ attendees, close-out typically runs 6 to 12 hours. This phase produces no visible output from the client’s perspective — the event is over — which makes it the phase most likely to generate invoice questions when it appears on the billing statement.

What event planning work is most commonly underlogged

Most event planners log client meetings, site visits, and day-of execution consistently. The categories that represent 30–50% of actual hours are systematically underlogged.

Venue research for venues that were not booked

Shortlisting three venues requires researching twelve. The nine venues that were evaluated and ruled out still consumed time: reviewing their websites, requesting proposals, comparing against the brief, and making the elimination decision. Log venue research by the number of properties reviewed and the evaluation criteria applied, not just the properties that reached site-visit stage.

Vendor vetting calls with vendors who were not selected

Selecting one AV company requires evaluating four or five. The vetting calls with the vendors who did not win the contract — typically 30 to 60 minutes each — are real work. Log them. An entry like “AV vendor vetting: 4 calls (45 min each), received proposals from 3, selected preferred vendor based on on-site reference and pricing” makes the selection process visible without requiring the client to understand that competitive vetting is part of their retainer.

Logistics coordination email threads

Confirming a single vendor’s setup window can consume 30 to 60 minutes of back-and-forth email across two or three days. Across the pre-event phase for a multi-vendor event, logistics coordination email accounts for 5 to 15 hours. This time is invisible because it does not feel like a discrete activity — it is embedded in the workday as a series of short interactions. Log it as a category (“vendor logistics coordination”) even when individual threads are short.

Contingency planning

Every professional event planner develops contingency plans. The client never sees the contingency plan unless something goes wrong, and when nothing goes wrong, the client has no way to know that the smooth execution they observed was the result of four hours of contingency documentation and four vendor backup relationships that were quietly maintained. Log contingency planning as a separate line item during the pre-event phase.

Scope change management

When the client increases the guest count from 80 to 120 six weeks before the event, every vendor contract needs to be renegotiated and every logistics assumption needs to be reviewed. This scope change management work — assessing impact, communicating with vendors, revising the run-of-show, updating the manual — is typically absorbed into existing time blocks rather than logged separately. Scope changes should be logged as a distinct category so the client can see the downstream impact of their changes on total hours.

How to log event planning retainer hours

Work log entries for event planning should capture the event, the activity type, and the specific output or decision made. The goal is to make the planning narrative legible to a client who is not managing the event day-to-day.

Effective format: [Event name] + [Activity type] + [Output or status]

Poor entry: “Event planning — 4 hours”
Good entry: “Q4 Client Dinner (Nov 15): venue research — reviewed 9 downtown properties matching 80-person capacity; shortlisted 3 for RFP; eliminated 6 based on capacity, parking access, or AV limitations”

Poor entry: “Vendor calls — 3 hours”
Good entry: “Annual Conference (Oct 8): AV vendor vetting — calls with 5 AV companies (30–45 min each), received proposals from 4, selected preferred vendor; primary criteria: previous-event reference from similar conference size, dedicated day-of technician, backup equipment policy”

Poor entry: “Planning — 5.5 hours”
Good entry: “Annual Conference: contingency plan development — documented backup protocols for 7 scenarios (keynote delay, AV failure, catering substitution, venue capacity restriction, weather delay, power outage, guest registration system failure); identified backup contacts for 3 critical vendors”

Poor entry: “Emails — 2 hours”
Good entry: “Q4 Client Dinner: vendor logistics coordination — confirmed setup windows for catering (7 AM), AV (6 AM), florals (4 PM), and venue operations; resolved catering vs. AV setup sequencing conflict with venue events manager”

A client who reads this log across a billing period can follow the event from venue research through vendor selection through contingency planning. The 35 hours for that period maps onto a visible planning progression rather than an opaque number.

Pricing event planning retainer engagements

Event planner retainer rates vary by market, specialization, and event complexity:

Corporate event coordinator (company meetings, team offsites, client dinners, 50–200 attendees): $65–$100 per hour. Generalist coordination with established vendor networks in the local market.

Conference and convention planner (industry conferences, multi-day events, 200–2,000+ attendees): $85–$150 per hour. Requires experience managing complex multi-vendor logistics, speaker coordination, registration systems, and sponsor deliverables simultaneously.

Executive and incentive planner (C-suite retreats, incentive travel, exclusive private events): $100–$200 per hour. High-touch coordination at luxury venues, often with international logistics and VIP accommodation requirements.

Cap sizing by event phase:

For ongoing corporate retainers covering multiple events per year, a flat monthly cap of 20–30 hours covers ambient advisory, early-stage planning for future events, and coordination work between active planning phases.

Contract clauses that prevent billing disputes

Scope definition per event. Define the parameters of each event covered by the retainer: guest count range, event type, venue category, and primary deliverables. A retainer that covers “corporate events” without parameters leaves the client expecting wedding-level coordination for a team offsite and the planner expecting to define scope event-by-event. Write the scope before planning begins.

Phase definitions and hours expectations. Communicate to the client, in the contract, that planning phases have predictable hours profiles. A client who understands that “weeks 4–6 before the event will require 35–50 hours this month due to vendor contracting and logistics confirmation” before they see the invoice is a client who approves the invoice without questions. A client who sees 50 hours for the first time on an invoice has no reference to evaluate it against.

Scope change protocol. Define what happens when the client changes the event: guest count increase, date change, venue change, added programming. Scope changes after vendor contracts are signed require renegotiation, and renegotiation takes time. A scope change protocol that defines how mid-planning changes are evaluated, communicated, and billed prevents the “I just thought it would be easy to add 20 more people” conversation from turning into a billing dispute.

Day-of coverage. Define explicitly whether day-of execution is included in the monthly retainer cap or billed as a separate project day. Day-of hours are high (10–16 hours), predictable, and should be scoped separately from planning hours so the invoice structure matches the client’s budget expectations.

Hours visibility access. Provide the client with a shared hours URL they can check throughout the planning cycle. Clients managing event budgets want to monitor hours consumption before the invoice arrives — particularly during the pre-event phase when hours spike and the event is imminent. Visibility eliminates surprise invoices and gives both parties a shared reference for consumption conversations.

The five most common event planning billing mistakes

1. Not logging the research that did not produce a result. Venue research that eliminated nine properties, vendor vetting that evaluated four companies, and logistics coordination that resolved a conflict before the client noticed it — these are real hours that produced real value. Omitting them creates a gap between hours billed and visible deliverables that clients cannot explain.

2. Logging day-of as a single entry. “Event day: 14 hours” is a defensible entry but a missed opportunity. Breaking the day-of log into setup (2 hours), registration (1.5 hours), program execution (6 hours), issue resolution (0.5 hours, with a note on the issue), dinner coordination (2 hours), and close-out (2 hours) makes the day legible and creates a reference record for future event planning.

3. Not logging contingency planning. Contingency planning is among the most valuable work an event planner does and is systematically invisible to clients. Log it explicitly, and when a contingency plan is actually invoked on event day, reference it in the day-of log: “executed backup catering protocol (documented in contingency plan) when primary caterer arrived 45 minutes late.” That single reference validates the contingency planning hours retroactively.

4. Absorbing scope change work into existing entries. When a scope change adds 8 hours of renegotiation work, logging it inside the existing “vendor coordination” entry obscures what happened. Log scope change work separately with a note: “Scope change: guest count increased 80 to 120 (client request Nov 3) — renegotiated venue, catering, and AV contracts; updated run-of-show and logistics manual.” This creates a paper trail and makes the downstream impact of client-initiated changes visible.

5. Sending an invoice without a planning summary. An event planning invoice without a planning status summary is asking the client to evaluate hours in isolation. A simple summary — “as of this invoice, venue is contracted, AV and catering are contracted, run-of-show draft is complete, guest invitations sent, RSVP count: 74 of 100 confirmed” — contextualizes the hours and shows the client exactly where the event planning stands at invoice date.

Making hours visible during a long planning cycle

For events with planning cycles of 12 or more weeks, a client’s understanding of the project status changes substantially between monthly invoices. A client who received a project update at the start of week 10 and sees an invoice at the end of week 6 has a two-week gap in their picture of where things stand. During the most hours-intensive pre-event phase, that gap is precisely when invoice questions are most likely to arise.

A shared retainer hours dashboard eliminates the gap. The client bookmarks a URL that shows hours used, hours remaining in the current period, and the work log of activities logged to date. The client can check at any point in the billing cycle — when they want to know if venue contracts are finalized, when they are wondering whether the RSVP list has been updated, when they are reviewing an invoice and want to confirm the period totals match the work log.

For event planning specifically, the work log on the dashboard is as important as the hours bar. A client who can read the log during week 8 of a 12-week planning cycle — “venue contracted, 4 AV vendors vetted and selected, catering shortlisted to 2 options, run-of-show draft in progress” — has a real-time picture of the planning status without requiring a status call. This reduces the number of “where are we?” client conversations and gives the planner a shared reference to point to when a client asks for a status update.

Updating the dashboard takes two to three minutes at the end of each work session. For a planning cycle that spans 10 to 14 weeks across two or three billing periods, the accumulated work log becomes a complete record of every planning decision, making it a reference document for future events with the same client.

Frequently asked questions

What is an event planner retainer and how is it structured?

An event planner retainer is a monthly fee arrangement covering a defined block of the planner’s time for planning, coordination, and advisory work. Two structures are common: per-event retainers covering the full planning cycle for a specific event, and ongoing advisory retainers for corporate clients with recurring events. In a per-event retainer, the hours cap typically increases through the planning cycle as work intensifies. In an ongoing retainer, a baseline monthly cap covers ambient planning and advisory work across multiple events at different stages simultaneously.

How many hours per month does an event planner retainer typically require?

Hours vary significantly by phase. Early planning runs 15–25 hours per month; active planning (vendor sourcing, contracting, timeline development) runs 25–45 hours; pre-event logistics runs 30–55 hours. Day-of execution for a full-day event is 10–16 hours. Post-event close-out runs 6–12 hours. Clients should be briefed on this phase-by-phase profile before planning begins so invoice amounts in the pre-event phase are expected rather than surprising.

What event planning work is most commonly underlogged?

Venue research for venues that were not booked, vendor vetting calls with vendors who were not selected, logistics coordination email threads, contingency plan development, and scope change management. These categories represent 30–50% of actual event planning hours and are systematically underlogged because they produce no visible deliverable that the client can directly observe.

What should an event planner retainer contract include?

Scope per event (guest count, type, venue category), phase definitions with expected hours profiles, scope change protocol defining how mid-planning changes are evaluated and billed, day-of coverage terms (included in cap or billed separately), and hours visibility access. Without a scope definition per event, mid-planning changes generate billing disputes that are difficult to resolve without a reference point.

How should event planning retainer hours be logged to justify the invoice?

Log entries should name the event, describe the activity type, and state the specific output or decision. “Q4 Client Dinner: venue research — reviewed 9 properties, shortlisted 3, eliminated 6 based on AV limitations and parking access” is far more defensible than “event planning: 4 hours.” A work log that tells the planning story makes the invoice legible and reduces the likelihood that a client questions individual entries.