TeamBoostWORKFLOW LIBRARY

Reporting decisions / Delivery leads and report reviewers

Drafting workbench

Compare reports after acceptance rules change

Document an acceptance-rule change before comparing delivery counts across report versions.

A constant set of work can produce different counts under two criteria; the bridge distinguishes rule changes from new delivery.

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Prepare a brief for human review

Drafting workbench

Synthetic case: Five items satisfied rule v1. Rule v2 requires an additional acknowledgment; four of the same five have it.

01

Freeze both criteria

Owner role · Acceptance owner

Evidence: v1 and v2 meanings and effective dates are written.

02

Reassess the unchanged cohort

Owner role · Reviewer

Evidence: The five same item IDs are classified under both versions.

03

Write the comparison bridge

Owner role · Report owner

Evidence: Five versus four is labelled rule-version movement.

Decision to make: Show five under v1 and four under v2 for the same cohort; state that the difference is a criterion change, not one lost delivery.

Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.

Filled review note

Invented planning text. Adapt it to your evidence and confirmed owners.

Bridge: the same five items yield four accepted under v2; E lacks the new acknowledgment. This is a rule-change comparison.

Put the outline to work

  1. Retain rule names and effective dates.
  2. Use the same records when illustrating the effect of the new criterion.
  3. Separate rule movement from later work and disclose unresolved acknowledgments.

From a useful outline to team work

Explore TeamBoostAI for your team

Bring this manual reporting policy and its owned checks into your TeamBoostAI work discussion. Native report/export fields and historical reconstruction depend on your account and implementation; this worksheet does not import or change product records. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

A practical decision workshop

Inspect the example before choosing a rule

Trace an invented case, preserve the evidence limits, then adapt the manual worksheet to your own decision.

Version comparison viewer

Keep the draft and its correction visible

Draft or earlier version · review its limits

v1 snapshot: five accepted items under the original criterion.

Revised example · limits retained

Bridge: the same five items yield four accepted under v2; E lacks the new acknowledgment. This is a rule-change comparison.

What the review changes
Review boundaryDraft to reviewRevised example
Same cohortFive stable item IDsOnly the criterion changes
New requirementNo acknowledgment gate in v1Acknowledgment required by v2

Wide tables scroll sideways on small screens.

Synthetic example · not customer data

Inspect the records

Synthetic reporting records
CohortOld evidenceNew evidenceCount
A–Dv1 yesv2 yesFour items
Ev1 yesv2 acknowledgment missingOne item

Wide tables scroll sideways on small screens.

Download records (.csv) · Download complete decision kit (.json)

Decision explorer

Choose an evidence situation

This returns a written example explanation. It does not inspect your records or approve a real report.

Choose a situation to read its example explanation.
Read every situation without the interactive tool
Both rules and the same cohort are known
Report both classifications and label the criterion change.
The cohort changed as well
Hold the trend comparison; separate criterion and cohort changes.
The old criterion is missing
Recover the old rule before claiming a comparable trend.

Questions about this workflow

Can I compare five and four as a performance trend?

Not without resolving the criterion change. The example holds work constant and changes the rule.

Must we recalculate every historical report?

That depends on the agreed reporting policy; preserve original versions and explain any restatement.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.