# Document structure and formatting rules

The output is a compact, branded Word document built by `scripts/build_booklet_content.py` and
rendered by the vendored generator in `booklet/`. Target length is the cover plus three content
pages (four pages total), and never more than four content pages.

## Section order

1. **Cover** (page 1). Title, subheading, a two-line tagline carrying the headline value per
   dollar, and the date. Branded gradient and logo.
2. **The opportunity.** The volume of decisions, the current process at a high level, and the
   hidden cost of average decisions. Plain language, no coefficients, no dollar headline yet.
3. **The proposed approach.** What changes, in lay terms, plus an emphasis list of two or three
   benefits (find more top performers at Nx the current rate; fewer costly mistakes; keep more
   of the right people, only if retention is modeled). No coefficients.
4. **Estimated impact.** A headline callout (value per dollar, Expected, with the horizon stated
   precisely and the full range), then the scenario table (performance; retention if modeled;
   total; value per dollar), then a one-paragraph plain-language read-out. If there is more than
   one segment, a compact per-population totals table follows.
5. **Methodology and assumptions.** ONE PAGE maximum. A short method note, then a compact
   inputs-and-assumptions table (merged into one table for a single segment; a global table plus
   a per-population validity table for multiple segments), then one or two sentences of
   defensive notes. Validity coefficients are allowed here and only here.
6. **About Deeper Signals.** The fixed call to action (see positioning.md). Same wording every
   time. This is the only promotional section.
7. **Important note on these estimates.** The standard disclaimer, verbatim, in a callout.

## Where coefficients may appear

- Sections 2, 3, and 4 (the body): NEVER. Use plain language and dollar figures only.
- Section 5 (methodology): YES. r, R, and the added validity are shown in the assumptions table.

## Compactness and pagination rules

These are enforced by the generator and the builder together:

- **Tight spacing.** Body line spacing is about 1.1 and paragraph spacing is small, by default.
- **No orphaned headings.** Every heading carries keep-with-next, so a heading never sits alone
  at the bottom of a page with its body on the next page.
- **Tables do not break mid-row.** Each table row carries cant-split.
- **No forced page breaks between sections.** Content flows; section headings provide the visual
  breaks. This avoids blank or near-blank pages.
- **Methodology is one page.** Keep the method note to five or six sentences and use a single
  merged table where possible.
- **Keep prose lean.** Two short paragraphs per body section is the target. The document is a
  business case, not a white paper.

## The scenario table

| | Conservative | Expected | Strong |
|---|---|---|---|
| Stronger workforce performance | ... | ... | ... |
| Lower avoidable turnover (only if modeled) | ... | ... | ... |
| **Total estimated value** | ... | ... | ... |
| **Value per $1 invested** | ... | ... | ... |

The total and value-per-dollar rows are emphasised (bold, light pink fill). Money is formatted
compactly ($2.1m, $77k). Value per dollar is shown as a multiple (14.1x).

## The headline callout

States value per dollar for the Expected scenario, with the horizon explicit, then the full
range. Example wording:

> For every $1 invested in better hiring decisions, the model estimates **$14.15 in value**
> over the time those selected stay with the organization, against one year of program cost
> (Expected scenario). Across scenarios the estimate ranges from $10.55 to $16.63 per $1.

## Content standards (apply everywhere)

- No em dashes or en dashes anywhere. Use commas, parentheses, or periods.
- No italics except for statistical symbols.
- All money in US dollars.
- The disclaimer appears verbatim in every document.
- Never evaluate, score, or rank a candidate. Never give a hire or no-hire recommendation.

## Cover meta fields

The builder passes these to the generator: `title`, `subheading`, `taglineLine1`,
`taglineLine2`, `date`. The two tagline lines carry the headline value per dollar and are set
automatically from the Expected benefit-cost ratio.
