Why Moved Project Dates Should Never Auto-Publish to Clients
Modern automation platforms encourage teams to connect everything to webhooks: change a status in Monday or Linear, and instantly trigger an automatic email to the customer. While this sounds efficient, in practice it causes catastrophic client misunderstandings.
Consider a real example: on a Friday evening, a project manager moves an internal task from Tuesday to Friday while rebalancing crew assignments. An automated system immediately emails the client: 'Notice: Your kitchen countertop install has been delayed.' The client spends the weekend furious, unaware that the final delivery date was completely unaffected.
A date change in an internal project board is a working fact. An email to a paying client is a serious human communication decision. Blurring those two concepts together destroys customer trust.
Orbit Signal solves this through a principled human-in-the-loop quarantine. When a date moves or a blocker is flagged in your source board, Signal holds it in the 'To check' approvals queue. You review the wording, confirm whether an email is even necessary, and only publish when you are ready.
