How to use the obligations tracker
G06 · v0.1.0 · Fictional practice materials; not a live compliance system.
The workbook contains Read me, Obligations, Sources and Change log sheets. The blank version has headers and blank working rows, not a hidden copy of the example. A CSV alternative and this field guide are included in the matching pack. The worked register supplies a readable alternative to the completed spreadsheet.
Fields that keep the tracker checkable
| Field | Meaning |
|---|---|
| item_id | Stable entry ID; a new obligation or recurring instance needs its own identity. |
| item_type | obligation, option or
internal_target. |
| performer | Contracting party or internal actor performing the task; not automatically the follow-up owner. |
| action | A bounded action, not a broad topic such as “reporting”. |
| source_ids / locators | Source IDs and exact bracketed passages, separated by
|; include amendments and event evidence. |
| trigger / period | What starts the clock and which occurrence is tracked. |
| due_at | ISO date-time with the stated offset, or blank when not settled. It is not automatically an approved legal deadline. |
| date_state | stated, calculated_example,
internal_target, unresolved or
event_not_observed. |
| date_basis | The source, counting rule, assumptions and unresolved inputs. |
| proposed_reminder_at | A separately justified internal proposal; blank where no agreed rule exists. |
| reminder_state | not_deployed, blocked_date or
blocked_owner. Descriptive only, not a software lock. |
| owner / owner_acceptance | Internal role and evidence of acceptance. Blank/unassigned stays visible. |
| completion_evidence | Evidence needed or supplied; receipt of a request/invoice is not performance/payment. |
| status / next_action | Open question, follow-up, escalation and who must decide. |
Date and editing discipline
All workbook cells are text, including ISO date-time strings. There
are no formulas, macros, external links or automatic reminders. Keep the
supplied +03:00 offset in this exercise; do not use
date-only display to hide it. Real local-zone daylight-saving rules
require separate checks and are not modelled by a fixed offset.
CSV does not retain text types or formatting. Import as UTF-8 and all columns as text; check dates and IDs after saving or reopening. Do not paste formulas. Sort whole records, not a single column. ISO strings are not a universal chronological sort key across different offsets, so do not rely on text sorting for a mixed-zone real register.
A source edit does not update a fixed date automatically. Recalculate
from the source and independently recheck the date worksheet. Keep unknowns blank, not zero,
1900-01-01 or today’s date. Make the status explain the
blank.
Updates and recurrence
Snapshot the baseline. Keep the source contract and all amendments. Record item, field, old value, new value, source locator, reason and human approval status in the change log. Update both the boundary and proposed reminder when affected. New obligations need a new ID; existing IDs remain stable.
The example contains one monthly report occurrence. Do not overwrite its period or completion evidence with next month’s date. Use a separate instance and reconcile future proposals after a changed clause. Status does not itself send, cancel or reschedule anything.
No application compatibility beyond recorded tests is claimed. Human reader testing and qualified legal/operations review are still required.