---
id: int.a_named_decider_and_a_written_rule_for_a_split_panel
type: intervention
title: "A named decider and a written rule for a split panel"
lang: en
registry: 1.1.0
canonical: https://hoba.work/interventions/int.a_named_decider_and_a_written_rule_for_a_split_panel
json: https://hoba.work/api/v1/interventions/int.a_named_decider_and_a_written_rule_for_a_split_panel.json
---

# A named decider and a written rule for a split panel

Before the panel sits, one member is named as holding the decision and the rule for an even split is written down; when the split happens, the candidate is told that it did and which way the rule ran.

## At a glance

- Actor: hiring manager
- Scope: team
- Cost: low
- Evidence: supported

## What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

**The rule, written before the panel meets** — *reconstruction*

```
> before  Decider for req #5120: the hiring manager. On an even split the decider decides and records one paragraph of reasons.
  after  Panel 2–2 on system design depth. Decider: no hire. Reason recorded: the two dissenting scores rested on the same unasked follow-up.
  sent  To the candidate: the panel did not reach agreement; the decision fell to the named decider under the rule set before the round.
```

*What to notice* Panels split, and no rule stops them splitting. What a written rule stops is the split being resolved by whoever is most tired, and then reported outward as a considered judgement about the candidate. The default nobody wrote down is almost always no hire — which means the absence of a rule is itself a rule, and an unstated one.

## From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

### Hiring manager

- **What reaches them:** A line to fill in before the panel is scheduled: who decides, and what happens on a tie.
- **What it means from there:** The tie rule was always there — it was just never written, and unwritten it defaulted to the outcome that requires nobody to be responsible for it.
- **What happens next:** Names the decider, writes the tie rule, and records a paragraph of reasons when the rule is used.

### Recruiter

- **What reaches them:** A debrief that ends with a recorded decision rather than a second round of scheduling.
- **What it means from there:** An impasse used to cost the candidate weeks and produce nothing to send; now it produces a sentence that is true and can be sent the same day.
- **What happens next:** Sends the outcome with the fact of the split in it, rather than converting it into a fit narrative.

### Candidate

- **What reaches them:** An outcome that says the panel disagreed and a named person decided under a rule fixed beforehand.
- **What it means from there:** Being split on is not the same as being found wanting: half the room was on the other side, and what settled it was a rule about ties.
- **What happens next:** Reads the result as a close call rather than a verdict, and reapplies where the registry says the same team reopens.

## Expected effects

- mech.hiring_manager_consensus_impasse keeps operating — panels will split — but stops resolving by default and unrecorded
- The candidate learns the outcome turned on a tie rule, not on a finding about them

## What to measure

- `tie_rule_declared_rate`
- `impasse_disclosure_rate`

## Related entries

- targets — [mech.hiring_manager_consensus_impasse](https://hoba.work/mechanisms/mech.hiring_manager_consensus_impasse) — Hiring Manager Consensus Impasse
- targets — [bar.team_cross_functional_panel](https://hoba.work/barriers/bar.team_cross_functional_panel) — Team & Cross-Functional Panel

---

hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.