Foundry Academy · CRM Operations · Lesson 5 of 6

Dashboards and exception reporting

Build decision-focused reporting with governed definitions, traceable sources, and visible data-quality limitations.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Dashboards and exception reporting

Objective: Build decision-focused reporting with governed definitions, traceable sources, and visible data-quality limitations.

Start with the decision and audience. A sales manager may need response backlog, stage movement, aging, next-step coverage, forecast change, and loss reasons; an executive may need a smaller view of demand, conversion, cycle time, concentration, capacity, and risk. For each metric, document numerator, denominator, population, date logic, filters, currency, source, owner, refresh cadence, and action threshold. Use counts with rates so a small denominator does not create a misleading trend.

Exception reporting often creates more value than decorative totals. Show records missing a next step, opportunities past aging thresholds, lifecycle conflicts, ownerless records, failed automations, consent problems, duplicates, and unusual forecast changes. Allow users to reach the controlled records behind a metric according to permission. Display the refresh time and known limitations. Reconcile important dashboard totals to source reports and sample records after changes. Do not publish individual performance rankings from unreliable data or use CRM measures for employment decisions without governance, context, and appropriate human review.

Before you begin

  • Confirm CRM populations, missing next steps, missing decision roles, former-employee owners, biased win-rate denominator, and integration-owner/token issues.
  • Define metric numerator, denominator, period, source, refresh, owner, threshold, and action before displaying a result.
  • No refreshed dashboard, corrected win rate, queue contents, or approvals are supplied.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This fictional training case uses fabricated company and contact records. It contains no real personal or confidential data and does not provide privacy, legal, employment, or technology-vendor advice.

OrbitWorks CRM repair

OrbitWorks is a fictional business-to-business maintenance software company with 14 sales and service users. Its CRM holds 8,420 company records, 11,780 contacts, and 1,360 open opportunities. An audit sample finds 23 percent of open opportunities have no dated next step, 18 percent lack a decision-role contact, and 11 percent are assigned to former employees. Two pipelines use different meanings for qualified, yet both feed one forecast. Sales moves opportunities forward when a meeting is scheduled; customer success uses the stage only after a written problem and buying process are recorded. A marketing import of 2,100 contacts is waiting. The source contains 430 probable duplicates, 280 records without a documented marketing basis, 17 personal notes copied into a free-text field, and country values in nine formats. The proposed automation sends four emails and creates a call task, but it has no stop rule after opt-out, reply, disqualification, or opportunity creation. A dashboard reports a 72 percent win rate because it excludes closed-lost records older than 30 days. A regional manager requests administrator rights for all representatives to fix records faster. The CRM also has three integrations whose owners left the company; one export token has not been rotated in 19 months. Leadership wants a clean forecast by Friday and suggests overwriting all records from the import. Learners must design a controlled repair that improves lifecycle clarity, data standards, follow-up, stage evidence, reporting, permissions, and change management. They must minimize unnecessary personal data, preserve auditability, and avoid claiming that a configuration alone establishes lawful processing or accurate forecasts.

Supported example — reference only

Section or field
Win rate
Purpose
Support funnel and forecast review using a complete closed-opportunity population.
Supported entry
Reported win rate is 72%, but older closed-lost opportunities are excluded.
Source input ID
M05-I04 (F10, confirmed)
Gap or learner proposal
Complete numerator, denominator, period, inclusion rules, corrected result, refresh time, and approval: not supplied.
Owner or reviewer
CRM process owner and data steward
Status
Metric invalid for decision use

A well-handled evidence gap

Section or field
Ownerless integration exception queue
Purpose
Surface integrations requiring ownership and credential review.
Supported entry
Three integrations have departed owners and one export token is nineteen months old.
Source input ID
M05-I05 (F11, confirmed)
Gap or learner proposal
Integration identities, new owners, credential policy, token action, review time, and result: not supplied.
Owner or reviewer
Authorized system owner and data steward
Status
Exception queue required — review pending

Flawed approach — do not copy

Marking this dashboard specification “approved and complete” without the required evidence or reviewer is a flawed submission. Stop using a dashboard measure when numerator, denominator, period, inclusion, source, refresh, owner, threshold, or action is absent or biased.

