How to Keep a Project Decision Log With an Assistant

Quick answer

Keep a project decision log by recording the decision, authorized owner, date, rationale, and work it changes. Ask the assistant to extract candidate decisions from approved sources and flag uncertainty. Preserve earlier entries when a decision changes, linking the replacement rather than rewriting history. The log should distinguish a proposal from an actual commitment.

Teams often remember a conclusion but lose the reason behind it. A month later, someone proposes the rejected alternative again, or a new teammate treats an old plan as current. A concise decision log makes the current choice and its context easy to find.

Use a small decision record

Each entry should answer practical questions:

• What was decided, in one clear sentence?
• Who had authority to decide it?
• When does the decision take effect?
• What evidence or constraint motivated it?
• Which tasks or commitments change as a result?
• What would trigger reconsideration?

Add a source link and status. Proposed, approved, and superseded are useful distinctions. A meeting note saying “we could postpone” should not become an approved postponement merely because the assistant summarized it confidently.

Worked example: changing the launch sequence

Imagine an illustrative team preparing a new service. The original plan is to launch publicly after the help documentation is complete. During review, the product lead approves a limited pilot first because two onboarding questions remain unresolved.

The decision entry should record the pilot-first approach, the product lead's authority, the review date, and the unresolved questions. It should link the prior public-launch decision as superseded for the current phase. It should also identify the affected announcement and onboarding tasks.

The assistant can prepare those entries from the approved meeting record. If the record contains an unresolved discussion rather than an explicit decision, it should ask for confirmation from the decision owner. A tidy log with invented certainty is worse than a log with one visible open question.

A decision log assignment

Maintain the project decision log from the approved meeting notes and decision messages I provide. Draft an entry for each explicit decision with owner, date, rationale, source, affected work, and review trigger. Mark uncertain items as proposed and ask me to resolve them. When a decision changes, retain the old entry and link the superseding one. Do not treat silence or casual suggestions as approval. Give me a weekly list of new decisions and unresolved authority questions.

Choose where the log lives. It can be a document, issue collection, or part of your existing project system. The location matters less than consistent use and clear ownership. Avoid keeping a private assistant-only log that the team cannot inspect.

Record enough rationale to support later review

A reason such as “leadership preference” does not help a future teammate understand the trade-off. A reason such as “the pilot must validate onboarding before we increase support volume” does. Keep rationale factual and brief; the log should not become a transcript of every debate.

Separate facts from assumptions. If the decision depends on an expected supplier date or an untested customer behavior, label that dependency. The review trigger can then identify when new evidence warrants another look.

Do not automatically log every minor choice. Focus on decisions that affect scope, schedule, budget, customer commitments, technical direction, or future interpretation. An overfull log makes significant choices difficult to find.

After a decision is approved, update the affected records through the agreed process. The log explains the choice; the delivery board or contract still owns the resulting work or terms. This prevents a documented decision from remaining disconnected from execution.

Frequently asked questions

Can the assistant decide what deserves an entry?

Give it selection criteria and review its first suggestions. It can flag candidates, while the project owner confirms ambiguous or consequential decisions.

Should we delete overturned decisions?

Usually preserve them with a clear superseded status. Their rationale can explain why the project changed and prevent stale references from being mistaken for the current plan.

Who should receive the log?

Give relevant teammates access while keeping confidential commercial or personnel information within its authorized audience. Prepare a separate client-facing summary when needed.

Use Righthand's product manager role, task delegation, and workflows as starting points for decision-log preparation and review.