A client asks for one extra page, another language or a different delivery format. Before implementing the request, record what changes and how it affects the agreed work. A scope change log keeps those decisions visible without turning every discussion into an argument.
Record the request in plain language
Use a row with the request date, description, requester, impact, decision owner and current state. Add a reference to the approved brief or proposal. Keep 'requested,' 'under review,' 'approved' and 'declined' distinct so a suggestion is not mistaken for permission to proceed.
Worked example: adding an English version
A project originally includes one Arabic presentation. The client requests an English version. Record which sections need translation, whether layouts change, who supplies approved terminology and which milestone is affected. Do not assume a second language is only a file-export task.
Assess three kinds of impact
- Output: new pages, formats or deliverables.
- Work: additional preparation, review or testing.
- Timing: dependencies and changes to the delivery plan.
Commercial adjustments should follow the actual agreement. The log records the decision; it does not create contractual rights by itself.
Keep the proposal and working records aligned
The DAZIREL Bilingual Business Proposal Template provides editable sections for scope, timeline, roles and optional services. Use those sections to explain the agreed change, then update your working record. For ongoing customer and task organization, compare the All-in-One Business, CRM and Sales Template.
The specific change-log structure in this article is a suggested method; check each product preview rather than assuming it includes that exact sheet.
Close the loop after approval
Record the decision, update the delivery plan and tell affected people what changed. Retain the previous version for reference instead of silently replacing the original agreement.
Explore the business proposal template
Use the client project toolkit for the complete document chain. The weekly update guide explains how to communicate an approved change without rewriting every project note.
0 comments