Further Reading — Chapter 7: Budget Management

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

On cash flow as distinct from profit

Any small-business finance primer, on the cash-flow statement. (Tier 1)

The distinction this chapter turns on — that a budget and a payment calendar answer different questions — is the oldest lesson in small-business finance, and it is the reason profitable businesses fail. A cash-flow statement exists precisely because an income statement cannot tell you whether you can make payroll on Friday.

What to read for: the cash conversion cycle, and the distinction between accrual and cash views of the same transactions. A wedding budget is an accrual document — it records what things cost. The payment calendar is the cash view. Both are correct and they describe different realities, which is exactly the chapter's argument.

Anything on working capital management. (Tier 1)

Directly relevant to §7.2.1's finding that some vendors can stage and some cannot. A florist buying stems four days before an event has a working-capital position that a caterer collecting a balance at −14 days does not. Understanding this makes the staging conversation better, because you will know which vendors you are asking to lend money and which you are merely asking to re-schedule.

On payment terms as risk instruments

Anything on trade credit and payment terms in B2B commerce. (Tier 2)

§7.2's central insight — that a vendor's balance date is set to manage cancellation risk rather than to meet a liquidity need — is a specific case of a general phenomenon well studied in trade credit literature. The general finding: payment terms encode risk allocation between parties at least as much as they encode cash needs.

Why this matters practically: once you know a term is about risk, the ask becomes obvious and unthreatening. "Same total, same protection for you, just spread for them" addresses the vendor's actual concern, which is why it works.

Deposit and retainer practice in professional services. (Tier 2)

Law, architecture, and consulting all use retainers, and all three have clearer conventions than events about what a retainer is and whether it is returnable. Reading a professional-services engagement letter's payment clause will show you what §7.3's "deposit versus retainer versus non-refundable" distinction looks like when a field has settled it.

On client funds — read this before you hold any

⚖️ This section is research guidance, not legal or accounting advice. Talk to a licensed professional in your jurisdiction before accepting funds intended for a third party.

Your state's requirements for holding client funds in a service business. (Tier 1)

There is no single answer. Requirements vary by state, by business structure, and sometimes by the nature of the service. Questions worth researching: whether a separate or trust account is required; whether client funds must be segregated; what record-keeping obligations attach; and whether any licensing implications arise.

Trust accounting rules in adjacent regulated professions. (Tier 1)

Attorneys, real estate brokers, and travel agents all have well-developed rules for handling other people's money, and reading one set — your state bar's trust accounting guidance is usually free and clear — will show you what rigorous looks like. Event planning is generally not subject to those rules, and reading them is still the fastest way to understand what the risks are and why the professions that handle client funds regulate it so heavily.

Your accountant. (Tier 1, and the actual answer)

Exercise C.3 asks you to have this conversation. It costs an hour and it is the single most important piece of professional advice in Part II.

On the conversation

Patterson et al., Crucial Conversations. McGraw-Hill. (Tier 1)

Recommended in Chapters 2 and 3, and load-bearing for §7.7. The shortfall conversation is the definitional high-stakes exchange: the client is embarrassed, the planner has information they need, and the natural instinct on both sides is to be vague.

Their concept of safety is exactly what the "you can tell me it's none of my business" preamble is establishing. Their contrasting technique — "I'm not asking to be nosy, I'm asking because they're different problems" — is verbatim in the script.

Anything on debt and financial shame. (Tier 2)

Worth reading a little of, because §7.7's prohibition on moralizing is not merely good manners. Financial difficulty carries substantial shame, shame produces avoidance, and avoidance is precisely what turns a solvable timing problem into an unsolvable one at −3 weeks. A planner who is safe to tell hears about problems early. That is the entire practical argument, and it is stronger than the ethical one.

On the events side

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

Her treatment of deposits, payment schedules, and vendor terms is oriented to corporate events, where the structure is nearly inverted — corporate clients frequently pay in arrears on invoice, thirty to sixty days after the event, while wedding clients pay almost everything in advance.

That inversion is worth understanding, and exercise E.2 asks you to explain it. The short answer is credit risk: a corporation is a durable entity with a payment history and an address; a couple is not, and disappears afterward. But the consequences run deep — a corporate planner has a cash-flow problem their wedding counterpart does not, and vice versa. Chapter 31 returns to it.

Real vendor contracts, read for the payment clause alone. (Tier 1, if you can get them)

Exercise C.5 asks for five. Read only the payment terms in each. You will find more variation than you expect, and you will find at least one term that is unusual enough to change what you ask for at booking.

On the planner's own finances

Anything credible on freelance and seasonal-business cash flow. (Tier 2)

Case Study 2's second half — modeling the planner's own income against their own effort — is a freelancer's problem, not a wedding problem, and the freelance-finance literature has thought about it more carefully than the events literature has.

Two concepts worth importing: the runway (how many months you can operate with no new income, which for a seasonal business must cover January to April), and payment terms that track delivery rather than convenience, which is the §7.7 fee-schedule fix.

Chapter 36 builds the annual model properly. Exercise E.3 asks you to start it now, and starting it now will make Chapter 36 much less abstract.

What to be careful with

Wedding-planning software that offers "budget tracking." Most of it tracks estimate and spent, which is two of the four columns and neither of the two that matter most — balance and variance. Almost none of it models a payment calendar. Chapter 39 assesses the category honestly; for now, assume you will need a spreadsheet alongside whatever platform you use.

Advice to "build in a buffer" without a number. Chapter 6 gave you 10% and a reason. Advice that says to be careful without specifying how much is not advice.

Anyone who tells you what percentage of a budget should fall in the final month. It is a property of your vendors' contracts, not a target. Model it, do not benchmark it.

A note on what is missing

The payment calendar is not, as far as this book can establish, a standard deliverable anywhere in wedding planning. Budget templates are abundant; cash-flow templates are essentially absent.

That gap is why §7.2 exists and why the mini-project asks you to build one. If you do build it and it works, it is a genuinely useful thing to share — see the contributing guide.

The claim in §7.2 that the final six weeks carry 40–55% of a budget is trade observation, not measurement. Exercise C.5 asks you to test it in your own market from real contracts. If your figure differs substantially, that is worth reporting, and it is the kind of correction this book was published openly to receive.