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

A chat decision belongs in the team handbook when it changes how future teammates should act, not only how today’s thread should end.

Many useful decisions start in chat: how to label severity, where to put customer wording, what counts as ready for review, when to escalate a billing question, or which channel should receive launch changes. If the decision stays only in chat, the next new teammate learns it through correction instead of onboarding.

Use three tests. First, will this decision apply again after the current project ends? Second, would a new teammate make a worse choice without seeing it? Third, does the decision change the meaning of an existing handbook rule? If two of those are true, the chat decision should move into a maintained document.

The move should not copy the whole thread. Extract the rule, the reason, one example, one exception, and the owner. Link back to the discussion only if the reasoning matters. Remove names, temporary frustration, and outdated screenshots. The handbook version should read like guidance, not like a preserved argument.

The practical boundary is reversibility. If the decision is experimental, mark it as a trial with a review date. If it is stable, make it part of onboarding. Either way, do not let permanent behavior depend on someone finding the right chat search result.

When to move a chat decision into the team handbook

// COMMENTS

ON THIS PAGE