In this guide
A domain renewal, accounts preparation and the annual members' meeting may each sit in a different person's inbox. A shared calendar makes the dependencies visible: the accounts need preparation before review, the papers need approval before circulation, and someone needs to renew a service before its billing contact leaves.
Your co-op's actual obligations depend on its legal form, rules, activities and circumstances. This is a planning method, not a list of universal statutory deadlines. Get applicable dates from your governing documents, regulator, accountant or adviser.
Collect the obligations
Start with six groups: member and board meetings; accounting and reporting; insurance and contracts; premises or equipment responsibilities; people and membership; technology and information. Ask the people currently doing the work what happens, how often, and what goes wrong if it is missed.
Record the source of every mandatory date. “Always done in June” is useful history but is not an authoritative deadline. Where a date depends on the financial year end or a contract anniversary, record the relationship as well as the next occurrence.
Use a small register
- Responsibility: the outcome that must happen.
- Source: rule, contract, regulator guidance or agreed internal practice.
- Due date: the actual deadline, with any dependency.
- Preparation date: when work needs to begin.
- Owner: the person or role responsible for making it happen.
- Backup: who can take over if the owner is unavailable.
- Evidence: where completion is recorded.
- Next review: when to check whether the entry is still correct.
An illustrative entry might be: “Review website hosting contract; source: current supplier contract; renewal: the contract's date; start review six weeks earlier; owner: operations role; evidence: approved renewal decision.” The six-week lead time is a planning choice, not a legal requirement.
Plan backwards from the outcome
For a meeting, work backwards through any required notice period, paper approval, drafting and information gathering. For a renewal, allow time to review use, compare options, agree spending and arrange a safe transition if needed. A reminder on the final day offers little room to act.
Show recurring tasks in a shared calendar, but keep the responsibility register as the place to find context. Calendar entries should link to the current record instead of containing copies of sensitive documents.
Review it with a human
Set aside a short monthly review: what is due soon, what has no owner, what is waiting on another task, and which completed item has no evidence? Automations can send reminders, but responsibility should still be clear when a reminder fails or someone changes role.
After the annual meeting or a committee change, check calendar access and transfer ownership deliberately. A calendar attached to a departed volunteer's account can be just as fragile as a spreadsheet on their laptop.
Keep the first version manageable
Begin with the commitments that could cause the most disruption if missed. Add routine work as the group learns what is useful. Avoid overwhelming members with reminders that do not need their attention; send tasks to the responsible role and use a separate overview for governance.
The digital handover register can help with technology responsibilities. Read the technology budgeting guide to connect renewals to next year's spending plan.