The question this page answers
What am I signing, what becomes true when I sign it, and may I be the one to sign?
What you see
- 1The declaration, the six declared numbers and who submitted them.
- 2What it arms, the engine's own dry-run read of what signing would do.
- 3Sign off, with its reason in ink beside it when the press is held back.
Sign off is the second signature: the moment a declaration starts owning money. Only a declaration Awaiting a second signature has anything to sign. The head names the commitment and what you are deciding in one sentence. The read-back leads: for an amended declaration, what the new version moved, as Number, Was, Now, with who moved it and their stated reason; then the declaration itself, the six with their declared figures, and who submitted it and when. What it arms is the engine's own answer from a dry-run compile, as Engine and What signing arms; it is the same read Ask Tightly runs as Preview what signing arms.
What else becomes true is a row set of consequences, each a fact and not a hint. The open-to-buy pool is claimed exclusively, one envelope per slice of it. An order over the envelope is reported weekly, not blocked: the envelope is not a wall. Weekly scoring starts on signing, one verdict per number per retail week. Orders, stock and prices are unchanged; arming writes no purchase order, moves no stock and changes no price. Moving a number afterwards is by amendment, once armed. There is no reject: the row says a submission is signed, by a second admin or, under the single approver policy, by an admin, or withdrawn by its submitter through Retire.
What to do
- Read The declaration and What it arms back before deciding.
- Type a note in the field beside the button if you want one recorded with the signature.
- Press Sign off.
Signing takes the Commitments door, and a seat without it reads why before the press:
Signing off a Commitment needs an admin, or someone named on the Approvals page.
Whether the submitter may sign their own is your organisation's approval policy, chosen on Approvals under Settings: a second admin must sign, or a single admin may declare and approve. Nobody has chosen is never read as permissive. Under the stricter policy the submitter's press goes, and the server's refusal lands beside the button:
You declared this; a second admin has to sign it off, or change the policy in settings.
The receipt renders where the button was and the standing word turns to Signed off, with no redirect: who signed, when, and the note. The sentence says what is armed, or that it claims no money:
Signed off, and it claims no money.
Where the pool the envelope claims was taken while the declaration waited, the approval is refused in the pool's own words. Two signatures explains the rule; the book's row door and the room's acts open this page, and the desk's Today reading can sign in place.
When it is empty or failed
No commitment at this address.
The declaration did not come back.
Closed · sign-off unavailable.
A declaration already signed says who signed it and when, and offers Open the desk instead of a button; a second approval would record an arming that did not happen, and the server refuses it. A compile that did not answer is a failed read, not an empty one, and Compile again is offered:
The compile did not answer: a failed read, not an empty one.
A signature the server refused renders the server's sentence beside the button, and nothing changed. A write whose outcome did not come back says so, and the button stays shut:
The sign-off could not be confirmed. Refresh and review the saved record before trying again.