Tie the decision to a version
Show the exact file or product version being reviewed, the acceptance criteria and who can approve it. If the work changes, explain whether another review is required. An old approval should not silently apply to a different deliverable.
Keep corrections visible
Record a correction or a new decision without replacing the earlier record. People should be able to understand what changed, when it changed and who made the decision. Access to that history should follow the project’s permission rules.
Explain what approval does
Tell the reviewer whether approval releases payment, closes a milestone or starts another stage. Give them a clear way to raise a question. Notifications can bring people back to the decision, while the project keeps the agreed record.
Cost and timing examples are Digigen planning guidance, not market averages or a fixed quote. Confirm the scope, assumptions and current provider requirements before making a project decision. About Digigen.