Two separate questions, always in this order: how far away is the date, then where may it land. Getting these the wrong way round is the single most common misreading of the feature, so the whole page is organised around it.
Updated ·6 min read·Applies to both triggers
In one sentence
“3 days after” always means three days on a wall calendar, weekends included. Your working week, closures and leave never change that count — they only decide which day the date is allowed to sit on.
1 · Counting is calendar days
Every day counts. A task set to three days after its anchor is three days later, whether or not the firm works those days. This is intentional: a firm that closes on Friday has not thereby bought itself an extra day of drafting time, and a deadline that silently stretches is worse than one that lands somewhere inconvenient.
What you can count from
The triggerThe moment the matter changed stage, or the event was booked onto the matter.
The event dateThe date a calendar event is booked for, counted before or after it. Reschedule the event and the tasks already in Clio are re-dated in place.
Another taskAnother task in the same template being ticked done in Clio. See the note below.
A task counted from another task being completed is created in Clio with no due date at all, and gets one the moment somebody ticks the task it waits on. Un-tick that task and the date is taken away again; re-tick it and it comes back. A chain resolves one link at a time.
2 · Where a date may land
Three settings decide which days are open: your working week, firm-wide closures, and leave recorded for one Clio person. A blocked day counts like any other day — a task simply cannot land on it, so it moves to the nearest open day, and by the least it can. Forwards for a date counted after something; backwards for one counted before it.
Worked example · 3 days after a Thu 17 Sep meetingMon–Fri week · Fri 18 closed for staff day
Thu
17
the meeting
Fri
18
day 1 · closed
Sat
19
day 2 · closed
Sun
20
day 3 · counted here
Mon
21
due here
Tue
22
The count reaches Sunday 20th. Sunday is not a working day, Monday is, so the task is due Monday 21st. Notice the count never changed: it is still three days. Only the landing moved, by one day, which is the least it could.
3 · Timezone
Dates are the ones your firm’s own calendar day shows, not UTC’s. Set the firm timezone once in Settings (419 zones are supported) and every anchor, count and landing is evaluated in it. A closing meeting at 8pm Eastern is on that day, not the next.
4 · What the field will not save
The due-days box corrects a value it cannot store as you type, and says what it did, rather than clamping quietly at save time.
You typeIt becomesWhat it says
-40A due date cannot be negative: set to 0, the trigger itself.
2.52Whole days only: rounded down to 2.
400003650Capped at ten years, which is the longest we will store.
Next
Blocked-out dates → soonWaiting on a task → soonHelp centre →
