01.01
Send an agreement from a template
Pick the template version, open the clause variants acceptable for this send, fill the fields you already know, and name the roles that must sign. What the counterparty receives is a single-use link.
Help centre
We write articles for what the product does today. If something you expect is missing, tell us — it is probably not built yet.
01.01
Pick the template version, open the clause variants acceptable for this send, fill the fields you already know, and name the roles that must sign. What the counterparty receives is a single-use link.
01.02
Per clause you decide which pre-approved variants the counterparty may see. What is not opened is not shown, and no new wording can appear at the table.
02.01
The form sits behind a single-use link and every field maps to a variable in the template. An amount is entered as SEK and a point in time as a date — nothing lands in free text.
02.02
Expired, used and replaced are normal states. Ask the sender for a reminder, which issues a new link and revokes the old one.
03.01
Read the agreement with the selected variants and filled fields, then sign. The hash of what you saw is stored with the signature. If the content changes afterwards, the signature is refused.
03.02
Declining is its own state, not an absent reply. It is recorded with timestamp and actor, and the sender sees it immediately.
03.03
Some named role has not signed, or whoever signed lacks statutory signatory right or a power of attorney. The roster shows which row sits empty.
04.01
The code, for example NORDEN-0142, is the readable identity of the agreement instance. It points at the instance rather than at a document, and holds through the whole lifecycle.
04.02
Every row is a transition with state, timestamp, actor and origin. Read it bottom to top to see how the agreement got where it is. Rows can only be added.
Then the flow is probably not built yet. Get in touch and we will tell you where it stands rather than write an article about something that does not exist.