Three people edited three different copies
The steering committee deck is due on Thursday. The consultant sends v7 to the manager, who comments on a PDF. The partner edits a copy directly, saved as v8_partner. The client sponsor emails comments on v6, which someone had forwarded earlier. By Wednesday night, the team is merging changes from four sources, and one of the client's comments, the one about the headcount figures, is missed.
In the meeting, the client points out that their comment was ignored. The team's credibility takes a small but real knock.
Why versions get out of hand
- Decks are emailed as attachments, creating copies at every step.
- Reviewers comment in the medium they prefer: PDF, email, direct edits, chat messages.
- File naming is improvised, and 'final' rarely is.
- Client comments on older versions are not mapped to the current one.
- Nobody records which version was formally accepted.
Co-authoring in PowerPoint and SharePoint helps within the firm, but client stakeholders often cannot or will not use it, and the partners' habits may not change.
Deadlines drive the chaos. When a deck is due in the morning, nobody stops to think about version discipline. People save a copy, make their change and send it, because it is the fastest thing to do in the moment, and the merging problem is left for someone else.
What version chaos costs
| Issue | Effect |
|---|---|
| Client comments missed | Credibility damaged in front of the sponsor |
| Late-night merging | Consultant time and morale |
| Wrong version sent | Errors in front of the client |
| Acceptance unclear | Disputes about whether a deliverable was accepted |
The effect builds over an engagement. A team that misses one client comment is forgiven. A team that repeatedly sends versions with old errors, or loses track of what the sponsor asked for, starts to look disorganised, and the client begins to check everything, which slows every future deliverable.
How we build a deliverable workspace
- Each deliverable has one home in SharePoint or Google Drive, with a version history and a clear current version.
- Internal reviewers comment on the current version in the file or via a simple review link.
- Client comments, whether by email, on a PDF or in a call summary, are captured into a comment log against the version they refer to.
- Each comment has an owner and status, and comments on old versions are flagged for mapping to the current one.
- Before sending, the manager sees open comments at a glance and cannot mark the version ready while any are unresolved without a note.
- Versions sent to the client are recorded with date and recipients.
- Client acceptance is recorded against a specific version, with the evidence attached.
A language model can extract comments from emails and PDFs into the log, and suggest where each applies in the current version. The consultant confirms each one.
We usually set the workspace up for one engagement with a manager who feels the pain most, and refine it before rolling it out. The habit that matters is simple: one current file, and every comment recorded against it, wherever it came from.
Thursday, with the workspace in place
The manager opens the deliverable and sees three open comments, one from the client sponsor about headcount. It is fixed on Tuesday, not discovered in the meeting.
The record of versions and acceptance also helps at engagement close, and if a question arises about what was delivered.
Is this your deliverable process?
- Deck file names include 'final' more than once.
- Comments arrive by email, PDF and chat on different versions.
- Client comments have been missed.
- Merging edits happens late at night before deadlines.
- Acceptance of deliverables is not formally recorded.