Every practice keeps a short list of dates that can't slip. A tax filing, an annual report with the state, a license renewal, the last day inside a statute-of-limitations window, a policy anniversary. Miss one and the cost isn't an awkward apology. It's a penalty, a lapsed registration, or a client who now has a very good reason to leave.
The trouble is where those dates live. Some sit in one person's head. Others hide in a matter file, a spreadsheet tab, a sticky note on a monitor, or the calendar of whoever opened the file two years ago. As long as that person is at their desk and remembers, you're fine. The system is really just them, and deep down they know it.
A tickler system fixes that. The name is old, older than any software, and it just means a simple record that "tickles" you about a date well before it arrives. Done right, it flags each deadline weeks ahead, tells your team what to gather, and nudges the client too, so nothing important rides on one person happening to remember on the right morning.
Start with the lead time, not the due date
The date that hurts you isn't the deadline itself. It's the day you needed to start and didn't.
An annual report due in ninety days is not a ninety-day problem if it takes three weeks to chase down a signature, a fee, and an updated address. So track two dates for every item: the hard deadline, and the day work has to begin to hit it comfortably. That second date, the start-by date, is what your reminders should fire on.
Give yourself honest lead times. A quick online filing might need a week. A tax return that depends on client documents needs a month or more, because the slow part is rarely you, it's waiting on them. Build the wait into the number.
Put every deadline in one place a computer can read
Reminders can only run themselves if the dates live somewhere structured. That means one list, one row per deadline, with the same fields every time. A spreadsheet is plenty to start. So is the calendar or practice-management tool you already pay for, if it lets you set custom reminders.
For each deadline, capture a handful of things:
- What it is in plain words: "Acme LLC annual report, Secretary of the Commonwealth."
- The hard deadline and the start-by date you worked out above.
- Who owns it on your team. One name, not a department.
- What you need from the client, if anything, and who on their side provides it.
- Whether it repeats, and how often: annually, quarterly, every two years on the license.
That last field earns its keep. A repeating deadline should recreate itself the moment you close it, so next year's date is on the list the day you finish this year's. You shouldn't have to remember to remember.
Let the reminders do the nudging, on a schedule
A tickler earns its name by nudging more than once, and by nudging the right person each time. One reminder that fires and vanishes is just a louder sticky note.
Here's a cadence that works for most practices:
- At the start-by date: a note to the owner on your team, listing the deadline and exactly what it needs.
- A few days later, if the client owes you something: an automatic message to the client asking for it, with a plain list and a due date of their own.
- Halfway to the deadline: a check-in that fires only if the item still isn't marked done. If everything's in, nobody gets pinged, which is the whole point.
- Final week: a louder reminder to the owner, copied to someone above them, so a single overloaded inbox isn't the only thing between you and a missed filing.
The client-facing nudge is the part people skip, and it's often the one that saves you. Plenty of these deadlines stall because you're waiting on a document only the client can send. A short, polite, automatic reminder ("we need your 2025 mileage log by the 14th to file on time") does the asking, so nobody on your team has to keep circling back by hand.
Where a human still has to sign off
Automation is good at watching the calendar. It's bad, and should stay bad, at deciding what a deadline actually requires.
A reminder can tell you the statute-of-limitations window on a matter closes in sixty days. It can't tell you whether a recent event reset that clock, or whether an exception applies. That's a judgment call, and it belongs to a person with a license and a reason to think hard about it.
So draw the line clearly. Let the system track dates, fire reminders, and assemble the checklist. Keep the human on the two things machines get wrong: confirming the deadline is calculated correctly in the first place, and giving the final "yes, file it" before anything leaves the office.
Review the deadline math when you enter it, not when it's due. If you set an honest start-by date the day you open the file, the reminders handle the rest. The mistake to avoid is trusting the alert to be right when nobody ever checked the underlying date.
Worth doing this week
You don't need new software to begin. You need one honest list and a few reminders that fire on their own.
- Write down the five deadlines that would hurt most if you missed them. Just five, the ones that keep you up.
- For each, add a start-by date, working backward from the deadline through your real lead time.
- Put all five in one place with an owner's name on each, even if that place is a shared spreadsheet today.
- Set one automatic reminder per item at the start-by date. Your calendar can already do this.
- Pick the one deadline that always waits on a client, and draft the short message you'd want sent automatically two weeks ahead.
Do that, and you've moved your riskiest dates out of one person's memory and into a system that doesn't forget. When you're ready to wire the reminders together properly, so the client nudges and team hand-offs run without anyone touching them, that's the kind of quiet plumbing we set up at AI Agency Mass. The goal isn't a fancy dashboard. It's lead time, every time, so the deadline you can't afford to miss stops depending on a good memory and a lucky morning.