What exists, what overlaps, and what can safely go?
Reports multiply. Ownership, definitions and dependencies become harder to trace. Clearing the estate starts with decisions about what people rely on, not a deletion list.
Before a change: Establish purpose, ownership and evidence.
Before new work: Check reuse and the prerequisites for the intended decision.
The reporting estate
A growing pile of reports. A different decision for each.
Two similar reports may need consolidation. A quiet report may still serve a critical review. Establish the purpose before choosing the action.
Daily Ride Completion
Completed Trips Daily
Period Close Exceptions
→
Check the purpose and evidence
→
Equivalent? Compare and consolidate.
Still required? Protect the dependency.
Unresolved? Hold the affected change.
Illustrative paths, not measured estate results. Consolidation still requires owner acceptance and a safe transition.
01 / Inventory
What exists, and what is still unknown?
Start with an asset and its intended use. The reporting analyst records owner, consumers, sensitivity, definitions, cadence and dependencies before proposing change.
Decision pathFollow the branch supported by the evidence.
Start with an asset
↓
Check / Reporting analyst
Is its purpose and evidence established?
Evidence established
Evidence complete → continue to equivalence or retirement assessment.
Evidence missing
Owner, telemetry or sensitivity unknown → hold the affected change; the reporting lead assigns the missing check.
What evidence belongs beside the decision?
Check ownership and coverage. The business owner confirms purpose and consumers. The analyst checks all use routes, including scheduled deliveries and periodic obligations. Keep the source, observed result, accountable role and next action together. If the check is incomplete, retain the gap rather than infer clearance.
02 / Authority
Are these reports interchangeable?
Compare what the reports mean for the same business decision. Titles and matching totals cannot establish equivalence.
Decision pathFollow the branch supported by the evidence.
Compare similar reports
↓
Check / Metric steward
Are they interchangeable for this purpose?
Equivalent and accepted
Equivalent and accepted → nominate one maintained source of record, then validate the transition.
Different or disputed
Meaning differs → retain and label a legitimate variant. Definition disputed → hold the combined claim and assign reconciliation.
What evidence belongs beside the decision?
Compare the contract behind the view. The metric steward compares definition, grain, population, cutoff, freshness, audience and dependencies. The business owner selects an authoritative version only within an agreed purpose. Keep the source, observed result, accountable role and next action together. If the check is incomplete, retain the gap rather than infer clearance.
03 / Retirement
What can safely go?
A candidate for retirement is not permission to delete. Protect the consumer before withdrawing the route.
Decision pathFollow the branch supported by the evidence.
A candidate for withdrawal
↓
Check / Reporting analyst
Can the change be reversed without disruption?
Transition ready
All conditions recorded → withdraw reversibly, observe and obtain final disposition before any irreversible removal.
Gap or broken dependency
A gap before withdrawal → hold. A required dependency breaks during observation → restore the route and return the current replacement to validation.
What evidence belongs beside the decision?
Validate, authorize, notify, then observe. The business owner approves the bounded change. The analyst verifies replacements and dependencies, records consumer notice, retention expectations, an observation window covering actual cadence and a rollback route. Keep the source, observed result, accountable role and next action together. If the check is incomplete, retain the gap rather than infer clearance.
04 / Access
Who can use which output?
Start with purpose, audience and fields. A restricted contributor may need structural metadata rather than sensitive source rows.
Decision pathFollow the branch supported by the evidence.
A task and its intended audience
↓
Check / Access reviewer
Are fields, audience and channel authorized?
Reviewed and authorized
Known review and explicit approval → provide only the stated alternative through the approved route.
Unknown or unapproved
Unknown classification, approval or destination → hold delivery and request review. A changed scope returns to this check.
What evidence belongs beside the decision?
Review the alternative, not just its title. The authorized access reviewer confirms classification, permitted audience, purpose, fields, channel and approval. A synthetic alternative must actually be synthetic. Keep the source, observed result, accountable role and next action together. If the check is incomplete, retain the gap rather than infer clearance.
05 / Prevention
What keeps the estate from refilling?
Give requests a front door. Start from a business question and search for reuse before commissioning another report.
Decision pathFollow the branch supported by the evidence.
A new business question
↓
Check / Sponsor + metric steward
Can existing work meet the accepted need?
Reuse or justified new work
Existing asset fits → reuse. A justified gap with accepted prerequisites → validate a new or revised view.
Prerequisite unresolved
A prerequisite is unresolved → hold the dependent claim. Ready independent work can proceed while the steward closes that gap.
What evidence belongs beside the decision?
Gate the use, then maintain the asset. The sponsor and metric steward agree definition, population, timing, source lineage, quality, access and acceptance evidence. Assign owner, steward and review triggers. Keep the source, observed result, accountable role and next action together. If the check is incomplete, retain the gap rather than infer clearance.
06 / Apply
Follow a decision through the work
Choose a fictional case, check its evidence and follow the next accountable action. Explore the conditions at each step; these choices do not approve or execute a real change. The five guides above stay fixed.
Earlier choices
Choose an earlier decision to change it. Later choices will be cleared.
Choose a case card, or read the worked examples below. Both access-evidence branches remain available without the walkthrough script.
Changes the walkthrough and its record only.
SC-01 / Fictional case
Two titles, one purpose
Give operations one agreed view of completed transport work.
Starting evidence: Both views have documented daily consumers; consumer interviews confirm the same use
Accountable role: Operations reporting owner. Unresolved: Replacement acceptance and retirement authorization are still required.
Step 1 of 3
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Reporting analyst
Establish equivalence
Compare definition, population, grain, cutoff, freshness and audience, not the titles.
Equivalent for the stated daily purpose → propose consolidation.
Material difference or missing comparison → retain both provisionally and reconcile the gap.
Exit: A documented comparison is ready for the reporting owner.
stop withdrawal or restore the old route and return to validation.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Explored path result / no real authorization
Proceed only with the bounded, reversible transition
Acceptance and authorization recorded → begin reversible withdrawal, then monitor before final disposition.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Original case evidence and worked records
Evidence behind this case
Authored case facts, not production documents. References stay visible so the decision can be inspected.
E-01A
Definition comparison
Source note
The two views share leg identifier, completed status rule, service-day population and overnight close.
No material definition difference was found in this fictional comparison.
E-01B
Consumer dependency check
Source note
The dispatch reviewer and briefing owner confirm the same purpose.
Both require replacement acceptance before the redundant route is withdrawn.
E-01C
Authority decision
Proposed authority
The operations reporting owner selects Daily Ride Completion as the proposed source of record because its ownership and maintenance route are explicit.
This is a worked recommendation, not a real approval.
SC-02 / Fictional case
Same total, different meaning
Distinguish service performance from financial posting activity.
Starting assets: Service Day Activity; Posted Activity
Starting evidence: Both owners identify a distinct recurring use
Accountable role: Finance reporting owner. Unresolved: Shared definition for a proposed combined leadership metric is unresolved.
Step 1 of 3
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Metric steward
Test the apparent match
Trace grain, event time and population behind the matching headline.
Different business meaning → document a legitimate variant.
If the definitions are actually equivalent → return to the authority and dependency review before consolidating.
Exit: Similarity is separated from substitutability.
keep that combined request on hold and assign the metric steward to reconcile it.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Explored path result / no real authorization
Retain the distinct uses and validate any combined claim
Definition agreed later → validate the combined use against its own requirements.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Original case evidence and worked records
Evidence behind this case
Authored case facts, not production documents. References stay visible so the decision can be inspected.
E-02A
Event-grain comparison
Source note
Service Day Activity groups completed legs by service date.
Posted Activity groups financial events by posting date.
Late postings can appear on a different day and several postings can relate to one leg.
E-02B
Owner disagreement
Unresolved definition
Operations needs service performance; finance needs posted activity.
Neither owner has approved a common interpretation of the proposed leadership headline.
The disagreement remains explicit.
SC-03 / Fictional case
Quiet but essential
Support a periodic contract review that daily usage logs can miss.
Starting assets: Period Close Exceptions
Starting evidence: Recent daily log has incomplete coverage and does not span a contract-review cycle
Accountable role: Contract reporting owner. Unresolved: Complete cadence-appropriate use evidence and field-level classification.
Step 1 of 3
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Reporting analyst
Question the quiet log
Check the window, telemetry coverage, delivery routes and expected use cadence.
Complete window and all routes covered → assess inactivity with the owner.
Window or coverage incomplete → record unknown use; do not label the asset unused.
Exit: Evidence coverage is explicit, including the missing scheduled route.
Starting evidence: Initial consumer review missed the periodic reconciliation route
Accountable role: Operations reporting owner. Unresolved: Replacement mapping for the periodic consumer and renewed acceptance.
Step 1 of 3
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Release analyst
Start a reversible transition
Confirm owner approval, consumer notice, replacement acceptance, observation coverage and a recovery route.
All conditions recorded → withdraw reversibly and observe; do not delete.
Any condition missing → hold withdrawal and return to validation.
Exit: Only a bounded, recoverable change is allowed in the fictional transition.
keep the restored route available and the retirement on hold.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Explored path result / no real authorization
Request a new bounded transition after validation
Repair and renewed consumer acceptance recorded later → request a new bounded transition approval.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Original case evidence and worked records
Evidence behind this case
Authored case facts, not production documents. References stay visible so the decision can be inspected.
E-04A
Initial transition record
Source note
The fictional owner accepted the daily replacement subject to reversible withdrawal, consumer notice and observation across the required operating cadence.
Destruction was not approved.
E-04B
Late dependency finding
Recovery trigger
During observation, the periodic reconciliation owner identifies a legacy route key missing from the replacement.
The stated rollback condition is met.
E-04C
Recovery disposition
Source note
The worked disposition restores the legacy route, preserves both revisions and returns the replacement to validation.
Final retirement and irreversible deletion remain unauthorized.
SC-05 / Fictional case
Useful work without sensitive rows
Let a restricted contributor improve the field dictionary without receiving member-level rows.
Starting assets: Claim Detail; Synthetic Field Map
Starting evidence: A dictionary review request, not permission to inspect Claim Detail
Accountable role: Access review owner. Evidence condition: Whether the alternative's classification and approval are established decides delivery; switch the condition below to compare both branches.
Step 1 of 3
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Metadata analyst
Separate the task from the source
Identify the fields and examples needed for dictionary work, then preserve the source restriction.
Task can use invented values and structural metadata → propose a separate alternative.
Task genuinely needs restricted rows → route an access request; do not copy source data into the alternative.
Exit: Claim Detail remains restricted in either branch.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Explored path result / no real authorization
Use only the reviewed alternative within its approved scope
Scope unchanged and evidence known → dictionary work can proceed on the alternative.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Original case evidence and worked records
Evidence behind this case
Authored case facts, not production documents. References stay visible so the decision can be inspected.
E-05A
Task and restriction
Source note
The contributor needs names, definitions and invented examples to improve the dictionary.
The contributor is not authorized to inspect member-level Claim Detail.
E-05B
Alternative review
Reviewed alternative
In the known-evidence branch, the authorized access reviewer confirms the Synthetic Field Map contains invented examples and structural metadata only, for the named contributor and purpose, through the approved metadata workspace.
E-05C
Unknown evidence condition
Review missing
In the unknown-evidence branch, classification and approval of the alternative have not been established.
A synthetic-looking title, redaction or removal of names does not establish safety.
Delivery is held pending review.
SC-06 / Fictional case
A strategic request at the front door
Answer which vendors need attention without inventing an agreed contract-performance definition.
Starting assets: Vendor Service Review; Proposed Vendor Scorecard
Starting evidence: A new strategic request has been recorded
Choose the condition that fits to see what happens next. Each choice leads to a different action. Finish with that result, or go back and choose a different condition.
Step 1 / Strategic reporting sponsor
Translate the request into a decision
State the business question, intended action, audience, cadence and existing reuse candidates.
Existing context fits part of the need → reuse it and identify the remaining gap.
No suitable view exists → justify a new asset through the same controlled intake, not a chat-only build request.
Exit: The request and reuse rationale have an accountable sponsor.
keep it held until the definition and evidence are accepted.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Explored path result / no real authorization
Continue only the work supported by the chosen conditions
Independent work is ready → continue it without pretending the disputed metric is resolved.
This recommendation follows the conditions selected above. Actual use still requires verified evidence and the accountable owner.
Original case evidence and worked records
Evidence behind this case
Authored case facts, not production documents. References stay visible so the decision can be inspected.
E-06A
Reuse assessment
Source note
Vendor Service Review supplies operational context, but its service-status rules do not establish the requested contract-performance measure.
Reuse is appropriate for context, not proof of the new claim.
E-06B
Definition gap
Definition missing
The fictional sponsor and metric owner have not agreed missed-service exclusions or the reporting cutoff.
The performance metric lacks an accepted definition and validation evidence.
E-06C
Bounded readiness decision
Source note
The metric steward owns reconciliation.
Existing supported operational review and unrelated cleanup can continue.
Readiness is assessed for this specific strategic question, not by requiring every legacy report to be retired.
07 / Inspect
Read the record behind the recommendation
Three records answer three different questions. Open a case's worked record to inspect the detail.
01 / Inventory
What is this asset?
Identity: asset, type and purpose.
Stewardship: owner, audience and sensitivity.
Meaning and use: definition, grain, cadence, coverage and dependencies.
02 / Decision
What can happen next?
Evidence: known facts and missing checks.
Authority: accountable owner and authorized approver.
Action: conditions, proposal and rollback or return trigger.
03 / Intake
Why does this work exist?
Need: business question and intended decision.
Reuse: existing assets and readiness prerequisites.
Acceptance: evidence and lifecycle owner.
Evidence state
Known: evidence supplied in the fictional case. Unknown: check unresolved. Not applicable: a reason is required. None of these means a workflow action occurred.
Disposition
The current recommendation or hold. Proposed consolidation is not completed retirement; an illustrative permission grants no actual access.
Review trigger
Changes in purpose, definition, population, dependencies, audience or channel send the affected decision back for review. Timing follows actual business cadence, not a universal interval.
08 / Boundaries
Keep the conclusion within its evidence
Fictional cases explain the decisions. Real changes still need evidence, review and accountable approval.
Progress supported work
A ready use can proceed while unrelated estate issues remain open.
Hold the affected change
Resolve missing definitions, unsafe delivery or broken dependencies before that change proceeds.
Keep accountability explicit
Business owners approve use and change. The reporting lead coordinates priorities.
Scope, sources and behavior notes
Teaching scope
This is an instructional reporting-estate playbook in the Claim Integrity setting. It is not a connected reporting tool, compliance determination or operational approval system.
Source basis
The five-decision framing comes from the project's reporting-estate problem statement. Assets, evidence notes and policy conditions are authored teaching examples. No interview estimates, actual member records or measured cleanup benefits are presented.
Temporary state
Changing cases resets their steps and evidence condition. Reload starts the linked case at its default state. Earlier steps remain as concise context while the current step is expanded. The case cards compact during scrolling; record titles sit below them. Nothing is submitted or stored.
Presentation baseline
Cascadia Web Design System 2.0, component package 2.0.0; instructional-playbook profile with installed system-font fallback. No quantitative exhibit is present.