Product names, plans and features change often. Check the vendor’s current documentation before relying on any detail here, and apply your own jurisdiction’s professional-conduct rules.
Every firm has one. A physical diary, a shared spreadsheet, a whiteboard, or a calendar that one person is silently responsible for keeping true. Someone reads correspondence, works out what it implies about dates, and writes those dates down somewhere.
It is a database maintained by hand, from memory, under time pressure, by someone doing three other things. The interesting question is not whether that is a good design. It is why it has survived, and the honest answer is that nothing has been reliable enough to replace it.
Scheduled tasks do not replace it either. They do something more useful: they remove the daily labour of finding out what is true, and leave the judgment where it belongs.
What a date diary really is
Pull it apart and there are three jobs stacked on top of each other, usually done by the same person in the same ten minutes.
- Gathering. Reading mail, orders, filings and messages to find anything that implies a date.
- Calculating. Working out the actual deadline. Service plus twenty-eight days, excluding holidays, subject to the local rule, subject to whatever the judge said.
- Recording and surfacing. Writing it down, and making sure the right person sees it in time.
Only the second is legal work. The first is search, and the third is data entry, and together they are most of the time and most of the anxiety.
Automate gathering and surfacing. Leave calculating alone. That split is the entire design.
How scheduled tasks work
The mechanics are unremarkable, which is the point.
Type /schedule in any Cowork task, or open Scheduled in the left sidebar to see and manage what you have. Claude saves your prompt as the task's instructions and runs them at the cadence you choose, daily, weekly or monthly. No code, no cron syntax, no API.
Two properties make this useful rather than a novelty.
They run in the cloud. Your laptop can be shut. A 6am brief is genuinely waiting at 6am, not queued until you open the lid at nine.
They have your full toolkit. A scheduled task has the same access as a task you run by hand: connected tools, skills, installed plugins. So the court formatting skill you wrote, or the connector into your billing system, is available to a task that runs itself.
What they cannot do
One limitation shapes everything else, and it is better to learn it here than three weeks in.
Scheduled tasks cannot be tied to a folder on your computer. They run against your connectors and files saved to your Claude account. That is it.
So the matter-folder workflow, where Claude reads Matters/Ferguson on your disk, does not go on a timer. If you want a recurring task over that data, the data has to live somewhere connected: a drive, a practice management system, something with an API.
This is not a flaw to work around so much as a fact to design against. It pushes you towards keeping live matter data in connected systems and reserving the local folder for work in progress, which is a defensible structure anyway.
The other constraint is softer but real: a scheduled task runs on the instructions you wrote when you created it. It does not learn that your practice changed. Stale scheduled tasks are a genuine nuisance, so review them quarterly and delete the ones you have stopped reading.
The morning brief
The single highest-value scheduled task for most lawyers, and the one to build first.
Runs at 6am on weekdays, reads mail, calendar and whatever case system is connected, and writes one short document. Not a dashboard. A briefing.
Every weekday at 06:00, produce a short briefing headed "Today".
1. TODAY'S COMMITMENTS. Everything in my calendar today, with the
matter each relates to. Flag anything with no matter attached.
2. NEW SINCE YESTERDAY. Any mail received since 17:00 yesterday that
appears to be from a court, opposing counsel or a client, grouped
by matter. One line each.
3. DATES MENTIONED. Any message that refers to a date, deadline,
hearing, service or time limit. Quote the sentence and name the
sender. Do NOT calculate any deadline. Do NOT decide whether a
date has been correctly computed. List and quote only.
4. AWAITING ME. Anything addressed to me, still unanswered, older
than 48 hours.
5. QUIET MATTERS. Any matter with no activity for 14 days.
Keep it under 400 words. If a section is empty, say "Nothing".Section 3 is the one that matters, and the capitals are deliberate. It does the gathering, which is search, and refuses the calculating, which is judgment. You get every date-shaped sentence from yesterday's correspondence on one page, quoted and attributed, in time to do something about it.
The instruction to say "Nothing" is not a nicety. A brief that pads empty sections stops being read within a fortnight, and an unread brief is worse than none.
Letting it write to the calendar
Reading the calendar is straightforward and safe. Writing is where you have to make a decision, and we make it the same way every time.
Propose, do not create. For anything with legal consequence, the task produces suggested entries and a human approves them. Two minutes a day.
The reason is an asymmetry, not a general distrust of the tool. A suggestion you have to approve, which turns out to be wrong, costs you a moment's attention. A limitation date silently calculated and written straight into the diary, which turns out to be wrong, costs you a claim. Those are not comparable, so they do not get the same permission.
For internal admin, automatic creation is fine and we use it. Call-backs, document review blocks, the half hour before a hearing, invoice chasing, the quarterly review of your formatting skills. Nothing there ends in a negligence claim.
The practical settlement in most firms we set up:
- Reads the calendar freely, every day, no approval.
- Creates internal admin blocks automatically.
- Proposes anything tied to a court date, a limitation period or a client commitment, for a human to accept.
- Never deletes or moves an existing entry. Deletion is not on the table.
Running it from your phone
This is the part people underrate, and it is the reason the whole thing sticks rather than becoming another system nobody opens.
Cowork is on mobile on Pro, Max and Team. So the brief that ran at 6am is readable on a phone at 7am, and more to the point you can reply to it. "Draft a holding reply to the second one." "Put forty minutes in on Thursday for the Ferguson exhibits." "What did the client actually ask for in that March email?"
You are not doing the work on a phone. You are directing work that runs in the cloud and lands on your desk. Read the brief on the train, fire off four instructions, and the outputs are waiting when you sit down.
The one thing mobile cannot do is local file access, which is desktop only. For this particular workflow that costs you nothing, because scheduled tasks cannot reach local folders anyway. The constraint you already accepted turns out to make the phone a complete surface for the scheduled side of your practice.
The line we do not cross
Plainly, because this is a post about automating deadline work and it would be irresponsible to end it anywhere else.
This does not replace a docketing system. If you practise where deadlines are hard and statutory, keep the docketing system and keep the person accountable for it. What goes away is the daily labour of reading five places to find out what is true. What stays is deadline calculation and the accountability for it.
It will miss things. An unusual phrasing, a date in an image, a scanned order, an attachment it could not open. The brief is a second pair of eyes that never gets tired, not a first pair that replaces yours.
It will be confidently wrong. A model can produce a completely fluent summary of an email it misread. Section 3 quotes the sentence for precisely this reason: you check the quote, not the summary.
Used that way, over a month or two, the diary stops being a thing somebody maintains and becomes a thing somebody checks. That is a smaller job, a less anxious one, and it is the actual win here.
If you want this built around your systems, with the permissions set the way we have described and the briefing tuned to your practice, that is what we do.