What Wedding Planners Charge for Day-Of Coordination

The name is wrong, and it costs people money

No coordinator has ever been hired for a day.

What is sold as "day-of coordination" almost always begins six to eight weeks before the wedding, because that is when it has to begin for the day to work at all. You cannot take over a wedding at 08:00 on a Saturday. You take it over in week six, when there is still time to discover that the caterer thinks service is at 19:00 and the DJ has 19:30.

Here is what the package actually contains, in the order the hours get spent:

That is 24–34 hours. The day is roughly 40% of it.

The reason this matters commercially is simple: a coordinator who prices the day prices about 40% of the job. And because the other 60% is invisible to the client, nobody pushes back — the coordinator just absorbs it.

The three pricing models

Flat fee

The most common, and the easiest to sell. The client knows the number, you know the number, and the conversation is over in one exchange.

The risk is entirely on you: a wedding with four vendors and one location, and a wedding with eleven vendors across two sites, are wildly different amounts of work for the same fee. Most coordinators handle this by banding — a base fee up to a guest count and vendor count, with a clearly stated uplift beyond it.

If you use one model, use this one, but band it.

Percentage of budget

Typically 10–15% of total wedding spend. It scales with complexity, which is genuinely fairer, and it means a lavish wedding pays for the work it creates.

Two real drawbacks. First, it invites negotiation, because the client can see exactly what they are paying and exactly what to argue about. Second, it ties your income to the couple's spending decisions, which you do not control — a couple who saves money by using a cheaper venue has just cut your fee for a wedding that may be more work.

Hourly

Rare for coordination, and for a reason: clients systematically underestimate the hours, so the invoice always reads as a surprise. Hourly works well as an overflow mechanism — a flat fee covering a defined scope, with hours billed beyond it — but it works poorly as the primary model.

Where the money leaks

Three leaks account for most of it, and all three are contract problems rather than pricing problems.

Unlimited revisions. This is the big one. The first timeline draft takes four hours. Revisions eleven through fourteen take another four, and they happen in the last fortnight when you are busiest. Name a number — two revision rounds after the first full draft, further changes billed hourly — and clients accept it readily when it is explained up front. They only resist when it arrives as a surprise.

Unbounded vendor confirmations. "We'll confirm your vendors" is open-ended. "We'll confirm up to eight vendors, with additional vendors at a stated rate" is scope. The couple who adds a live saxophonist in week three has added work, and it should be visible.

No overtime rate. Weddings run long. A stated hourly rate beyond the contracted hours costs you nothing to include and occasionally saves an entire evening's unpaid work. It also, usefully, makes the couple the ones telling the DJ to wrap up.

Why the timeline work is the part that disappears

Ask a coordinator where their hours go and most will say the same thing: rebuilding the timeline after every change.

The ceremony moves twenty minutes. That is not one edit — it is a recalculation of every downstream item, a fresh export, and a round of messages to seven vendors telling them what changed. Do that four times across a planning cycle and it is a full working day, unbilled, invisible, and impossible to explain on an invoice.

This is the strongest argument for treating your timeline structure as an asset rather than a document. A schedule that recalculates downstream items when one time changes, and a share link vendors can check rather than a PDF you re-send, removes most of that unbilled labour. The work does not become less valuable — it becomes less expensive to deliver, which is the same thing as a rate increase.

Wedding planners running six or eight weddings in a season feel this most acutely, because the hours compound. Event planners carrying corporate work alongside weddings feel it differently: the corporate timelines are structurally similar enough that they should be reused, and usually are not.

What to put in the contract

Six lines, and most disputes never happen:

1. When the engagement starts — a date, not "closer to the time".
2. How many vendors are included, and the rate beyond it.
3. Whether the rehearsal is covered, and for how long.
4. Hours on the day, with a start time, an end trigger, and an overtime rate.
5. How many timeline revision rounds are included.
6. Who decides on the day if the couple cannot be reached — a named person, agreed in advance.

That last one is not a pricing clause, but it is the one that saves the wedding. At 17:40, with rain starting and a decision needed about moving the reception indoors, "I'll ask the couple" is not an answer.

A note on rates

I have deliberately not printed a dollar figure, because coordination rates vary more by market than by anything else — a fair fee in a metro area and a fair fee in a small town differ by a multiple, not a margin.

What travels between markets is the structure: know your real hours, band your flat fee, bound your revisions, and charge for the invisible work. A coordinator who knows the job is 24–34 hours prices very differently from one who thinks it is a long Saturday, regardless of what the local market will bear.

For the operational side of the job, see who needs what from the timeline and when, and the wedding template collection for structures worth reusing between clients.