A case has a due date on it. Friday. You did not set it, the person who did has left or is on vacation, and the case has eleven emails attached to it.
What is due on Friday?
That question costs more time than it should. You open the thread and read backwards. You check the notices. Somewhere in there is the sentence that produced the date, and until you find it you cannot tell whether Friday is an inspection, a deadline you gave the resident, a statutory clock, or somebody’s optimistic guess from three weeks ago.
Riley Kay, CAO Executive Assistant at the Township of North Frontenac, described exactly this when she joined our recent session for Ontario municipalities under 15,000 residents. She had come into the role after the township was already running AccessE11, which is a useful vantage point: she inherited other people’s cases and had to work out what they meant.
A date is not an instruction
Here is the problem stated plainly. A due date on a case is a single field. It holds a day. It does not hold the reason for the day, who agreed to it, or what has to happen before it.
That is fine while the person who set it is the person working it. It stops being fine the moment anyone else opens the case: a colleague covering, a manager reviewing, a new hire six months later, or you on a Monday when you have forgotten.
Most systems let you set that one date and consider the job done. The date then quietly becomes a thing people ignore, because an unexplained deadline is easier to ignore than an explained one.
What to do instead
Break the case into the work, and let each piece of work carry its own date.
A pothole report is not one deadline. It is an inspection, a repair, and a note back to the resident. Each has a different owner and a different timeline. If the case holds a single date of “next Friday”, you have compressed three facts into one and lost two of them.
Put them in as tasks instead:
Inspect the location. Due Wednesday. Assigned to whoever is out that way.
Complete the repair. Due the following week, because it depends on the inspection.
Close the loop with the resident. Due the day after the repair.
Now the Friday date is not a mystery. There is no Friday date. There are three dates, each attached to a thing a person does, and anyone opening the case can read the sequence without reconstructing it.
Riley put it more simply than that. She said it is easier to go through the tasks list and trace the due date back to something on it than to go hunting through emails to work out where the date came from.
The part that is not about software
This is a habit before it is a feature. You can do a version of it in any system that lets you write a line of text, and you can fail to do it in a system with every feature available.
The habit is: when you set a date, record what the date is for in the same movement. Not in a separate note, not in the email thread, not in your head. Attached to the date.
Three questions are worth asking of whatever you run today.
Can a colleague open a case you are working on and tell, without asking you, what the next thing to happen is and when? If the answer is no, the case is holding dates but not meaning.
When a date passes, does anything happen? An overdue task that nobody sees is the same as no task. The list has to surface, somewhere a person looks.
Can you tell the difference between a date you chose and a date somebody is owed? These behave differently. A commitment you made to a resident is not the same kind of object as an internal target, and treating them identically is how commitments get quietly missed.
What to try this week
Take ten open cases that have a due date. For each one, write down in a sentence what the date is for. If you cannot do it from the case alone, that case is a worked example of the problem.
Then take the next case that comes in and do it the other way. Before setting a date, write the task. Let the date hang off the task rather than the case.
It takes about the same amount of time at intake and saves the reconstruction later, which is the trade most process improvements fail to make.
Watch the session
Riley’s segment is worth hearing in her own words, and Davyn Goodale of the Township of Georgian Bluffs follows her with how a growing township handles waste collection and work orders. The full recording is on the event page for AccessE11 for Ontario Municipalities: Under 15,000, with chapters so you can go straight to the part about tasks. Her chapter is “Tasks, and tracing a due date back to its reason”.
Other sessions, past and upcoming, are on the events listing.
Frequently asked questions
Can we set more than one due date on a case?
Yes. Each task carries its own date and owner, so an inspection, a repair and the note back to the resident can sit on the same case with different deadlines.
What happens when a task goes overdue?
It surfaces in the assigned person’s own list rather than only on the case, so overdue work is visible without anyone opening every file.
Do we have to use tasks on every case?
No. A single-step request does not need them. They earn their place when a case has more than one thing to do, or more than one person doing it.
See it for yourself
If you are not yet using AccessE11, our walkthroughs are an hour, free, and built around the requests your office actually handles rather than a script. If we finish early, the rest of the hour is yours.
Read how AccessE11 works, or see what it does for a front counter team. AccessE11 is built and priced for small and medium municipalities.