Notice the “if” and “when” language
Some duties don’t have a date until something happens. A change of key people may need approval. A data breach starts a notification deadline. A request from the other side starts a response period. A calendar alone can’t track these.
Write down the trigger and the action separately
Use a simple structure: when this happens, this person must do this, within this time. Keep the clause it comes from. Don’t turn a duty that applies only in some circumstances into a routine task.
Be clear about how you’ll know
Someone has to notice the event. Name the person closest to it, the project lead for a staffing change, IT for a security incident, and make sure they know the duty exists.
Confirm the timing rule
“Before the replacement starts” is different from “within 24 hours of becoming aware”. Keep the rule attached to the event, and when it’s unclear, say so rather than guessing.
Report the event, then act
In ContractSorted, conditional duties are watched rather than scheduled. When the event happens, report it on the commitment: you confirm the deadline that follows and the owner gets a dated task with reminders.
Keep the record
Note what happened, when it was reported, who acted and what evidence shows it was done. If it’s ever questioned, the history is on the commitment.
WORK THROUGH IT
Your checklist
Adapt it to your contracts. Or let ContractSorted do most of it: start free.