Fictional renewal register
All engagements, agreements and dates are fictional. They do not establish legal deadlines or confirmed client commitments.
| Engagement and period | Agreement | Delivery | Decision by | Internal review | Owner | State | Next action |
|---|---|---|---|---|---|---|---|
| WEB-014/2026-10 | Model A | 2026-10-28 | 2026-11-30 | 2026-11-10 | Lena | Awaiting decision | Prepare scope and request a reply on November 10 |
| WEB-015/2026-10 | Model B | 2026-10-28 | 2026-10-30 | 2026-10-10 | Petra | Ending | Finish October; no accepted next period; remove future reminders after confirmed ending |
| WEB-016/2026-10 | Unverified version | 2026-10-28 | Unverified | 2026-10-12 | Lena | Exception | Check the agreement and date before recording an accepted renewal |
| WEB-017/2026-10 | Model D | 2026-10-28 | 2026-11-30 | 2026-11-10 | Missing | Exception | Team lead assigns owner and backup by October 12 |
At the illustrative November 10 check, WEB-014 and both exceptions must be visible. Inspect ending WEB-015 for remaining delivery and reminder removal; never automatically create new accepted work. A missing date is neither zero nor evidence that nothing is due.
After explicit confirmation retain the reply __ and create the new period __ linked to the original engagement. Do not overwrite the October row. Actual trial outcome __; these are expected branches, not account-test results.