What belongs in an executive delivery report?
Broadcastwell measures and fixes whether AI search engines name B2B software companies.
Run the free checkThis page preserves a delivery template for orders before 26 October 2026. It is a historical example, not a current offer.
Classification: Template only; a blank field blocks client delivery. Version: bw-content-2026-09-24-v1.
Executive decision
Company, intended buyer and confirmed category: [enter]. Scope approval ID/date and question-set version: [enter]. Decision requested: [implement a supported bounded fix / refine scope / gather missing evidence / no further purchase justified]. Name the strongest supported finding, its limitation and the next decision in three sentences. Implementation is separate unless the actual contract explicitly includes it; do not infer a review session or new allowance.
Coverage that actually ran
Expected observation slots under the confirmed scope: [N]. Completed [N]; failed [N]; untested [N]; uncertain [N]. These result states must sum to the expected slots. Within completed records: reviewed present [N], reviewed absent [N], not yet evaluated [N]. Explain every exclusion. Do not calculate a mention rate over failed or unreviewed records. If a percentage is useful, name its precise eligible denominator and preserve counts. Repeats are not assumed independent buyers.
Record actual engine, interface, provider, locale, time window, method version, question IDs and receipt references. Consumer interfaces, API/provider proxies, public historical research, synthetic fixtures and fresh customer measurement must remain distinguishable. Unknown fields remain unknown; they do not inherit marketing labels.
Findings with decision context
For each finding provide: stable finding ID; exact question; dated completed receipt or failure state; observed wording and mention classification; returned sources; separate verified product/page evidence; interpretation; alternative explanations and uncertainty; buyer relevance. No screenshot alone establishes lost revenue or the cause of an absence. Include inconclusive and no-improvement findings.
Three prioritized work orders
Use the work-order interchange schema and companion implementation notes. For each include the evidence-supported problem, exact affected page/source, proposed wording/change, dependencies, priority rationale, recommended role, bounded allowance, acceptance checks, real owner/approver when confirmed, due date when confirmed, and recheck eligibility. Delivered states require real completion and recipient-facing access evidence. Do not prefill approvals, dates or owners as facts.
Next decision and purchase boundary
State why the evidence supports the recommended next step and when no implementation purchase is justified. Link only the current reconciled offer if recommending a service. Record included/excluded work, prerequisites and actual purchased allowance. Written explanation is the default until any live review session has a confirmed owner, cost, staffing and prospective inclusion.
Evidence appendix and delivery
Attach the exact approved observation export, source passages/fact versions, receipts or permitted receipt references, work orders and failure/exclusion table. Record classification and tenant permissions. Reviewer identity: [record actual]. Reviewer type: [record actual]. Review date: [record actual]. Review reference: [link to the supporting review record]. Technical reviewer identifiers belong in that supporting record. Candidate version/hash: [required]. Intended recipient/account access test: [required]. Delivery receipt/time: [required]. All remain open until evidence exists. A local file or passing fixture does not establish delivery.