Monthly Reputation Report — Separate Change From Unknowns
An unchanged star rating can hide late data, a different location scope or a revised measure definition. Care Journey fixes the source, location, measure, cutoff and comparison boundary for the month, then separates observed change from exceptions and unknowns. The clinic receives a trustworthy month-close view and a clear next question instead of a decorative reputation dashboard.
The headline can stay still while the evidence changes
Successive month-close snapshots show the same public rating. One includes evidence that arrived after the earlier cutoff; another applies a clarified location boundary. The headline looks comparable, but the evidence base is not. Reading the difference as stable reputation would conceal both the late arrival and the definition change.
The report resolves that ambiguity at the reporting layer. It records what each measure means, where it came from, which locations and period it covers, when the evidence was cut off and whether the comparison is mature enough to interpret. If those conditions cannot be explained, the report retains an exception or an unknown instead of manufacturing a direction.
Freeze a measure dictionary before reading direction
| Report Field | Question It Answers | Visible Boundary |
|---|---|---|
| Measure Definition | What exactly is being reported? | Formula, unit or category definition used at this close |
| Source and Location Scope | Which evidence and clinic footprint are represented? | Included source surfaces and locations; exclusions remain named |
| Cutoff and Period | When did evidence qualify for the snapshot? | Reporting window and evidence cutoff, distinct from later availability |
| Comparison Boundary | Which prior snapshot is genuinely comparable? | Prior definition, scope and cutoff basis |
| Evidence State | How confidently can the difference be read? | Comparable, changed definition, late, restated or unknown |
| Exception Note | What prevents a clean interpretation? | Missing history, unresolved source state or other material limitation |
A measure enters the decision layer only with this boundary sheet. A polished number without a stable definition or comparison basis remains reported evidence, but it should not receive an up, down or unchanged interpretation. The report preserves the gap rather than filling it from an adjacent source or a later snapshot.
The monthly label describes the decision horizon. It does not promise a delivery timetable, a fixed meeting rhythm, a standard metric set, a platform inventory or a result. The clinic's approved evidence and the report's declared cutoff determine what can be stated for a particular close.
Move evidence through a change-accounting ladder
| Evidence State | Report Treatment | Allowed Reading |
|---|---|---|
| Comparable Change | Keep the same definition, scope and cutoff logic | Describe the bounded direction without claiming a cause |
| Definition Change | Show the old and new basis and break the trend | Do not combine the difference with operational movement |
| Late Evidence | Attach it to the period it describes and flag when it became available | Do not silently shift it into the current period |
| Restatement | Preserve the earlier snapshot and identify the revised value or classification | Read the revised comparison only with the restatement note |
| Unknown | State which definition, history or source condition is unresolved | Ask a bounded question; show no directional arrow |
The ladder is report-specific synthesis, not a platform taxonomy. It separates states that would otherwise look alike on a scorecard. Evidence can move from unknown to restated or comparable when its boundary becomes clear, but the report should preserve the earlier classification and explain the change rather than rewriting history.
What Monthly Reputation Reporting Covers
This capability assembles and qualifies a bounded month-close report. It does not build or operate a live dashboard, implement source connections, certify or repair underlying data, reconstruct missing platform history, rerun narrative coding, choose a growth strategy or execute a reputation-management response.
- This service covers one monthly reputation report with stable definitions, comparison boundaries, exceptions and routed next questions.
- Theme analysis, strategy review, response management, service recovery and continuous dashboard operation remain separate.
- The report describes the evidence available at close; it does not prove why a public metric changed.
A theme may appear only as an already-qualified upstream input with its analysis boundary attached. The report can place that input beside a defined measure or exception; it cannot reconstruct the corpus, reassign sentiment, promote an inference to an observation or imply that public commentary confirms a patient relationship.
When evidence remains immature at cutoff, the honest report may contain fewer directional statements and more exceptions. That is not a defect to conceal. It tells the reader which next decision is supported now and which question needs a different owner or later evidence.
Questions to settle before accepting the report
- Can every directional measure be traced to a definition, scope, cutoff and comparable prior snapshot?
- Are late evidence, restatements and unresolved source conditions visible beside the affected measure?
- Are imported themes clearly labelled as upstream analysis rather than findings created by this report?
- Does each material exception end in a bounded question and an existing accountable owner?
- Are dashboard work, data repair, strategy and execution kept outside the report decision?
The answers below clarify how the month-close, restatement logic, unknowns and next-question routes work. They do not add a delivery promise or broaden the service into a standing reporting system.
It names the month-close decision horizon and comparison boundary. It does not promise a fixed delivery date, meeting cadence, source count, metric set or ongoing management programme.
Only when the measure definition, source and location scope, cutoff logic and prior comparison basis are sufficiently stable. Otherwise it should show a definition change, late evidence, restatement or unknown rather than a simple direction.
Evidence may arrive after the earlier cutoff, a source state may become clearer or the report may discover that a definition or location boundary changed. The earlier snapshot stays preserved while the revised comparison is identified as a restatement.
No. It may carry an already-qualified theme as an upstream input with its boundary and limitation attached. Corpus selection, coding, ambiguity treatment and theme construction remain with the separate analysis capability.
The report keeps the unknown visible, records the affected definition, period or source condition, and routes a bounded next question to the existing owner. It does not impute a result or include the downstream work by implication.
Is Monthly Reputation Reporting the Right Next Step?
Share the relevant profiles, locations, prior report, metric definitions, cutoff date and known data exceptions with Care Journey. The discussion will clarify which month-to-month changes are comparable and which remain uncertain and what should happen next.
Readiness handoff
Name the intended decision, the clinic locations and source surfaces in view, the reporting cutoff, the comparison snapshot and every known exception. The first useful output is a defensible report boundary—not a forecast, a dashboard promise or a prescribed intervention.