Turn tracking ⬇ Excel CSV

Billing — documents at or over their turn threshold

Default threshold is 10 turns; clients on a 5-turn plan are set in turn-billing-thresholds.json (source: finance — not derivable from the data). "Crossed" = the date the threshold-th turn landed; this month = June 2026.

Why these deals have so many turns (8+ turns)

The 3 documents at 8 or more turns — each card shows the recurring points the counterparty kept reopening (with dates), where it escalated, and any obvious earlier opportunity. Click a tag in the Turns tab to jump here.

Version audit — every version, real turns highlighted

For each billing-relevant document (5+ turns), its full version history (like the Bailiff version list). ● turn marks a version dated on a counted counterparty turn; the rest are our drafts / clean copies / internal. Click a row to expand. (Highlight is by date + uploader — best-effort; confirm against the Turns-tab quote.)

By client → document type

Per client: active counterparties, documents, how many are over their turn limit (NDA 3 / DPA 6 / MSA 8), and the per-type spread.

What this shows

Every document across the active book that took a new turn in the last three weeks (since 2026-06-03) and already had turn history. The window is the filter; the number is the document’s total lifetime turn count. Every deal was read in full from its Slack thread.

Counting rules

• A turn = a substantive counterparty come-back — a redline, a relayed legal question, a security/diligence ask, or a new position. With or without a document.
• Per document lineage, by real title. One lineage with multiple labels = one count (combined); a lineage that changes type keeps one count (⇄).
• Near-simultaneous = one turn. Confidence reflects how clean the read was; Why (for over-limit docs) names the recurring sticking points.

Does not count

• Clean copies / pure acceptances; calls/meetings; standalone compliance questionnaires Crosby never acts on; our own outbound; client asking us to draft; internal client deliberation; scheduling; same-document re-sends.

Simulation — model the turn threshold

Two billing lines from one control. Set the full (standard) max; the recharge line is automatically half of it, rounded up (max 10 → 5 & 10 · max 6 → 3 & 6 · max 9 → 5 & 9). ≥ recharge and ≥ full count documents at or above each line. Set a global default, then override any single client.

Documents crossing the threshold