Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- E-signature Platform
- Signing provider
- Document source
- Identity source
E-signature Platform organizes a signature packet from its first draft through preparation, review, sending, signer progress and completion. A packet belongs to an organization, has an owner and points to a signing template.
Signature packets in one list
Signature Reviewer approves or returns the prepared revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep the document, owner and signing result on the same packet.
Approval conditions
| Number | Name | Status | Owner | Definition | Document hash | |
|---|---|---|---|---|---|---|
| SP-40651 | Westhaven services agreement | Draft | Talia Brooks | Purchase approval form | sha256:7f29c1d8a340 | |
| SP-45983 | Cedarbank vendor onboarding | Draft | Talia Brooks | Data processing addendum | sha256:86ab24e19d05 | |
| SP-62096 | Harbor Point lease renewal | Draft | Talia Brooks | Vendor onboarding packet | sha256:0c73f89a42be | |
| SP-83220 | Northline employment offer | Draft | Owen Mercer | Vendor onboarding packet | sha256:d4918e05c62a | |
| SP-97221 | Pineford board consent | Draft | Owen Mercer | Purchase approval form | sha256:35bc7109e4f8 |
Keep a signing definition with the organization that uses it.
Signature templates
| Name | Code | Effective from | Effective to | Policy reference | Organization | |
|---|---|---|---|---|---|---|
| Two-party services agreement | TPL-SVC-001 | 12 Oct | 16 Oct | SIG-POL-01 rev 4 | Pineford Civic Partners | |
| Vendor onboarding packet | TPL-VND-002 | 17 Oct | 23 Oct | SIG-POL-02 rev 3 | Pineford Civic Partners | |
| Commercial lease renewal | TPL-LEASE-003 | 20 Oct | 25 Oct | SIG-POL-03 rev 2 | Cedarbank Fabrication | |
| Employment offer acceptance | TPL-OFFER-004 | 03 Nov | 07 Nov | HR-POL-07 rev 5 | Elmbridge Data Services | |
| Board written consent | TPL-BOARD-005 | 20 Oct | 22 Oct | BOARD-POL-02 rev 1 | Westhaven Advisory Group |
Tie signature progress to a verified signer event and packet.
Signer events
| Parent | Sequence | Outcome | Signer identity | Signed at | Document hash | |
|---|---|---|---|---|---|---|
| Elmbridge data agreement | 20 | Pending | Nora Delgado, legal director | 27 Oct | sha256:7f29c1d8a340 | |
| Northline employment offer | 10 | Accepted | Amir Qureshi, vendor manager | 11 Oct | sha256:86ab24e19d05 | |
| Harbor Point lease renewal | 40 | Pending | Talia Brooks, property lead | 12 Oct | sha256:0c73f89a42be | |
| Elmbridge data agreement | 60 | Accepted | Minh Tran, new hire | 17 Oct | sha256:d4918e05c62a | |
| Cedarbank vendor onboarding | 40 | Pending | Elena Rossi, board chair | 22 Oct | sha256:35bc7109e4f8 |
Give each prepared revision a named decision and supporting proof.
Approval conditions
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| Pineford board consent | 900 | Pending | Priya Shah | EV-SIGN-2026-041 | |
| Westhaven services agreement | 710 | Pending | Samira Haddad | EV-SIGN-2026-042 | |
| Harbor Point lease renewal | 80 | Pending | Owen Mercer | EV-SIGN-2026-043 | |
| Westhaven services agreement | 310 | Pending | Samira Haddad | EV-SIGN-2026-044 | |
| Elmbridge data agreement | 950 | Pending | Kofi Mensah | EV-SIGN-2026-045 |
Understand every attempt, operation run and provider receipt.
Signature packets
| Number | Name | Completed at | Completed signer count | Revision | Document hash | |
|---|---|---|---|---|---|---|
| SP-83790 | Westhaven services agreement | 15 Oct | 22 | 620 | sha256:7f29c1d8a340 | |
| SP-37580 | Cedarbank vendor onboarding | 21 Oct | 39 | 580 | sha256:86ab24e19d05 | |
| SP-30988 | Harbor Point lease renewal | 13 Oct | 29 | 620 | sha256:0c73f89a42be | |
| SP-98160 | Northline employment offer | 12 Oct | 27 | 840 | sha256:d4918e05c62a | |
| SP-60715 | Pineford board consent | 09 Oct | 33 | 650 | sha256:35bc7109e4f8 |
Assign signing exceptions and retain the earlier decision trail.
Follow-up actions
| Source | Title | Due date | Status | Resolution | |
|---|---|---|---|---|---|
| Harbor Point lease renewal | Confirm Westhaven signer address | 03 Nov | Open | Updated signer email and resent | |
| Westhaven services agreement | Replace Cedarbank tax form | 30 Oct | In progress | Added witness field to packet | |
| Northline employment offer | Add Harbor Point witness field | 25 Oct | Completed | Regenerated approved document | |
| Harbor Point lease renewal | Resend Northline offer link | 12 Oct | Open | Corrected signer sequence | |
| Stonefield settlement release | Verify Pineford board authority | 22 Oct | In progress | Completed identity verification |
Packet preparation to signed evidence ships ready to use. One step needs a named approval before the work moves on: Review decision (Signature Reviewer).
Give the document an owner, organization and signing definition.
Fix the revision, signer order and document hash.
A named reviewer decides on that prepared revision.
Keep the provider envelope identity with the packet.
Compare provider evidence with the prepared document.
Retain the result and explain any successor revision.
Open any signature packet to see its evidence documents, the roles that work on it, its process stages and its approvals on one page.
Sent date, Completed signer count and Signing order.
Each line is linked to this signature packet.
Packet Owner, Signature Reviewer and Signing Operations, each with their own permissions.
Create packet, with the role that acts.
Review decision, with who decides.
Sent
| Source | Title | Attachment |
|---|---|---|
| Pineford board consent | Westhaven signed agreement | westhaven-signed-agreement.pdf |
| Cedarbank vendor onboarding | Cedarbank identity verification | cedarbank-identity-check.pdf |
| Cedarbank vendor onboarding | Harbor Point witness statement | harborpoint-witness-form.pdf |
Signed in as Signature Reviewer
| Decision | Approver | |
|---|---|---|
| Review decisionA named reviewer decides on that prepared revision. | Signature Reviewer |
Everyone opens E-signature Platform to the work that is theirs. Pick a role to see what it starts with.
Prepares a packet and follows it through the signing cycle.
This is the first screen this role sees.
Signature packets · Packet Owner
| Number | Name | Status | Owner | Definition | Document hash | |
|---|---|---|---|---|---|---|
| SP-40651 | Westhaven services agreement | Draft | Talia Brooks | Purchase approval form | sha256:7f29c1d8a340 | |
| SP-45983 | Cedarbank vendor onboarding | Draft | Talia Brooks | Data processing addendum | sha256:86ab24e19d05 | |
| SP-62096 | Harbor Point lease renewal | Draft | Talia Brooks | Vendor onboarding packet | sha256:0c73f89a42be | |
| SP-83220 | Northline employment offer | Draft | Owen Mercer | Vendor onboarding packet | sha256:d4918e05c62a | |
| SP-97221 | Pineford board consent | Draft | Owen Mercer | Purchase approval form | sha256:35bc7109e4f8 |
Makes an independent decision on a prepared packet revision.
This is the first screen this role sees.
Signature packets · Signature Reviewer
| Number | Name | Status | Owner | Definition | Document hash | |
|---|---|---|---|---|---|---|
| SP-40651 | Westhaven services agreement | Draft | Talia Brooks | Purchase approval form | sha256:7f29c1d8a340 | |
| SP-45983 | Cedarbank vendor onboarding | Draft | Talia Brooks | Data processing addendum | sha256:86ab24e19d05 | |
| SP-62096 | Harbor Point lease renewal | Draft | Talia Brooks | Vendor onboarding packet | sha256:0c73f89a42be | |
| SP-83220 | Northline employment offer | Draft | Owen Mercer | Vendor onboarding packet | sha256:d4918e05c62a | |
| SP-97221 | Pineford board consent | Draft | Owen Mercer | Purchase approval form | sha256:35bc7109e4f8 |
Reconciles provider events and execution exceptions.
This is the first screen this role sees.
Signature packets · Signing Operations
Resolves assigned exceptions and records the disposition.
This is the first screen this role sees.
Follow-up actions · Follow-up Owner
Maintains organization-specific signing definitions and mappings.
This is the first screen this role sees.
Signature templates · Template Manager
| Name | Code | Effective from | Effective to | Policy reference | Organization | |
|---|---|---|---|---|---|---|
| Two-party services agreement | TPL-SVC-001 | 12 Oct | 16 Oct | SIG-POL-01 rev 4 | Pineford Civic Partners | |
| Vendor onboarding packet | TPL-VND-002 | 17 Oct | 23 Oct | SIG-POL-02 rev 3 | Pineford Civic Partners | |
| Commercial lease renewal | TPL-LEASE-003 | 20 Oct | 25 Oct | SIG-POL-03 rev 2 | Cedarbank Fabrication | |
| Employment offer acceptance | TPL-OFFER-004 | 03 Nov | 07 Nov | HR-POL-07 rev 5 | Elmbridge Data Services | |
| Board written consent | TPL-BOARD-005 | 20 Oct | 22 Oct | BOARD-POL-02 rev 1 | Westhaven Advisory Group |
Sets up organizational records, people and access.
Review packet progress, signer evidence, decisions and exceptions.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 39 | ||
| Prepared | 9 | 23% | |
| Sent | 4 | 44% | |
| Partially signed | 1 | 25% |
Sample totals per stage
Group packets by organization and status to find signing work still open.
Compare each packet's completed signer count with its signer events.
Show decisions, reviewers, dates and reasons for each packet revision.
List failed or unknown attempts with their operation key and failure reason.
Compare run status and result reference by packet and source revision.
Show open actions by assignee and due date.
List documents marked No with their source packet and verifier.
Show status changes and reasons by packet and revision.
See how E-signature Platform fits your kind of team.
Each stage of packet preparation to signed evidence names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare packet work and examine exceptions.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tablesStart with one team and one process, then add the rest once the basics are running.
Name the document source, signing provider, packet owner and reviewer. Decide which organization owns the record.
Bring in organizations, people and templates before packets. Preserve original packet revisions, provider references, decisions and signer events.
Use one document type and one signing definition. Rehearse preparation, review, sending and a verified signer event.
Return a revision for correction, send a duplicate event and investigate an unknown provider attempt. Confirm the prior receipt and decision remain visible.
Compare the pilot packet with the provider envelope and signed evidence. Check role access and obtain the named owners’ acceptance.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure E-signature Platform for your business. Pilot one document type, one signing template and a packet that the owner and reviewer can reconcile with the signing provider.
It is the working record for a document sent for signature, with an owner, organization, template, revision, signer information and current status.
A packet points to a template for its organization. The template holds its code, effective dates and policy reference.
A named Signature Reviewer records a decision on the prepared revision, with a reason and evidence reference.
Yes. The packet tracks its status and completed signer count, while signer events hold the provider reference, signer identity and signed time.
Execution attempts and operation runs preserve the operation key, result and failure reason. The team checks the original provider receipt before retrying an uncertain action.
Keep the earlier revision and signed evidence. Record a successor revision, correction reason and follow-up action, then review the change.
Yes. Templates, people and packets each connect to an organization, so the setup can keep their records together.
Map packet numbers and revisions first, then bring in decisions, signer events, execution references and status history. Reconcile a pilot set against the signing provider.
Start free, then use Proto to change fields, steps and approvals before your team goes live.