The Alactic library
Reports and dashboards guides
From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.
20 articles in Reports and dashboards
Clear filtersCorrect a Dashboard Summary After It Has Been Shared
When a shared dashboard turns out to be wrong, fix more than the chart. Assess which decisions change, send a clear correction, and identify the conclusions recipients can still use.
10 min readTurn a Weekly Report Into a Short, Evidence-Linked Action Summary
Stop retelling every chart. Use a compact decision brief to connect a few report-supported actions with evidence, uncertainty, responsible roles, and conditions for reassessment.
10 min readWrite a Dashboard Summary That Separates Facts From Explanations
A dashboard can show a change without proving its cause. Use this worked example to separate observations, hypotheses, caveats, and the evidence needed for the next decision.
10 min readChoose Chart Scales That Do Not Exaggerate Dashboard Changes
Use chart scales that make dashboard comparisons accurate: zero-based magnitude bars, clearly labelled trend close-ups, consistent panel ranges and visible gaps in time.
9 min readInterpret a Dashboard Change When the Team Mix Has Shifted
When an overall rate falls while team rates rise, check the mix of completed work. Use this worked report and reusable review record to explain the change accurately.
9 min readExplain Why a Weekly Total Cannot Always Be Built by Adding Daily Cards
Daily cards may count events, show a backlog at a moment, or count people who return on several days. Use this filled report-reading guide to choose a valid weekly interpretation before adding anything.
9 min readCompare Weekly Reports When Holidays or Closures Change the Context
A shorter operating week can complicate a reported decline. Use raw totals, calendar notes and matched weekdays to show what changed without claiming to know why.
9 min readRead Daily Spikes Without Mistaking Them for a Weekly Trend
A striking day deserves attention, not an instant trend label. Use an annotated daily series, comparable weekly totals and a decision checklist to separate a reporting event from a sustained change.
9 min readMake Saved Dashboard Filters Visible Before Readers Interpret Results
A correct dashboard total can still mislead when readers miss inherited filters. Use a visible scope strip and verify saved, shared, and exported populations before distribution.
10 min readInvestigate Conflicting Dashboard Totals Before Choosing One
When a dashboard, saved report, and export disagree, compare their reporting scope, date basis, filters, cutoff, and refresh state in order. Use a filled fictional worksheet to separate explainable differences from issues worth escalating.
9 min readAdd Freshness Labels That Show What a Dashboard Actually Knows
A refreshed page can still contain old data. Give readers separate timestamps for the page, source availability, and verified coverage—and tell them which conclusions must wait.
10 min readDecide Whether an Incomplete Dashboard Is Safe to Use
A dashboard can load successfully and still be unsuitable for a decision. Use this readiness checklist to identify what remains usable, what needs restrictions, and which conclusions must wait.
10 min readShow Zero, Missing, Delayed, and Not Applicable as Different States
A blank cell is not evidence of inactivity. Use a clear display contract to distinguish confirmed zero, missing values, delayed data, and measures that do not apply—with a worked dashboard legend and annotated report excerpt.
10 min readChoose Between Event-Date and Entry-Date Reports
A spike in records entered today may describe work completed earlier. Use a worked example and a reusable report card to choose the right date basis and make recording delays visible.
10 min readExplain Why a Report Changes After the Reporting Period Ends
A reporting period can end before all its records arrive. Use clear cutoffs, version labels, and a revision log to explain what changed without asking readers to disregard the earlier report.
10 min readPrevent Off-by-One-Day Errors in Report Date Filters
An end date can mean midnight at the start of a day or the end of that entire day. Use explicit boundaries, a named reporting time zone, and a filled boundary-test checklist to make adjacent exports reconcile.
9 min readChoose a Weekly Reporting Window That Readers Can Compare Reliably
Use completed calendar weeks for settled weekly comparisons, rolling windows for recent conditions, and matched week-to-date periods for progress checks. A filled decision table shows how to label each without inviting unequal comparisons.
9 min readSet Reporting Day Boundaries for Teams Working Across Time Zones
Stop conflicting daily totals by choosing one reporting time zone, separating it from local display time, and testing exactly where midnight events belong.
10 min readMake Today’s Partial Results Comparable With Previous Days
Compare unfinished days fairly using matching cutoffs, verified data completeness, and a filled worksheet—without inventing an end-of-day forecast.
10 min readChoose What Belongs in a Daily Dashboard and What Can Wait Until Weekly
Separate urgent exceptions from trends and unfinished outcomes. Use a filled decision table to assign each report component a reading frequency, maturity rule, and warning label.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.