Capstone: Make a Workflow Reportable

Reconstruct the prepared Q3 record packet

This packet uses the guide's stated event-order and quarter rules. Classify each request, then inspect how one unlinked booking remains a capture gap rather than a confirmed failure. These records are supplied, not fetched from a live CRM.

Your current placements are proposals until checked

Finish classifying the rows to see the prepared result.

Restoring the saved packet…

Questions the saved specification should answer

Compare these questions with the record packet and the definitions you assembled. Each connects to a different part of the reporting specification.

• What share of qualified requests reached a booked conversation last quarter?Needs: The population and the counting rule.
  In this four-choice example, several combinations can describe different questions. Write down the population and counting rule so readers can tell which one this figure uses.
• Has that got better or worse since we changed the eligibility rule?Needs: The history design.
  If no versioned snapshot or independent archive exists, the current record alone may not show what changed.
• Which segment is performing worst?Needs: The absence handling.
  In the prepared example, treating every missing duration as zero reverses the apparent segment ordering. Check capture coverage before interpreting either average.
• Who do I talk to about changing how that is calculated?Needs: The owner and source of truth.
  When two calculations have no agreed owner, the specification gives readers no stated way to resolve a disagreement.

Run all 11 validation checks

The checks test the seams between sections, since every section was written while looking only at that section. Each runs by its stable ID and reports pass or fail with a reason.

Approve the current saved version