Describe the baseline with examples
Record approved page types, functions, content responsibilities and acceptance tasks. Then discuss likely changes: correcting a broken button is different from adding a booking integration. A reasonable revision process needs more precision than an unexplained number of rounds. Group feedback around decisions and versions so the same question is not reopened indefinitely.
Make a change request show its consequences
Ask for the proposed scope, cost and schedule impact before authorising extra work. A requested addition may also affect testing, content and support. If the budget is fixed, decide what can be exchanged or deferred rather than silently expanding the release. Keep the approved baseline alongside the change record so handover has a clear reference.
A practical check before you buy
Use three hypothetical requests: a defect, a revised headline and a new customer portal. Ask the supplier to classify each, explain the approval route and identify any effect on the delivery date.
| Decision | What to consider | What to check |
|---|---|---|
| Defect | Agreed function fails | Correct against the baseline |
| Refinement | Within approved direction | Use the agreed review process |
| New scope | Additional function or page type | Approve price and timing first |
An illustrative business scenario
A US franchise business can separate local stakeholder comments from the single approval needed to change the shared website scope.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.