This document explains how content is collected and frozen, how change requests are handled during execution, and how revisions are applied in a controlled and efficient manner.
Content is collected in three structured phases, aligned with project planning and execution:
Each phase is reviewed and approved independently.
At the end of each phase, the submitted content enters Content Freeze.
There are three content freezes in a standard project, one after each content phase.
After a phase is frozen, clients may still identify changes or improvements. These are handled through a change request process, not immediate implementation.
In most cases, clients choose to defer changes to the consolidated revision stage.
Deferred change requests are:
This ensures:
After content freeze, any requested change must be shared with the Project Manager.
The client may choose to:
If a revision is used immediately:
The Project Manager will advise on the impact of applying the change immediately versus deferring it. Additional approval or fees apply only if the requested change exceeds the agreed revision scope or affects finalized blueprints, structure, or development logic.
Design is executed based on:
Design Revisions
Once design blueprints and references are approved:
One (1) revision is defined as:
Multiple or staggered feedback submissions are treated as additional revisions.