Agreement lifecycle
Ultron can draft a contract, place the signature fields, send it, collect legally-binding signatures, and hand every party a completed PDF — end to end, inside the same workspace where the deal happened. This page follows an agreement from a blank draft to a completed, countersigned document. For what makes those signatures binding, see the signature page.
Overview
- Create from
- A template, AI-written text, or an uploaded PDF
- Recipients
- Signers (who sign) and viewers (who receive a copy)
- Field types
- Signature, initials, date, text
- Expiry
- 30 days after sending, if not fully signed
- On completion
- A signed PDF and a certificate go to every party
The states
Two levels: the agreement, and each recipient.
| Level | State | Meaning |
|---|---|---|
| Agreement | draft | Being prepared; not yet sent |
| Agreement | pending | Sent, waiting on signatures |
| Agreement | completed | Every signer has signed |
| Agreement | expired | Still unsigned 30 days after it was sent |
| Recipient | not opened → opened | Whether the signer has opened their link |
| Recipient | pending → signed | That signer's own signing status |
Draft to completed
The full path, step by step.
- 01Draft the agreementThe owner creates it from a template, from AI-written contract text, or from an uploaded PDF.
- 02Add recipientsEach recipient is a signer (who must sign) or a viewer (who receives a copy). Signers get fields; viewers do not.
- 03Place the fieldsClick directly on the page to drop a field where it belongs. Positions are stored as page fractions, so they land correctly on any page size or zoom.
- 04SendSending flips the agreement to pending, emails every signer a unique private link and every viewer a copy, and starts the 30-day clock.
- 05The signer signsOpening the link records that the signer opened it. They fill the fields, adopt a signature, give consent, and submit.
- 06Auto-completeWhen the last signer has signed, the agreement completes on its own. The signed PDF and a certificate of completion go to every party.
Fields
What a signer fills, and how they sign.
| Field type | For |
|---|---|
| Signature | The signer's full signature |
| Initials | Initialling a clause or page |
| Date | The date of signing |
| Text | A typed value the signer supplies |
A signature or set of initials can be drawn, typed, or uploaded. Whichever they choose, the specimen is captured and preserved with the completed document.
Notifications
Everyone is kept in the loop.
| Trigger | Who is notified |
|---|---|
| Sent | Each signer gets a signing invite; each viewer gets a copy |
| Sent confirmation | The owner is told it went out |
| Each signature | The owner gets a progress notice as signers sign |
| Completed | Every party receives the completion email with the signed PDF and the certificate |
Expiry and reminders
A background job keeps things moving.
A durability job runs behind the agreement: it expires one left unsigned past 30 days, retries a failed invite, sends a small, capped set of reminders to signers who have not yet signed, and retries finalization if needed. Reminders are deliberately limited — a couple of nudges over the following days, not an inbox flood.