A decision log your client actually confirms

The problem with the spreadsheet

The usual decision log is an Excel sheet or a page in the project wiki. Your project manager adds a row after a call: the decision, a date, maybe an owner. It's useful until it's needed. When the client disputes a decision, the log shows what your side wrote down, not what their side agreed to. "That's your log" ends the conversation.

The log also falls behind. Nobody has time to write up every call properly, so the rows that matter most, the casual "fine, let's do that" on a Thursday call, are the ones missing.

What a confirmed log looks like

• Rows come from the meeting itself: Sealbook reads the transcript and proposes each decision with the exact quote and time.
• Your project lead checks and edits the wording, then confirms for the firm.
• The client's named reviewer confirms the same wording from an email link, or asks a question first.
• Only then is the row agreed. Changing it later means a change request both sides approve, and the old version stays visible.

The result is a log the client can't call "yours", because they confirmed every line of it.

Keep your current log

Import the spreadsheet you already have. Each row arrives as a proposal with the original row kept as its source, so history isn't lost and the client confirms it once, properly.