Project Delivery and Revision Policy

Projects move through clear stages — typically scope and setup, build or improvement, review, and final delivery. You will know what stage the work is in and what is expected from you at each step.

Larger projects are broken into milestones. At each milestone, you review the work and confirm it before we continue. Approving a milestone helps us build on a stable foundation and avoid rework later.

Your project scope states how many rounds of revisions are included. A revision is an adjustment to work already delivered within the agreed scope — for example, refining layout, copy placement, or styling that was part of the plan.

New pages, new functionality, a change in direction, or work beyond the agreed scope are change requests rather than revisions. We will estimate any change request before starting so you can decide how to proceed.

• Included revisions — refining and correcting agreed deliverables.
• Change requests — new scope, features, or a different direction, quoted separately.

To keep the project on track, we ask that you consolidate and return feedback within the timeframe noted in your agreement. Clear, batched feedback is faster to apply than scattered, conflicting notes.

If a project stalls while waiting on content, access, or approvals from your side, the timeline shifts accordingly, and we may need to reschedule around other committed work. We will always flag this early.

On approval of the final work, we complete handover — publishing or transferring the deliverables as agreed and sharing any relevant guidance. Ownership of deliverables follows our Intellectual Property Policy.