Further Reading — Chapter 2: What a Planner Actually Does

Tier 1 = real, published, verifiable. Tier 2 = widely known practice, attributed without invented bibliographic detail. Nothing here is fabricated.

On scoping professional services

This chapter's core problem — defining the boundary of an open-ended service sold to an anxious buyer — is not unique to events, and the fields that have solved it best are worth raiding.

Weiss, Alan. Million Dollar Consulting and Value-Based Fees. McGraw-Hill / Wiley. (Tier 1)

Weiss is a consultant writing about consulting, and his central argument maps onto event planning almost without translation: charge for outcomes rather than hours, define scope by deliverable, and never let the client buy your time. Read him critically — the tone is bracing and some of the advice assumes a corporate buyer who does not exist in the wedding market — but §2.6's insistence on counted deliverables comes from exactly this tradition.

The AIA (American Institute of Architects) standard agreement documents. (Tier 1, purchasable)

Architecture solved the scope problem a century ago because it had to: a building is an open-ended service sold to an emotional buyer with a fixed budget and a fixed completion date, which is a wedding with better drawings. The AIA's standard owner–architect agreements contain the most mature scope language in any comparable field — particularly on phases, additional services, and owner's responsibilities. Exercise E.2 asks you to import two clauses. These documents are what to import them from.

Engagement letters in professional services. (Tier 2)

Law and accounting both use engagement letters that define scope, exclusions, and the mechanism for expanding work. Many firms publish samples or discuss structure publicly. What they do well: exclusions are stated affirmatively and at length. What they do badly: they are written for enforceability rather than comprehension, which is why §2.6 recommends a separate plain-language one-pager. Read one to see both halves of that lesson at once.

On the events industry specifically

Allen, Judy. The Business of Event Planning. Wiley. (Tier 1)

Chapter 1's recommendation, and doubly relevant here. Allen's treatment of proposals and client agreements is the closest thing in the published events literature to a rigorous scoping methodology. Her orientation is corporate, which means her scope documents are more disciplined than most wedding-side practice — a useful corrective.

Published service menus from working planners. (Tier 2)

Exercise C.2 asks you to collect three. This is genuinely the best reading available on how the field actually scopes, as distinct from how it should. You will find that the majority use adjectives where counts belong, that exclusions are rare, and that "unlimited" appears constantly. Reading twenty of these will teach you more about the standard of the field than any book, and it will show you exactly how to differentiate.

Trade press coverage of coordination pricing. (Tier 2)

Special Events and BizBash both periodically run pieces on planner compensation and on the day-of/month-of naming problem. The comment sections on these articles are, unusually, worth reading — they are where working planners say what they actually think about the pricing conventions of their own industry.

On the underlying mechanism

Kahneman, Daniel. Thinking, Fast and Slow. Farrar, Straus and Giroux. (Tier 1)

Relevant to this chapter for one specific reason: the planning fallacy — the robust finding that people systematically underestimate how long a task will take, even when they have done it before and even when they know about the bias. This is the mechanism behind the 20–25% hour under-count in Case Study 1, and it is why §2.2 exists as a table rather than as advice to "estimate carefully." You do not fix a cognitive bias with effort. You fix it with a reference class and a written record.

Reference-class forecasting. (Tier 2, associated with Bent Flyvbjerg's work on large projects)

The remedy for the planning fallacy: rather than estimating a task from the inside, look at how long similar tasks actually took. This is precisely what a well-kept hours log gives you, and it is the reason Chapter 37 asks you to track one full engagement before setting a price. Flyvbjerg's work is on infrastructure megaprojects and the parallel is not as absurd as it sounds — both domains feature fixed deadlines, emotional stakeholders, and estimates made by people who want the project to happen.

On the conversation

Voss, Chris. Never Split the Difference. Harper Business. (Tier 1)

A negotiation book by a former hostage negotiator, and the single most useful non-events book for the scripts in this chapter and in Chapters 3, 7, and 12. Two techniques transfer directly: labeling ("it sounds like the budget is the part you're most worried about") and calibrated questions ("how would you like me to handle it if the florist can't hold the date?"). The chapter's scope-creep response — yes to the person, terms on the work — is structurally a labeling move followed by a calibrated question.

Patterson, Grenny, McMillan, and Switzler. Crucial Conversations. McGraw-Hill. (Tier 1)

For the conversations you will avoid having, which are the ones that produce the sixty-three-hour wedding. Its core insight — that people withdraw from a conversation the moment they feel unsafe, and that safety must be restored before content can be discussed — is exactly what the §2.5 script's "Happy to" is doing in the first two words.

What to skip

Wedding-planner certification course materials, at this stage. Many include scope templates. Most of those templates contain the exact failures §2.6 catalogues — "unlimited communication," "full design services," no exclusions section. Read them after you have written your own scope, as an exercise in spotting the problem, not before, as a model.

Anything promising a "complete planner package" of fill-in-the-blank documents. Templates are useful and this book supplies them (Appendix A). But a scope document you did not write is a scope document you will not enforce, because you will not remember why each line is there. The value of §2.6 is in the writing, not in the artifact.

A note on where this chapter's material comes from

There is no authoritative published source for the four-tier service structure, the hour counts, or the "day-of is a misnomer" argument. These are trade knowledge — widely held, inconsistently practiced, rarely written down, and passed between planners in conversations that mostly happen at 11 p.m. in a parking lot after an event.

That means two things for you. First, the hour figures in §2.2 are a reference class, not a measurement — they reflect commonly reported patterns and should be replaced with your own data as soon as you have any. Second, the strongest source available on this topic is a working planner willing to talk, which is why exercise C.4 asks you to find one. Buy them coffee. Ask what they wish they had excluded. They will tell you immediately, and in more useful detail than anything on this page.