These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- E-signature Platform
- Data model and import order
The tables behind E-signature Platform
E-signature Platform ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Packet work:
Signature packets, signer events. Keep the packet revision and signer observations together.
Definitions:
Organizations, People, signature templates, source mappings. Select the right organization and signing instructions.
Review:
Review decisions, evidence documents, follow up actions, state history. Retain decisions, proof and correction reasons.
Execution:
Execution attempts, operation runs, operation steps. Reconcile the provider result from the attempt through the receipt.
Every table, by feature
- Signature packets5
- Templates and organizations5
- Signer progress5
- Review and evidence5
- Execution trace5
- Follow-up and corrections6
- Shared and settings1
- Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates - Signature templates
A reusable signing setup for a type of document, used by the team to keep signature requirements consistent.
Linked to Organizations - Organizations
A company or business unit using the platform, used by the team to keep separate accounts and settings for each one.
- People
A person who works with or is tracked by the platform, used by the team to manage who does what.
Linked to Organizations - State history
A record of a status change, used by the team to see how and when something moved from one state to another.
Linked to Signature packets, People
- Signature templates
A reusable signing setup for a type of document, used by the team to keep signature requirements consistent.
Linked to Organizations - Source mappings
A rule for translating a value from one system's field to another, used by the team to keep data in sync across systems.
Linked to Signature templates - Organizations
A company or business unit using the platform, used by the team to keep separate accounts and settings for each one.
- People
A person who works with or is tracked by the platform, used by the team to manage who does what.
Linked to Organizations - Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates
- Signer events
An update on a signer's progress on a document, used by the team to track how far a signature request has gotten.
Linked to Signature packets - Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates - Execution attempts
A single try at carrying out an operation, used by the team to see what was attempted and whether it succeeded.
Linked to Signature packets - Operation runs
A full run of an automated operation, used by the team to see what happened end to end and its final result.
Linked to Signature packets - Operation steps
A single step within a run, used by the team to trace exactly what happened and when during execution.
Linked to Operation runs
- Review decisions
A ruling made on a submitted item, used by the team to record whether it was approved or rejected and why.
Linked to Signature packets, People - Evidence documents
A file or attachment proving something happened, used by the team to back up a decision with proof.
Linked to Signature packets, People - Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates - People
A person who works with or is tracked by the platform, used by the team to manage who does what.
Linked to Organizations - State history
A record of a status change, used by the team to see how and when something moved from one state to another.
Linked to Signature packets, People
- Execution attempts
A single try at carrying out an operation, used by the team to see what was attempted and whether it succeeded.
Linked to Signature packets - Operation runs
A full run of an automated operation, used by the team to see what happened end to end and its final result.
Linked to Signature packets - Operation steps
A single step within a run, used by the team to trace exactly what happened and when during execution.
Linked to Operation runs - Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates - State history
A record of a status change, used by the team to see how and when something moved from one state to another.
Linked to Signature packets, People
- Follow up actions
A task assigned after a review, used by the team to track who must fix or address something and by when.
Linked to Signature packets, People - State history
A record of a status change, used by the team to see how and when something moved from one state to another.
Linked to Signature packets, People - Signature packets
A batch of documents sent out for signature, used by the team to track who's signed and whether it's complete.
Linked to Organizations, People, Signature templates - Signer events
An update on a signer's progress on a document, used by the team to track how far a signature request has gotten.
Linked to Signature packets - Review decisions
A ruling made on a submitted item, used by the team to record whether it was approved or rejected and why.
Linked to Signature packets, People - People
A person who works with or is tracked by the platform, used by the team to manage who does what.
Linked to Organizations
Keys and references
Use the packet number and revision to identify document work. A signer event belongs to a parent packet and carries a provider source record identity. Keep the document hash and provider envelope reference with the relevant packet and event. Operation runs link to packets, and operation steps link to runs. Decisions and evidence link back to the packet. Store original external references so later reconciliation does not depend on a display name.
Migration order
- Load Organizations, People and Users with their stable identities.
- Load signature templates and source mappings, then check the intended organization and effective dates.
- Load signature packets with their revisions, owners and definitions.
- Load review decisions and evidence documents for each packet revision.
- Load signer events, execution attempts, operation runs and operation steps with their provider references; add state history and follow up actions.
- Reconcile packet statuses and completed signer counts against accepted events before opening work to the team.
Set up E-signature Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.