The 8-Row Decision-Rules Format

The eight kinds of decisions a senior hire in a founder-led firm needs written down before day one. Plus the three-column format that makes the worksheet useful, not just tidy.

You've decided the hire is the right move. You've sat with what it costs the hire. You're somewhere between "I should write the rules down" and "I'll get to it before the start date."

Block the afternoon. Run the eight rows below. The output is a 2 to 4 page document. The hire reads it in week one and works from it in week two.

Founder-led firms know the rules exist. The harder question is whether the rules are written clearly enough that someone other than the founder could read them and act.

Why eight rows, and why this format

The eight rows below are the ones that cause most of the routing-tax pattern in founder-led firms. Not every decision a hire makes. Just the ones that matter most. The ones that, if not written down, lead to the cc-the-founder pattern by week three.

The three-column format (rule, exception, escalation threshold) exists because each column does a different job.

The rule column commits the founder to a stated logic. Not the perfect logic. The current logic. The exception column lets the founder name the cases the rule doesn't apply to. That way the rule doesn't have to cover every edge case. The escalation column lets the founder name the line above which they want to stay involved. In writing. So the hire knows where the band ends.

The format is tighter than most operating docs on purpose. Two columns (rule and exception) leaves too much out. Escalation is the line that tells the hire they're free to act. Four columns is too many. Each extra column adds a week of writing. And it lowers the odds the doc actually gets finished.

Three columns is the format that gets written. That matters more than format elegance. The unwritten elegant doc costs the hire every week.

The 8 rows

These are the eight kinds of decisions a founder-led firm should write down before the senior hire walks in. Each row is a 15 to 30 minute writing exercise for a founder who knows the firm. None of them are nice-to-haves. Each one maps to a specific failure if it's missing.

Row 1. Pricing exceptions

The decision: when a prospect or client asks for a price below your standard band, what does the hire say?

The rule names the standard band, the discount logic, and the conditions under which you flex. The exception names the named-account band, the volume break, and the strategic-relationship case. The escalation threshold names the discount percent or dollar value above which the call comes back to you.

Failure if missing: the hire either turns down all flex and loses deals you would have won, or grants flex you wouldn't have. Either way, pricing becomes hard to predict for the firm and for clients.

Row 2. Scope creep

The decision: when a client mid-engagement asks for an out-of-scope item, what does the hire say?

The rule names the size of out-of-scope ask the senior team can absorb, the size that triggers a change order, and the size that triggers re-scoping the engagement. The exception names the strategic-account case and the new-relationship case. The escalation threshold names the percent of remaining engagement value or hours above which it comes to you.

Failure if missing: the firm absorbs out-of-scope work it shouldn't. Margin erodes. The hire becomes the unwilling enforcer of a rule that was never written down.

Row 3. Client escalations

The decision: when a client raises a concern (deliverable quality, timeline, team interaction), what does the hire do, and at what point does it come to you?

The rule names the categories the hire owns start-to-finish, the categories where the hire informs you but acts, and the categories where the hire stops and waits. The exception names the named relationships that always come to you. The escalation threshold names the severity, the dollar value, or the relationship class above which it escalates.

Failure if missing: the hire defers to you in front of clients on questions inside their stated scope. That trains clients to route around the hire. Which makes the hire less effective and the founder more central, no matter what the org chart says.

Row 4. Refund authority

The decision: when a client asks for a refund or credit, what authority does the hire have?

The rule names the dollar value the hire can issue without checking, the conditions that trigger an automatic credit, and the cases that need your approval. The exception names the strategic-relationship case where the hire might recommend more than policy. The escalation threshold names the dollar value or recurrence above which it escalates.

Failure if missing: every refund conversation routes through the founder. That slows things down. It signals to clients that the hire isn't the authority. And it leads to inconsistent calls because the rule is "whatever the founder decides today."

Row 5. Hiring authority

The decision: who can the hire bring on, replace, or have hard conversations with, without checking?

