Revisions and amendments without surprises
In-scope revisions follow rules. Larger changes go through an amendment. That keeps the project readable when intent shifts.
Changing your mind is fine. Changing without a record is not.
Revision vs amendment
A revision corrects within agreed scope. An amendment changes scope: new programme, new storey, new intervention boundary, or a request that breaks already coordinated disciplines.
Write before redrawing
Large changes pull structure, services, reports, and time. If that is not written, someone pays for a surprise later.
What an amendment should state
What changes. What stays. Time impact. Fee impact. New deliverables if needed. Date and agreement.
A question about what you just read? Write to us.
How TENET runs it
Proposal sets revision boundaries. Larger changes pause drawing until the amendment is clear. Decisions are recorded. See Modus operandi.
Questions around this topic
- In-scope revisions follow clear rules in the proposal. Larger changes go by written annex with time and fee impact before work continues.
- A written impact assessment, your approval or refusal, then a document that changes scope, timeline, or fee. No verbal 'we thought'.
- Stages end with a document. Completed-stage documentation remains yours. Resume starts from the last completed document after checking assumptions.