A Google Ads ROAS report that creates no disagreement has failed.
Agreement can be valid when the evidence is decisive, but manufactured harmony hides the cost: budget moves while nobody accepts responsibility. A report that nobody could disagree with is a report that decided nothing.
The ROAS reporting template that works forces a named recommendation and a named risk onto every page. The deliverable is a controlled commercial argument, not a catalogue of metrics.
Why a ROAS reporting template should force a decision
Four systems can hold four different versions of return. Google Ads may show attributed conversion value, GA4 recorded activity, the CRM qualified pipeline and finance recognised revenue.
Blending those numbers does not resolve the disagreement. It conceals it.
If the underlying definitions remain contested, settle them separately using our guide to reconciling reported and finance-recognised return. The report should then expose the remaining difference and request a decision.
Apply the vagueness test bluntly: if a line in a report cannot be wrong, it is not reporting; strike it.
“Lead quality improved” cannot be disproved. An illustrative line such as “7 sales-accepted opportunities versus 5 planned, according to the CRM at 3 August” can be challenged, checked and acted upon.
Our claim is falsifiable: every page using this structure will produce an approve, reject or defer decision; one completed review containing an undecided page proves the structure failed.
The honest limit here is that reporting cannot establish facts the business never captured. It can label uncertainty and assign ownership, but it cannot manufacture evidence. A structured attribution audit belongs before reporting when definitions remain unresolved.
Useful reporting makes disagreement precise.
Three audiences, three cadences, one ROAS truth
Sending every detail to everybody is not transparency. It transfers the editor’s job to the reader.
| Audience | Cadence | What they receive | What is deliberately withheld |
|---|---|---|---|
| Operator | Every Monday, covering the previous 7 days | Spend versus pace, source-level outcomes, material changes, exceptions and the open decision queue | Board narrative, valuation assumptions and decisions outside delegated authority |
| Marketing lead | Monthly, by the third working day | Commercial summary, 30-day versus 90-day comparison, recommendations, risks and unresolved ownership | Search-term rows, tag-debugging detail and daily volatility |
| Board | Quarterly, within 10 working days of quarter-end | Budget versus plan, finance-recognised return, two-quarter direction, major risk and requested decision | Keyword detail, operator change logs and platform value presented as revenue |
“Withheld” means absent from the default pack, not hidden. Supporting evidence remains available when it could change the decision.
The marketing lead should not receive the operator’s report with rows collapsed. The board should not be asked to arbitrate between attribution settings. Each audience receives a purpose-built reading layer over the same definitions.
Implementation evidence belongs in the 30-point measurement implementation check, not inside a commercial decision pack.
Audience discipline protects decision quality.
The ROAS report’s four-part contract
Metrics earn space only when they change an accountable choice.
Every report section uses the same four fields:
- The number. State the measure, system, cut-off date and whether it is final or provisional.
- The comparison. Name the plan, previous period, mature cohort or alternative source used as the baseline.
- The decision. Specify which of three states is required: approve, reject or defer.
- The person. Give one person’s full name, decision deadline and consequence of silence.
The copyable sentence is:
[Number and source] measured against [named comparison], supporting [decision], owned by [full name] by [date].
Adopt these five release rules as governance defaults, not claimed industry benchmarks:
- Spend more than 10% above or below planned pace by day 10 triggers an operator explanation and a marketing-lead decision within one working day.
- A platform ROAS more than 25% away from finance-recognised ROAS for two consecutive months puts both figures on the page and makes finance’s figure primary for board decisions.
- More than 20% of qualified pipeline lacking an assigned source makes the month provisional and blocks budget expansion.
- A median sales cycle above 45 days paired with a 30-day report triggers a 90-day cohort comparison and withholds the current-month revenue verdict.
- A recommendation left undecided for five working days is escalated to the named executive, while dependent changes remain paused.
The report records strategic choices; it does not invent them. Budget allocation should follow a defined B2B paid-search strategy agreed before individual campaign results arrive.
Ownership turns reported variance into action.
If the path from ad click to signed revenue still has gaps, Actualyse will trace each hand-off with you — book a call
A copyable ROAS reporting template with a worked month
Page order should follow the decision being requested. Repeat this six-block structure for every material issue:
1. CONTEXT
Audience: [operator / marketing lead / board]
Period and cut-off: [dates]
Status: [final / provisional]
2. NUMBER
Measure: [value]
Source: [Google Ads / GA4 / CRM / finance]
Definition: [what is included and excluded]
3. COMPARISON
Current: [value]
Baseline: [plan / prior period / mature cohort / other source]
Variance: [value and direction]
4. RECOMMENDATION
Action: [approve / pause / reallocate / investigate]
Amount and timing: [£ and date]
5. NAMED RISK
Risk if approved: [specific downside]
Risk if rejected: [specific downside]
6. DECISION CONTROL
Owner: [full name]
Decider: [full name]
Deadline: [date]
Status: [approved / rejected / deferred]Take an illustrative UK industrial consultancy spending £8,000 in July. Every input below is invented solely to demonstrate the structure and arithmetic.
Worked month’s summary — illustrative account
Input — media spend: £8,000 actual versus £10,000 planned
Input — Google Ads conversion value: £48,000
Input — CRM qualified pipeline: £32,000 actual versus £25,000 target
Input — finance-recognised cohort revenue: £12,000
Input — sales-accepted opportunities: 4 actual versus 5 planned
Input — form leads: 14 actual versus 18 planned
Input — unassigned qualified pipeline: £4,000
Input — median sales cycle: 75 days versus a 30-day reporting window
Platform-reported ROAS = £48,000 ÷ £8,000 = 6.00x
Qualified-pipeline ROAS = £32,000 ÷ £8,000 = 4.00x
Target qualified-pipeline ROAS = £25,000 ÷ £10,000 = 2.50x
Finance-recognised revenue ROAS = £12,000 ÷ £8,000 = 1.50x
Spend variance = (£8,000 − £10,000) ÷ £10,000 = −20%
Unassigned pipeline share = £4,000 ÷ £32,000 × 100 = 12.5%
Comparison: platform-reported ROAS is 6.00x versus finance-recognised ROAS of 1.50x; pipeline ROAS is 4.00x versus the 2.50x target.
Recommendation: keep August spend at £8,000 rather than returning to the £10,000 plan until the 90-day cohort update.
Named risk: false restraint — the cap could suppress demand while pipeline ROAS remains above target.
Illustrative owner: Amira Khan, marketing director.
Decision required: approve or reject by 5 August.
The recommendation follows the 75-day versus 30-day timing conflict, not an industry benchmark.
Use ongoing Google Ads management when an external owner should run the cadence and execute decisions. Choose a scoped paid-media optimisation project when an internal team will operate the report after a defined reset.
A recommendation without a named risk is sales copy.
Four ROAS reporting habits that do not work
Polished packs often survive because they make weak performance easier to discuss without forcing a choice.
- One blended ROAS. Combining platform value, pipeline and recognised revenue erases the exact attribution disagreement the report needs to expose.
- Green, amber and red without thresholds. Colour expresses the author’s mood unless the trigger and resulting action are written beside it.
- Automated commentary such as “performance remained strong”. The sentence cannot be falsified, identifies no comparison and leaves nobody accountable.
- A 30-day campaign league table for a 75-day sales cycle. The ranking penalises recent spend before revenue matures and rewards older campaigns with more elapsed time.
Decorative reporting preserves arguments.
FAQ
1. What should the report show before any deal closes?
Once a cohort reaches one median sales cycle without recognised revenue, the sales director must choose whether to extend observation, reject pipeline quality or stop spend. Before that threshold, pipeline remains pipeline; revenue ROAS is unavailable, not zero.
2. How much history should the first report include?
Use 13 complete weeks or 3 complete months, whichever provides the longer period under one consistent definition. If definitions changed halfway through, split the before-versus-after periods and let the marketing lead choose the new baseline.
3. Who breaks a sales-versus-marketing attribution deadlock?
When disputed opportunities represent more than 10% of qualified pipeline, the chief revenue officer adjudicates the affected records within five working days. Accepted and disputed values remain separate until that decision.
4. Should agency and technology fees be included in ROAS?
Show media-only and fully loaded return side by side whenever management and technology fees exceed 10% of media spend. Finance uses the fully loaded figure for cash allocation; the operator uses media-only return for auction decisions.
5. When should the board receive a monthly report?
Switch from quarterly to monthly when paid media exceeds 15% of controllable growth spend or cash runway falls below 6 months. The board sponsor ends the exception after two consecutive on-plan months.
Quarterly board reporting keeps strategic decisions above campaign noise.
Summary
- Rule 1 of 5: Any line without a falsifiable number and source is struck.
- Rule 2 of 5: Every page carries one recommendation, one named risk, one owner and one deadline.
- Rule 3 of 5: More than 20% unassigned pipeline makes the report provisional.
- Rule 4 of 5: A platform-to-finance gap above 25% for two months puts finance first.
- Rule 5 of 5: Every recommendation unresolved after five working days goes to the named executive.
Actualyse builds measurement and attribution setups that tie B2B ad spend to real revenue. Book a call to talk through where yours stands.
