Revisions, sign-off and keeping it current
Who signs, what they sign, and what happens when the kitchen changes underneath a signed plan.
You sign your own plan
The preparer is named on the document and the operator signs it. No regulator has approved, certified or guaranteed it, and the plan says so on its own face. That sentence is a hard rule in the product, and it is the difference between an honest document and a generated one.
What a signature is attached to
One exact revision, not a moving document. Every revision is stored with its own identifier and a content hash, so the thing that was signed can always be produced.
When the kitchen changes
Tell Sage — a new dish, different equipment, a new supplier, a changed process, new staff — and the plan is rebuilt. The previous revision is archived rather than overwritten.
A signed plan that has drifted
If answers change after a plan was signed, the system flags that signed revision as stale against the newer answers. It does not quietly let a signature sit on top of facts that have moved.