The Business Has Targets but No Trusted Baseline

What the problem looks like and why it affects the business

If leadership approves a growth or service target without agreeing the starting population, period, source and exclusions, later performance can be made to look better or worse simply by changing the comparison.

Bottom line: A target without an accepted baseline turns investment review into an argument about history instead of a decision about progress.

Use this guide to agree a reliable baseline before judging a target. It is written for executive sponsors, product leads or analytics leads. Confirm budget approval with the executive sponsor or investment owner. Scope: This measurement question only. A full data or reporting redesign needs a separate assessment. Check commercial figures against the authoritative source, keep correlation separate from causation and collect only data that serves the decision.

What you should be able to decide

Use the evidence to decide what to keep, correct, investigate, pause or retire. The task is to define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement.

What to expect in the working pack

The Baseline Evidence and Acceptance Register contains six XLSX sheets to complete as you follow the method:

1. Decision charter records the decision about “the business has targets but no trusted baseline”, its authority, economic or service exposure, scope and evidence threshold.
2. Metric contracts prevents labels from hiding different populations, periods, exclusions or meanings.
3. Collection and lineage traces permitted records and events from source through transformation and destination.
4. QA and reconciliation keeps expected results, observed results, discrepancies and evidence classifications separate.
5. Issues and actions converts verified problems into owned, reversible work with acceptance gates.
6. Decision and learning log preserves the decision, confidence, limitation, review date, observed outcome and reopen trigger.

Open the pack before Step 1. Record the task to define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement. Use stable IDs such as DEC-001, MET-001, LIN-001 and TST-001 to connect the decision to its sources and tests. Update the sheets as you work so the audit trail does not depend on memory.

What evidence distinguishes the real cause

One dashboard cannot establish the cause. To agree a reliable baseline before judging a target, compare relevant operational, customer, CRM, finance and platform evidence using authorised sources.

To agree a reliable baseline before judging a target, label each material item VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION. A verified item has an authoritative source or reproducible test; it does not make the conclusion universally true. Explain inferences and alternative causes. Keep proposed controls separate from existing ones, and mark missing authority, access or evidence as requiring validation.

Establish the metric contracts before interpreting movement

Use the definitions below in Metric contracts to agree a reliable baseline before judging a target Agree any changes with the accountable owners. These are working definitions, not universal benchmarks.

For “the business has targets but no trusted baseline”, capture data freshness, sampling, thresholding, cardinality, missing values and late-arriving outcomes wherever they could change the decision. A platform can correctly process the data it received while the organisation still has the wrong definition, an incomplete population or an unsafe conclusion.

How to fix it step by step

Step 1: Charter the decision and the exposure

Write the exact decision before discussing a dashboard, event or metric: Define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement. Name the accountable authority, the economic or customer exposure, the scope boundary and the latest useful decision date.

Use in the working pack: Decision charter.

Required output: A charter for “the business has targets but no trusted baseline” with a stable Charter ID, named authority, scope, evidence threshold and a condition for stopping or escalating.

Decision gate: Agree who can authorise this task before continuing: Define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement.

Step 2: Preserve the current evidence before changing it

Capture the reports, source records, definitions, dates, filters, exclusions, versions and meeting or workflow evidence that currently produce the symptom. Rewrite the target as a decision contract: the measure, eligible population, observation window, desired direction, guardrails and what action follows success or failure.

Use in the working pack: Decision charter and QA and reconciliation.

Required output: A dated current-state record of “the business has targets but no trusted baseline” that another reviewer can reproduce without relying on screenshots alone.

Decision gate: For this investigation, treat missing source access, unexplained transformations or changed historical reports as visible limitations, not permission to infer the missing evidence.

Step 3: Define the measures and their boundaries

Inventory candidate baseline sources and identify definition changes, missing periods, late data, sampling, thresholding and operational incidents. For each retained measure, write the name, definition, eligible population, period, dimensions, source of truth, exclusions, owner and version.

Use in the working pack: Metric contracts.

Required output: Metric contracts for the decision to define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement, with distinct definitions for unlike measures.

Decision gate: Reproduce each measure from authorised evidence. A platform display cannot, by itself, support the decision to define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement.

Step 4: Trace source, collection and transformation

Select a representative window or a clearly bounded range. Do not choose a convenient low point merely because it makes the target easier to reach. Link the originating record or permitted event through every material transformation and destination. Record consent or lawful-use state when personal information or identifiers are present.

Use in the working pack: Collection and lineage.

Required output: A source-to-decision lineage for “the business has targets but no trusted baseline” that exposes broken, duplicated, delayed, transformed or non-comparable evidence.

Decision gate: Pause work on the business has targets but no trusted baseline wherever the source records and transformations cannot explain the reported value.

Step 5: Test contradictions and negative cases

Recalculate the baseline independently from source evidence and reconcile it to the current report. Classify unresolved gaps rather than averaging them away. Use a bounded sample that includes normal records, exceptions, missing values, delayed outcomes, duplicates and a case expected to fail. Record expected and observed evidence separately.

