Case Study 2: Fourteen Months of Email

🔬 Deep Dive. A reconstructed communication record across one full engagement, annotated. The purpose is to show where the relationship was actually decided — which is not where most planners think.

Tier 3 — Illustrative. The Hartnell–Vukovic wedding and all correspondence are composites constructed for teaching. Message counts and timings reflect commonly observed patterns.

The Engagement

Beth Hartnell and Nikola Vukovic. 95 guests, $51,000, a coastal inn with a marquee on the lawn. Full-service, $6,400, engaged fourteen months out.

The complete communication record: 411 messages, 22 scheduled calls, 6 in-person meetings, across 14 months.

That is 30 hours — exactly the figure Chapter 2 §2.2 estimated. Here is where it went, and what it was for.

📊 Volume by month

Month: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Msgs: 38 22 19 14 11 9 13 17 16 24 31 47 63 87 ██ █▌ █▎ ▉ ▋ ▌ ▉ █▏ █ █▌ ██ ███ ████ ██████ Alt-text: A bar chart of message volume by month. It starts high at 38 in month one, drops to a trough of 9 in month six, then climbs steadily, accelerating sharply from month eleven to reach 87 in month fourteen — the month of the wedding.

The shape is universal. High at onboarding, a trough in the middle, and a steep climb in the final quarter. Roughly 40% of all communication in a fourteen-month engagement occurs in the last two months.

Two implications for how you price and staff. If you quote a flat fee, your effort is heavily back-loaded and your cash was collected long before. And if you take two weddings whose final months overlap, you have taken 80% of two engagements' communication load into a single eight-week window. Chapter 37 §37.6 covers the scheduling rule that follows from this.

Month 1 — 38 messages

The heaviest month that is not the wedding month. Nearly all of it is onboarding: documents, scheduled calls, the intake questionnaire, the decision-rights confirmation, and the first deliverable.

Message 7 — the one that mattered

Beth, day 4: "Sorry, one more question — is it okay to text you? I know we said email but sometimes I think of things at odd hours and it feels weird to write a whole email."

Planner, day 4: "Of course, and I'd rather you did than sit on something. Two things so you know how it works on my end: I answer email within a business day, Monday to Friday. Texts I'll see when I see them, and I'll answer during working hours — so please don't read a slow reply as anything other than me being at an event. If something's genuinely urgent, call. I'll always pick up for a call."

Annotation. Chapter 2 §2.6 and Chapter 3 §3.7, delivered in three sentences on day four, in response to the client's own question, framed entirely as service.

This exchange is the reason months 6 through 11 look the way they do. The boundary was set before it was ever tested, in a moment when it read as reassurance rather than restriction. A planner who sets the same boundary in month nine — after answering fifty texts at all hours — is not setting a boundary. They are withdrawing, and the client will experience it as such.

Cost of this message: ninety seconds.

Message 22 — the first deliverable

Day 6. A one-page budget sketch, rough, clearly labeled "first draft, expect this to change."

Annotation. The gap between signing and the first tangible thing is when clients most doubt the decision. Six days is good; two weeks is too long. It does not need to be right — it needs to exist and to be visibly the product of thought.

Months 2–5 — 66 messages

Vendor sourcing. The substantive work of the engagement, and the correspondence is largely functional: proposals forwarded, meetings scheduled, contracts circulated.

Message 94 — a proxy, missed

Beth, month 4: "The photographer's proposal looks fine I guess. Whatever you think."

The planner replied with a comparison of the three proposals and a recommendation.

Annotation: this was the wrong answer, and it cost eight hours in month eleven.

"Whatever you think" from a client who has been engaged and opinionated for four months is not delegation. It is disengagement, and disengagement in this job almost always means the client has a feeling they have not identified. The correct response was a question:

"That's the least enthusiastic I've heard you all year. Is it the photographers, or is it something else?"

What was actually happening — and what surfaced in month eleven, expensively — was that Beth hated being photographed, had hated it since she was a teenager, and had not told anyone including Nikola. She was not indifferent to the photographer. She was dreading the entire category.

Caught in month four, that is a conversation and a different photographer — someone whose portfolio is documentary rather than posed, and a briefing about what she does not want. Caught in month eleven, it is a renegotiation, a rescheduled engagement shoot, a very difficult evening, and a client who has spent seven months quietly miserable about a fifth of her wedding day.

