Contract operations / Companion to the guide

Check the contract dates and reminder inputs

Trace each fictional date to its inputs and counting rule, and recognise when not to calculate.

Return to the main guide
On this page

Baseline checks

Read C01–C05 first. The teaching terms supply a fixed UTC+03:00 offset and calendar-day rules with no weekend/holiday adjustment. Confirm the input, counting convention and source before checking arithmetic.

Baseline date calculations and unresolved inputs
Entry Independent calculation or reason not to calculate
O01 workshop Date is stated: 15 June 2026, 17:00. Four calendar days earlier = 11 June, 17:00. Both are past at the baseline; seek evidence, do not activate an old proposal.
O02 June report Month after June = July; C02 says seventh, not fifth. Boundary = 7 July 2026, 17:00. Less four days = 3 July, 17:00.
O03 access 28 June 2026, 10:00 plus 48 elapsed hours = 30 June, 10:00. Less 24 hours = 29 June, 10:00. No business-day conversion.
O04 non-renewal 31 May 2027, 17:00 less 60 calendar days = 1 April, 17:00. From 1 April to 1 May is 30 days; to 31 May is another 30. Ten days earlier = 22 March, 17:00. Receipt/method/authority still need review.
O05 internal target 31 May 2027, 17:00 less 90 calendar days = 2 March, 17:00. This is an internal planning rule, not the contractual notice boundary.
O06 transition Do not calculate: contractual meaning, evidence and business-day calendar unresolved.
O07 payment Do not calculate at baseline: a valid invoice receipt has not been supplied. Do not borrow another task’s reminder lead time.

Blank check record

For each edited or added row record: source and version; trigger evidence; counting rule; date/time/offset; calendar and adjustments; calculation method; independently obtained result; exception; reviewer decision; internal reminder rule; deployment authority. The blank date-check CSV in the pack has these columns.

An independent arithmetic result verifies only the supplied calculation. It does not establish that the clause, trigger or notice interpretation is legally correct. A stop for missing inputs is a successful check.

Transfer checks before automation

Test a December reporting period rolling into January, a leap-year February and a changed period-specific amendment. Preserve the offset and clock time where the fictional rule requires it. For a real contract, resolve the actual calendar, time-zone and notice rules first. This workbook implements no live recurrence or reminder service.

Try the changed-facts task after the baseline. Its expected results are in the separate reviewer packet, not on this worksheet.