An amendment is not the same document, edited

A scope changes, so someone opens the contract file and updates the number. It feels efficient. It also means the thing both sides signed no longer exists anywhere — there's just whatever the file currently says, with no record of what it said before.

Why this matters more than it seems

A dispute about scope almost always comes down to one question: what did we actually agree to, on the day we agreed to it. If the contract is a live file, that question has no answer. If it's a version, it does.

What a versioned contract needs

• The issued contract is frozen the day it's signed — hashed, not editable
• A scope change produces a new version, referencing what it amends
• Both versions stay accessible, not just the current one
• The BOQ and payment schedule version alongside the contract, not separately

How Studio versions this

Archgrid Studio issues contracts and BOQs as hashed, frozen snapshots. An amendment is a new version, not an edit — so "what did we agree to" stays answerable for the life of the project, not just until someone opens the file again.