⚠️ Common Pitfall: the flat reply. Watch for tonal drops. A client whose messages have been warm and detailed and who suddenly sends four words has told you something. It is nearly always one of: they are overwhelmed, they disagree and do not want to say so, or there is something about this category they have not admitted. All three are cheap to resolve now and expensive later. The intervention is a single question, and it is the same question every time: "That's a change in tone — is it the thing, or is it something else?"

Month 6 — 9 messages. The trough.

The quietest month of the engagement. Vendors are booked, the wedding is eight months away, and there is genuinely nothing to decide.

What the planner did anyway

Planner, month 6, unprompted: "Nothing needs doing this month, which I know feels odd. Quick state of play so you're not wondering: nine of eleven vendors booked, budget is $1,100 under, next real decision is the menu tasting in October. Enjoy the quiet — it doesn't last."

Annotation. This message had no functional content. It is the most efficient thing in the entire record.

The trough is where clients most often start to worry that nothing is happening, and where the worry is least justified. An unprompted status message during a quiet period does three things: it proves the system is running, it pre-explains the silence so it is not interpreted, and it costs four minutes.

The general rule: send a status update precisely when there is no news. A message when there is news proves you respond. A message when there is nothing proves you are watching. The second is the product.

Months 7–10 — 70 messages. The climb.

Design decisions, guest list, invitations, the seating chart's opening skirmishes.

Message 218 — bad news, delivered correctly

Month 9. The marquee company had double-booked and could supply the marquee but not the flooring and lighting package.

Planner, 40 minutes after learning: "I need to tell you something — this is the call I warned you about in our first meeting, and it's not a disaster.

Coastal Marquee has double-booked. They can still do the marquee. They cannot do the flooring and lighting, which we'd priced at $3,900 as part of their package.

What that means: I need to source flooring and lighting separately, and separately will cost more — I'd guess $4,800 to $5,400. So we're looking at $900 to $1,500 over on that line.

What I'm doing: I have calls in to three companies and I'll know by Thursday. I've also asked Coastal for a concession on the marquee price given they're the ones who dropped it, and I expect to get something.

What I need from you: nothing today. On Thursday I'll bring you the numbers and two options.

I'm sorry — this is annoying and it's not what you needed in month nine."

Annotation. The structure is worth memorizing, because you will use it thirty times a year:

1. Name the frame. "This is the call I warned you about" — invokes the bad-news promise from month one, which converts an alarming message into an expected category.
2. The fact, unsoftened, immediately.
3. The consequence, quantified, with an honest range. Not "it might cost a bit more."
4. What you are already doing. Before they can ask.
5. What you need from them. Usually nothing, and saying so is a relief.
6. A date.
7. One sentence of acknowledgement. Not an extended apology, which makes it about your feelings.

Beth's reply, in full: "Ok. Thank you for telling me straight away. See you Thursday."

That is what fourteen months of correctly set expectations buys you — a client who receives $1,500 of bad news with three sentences and no anxiety, because the delivery matched a promise made in month one.

Months 11–12 — 78 messages. The acceleration.

The seating chart, the guest list's final cuts, and the photographer conversation that should have happened in month four.

Message 291 — the third conversation

Month 11. Beth's third sharp email in four weeks, this one about the invitation proofs, copying nobody but noticeably clipped.

The planner called. The script is §3.6's, more or less verbatim.

What came out: Nikola's mother had been sending three messages a day for a month about the guest list, Beth had told no one, and she had been absorbing it entirely alone while also, separately, dreading the photography.

Annotation. Note the compounding. The photography issue from month four had not gone away; it had become one of two loads, and the second load is what made the first one visible. The sharp email was not about the invitation proofs and was also not about the mother-in-law. It was about carrying two undisclosed things at once.

The call took 50 minutes. It produced: a boundary Beth set with Nikola's mother (Nikola set it, actually, which was the correct routing — Chapter 3's rule about scripts versus delivery), a change of photographer approach, and — the planner's own note in her file — "should have caught 94."

Months 13–14 — 150 messages. 36% of everything.

Final confirmations, the timeline, the run sheet, and the last-fortnight surge in which a client who has been calm for a year becomes, briefly, someone else.

