How to Attribute Books vs Closes Fairly (Without Floor Politics)

How to Attribute Books vs Closes Fairly (Without Floor Politics)

Spiffs die in ambiguity. A setter books the sit, a closer runs it, money lands — and then the room argues about who "really" earned the credit. Learning how to attribute books vs closes fairly is not a philosophy seminar. It is a small set of written rules, fields that cannot be edited quietly after the fact, and a call log both roles trust before payday.

This playbook is for any setter→closer dial floor — roofing, HVAC, solar, windows, pest, fiber, landscaping, insurance, and other high-activity outbound shops. Same failure mode every time: books and closes live in different heads, Slack threads, or a shared spreadsheet tab. Credit gets political. Good people quit. Bad habits stick.

Why book vs close fights start

Fair attribution fails for predictable reasons:

• There is no written rule for booked-by vs closed-by when both touch the deal
• Shared logins make "who booked it" impossible to prove
• Confirmation and no-show recovery sit in nobody's name, so ownership blurs
• Leaderboards rank dials or revenue with no split between book credit and close credit
• Managers reverse-engineer payday from memory and "I thought you said…"
• Self-reported sheets get edited after the sit when the story changes

If your floor cannot answer "who booked this sit?" and "who closed it?" in under five seconds from the same record, you do not have a compensation problem — you have a logging problem. That is the same muscle as how setters and closers share a call log: one truth, two roles, clear fields.

Define the credit events (write them down)

Print this. Coach to it. Do not renegotiate per deal.

Booked-by

The rep who secured the appointment (or site survey / install book / demo) that entered the calendar as a real sit. Soft yes with no date is not a book. "Call me next week" is a callback, not credit.

Confirmed-by (optional but useful)

The person who completed the confirmation call or text that kept the sit alive. Some floors pay a small confirmation spiff; others treat it as duty. Either way, logging it stops "who owned confirmation?" fights.

Showed / no-show

Outcome of the sit itself. No-show recovery should have a dated owner — usually the closer or a dedicated ISA — so recovery dials do not orphan the original book credit.

Closed-by

The closer (or dual-role rep) who ran the sit and wrote the deal. Closed-by does not overwrite booked-by. Both stay on the record.

Split and assist rules (pick one and stick)

Common fair patterns:

1. Fixed split — e.g. 40% book / 60% close (or your numbers) on every attributed deal
2. Dual spiff — flat book spiff + close commission; no percentage fight
3. Self-gen exception — if the closer booked their own sit, they get both book and close credit; document it
4. Assist only with a field — no verbal "I helped" claims without an assist field and a written rule

Whatever you pick, write the edge cases: reschedules, no-shows that later show, dual-decision-maker sits, and storm-week temps. Ambiguity is where politics live.

The fields your call log must have

A cold call tracker for sales teams beats a full CRM here when these fields are phone-first and hard to fake:

1. Booked-by — setter seat, not a shared account
2. Closed-by — closer seat when the deal lands
3. Confirmed-by — if you pay or coach confirmation
4. Outcome — booked, confirmed, showed, no-show, closed, dead (specific reason)
5. Due date / owner — confirmation and recovery work that surfaces on the right morning
6. Campaign / source — promo, storm, referral (helps coaching, not just pay)
7. Short handoff note — why they said yes, spouse involved, competitor quotes

If reps share one login, none of this is honest. Fix seats first — see multi-rep call tracking without shared logins.

Ops rules that keep payday calm

1. Credit is set at the event, not at commission night

Booked-by locks when the appointment is logged. Closed-by locks when the close outcome is logged. Managers can dispute with evidence; they should not rewrite history from vibes on Friday.

2. Confirmation does not steal the book

Unless your written policy says confirmation reassigns credit (almost never), the setter who booked keeps booked-by even if someone else confirmed. Confirmation is a separate field and, if paid, a separate spiff. Pair this with an appointment confirmation call system so the sit still happens.

3. No-shows do not erase the book overnight

A no-show is an outcome, not a rewrite of who booked. Recovery may earn its own small credit; it should not silently reassign the original book unless policy says so for abandoned sits after N days.

4. Self-gen closers are explicit

When a closer books their own calendar, mark self-gen (or set booked-by = closed-by). Do not make setters guess why their leaderboard dropped.

5. Leaderboards show both books and closes

A board that only ranks revenue or only dials trains the wrong behavior. Show books, shows, closes — and keep vanity dials in a secondary view. Same idea as a honest sales leaderboard for dialing teams and a sane outbound sales KPI dashboard.

6. One dispute channel

Disputes go to a manager with the call-log record open — not a group chat pile-on. If the log is blank, the claim is weak. That incentive alone improves logging.

A simple weekly attribution ritual

Spend ten minutes, same day each week:

1. Export or filter deals closed in the last 7 days
2. Spot-check booked-by / closed-by vs calendar and notes
3. Flag missing confirmation owners and ghost "booked" statuses
4. Publish the book and close counts next to revenue (not instead of it)
5. Coach the gaps — shared logins, late logging, mushy outcomes — not the personalities

Sara AI can help summarize weekly outcomes from real call data; it does not replace the written credit policy.

What "fair" looks like in practice

Fair does not mean equal pay for every role. It means:

• Rules are written before the blitz week, not after
• Fields exist so credit is observable
• Both book and close work are visible on the board
• Edge cases have a default answer
• Disputes use the log, not volume of argument

Unfair floors feel like this: "Trust me, I booked half of those," "The closer always steals credit," "We fix it in the spreadsheet later." Fair floors feel boring — and boring pays clean.

Soft start if your log is a mess today

You do not need a six-month CRM project.

1. Write the book vs close rules on one page and post them
2. Give every dialer their own seat — kill shared passwords
3. Require booked-by on every book and closed-by on every close the same day
4. Put confirmation and no-show recovery on dated queues
5. Rank books and closes separately for a month before you tweak spiff math

Grab a free starter layout from the cold call log template if you are still on sheets, then graduate to a phone-first tracker when the sheet fights start again.

Where Dialed Sales fits

Dialed Sales is built for high-activity dial floors that need outcomes, due queues, and per-rep activity without enterprise CRM homework. Attribution stays honest when logging is fast enough to happen between dials and seats are not shared. See pricing when you are ready, or start a free 2-week trial and run your next promo week with booked-by and closed-by already on the record.

Fair books vs closes is not about being nice. It is about a log both roles can defend when the spiff hits.