Support/Getting Started/How decisions get recorded
Getting Started

HOW DECISIONS GET RECORDED

2,990 views
processdocumentation

Every scope decision lives in writing, so nobody relies on remembering a call.

The rule

If a decision changes scope, timeline or deliverables, it goes in writing before it takes effect. A call can produce a decision; the call is not where the decision lives.

What gets recorded

  • Scope changes and their effect on the date
  • Approvals that close a round
  • Anything the client asks us to skip
  • Anything we recommend against but do anyway at the client's request

Why the last one matters

Sometimes a client wants a choice we would not make. That is entirely their right — it is their project. Recording it protects both sides later, when the question "why is it like this" comes up months on.

Where it lives

In the project thread, in plain language. No separate tool to learn, no login to chase.

Was this helpful?

Tell us honestly. It is read by the people who write these pages.

If this didn't answer your question, ask Xylo.

Back to Getting Started