Communications wants a shorter form. Operations needs more information. A manager requests another change, and the supplier receives three messages with different instructions. Another meeting will not necessarily solve the problem.
Before work starts, establish who provides expertise, who consolidates feedback and who decides. These arrangements affect the time required on both sides of the project.
Assign responsibility by area
You do not need a large committee. You need named people for content, service processes, data, technology, budget and acceptance. One person can cover several areas if they have the time and authority.
For each area, identify cover and the point at which a decision needs escalation. A project contact should not have to guess the organisation's position or pass every question between departments without resolution.
Send one agreed response
Gather feedback in one place. Distinguish a defect against the agreed scope, a question and a proposed new feature. If two departments want conflicting outcomes, resolve that internally before instructing the supplier to make a change.
A short decision record helps: the issue, the decision, the reason and the approver. When the subject returns a month later, nobody needs to reconstruct the discussion from several inboxes.
Agree response times
Match approval dates to people's actual availability. If several departments need to be consulted, allow for that in the plan. A missing response should trigger an agreed follow-up, rather than an unclear assumption of consent.
Ask suppliers to explain the effect of a delayed answer and the available options when raising a question. That makes decisions easier to take. Include your own team's work in the schedule, alongside the dates when the supplier must deliver something.
Every number in this article, plus thousands of other contracts, is in the database.
Open the database