Repair: Rework the dashboard specification as an evidence-backed draft, not an approved result. List the management decisions the dashboard must support before choosing metrics or charts. Define win-rate numerator, complete denominator, period, inclusion, exclusion, and refresh rules. Create separate exception views for missing next steps, decision roles, departed owners, stalled work, and automation or integration failures. Check the revision against this requirement: Every metric defines numerator, denominator, period, inclusion, source, refresh, owner, threshold, and action. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the dashboard specification.

Recalculate decision metrics using transparent populations, periods, and exclusions.

Deliverable: A dashboard specification and exception-report mockup.

Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F10, F11, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M05-I01 · F01 — The CRM contains 8,420 companies, 11,780 contacts, and 1,360 open opportunities.
  • M05-I02 · F02 — Twenty-three percent of sampled open opportunities lack a dated next step.
  • M05-I03 · F03 — Eighteen percent lack a decision-role contact and eleven percent have former-employee owners.
  • M05-I04 · F10 — The reported 72 percent win rate excludes older closed-lost opportunities.
  • M05-I05 · F11 — Three integrations have departed owners and one export token is nineteen months old.
  • M05-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M05-S01 · F01, F02, F03, F10, F11 — Build a starter version of “A dashboard specification and exception-report mockup.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. List the management decisions the dashboard must support before choosing metrics or charts.
  2. Define win-rate numerator, complete denominator, period, inclusion, exclusion, and refresh rules.
  3. Create separate exception views for missing next steps, decision roles, departed owners, stalled work, and automation or integration failures.
  4. Use aggregate supplied percentages only and do not infer record identities or a corrected win rate.
  5. Assign metric and queue owners plus provisional thresholds and required actions.
  6. Route denominator policy, privacy, integration, and production-report changes to authorized owners.
  7. Quality-check every dashboard field for source, refresh, definition, owner, action, limitation, and no misleading percentage.
Field-by-field guidance
Section or field
Name one dashboard metric, exception queue, limitation, or refresh field.
Purpose
State the management decision or control the field supports.
Supported entry
Record the supplied aggregate fact without inventing recalculated results.
Source input ID
Cite the exact M05-Ixx evidence.
Gap or learner proposal
State missing numerator, denominator, period, refresh, owner, threshold, action, or record detail.
Owner or reviewer
Use CRM process owner and data steward, adding system owner where needed.
Status
Use Fact supplied, Metric invalid, Definition proposed, Queue design pending, or Approval pending.
Dashboard specification · learning draft
Section or fieldPurposeSupported entrySource input IDGap or learner proposalOwner or reviewerStatus

Start with 2 rows; the complete workbook specifies 2 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 5 · 2-item formative check

Dashboards and exception reporting

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 5 · knowledgeWhich dashboard element is most likely to support a specific corrective action?
Question 2 of 2 · MODULE 5 · scenarioOrbitWorks discovers its 72 percent win rate excludes older losses. Which update process protects the Module 5 decision?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Every metric defines numerator, denominator, period, inclusion, source, refresh, owner, threshold, and action.
  • Ownerless, incomplete, stalled, and automation or integration exceptions remain visible.
  • The 72% figure is not presented as valid or silently recalculated.

Stop: Stop using a dashboard measure when numerator, denominator, period, inclusion, source, refresh, owner, threshold, or action is absent or biased.

Go: Go to management review only with defined measures and visible exception queues.

Escalate: Escalate production metric definitions, integration ownership, credentials, privacy, and forecast use to authorized owners.

04 · Evidence to keep

Leave with usable work.

Dashboard wireframe, metric dictionary, source reconciliation, exception definitions, access map, and management action notes.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Customer operations team discussing data and lifecycle information in a meeting.
Learn the standard. Practice the work.
Revenue operations colleagues coordinating a shared customer workflow.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ws-crm-operating-standard · Academy internal operating standard

Wealth Synergy CRM operations internal operating standard

Academy-selected lifecycle, field, queue, stage, dashboard, change, and review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.