Retain original forecast evidence
Owner role · Recorder
Evidence: The three-day prediction and its pre-outcome timestamp remain immutable in the evaluation ledger.
Forecast evaluation / Delivery leads, planning owners and acceptance reviewers
Handoff sequencePreserve the forecast made before the outcome
Prevent a revised post-outcome number from replacing the prediction being evaluated.
The artifact protects prospective evaluation from replacing a saved forecast with hindsight.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Put the outline to work
- Retain original forecast evidence. Check: The three-day prediction and its pre-outcome timestamp remain immutable in the evaluation ledger.
- Separate recap from prediction. Check: The six-day recap is labelled after-outcome information.
- Evaluate the declared vintage. Check: The three-day error is reported for the original forecast rather than a hindsight value.
Original worked case · Manual planning resource
Inspect the decision, not just the summary.
Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.
01 · Inspect the inputs
Every record stays visible
| Record | Timing | Duration value | Evaluation use |
|---|---|---|---|
| Original prediction | Before start | 3 days | Eligible original forecast |
| Observed result | After finish | 6 days | Outcome |
| Recap replacement | After outcome | 6 days | Not a genuine earlier prediction |
Use horizontal scrolling for wide tables. These records are invented, not customer data.
02 · Follow the reasoning
How the case leads to a decision
Original signed error=6−3=3 days. Using the post-outcome replacement gives 6−6=0 but changes the evidence vintage and invalidates that evaluation.
The bounded result
Evaluate the original three-day forecast against the six-day outcome, giving a three-day signed error. Preserve the after-outcome recap as a different record, not a replacement prediction.
Definitions and method context
Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.
Forecasting: Principles and Practice — accuracy ↗
Genuine held-out forecast and point-error evaluation context. Binary scoring examples use their own explicit toy definitions; no real task model is validated.
External references checked 6 October 2026. Demand for these topics has not been measured.
Make each handoff explicit
Sequence worksheetSynthetic planning case: Before a proof starts, a duration forecast of three days is saved. After the actual six-day finish, a recap changes the forecast field to six and reports zero error.
Separate recap from prediction
Owner role · Reviewer
Evidence: The six-day recap is labelled after-outcome information.
Evaluate the declared vintage
Owner role · Planning lead
Evidence: The three-day error is reported for the original forecast rather than a hindsight value.
Decision to make: Evaluate the original three-day forecast against the six-day outcome, giving a three-day signed error. Preserve the after-outcome recap as a different record, not a replacement prediction.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
Evaluate the original three-day forecast against the six-day outcome, giving a three-day signed error. Preserve the after-outcome recap as a different record, not a replacement prediction. Original signed error=6−3=3 days. Using the post-outcome replacement gives 6−6=0 but changes the evidence vintage and invalidates that evaluation. A timestamp alone does not prove the complete training or information boundary. This worksheet preserves the stated prediction vintage only.
From a useful outline to team work
Explore TeamBoostAI for your team
Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product. 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.
Questions about this workflow
May forecasts be updated before outcomes?
Yes. Keep each dated vintage and evaluate it at its own declared horizon; do not erase the earlier prediction.
Does a corrected clerical entry require the same treatment?
Record the correction reason and evidence explicitly instead of silently rewriting the evaluated record.
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.