Prepare a renewal register where ending engagements and missing dates remain visible.
Next month needs a decision as well as a reminder
You maintain a client’s website every month and revisit the agreement once a year. There is a recurring calendar event, but nobody knows who should confirm next year’s scope. The event also keeps returning after the client ends the service. Your calendar remembered a date; the decision and responsibility remained elsewhere.
For a small team, start with a recurring-work register and a brief regular review. Each row represents one period of one engagement. Preserve the previous period and create the next accepted period only after an actual decision. A reminder brings someone back to the register.
Download the blank register and instructions and completed fictional example. They do not contain real contracts or determine legal notice periods.
Separate delivery from renewal
A monthly report has a delivery date. An annual agreement may have a different date by which you must agree on continuation or give notice of a change. Combining them into “next date” hides which action is due.
Record the client, agreement link, work period, delivery date, continuation decision date, internal review date, and responsible person. Take the decision deadline from the actual agreement. If it is unclear, mark it unverified and name someone to resolve it. Automation should not interpret the contract for you.
Choose the internal review date around the time the team needs to decide. If you allow twenty calendar days, subtract twenty from the verified decision date. That is an operating choice, not a standard cancellation period.
One period, one next action
Fictional example: a studio records October website maintenance as WEB-014/2026-10, with delivery on October 28. Its illustrative agreement requires a continuation decision by November 30, so the internal review is November 10. Lena checks scope and price rather than merely creating another row.
| State | What the record should show |
|---|---|
| Active | Delivery date and person responsible for the work |
| Awaiting decision | Specific question, recipient, and next-action date |
| Continuation confirmed | Confirmed scope and new period |
| Paused or ending | Remaining delivery and when future reminders stop |
Once continuation is confirmed, create a new row with the new period and a link to the engagement. Do not overwrite October’s actual delivery with November’s plan. A proposed future period may exist while the client decides; it should remain visibly proposed.
Review approaching decisions in one place
In Google Sheets, select the complete register including headers and create a view for rows whose internal review date has arrived but whose decision is missing. Filter views support separate selections; they do not restrict access to the other rows.
A personal recurring task can remind you to perform the weekly review. In Google Tasks, open the task’s date and set repetition. Shared tasks and subtasks cannot repeat, so keep the shared agreement register separate from that personal reminder. Someone with register access must take over the review during leave.
Also inspect rows without an owner or verified deadline. A missing date may never appear in a “due next week” view. Give every unresolved decision a next action and record the result when that action is complete.
Automate a stable decision rule
An existing spreadsheet may cover a handful of recurring engagements. Consider a connection when the review repeatedly falls behind or confirmed periods need to reach another system. First identify which record establishes continuation and where an unclear deadline waits for review.
Test a copy with an approaching renewal, an ended engagement, and a row without a verified date. The first should await a decision; the second should not generate another accepted period; the third should appear as an exception. Record what happened. The template does not claim those tests have run.
Include setup, recurring review, and repairs after agreement changes in the cost of a connection. For a small volume, maintenance can outweigh a few minutes of joint review. Once a period is delivered, use the delivery-to-payment workflow.
Feature documentation checked October 10, 2026. The examples and register are an original Chill&Automate design. Your actual agreement determines contractual deadlines.
Use two views so exceptions remain visible
After adding headings and rows in Google Sheets, select the entire range and choose Data → Create filter view. Name the first “Decisions due”: select unended rows without confirmed continuation whose internal-review date is today or earlier. Use actual date values rather than date-shaped text, replacing sample dates. Save with Save View.
The second view, “Unverified records”, selects the Exception state. Before filtering, review the complete list and mark every row with a missing owner or unverified date as Exception; an empty state may otherwise disappear. Check both branches against the four-row example. A person configures filters for the actual date and data type, not the sample month label.
A personal weekly task can prompt the internal review. It does not renew agreements or decide continuation. Remove a terminated engagement’s future reminders separately; the register-wide review continues.