A shared calendar is useful if people can act on it without an extra call. An overly complex spreadsheet soon stops being updated and loses everyone's trust.

Keep the fields that affect decisions

A task needs only a name, a person responsible, the date of the next action, a status and a link to proof. A separate dependency field shows exactly what is blocking progress. Do not attach personal documents to a calendar that others can access.

Agree on update rules

Decide who changes dates and how the others are notified. Record appointments with the address, time and list of documents. After a task is done, keep the result rather than simply deleting the line: you may need the proof later.

How to write a task that needs no explanation

The name should describe an action: get the date confirmed, send the agreed documents or check access to the flat. Next to it, give the person responsible, the next deadline and the result. An appointment also needs an address, a time and a list of participants. For something you are waiting on, record the expected event and the date you will follow up. Share links to personal documents only with those who need them. If a task is written as a general wish such as “sort out housing”, it needs to be broken down: a line like that tells you neither what work is going on nor when it is finished.

How to avoid several competing versions

Choose one place for the current plan and use messages only to announce changes. Before moving a dependent appointment, check which other tasks are affected. Keep completed entries with their result instead of deleting them. Agree who may change key dates and how important decisions are approved. At a set interval, review only changes and open blockers. This keeps the calendar a working tool rather than an archive of scattered reminders that nobody trusts without an extra call.

What to check

  • Separate appointments from tasks without a set time.
  • State the time zone for remote calls.
  • Add a follow-up date for everything you are waiting on.
  • Review the calendar together on a fixed day.

Example situation

The task “get an answer” becomes a concrete action: write to the person responsible on Wednesday and save the reply in the project folder.

Next step

A practical calendar cuts down on follow-up questions and shows whose action is needed right now.

Official information on this topic

Checklists and examples are organisational recommendations. Requirements depend on the procedure, the city and your situation; check them with the relevant office before you act. Please discuss legal and tax questions with an authorised professional.

This article was prepared with the help of AI. The example illustrates the approach and does not describe a client case.