Use in the working pack: QA and reconciliation.

Required output: Reproducible tests for “the business has targets but no trusted baseline” with source evidence, destination evidence, discrepancies, disposition and retest ownership.

Decision gate: Include failed and exception cases when investigating the business has targets but no trusted baseline. Evidence that passes only the easiest route or hides important contradictions is insufficient.

Step 6: Choose, own and release the correction

Turn each verified gap into an action with severity, affected decision, evidence reference, owner, dependency, rollback trigger and acceptance gate. Approve the baseline with a version, confidence statement, exclusions and reopen conditions before using it to judge performance.

Use in the working pack: Issues and actions.

Required output: Prioritised actions for “the business has targets but no trusted baseline”, with definition, collection, source, operating and decision-use changes recorded separately.

Decision gate: The owner must accept the corrected evidence for its intended use: Agree a reliable baseline before judging a target. Confirm its limits before release; technical completion alone is insufficient.

Step 7: Record the decision and later learning

Record the decision about “the business has targets but no trusted baseline”, who made it, which evidence was used, the confidence and every known limitation. Assign the action and schedule a review after enough time has passed for the relevant outcome or guardrail to be observed.

Use in the working pack: Decision and learning log.

Required output: A recorded decision that can be checked against this acceptance condition: The target and baseline use the same definition and population, source changes and uncertainty are visible, and an authorised owner has accepted the comparison and reopen triggers.

Decision gate: A changed report does not resolve “the business has targets but no trusted baseline”. Close the work when the owner accepts the evidence for the decision and schedules a later outcome review.

Who must be involved

The six value paths cross functional budgets, evidence and ownership; diagnosis therefore needs cross-functional authority, access and independent challenge, whether led internally or externally. A capable internal team can lead when it has the required authority, source access, domain competence and ability to challenge the original assumptions. Escalate or use qualified external support where material evidence is contested, privacy or legal judgement is required, system access is fragmented, or the same incentives that produced the measure could suppress contrary findings.

Worked example

A team targets a 20% improvement using last month as the baseline. Review shows that last month contained a tracking outage and a holiday closure. The owner adopts a multi-period range with explicit exclusions and keeps the anomalous month visible as an incident, preventing the target from being judged against an artificially low start.

This is a hypothetical method example, not an Abrasim client result, benchmark or performance promise.

How to verify the data can support the decision

To check whether the correction supports the task to define eligible population, period, source, exclusions, uncertainty and acceptance before judging movement, test collection, definitions, reconciliation, decision use and later outcomes separately. A firing tag, populated report or better-looking dashboard is insufficient:

• Collection gate: the permitted event or record needed for “the business has targets but no trusted baseline” is observed with the expected fields and consent or lawful-use state.
• Definition gate: the metric can be reproduced from its contract, population, period, exclusions and version.
• Reconciliation gate: representative normal and exception records agree with the authoritative source within an approved, explained tolerance.
• Decision gate: the accountable owner can interpret the measure, its confidence and its limits and can choose an authorised action.
• Outcome gate: after the relevant lag, the action and later customer, operational, commercial or risk evidence are reviewed separately.

Accept the work only when: The target and baseline use the same definition and population, source changes and uncertainty are visible, and an authorised owner has accepted the comparison and reopen triggers.

Use at least one negative case. A precise baseline is not trustworthy merely because it contains decimals; precision cannot repair missing coverage or a changed definition.

Record failed tests for “the business has targets but no trusted baseline” rather than deleting or overwriting them. Reopen the decision when the definition, source, transformation, ownership, material market condition or observed relationship changes. Roll back a release that duplicates outcomes, hides an unknown population, breaks a control, exposes personal information or removes an evidence path needed for this decision.

How to keep the problem from returning

• Version baselines and retain the calculation evidence.
• Reopen the baseline after material source, policy, product or market changes.
• Report non-comparable periods separately instead of restating them silently.
• Review metric contracts, lineage and decision use at the recorded review-by date and after material system or operating changes.
• Retain source evidence and version history long enough for the authorised review while following approved access, retention and deletion controls.
• Keep implementation acceptance, operating adoption and later business movement as separate records.

Primary sources and evidence boundary

Primary guidance was reviewed at the 30 August 2026 source cutoff:

• US Government Accountability Office : Assessing Data Reliability : Primary government audit material covering planning, source review, testing, control consideration and explicit reliability determinations.
• Google Analytics Help : Data freshness : Official platform documentation on processing intervals, late data and the possibility that reported values change after initial availability.
• Google Analytics Help : About data sampling : Official platform documentation on sampled results, query limits and approximate distinct counts.

The sources above establish controls relevant to “the business has targets but no trusted baseline”; they do not prove Abrasim client outcomes or the cause of a specific organisation's performance. POPIA, privacy, employment, financial and sector-specific decisions remain with qualified authorised owners.

Where definitions, sources, ownership or commercial consequences remain contested, Establish the evidence needed for a valid target. You can use this guide internally. Seek support when the decision needs cross-team access, independent challenge or assurance over a high-risk change.