Workplace docs route for moved deadlines, handbook rules, support macros, and async handoffs

A deadline change needs a decision log entry that explains what moved, why it moved, and what work is affected.

The weak version only says “deadline moved to Friday.” That may be enough for today, but it is not enough for the teammate who joins later, the customer-facing owner who needs a new message, or the manager who has to understand whether the delay came from scope, staffing, dependency, review, or risk acceptance.

A durable entry should include five fields:

- Previous date and new date.
- Reason for the change, written as a cause rather than blame.
- Work that is now blocked, reduced, or moved out of scope.
- Person who owns follow-up wording.
- Next review point if the date is still uncertain.

The reason field matters most. “Need more time” is vague. “Legal review added one required approval step” or “migration test failed on the staging dataset” helps future readers decide whether the same risk can return. If the deadline affects customers, the entry should also separate internal reasoning from external wording.

The practical rule: a moved deadline is not only a calendar edit. It is a change in expectations. The log should preserve enough context that nobody has to reconstruct the meeting to explain the new date.

How to write a decision log entry when a deadline moves

// COMMENTS

ON THIS PAGE