The Copilot Allocation Method
Decision Checklist
Twenty minutes to a defensible method for the Copilot metered line. Five for the materiality gate, ten for twelve yes/no questions, five to write the decision down. No workshop. No steering committee.
Free to read and print. No signup, no gate, no email required.
What this is
The decision half of a chargeback model. Everything you need to choose a method and defend the choice.
What this is not
The build. It does not calculate your allocations, draft the policy finance signs, or run your monthly close. If you finish this and the answer is “build it,” the tooling is linked at the bottom.
The one fact worth getting right first
The June 2026 Copilot billing change is additive. Cowork credits and agent runs bill in Copilot Credits at $0.01 per credit (Microsoft list price, as of June 2026), on top of the flat per-seat licence. The per-seat price did not change. If someone in your organisation is saying Copilot moved to consumption pricing, correct them before you design anything.
What did change is that one invoice now needs two allocation methods. Headcount logic still splits the seats correctly. It cannot split a credit pool. That is the entire problem this checklist solves.
If you are on an enterprise agreement, your negotiated rates differ from list. Swap in your own numbers. The method does not change.
The four methods you are choosing between
Direct metered attribution
Each user's or agent's credits map to a cost center.
Consumption-share allocation
The metered pool splits by each business unit's share of total credits.
Seat-weighted allocation
The metered pool splits by each unit's share of assigned seats. The honest fallback.
Fixed percentage with quarterly true-up
Agreed percentages, trued up against actual consumption each quarter.
The materiality gate
One division decides whether you build anything at all.
metered_line / invoice_total
If the result is under 5%, stop here. Do not build chargeback machinery for a rounding error. Run showback for two quarters instead: publish each unit’s number, charge nobody, and re-run this gate at every monthly close.
The 5% floor is a working assumption, not a FinOps standard. If your finance partner already has a materiality threshold, use theirs and cite it in the policy.
Clearing the gate does not force chargeback onto every line. You can charge back the lines that attribute cleanly (an agent that maps 1:1 to a cost center) and show back the rest. Arithmetic where attribution is clean, patience where it is not.
Record your result now, with today’s date. A gate you fail at 3% today can pass by autumn, and the only way to know is a dated series.
The twelve questions
Answer yes or no. Each yes is one point for the method named in its block. If you have to guess, the answer is no.
Method 1, direct metered attribution
Questions 1 to 3- 1.Does your admin-center usage export tie at least 90% of metered credits to a named user or a specific agent identity? Below 90% you will chase orphan credits every close.
- 2.Can you map those identities to cost centers from data you already maintain (Entra attributes or an HR feed), refreshed at least monthly?
- 3.Will unit leaders accept statements that name consuming users and agents, and has your privacy team cleared user-level cost reporting?
Method 2, consumption-share allocation
Questions 4 to 6- 4.Can you get reliable credit totals per unit or department even where user-level rows are missing or masked?
- 5.Is consumption visibly uneven, with the heaviest unit burning at least twice the credits per seat of the lightest? An even spread kills the case for consumption math, because seat-weighting gives the same answer cheaper.
- 6.Will budget holders tolerate charges that move with actual usage month to month?
Method 3, seat-weighted allocation
Questions 7 to 9- 7.Is your usage history thin: under three full months of exports, or missing attribution for a large share of credits?
- 8.Do you need a defensible number in this month’s close, before any identity mapping exists?
- 9.Are credits roughly proportional to seats anyway? Check it. Divide each unit’s credits by its seats. If the ratios land within about 25% of each other, seats are an honest proxy.
Method 4, fixed percentage with quarterly true-up
Questions 10 to 12- 10.Does finance require a predictable charge, the same number every month within a quarter, for budget holders?
- 11.Do you have more than ten units, where monthly recomputation costs more in meetings than the variance is worth in dollars?
- 12.Is monthly credit volume swinging more than 30% month over month (an illustrative bar, calibrate against your own history), so a consumption charge would whipsaw budgets?
How to read your answers
- •Tally the yes marks per block. The highest score is your method.
- •Ties break toward the lower-numbered method. More granular attribution survives finance review longer.
- •One override: yes on both question 1 and question 2 means Method 1 wins any tie outright. You have the data, so use it.
The most common tie is Method 1 against Method 2 at two points each: your export attributes well, but the privacy answer on question 3 was a guess. That is what the override is for. Take Method 1, and get the privacy answer in writing before the first statements go out.
The shared-pool rule applies whichever method wins
Some agents serve everyone: the IT helpdesk bot, the HR policy bot. Their credits are real, billed, and unownable by any single cost center. Pool them and reallocate by seat share, not consumption share:
unit_shared_cost = shared_pool_total * (unit_seats / total_seats)
A shared agent’s cost scales with who can call it, not with who runs Cowork hardest. Reallocating shared cost by consumption charges your heavy users twice. No method exempts you from this.
Write it down
The decision is worthless undocumented, because in four months nobody will remember why. Record these lines on a single page and get it in front of whoever owns the budget.
COPILOT COST ALLOCATION DECISION Gate result: metered / total = ____% as of ____________ Verdict: [ ] showback only [ ] chargeback Method per line type: Per-seat layer: ______________________________ Attributed credits: ______________________________ Shared-agent pool: seat-share reallocation Reopen this decision when: 1. The metered line crosses the gate threshold in either direction 2. Attribution coverage crosses 90% in either direction 3. ______________________________ Decided by: ______________ Date: __________ Next review: __________
Those are the two triggers that fire most often, so they are pre-filled. The third line is yours.
A signed page like this is the difference between a chargeback model and an opinion. Twenty minutes, one method, and a written record finance can hold you to. That last part is the point.
If the answer was “build it”
This checklist got you the decision. The build is four things: a calculator whose totals tie to the invoice to the cent, a policy page finance will actually sign, a repeatable monthly close, and the reconciliation discipline that survives a disputed statement.
The Copilot Chargeback Playbook is that build: a 22-page playbook with two worked examples, a 10-tab workbook with the formulas live in the cells, the one-page policy template, and a 40-minute monthly close runbook.
Get the Chargeback Playbook, $49You do not need it to use this checklist. That was the point of publishing the checklist.
Copilot cost changes again next quarter
AI at Work goes out every other Tuesday: what changed, what it costs, and what to do about it. No vendor sponsorship.
Where to next
The Copilot Chargeback Playbook
The calculator, the policy template, the monthly close runbook, and two worked examples. $49.
Open→The Real Cost of Copilot
What a Copilot rollout actually costs once you count the credit line, the licences and the time. $29.
Open→M365 Copilot Field Guide
Free reference guides for every Copilot surface, including Cowork, Work IQ and the admin analytics.
Go→Kesslernity. Independent practitioner, no vendor sponsorship. Prices cited are Microsoft list as of June 2026. Worked examples in the playbook use invented organisations and are labelled as illustrative. This is cost-allocation guidance, not tax, accounting or legal advice.