Message 366 — the 2 a.m. message

Beth, month 14, 2:07 a.m.: "I can't sleep. Is the shuttle definitely coming at 10:30 or 11? I can't remember and I can't find the email and I keep thinking about it."

Planner, 8:12 a.m.: "10:30. It's in the run sheet on page 4 and I've attached it here so it's at the top of your inbox.

You're at the stage where everything feels like it might be the thing you forgot. Nothing is. Every vendor is confirmed twice, I have the run sheet, and there is no decision left that you need to make.

If you can't sleep again, message me — I won't answer at 2 a.m. but I will first thing, and writing it down usually gets it out of your head."

Annotation. The reply came at 8:12, not 2:08. It answers the literal question first with a specific location in a document. It names the state she is in and normalizes it. And it explicitly permits the 2 a.m. message while restating the response window — which is the boundary from day four, held for fourteen months, and held gently.

A planner who had been answering at 2:08 all year could not send this message. They would have to either answer at 2:08 again, or withdraw for the first time in the worst possible week.

The Analysis

💰 Run the Numbers: where 30 hours went

Category	Messages	Hours	What it was
Functional coordination	168	7.5	Scheduling, forwarding, logistics
Substantive decisions	74	8.0	Vendor selection, design, budget
Reassurance	131	9.5	Proxy questions and status
Problem management	26	3.5	The marquee, the photographer, the mother-in-law
Relationship repair	12	1.5	The third conversation and its aftermath
Total	411	30.0

Reassurance is the largest single category — nearly a third of all client communication time, and it produces no artifact. It cannot be delegated, cannot be templated, and cannot be made efficient, because efficiency is the opposite of what it delivers. This is Chapter 1's threshold concept measured in hours.

Where the relationship was actually decided

Not in the big moments. Four messages, none of them dramatic:

Three of the four cost under five minutes. The fourth cost nothing and was a failure of attention rather than effort.

That is the finding. The relationship was determined by four small choices about how to communicate, made in ordinary moments, three of which were nearly free. Not by the quality of the vendors, the beauty of the design, or the excellence of the wedding — all of which were good, and none of which appear in this analysis.

Discussion Questions

1. Message 94 — "whatever you think" — was answered helpfully and correctly, and it was the engagement's most expensive mistake. What routine would catch a tonal drop reliably, given that you will read hundreds of messages while doing something else?

2. The month-six status update had no content. Argue that it is filler, and that a client paying $6,400 deserves substance rather than reassurance theatre. Then respond.

3. Forty percent of communication occurred in the last two months, after all fees were collected. What does this imply about payment schedules? (Chapter 7 will answer; commit to a position first.)

4. The planner did not answer at 2:07 a.m. and Beth was suffering at 2:07 a.m. Is holding the boundary here compassionate or self-serving? Would your answer change if it were the night before the wedding rather than three weeks out?

5. Reassurance was 9.5 hours and produced no artifact. If you were forced to reduce the engagement by ten hours, would you take them from here? What would happen?

Mini-Project

Build the tonal-drop tripwire.

Design a lightweight, actually-sustainable routine that would catch message 94. Constraints: it must work while you are managing eight other engagements, it must not require re-reading correspondence, and it must not depend on you being in a good mood.

Consider: a per-client note in your CRM after each substantive exchange; a monthly two-minute scan of the last three messages from each client; a standing question in every scheduled call ("anything you've been sitting on?"); a rule that any reply under ten words from a client who normally writes more triggers one clarifying question.

Then test it against the record: which of your candidate mechanisms would actually have caught message 94, and which merely sound like they would?

References

Tier 3 — Illustrative. The Hartnell–Vukovic engagement, all correspondence, and all figures are composites. The message-volume curve, the roughly-40%-in-the-final-two-months pattern, and the ~30-hour communication total reflect commonly observed patterns (Tier 2) rather than measured data from any specific practice.

Related chapters: Communication boundaries — Chapter 3 §3.7. Bad news structure — Chapter 3 §3.5. Payment schedules against back-loaded effort — Chapter 7. Photography briefing and client discomfort — Chapter 23. Final-fortnight confirmations — Chapter 26. Scheduling engagements so final months do not overlap — Chapter 37.