The rule names the junior hires the hire owns start-to-finish, the senior hires the hire screens but you decide on, and the contractor and vendor decisions the hire owns. The exception names the categories where you stay involved. The escalation threshold names the seniority band, the budget impact, or the team-impact size above which it escalates.

Failure if missing: the hire feels they can't move on team decisions without checking. That slows hiring. It slows performance management. And it makes the hire act like a coordinator rather than a leader.

Row 6. Vendor selection

The decision: when the firm needs a new tool, contractor, or service provider, what does the hire decide alone and what comes to you?

The rule names the budget threshold the hire can spend against without checking, the categories where the hire chooses but informs, and the categories where you choose. The exception names the existing-vendor expansion case and the strategic-partnership case. The escalation threshold names the annual contract value, the multi-year commitment trigger, or the strategic-tier flag above which it escalates.

Failure if missing: every tool, vendor, and contractor decision routes through the founder by default. The founder built the existing stack. So the hire reads the silence on this category as "ask first."

Row 7. Project sequencing

The decision: when there are more requests than capacity (the normal state), what gets prioritized, and who decides?

The rule names the ranking logic the hire applies (revenue weight, strategic-account weight, capacity fit, deadline). The exception names the named-account case and the strategic-priority case. The escalation threshold names the trade-off size or the strategic-account flag above which it escalates.

Failure if missing: the hire either over-prioritizes the founder's named accounts (because those are the only signals they have), or under-prioritizes them (because they didn't know which accounts were named). Capacity becomes a weekly negotiation rather than a written logic.

Row 8. Quality bar

The decision: what does "ready to ship" mean for client work, and who decides it has been met?

The rule names the concrete things a deliverable must show before it goes out (brief-fit, sign-off, formatting, summary, citations). The exception names the high-stakes deliverable that always sees your eyes and the new-format deliverable that needs more checking. The escalation threshold names the engagement value, the named-account flag, or the new-service-line flag above which it escalates.

Failure if missing: every real deliverable routes through the founder for final review. The bar lives in the founder's taste. The hire has no other way to verify they've cleared it. The founder stays the quality gate forever.

Reading the worksheet (the missing score is the point)

The worksheet doesn't produce a score. It produces a 2 to 4 page document. That's the deliverable.

Three honest readings to run when you finish.

Readability. Could a senior person who doesn't yet know your firm read this and act on a real decision in week one? If the answer is "they could try, and you'd correct them on most of it," the document needs another pass. The goal isn't perfect rules. The goal is rules clear enough that the hire's first 30 actions match 80% of the calls you would have made.

Honesty. Mark the rows you couldn't write in 15 minutes with a star. Stars aren't failures. Stars are the categories you've been making by feel. They're the rows the hire is going to need the most help with on day one. Each star is either a category to come back to in the next two weeks, or one to tell the hire you'll own yourself for the first quarter while you both work it out.

Coverage. Are there decision categories that route through you weekly that aren't on this list? Add them. The eight rows are a starting point built from the patterns founder-led firms most often produce. Your firm may have nine rows. Or eleven. Add what's real.

A clean eight-row document, with the stars named, is what we mean by a hireable decision-rules artifact. A worksheet with three or more stars and no plan to address them is the same document the firm started with. An invitation for the founder to stay the routing hub.

Closing

Tomorrow we walk through what a Decision-Rules Document actually looks like in a firm that has done the work. With real examples for each of the eight rows.

The worksheet is the format. The document is what passes through it.

The gap between "the hire will figure out our rules over time" and "the hire walks in with the eight rules already written, the exceptions named, and the escalation thresholds set" is the difference between a senior person who is autonomous by month three and one who is still cc-ing you in month nine.

Continue the series

This is part 3 of a 5-part series on The Decision-Rules Document Your Next Hire Should Inherit. The full arc:

• Monday: When Founder-Judgment Becomes a Routing Tax
• Tuesday: What It Costs the New Hire When the Rules Live in Your Head
• Wednesday: The 8-Row Decision-Rules Format (this post)
• Thursday: What a Decision-Rules Document Actually Looks Like
• Friday: Why "Trust Your Judgment" Is a Non-Handoff

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.