Metered Copilot spending goes wrong in a specific way: everybody can see the number and nobody owns it. IT can read the admin center but did not approve the budget. Finance holds the invoice but cannot tell which agent workload it covers. The team using it never sees a figure at all. By the time anyone asks, the period has closed and the answer is a shrug.
A workable ownership model needs five named owners, not one. This checklist sets out who they are, what each one has to supply, and how to run a monthly review that ends in recorded decisions rather than a discussion.
Everything below is a suggested operating practice. It is not a Microsoft requirement, a control framework, a compliance obligation or an audit standard. Adapt it to how your organisation actually works.
Quick answer: five things somebody has to own
- Budget approval — the number the spend is measured against, and who agreed to it.
- The financial source — which figure is authoritative, from which system, on what basis.
- Technical scope — what each charge actually covers, and whether two lines overlap.
- The review decision — accept, investigate, or correct, made monthly and recorded.
- Follow-up — the action, its owner, its due date, and whether it closed.
Missing owner 3 is a practical risk: without someone who can say what a charge covers, "investigate" can become a permanent state.
Why metered spend needs different owners than a renewal
A fixed-price SaaS renewal often has an agreed price, a renewal date and a notice deadline, whether its term is monthly, annual or something else. Those are the decisions renewal ownership assigns to an accountable person and a calendar.
Metered spend is different in four ways:
- The amount is not known in advance. It is the result of how much work ran.
- It changes every month, so a decision made once does not hold.
- Consumption and cost live in different systems and are measured in different units, which is a category of confusion in itself — see Copilot credits vs billed charges.
- Multiple workloads can share one billing line, so attributing a figure needs someone who knows what was running.
That is why this is a separate routine rather than an extra row in the renewal meeting. Your renewal register still owns notice deadlines, cancellations and contract dates; the monthly vendor renewal review agenda still owns that meeting. This checklist owns the metered number.
A suggested responsibility table
Roles here are functions, not job titles. In a ten-person company one person may hold three of them — that is fine, as long as it is written down and the person knows it.
| Responsibility | Suggested owner | What they decide | What they must supply |
|---|---|---|---|
| Budget approval | Budget holder — department head, or the founder in a small company | The monthly figure this spend is measured against, and what happens if it is exceeded | A budget per scope, or an explicit statement that there is none |
| Financial source | Finance partner, or whoever receives the bill | Which figure is authoritative, and whether the period has closed | The monetary figure, its source reference, its date, the currency and the tax treatment |
| Technical scope | IT or platform owner who administers the tenant | What each charge covers, and whether two scopes overlap | A scope label and workload per line, plus confirmation that scopes are distinct |
| Review decision | Review owner — usually IT or operations, running the routine | Accept as supplied, investigate, or correction needed, per line | A decision and a reason for every row, monthly |
| Follow-up | Accountable role or team in the tool; agree the responsible person within your own team | Whether the action is done, blocked or overtaken | An owner and a due date on every open action |
| Tenant controls | Whoever holds the administrative role that can change limits | Spending limits, policies and alert thresholds inside the vendor's admin surface | Current limits and who was alerted, as context for the review |
The last row has a documented constraint worth checking before you assign it. In the Microsoft 365 admin center, Global administrator and Billing administrator roles can add, select and change billing methods; AI administrator and License administrator roles can create spending policies and manage limits and alerts but cannot set or modify the billing method. For an already-created spending policy, Microsoft says changing its billing method requires deleting and recreating that policy; the role capability is not an in-place edit guarantee (Microsoft Learn, checked 8 September 2026). Microsoft also recommends roles with the fewest permissions rather than defaulting to Global administrator. A person who only compiles this local review does not need tenant-admin permissions; assign administrative access only to whoever must change the vendor controls.
What each owner actually supplies
The reason this table is worth writing down is that the monthly artifact has empty fields until someone fills them. Mapping owners to fields makes chasing concrete.
- Budget holder → budget per scope. If there is no budget, say so explicitly. In the Copilot Cost Review an empty budget stays unknown rather than becoming zero, and the report prints coverage — "2 of 3 records" — so a partly budgeted review is visible rather than averaged away.
- Finance → the monetary figure and its basis. One currency, one period, and a declared basis of finalized or provisional. A provisional review prints a caveat saying the costs may still change, which is what stops a mid-month figure being quoted as final three weeks later.
- IT → scope labels, workloads and the non-overlap confirmation. No software can verify that two charge scopes do not double-count the same work. Somebody has to assert it, and it should be the person who knows the tenant.
- Review owner → the decisions. Every row gets one, including "accept as supplied".
- Action owners → closure. An action with no owner and no date is a note, not an action.
The monthly agenda
Twenty to thirty minutes, run in this order:
- Confirm the context — period, currency, financial basis, tax treatment. Two minutes, and it prevents most disputes.
- Confirm the scopes are distinct. Ask directly: does any line double-count another? Record the answer.
- Read the total and the coverage — total cost, how many rows have budgets, and the variance on the rows that do.
- Walk the exceptions only. Lines over budget, lines with no owner, lines with no source reference, lines with mixed or unconfirmed workload, and negative adjustments. Do not read out lines that are fine.
- Decide every unreviewed line. Accept, investigate, or correction needed — with a reason.
- Assign follow-ups with a named owner and a due date.
- Check last month's actions. Closed, still open, or overtaken.
- Record the review — reviewer, date, summary, and the next review date.
If the meeting regularly overruns, the problem is usually that the source figures arrive at the meeting rather than before it. Collect them in advance; the review is for decisions.
A worked decision and action example
All figures are synthetic.
Northwind Trading — August 2026, EUR, finalized bill, tax exclusive. Included supplied cost 1,400.00. Budget coverage 2 of 3 records. Budgeted rows only: 1,200.00 cost against 1,000.00 budget, variance 200.00 / 20.0%. Whole-review variance not available — one budget is unknown.
Line
sample-001— Sales enablement pilot, Copilot Cowork, 1,250.00 against a 1,000.00 budget. Decision: Investigate. Note: 25% over the approved pilot budget in the first full month; usage grew in the last week of the period. Follow-up owner: IT Operations. Due: 2026-09-19. Action: confirm which team drove the increase and whether the pilot budget or the pilot scope should change before September closes.Line
sample-002— August service credit, −50.00. Decision: Accept as supplied. Note: monetary service credit applied by the vendor; this is money, not usage credits.Line
sample-003— Service desk automation, Copilot Studio, 200.00, no budget supplied. Decision: Correction needed. Note: this scope was never given a budget. Follow-up owner: Service Desk lead. Due: 2026-09-30. Action: agree a monthly figure with the budget holder, or record a decision that this scope runs unbudgeted.
Three things make that example useful rather than decorative. The over-budget line has a named owner and a date, not "IT to look into it". The credit line is explicitly identified as money rather than usage credits, which is the single most common mix-up in this subject. And the missing budget produces a decision — agree one, or consciously record that there is none — rather than remaining a blank cell forever.
Closing the loop: follow-ups and the next review
A review that produces actions and never checks them is theatre. Two habits fix it.
Manually carry the open actions into the next agenda item 7, by name, using the saved review or your own action tracker. The tool does not transfer them into a new period. An action that has slipped twice needs an explicit owner and closure decision.
Start the next period cleanly. In the Copilot Cost Review, Start next review keeps only the organization, scope and owner labels and clears every amount, budget, reference, date, decision, action and the sign-off. There is no projected cost and no date carried forward — you choose the new period and re-confirm the scope and budget declarations against the new figures. That is deliberate: last month's approval must not silently become this month's.
The completed review is your own record. In the tool the reviewer label is a role or team rather than a personal identity claim, and the report states that a completed review is the reviewer's own record, not an identity-verified approval or an audit sign-off. Keep the saved JSON and the PDF; the Copilot cost report template covers what each output preserves.
Where this stops
- This is a suggested operating model. Microsoft does not require it, no standard mandates it, and following it is not compliance with anything.
- It is not about people. Ownership is recorded at the role or team level. This is not per-user cost attribution, usage inspection, productivity measurement or employee monitoring, and the tool has no ability to do any of them.
- CertPilot does not enforce it. There are no reminders, escalations, notifications or approvals. It records what you decided.
- It does not replace renewal accountability. Notice deadlines, cancellations and contract decisions stay with your renewal process and the Renewals & Vendor Register.
- It does not replace a systems record. If you keep business and technical owners in a systems catalog, use it as the source for the owner labels rather than maintaining a second list.
The free Copilot Cost Review runs entirely in your browser tab, with no account and no upload — your figures stay with you, which also means nothing is saved to a CertPilot workspace. For the artifacts that do live in the platform, see the sample evidence reports; for how CertPilot draws the line between what it can and cannot prove, see the methodology.
Frequently Asked Questions
Should IT or finance own the number?
Both, for different parts. Finance owns which monetary figure is authoritative, its period and its basis. IT owns what each charge covers and whether the scopes overlap. Splitting it this way avoids the usual deadlock where finance cannot explain the line and IT cannot vouch for the amount.
What does an MSP own when the client holds the subscription?
Usually technical scope and the review routine: labelling what each charge covers, running the monthly review, and producing the artifact. Budget approval and the authoritative financial figure normally stay with the client, because they hold the billing relationship. Write the split down at the start of the engagement — this is exactly the boundary that gets disputed later.
What if there is no budget at all?
Record that explicitly rather than leaving budgets blank by accident. The review will show coverage — how many rows have budgets and how many do not — and the whole-review variance is withheld rather than guessed. "No budget agreed yet, owner and date assigned" is a legitimate, reviewable position. A blank cell is not.
What happens to an unresolved action?
It stays open in the saved review until you resolve it. Start next review clears actions, so carry follow-ups manually into your next agenda or action tracker. An investigate or correction_needed action can remain open in a Reviewed report if it has a note, owner and due date. The tool blocks Mark reviewed for unreviewed decisions or incomplete actions, not for every open action; the other review-completion conditions still apply.
Is any of this a Microsoft or compliance requirement?
No. The responsibility table, the agenda and the cadence are suggested operating practices for lean teams. The only externally documented items are Microsoft's own administrative role capabilities, which are cited above. Nothing here is certification, an audit standard, or legal or financial advice.