Definitions for the terms behind live signing visibility, recipient verification, and outcome follow-through.
Peekop uses a broader model than basic sent-and-signed status updates so senders can understand what happens in between and what happens after completion.
A signing request is created, assigned to a recipient, and prepared for delivery.
A protected signing link is created for the intended recipient.
The intended recipient confirms the email tied to the signing request and enters the protected signing session.
The verified recipient has opened the document.
A verified recipient has begun actively completing the document.
The required signing action is completed.
The signed document moves into evidence, follow-through, and next-step readiness.
A signing request is the primary workflow object in Peekop. It assigns a recipient, controls delivery, verification, signing activity, and completion evidence.
Why it matters: It establishes that the workflow starts with an assigned request, not with a public link.
Related terms: Recipient-Specific Link, Verified Access, Viewed, Completion Record
Secure Send is the moment a document or packet is delivered through a protected signing link.
Why it matters: It makes delivery part of a trusted workflow rather than a simple file handoff.
Related terms: Signing Request, Recipient-Specific Link, Verified Access, Viewed
Viewed is a signal that a verified recipient has opened the document.
Why it matters: It confirms awareness, but it does not yet confirm active participation.
Related terms: Secure Send, Verified Access, Signing Started
Verified Access is the moment the intended recipient confirms the email tied to the signing request and gains access to the protected signing session.
Why it matters: It makes recipient verification visible, durable, and distinct from anonymous link access.
Related terms: Recipient-Specific Link, Viewed, Protected Signing Session
Signing Started is a signal that a verified recipient has begun actively completing a document.
Why it matters: It is often the strongest pre-completion signal that active completion is happening.
Related terms: Viewed, Verified Access, Protected Signing Session, Follow-Up Timing Intelligence
Signed is the moment the required signing action is completed.
Why it matters: It confirms document completion, but it does not always mean the broader workflow is finished.
Related terms: Signing Started, Completion Record, Secure Outcome
Secure Outcome is the state in which a signed document has moved into trusted follow-through, evidence, and next-step readiness.
Why it matters: Many workflows require more than a completed signature. They also require proof, delivery, and operational completion.
Related terms: Signed, Outcome Workspace, Completion Record, Outcome Readiness
Signal Center is the live visibility surface that shows document activity as it happens across the signing journey.
Why it matters: It answers the question: What is happening right now?
Related terms: Viewed, Signing Started, Request Journey
Request Journey is the historical view of how a request progressed from send through completion.
Why it matters: It answers the question: How did this request get here?
Related terms: Signal Center, Signing Started, Signed
Outcome Workspace is the operating surface used to manage a completed document outcome.
Why it matters: It answers the question: What should happen next?
Related terms: Secure Outcome, Completion Record, Outcome Readiness
A Completion Record is the evidence package that proves what happened throughout a document outcome.
Why it matters: It can include signer verification, timeline evidence, signing activity, generated artifacts, and follow-through status.
Related terms: Outcome Workspace, Workflow Evidence, Protected Record
Outcome Readiness is the state in which a completed request has the necessary evidence, artifacts, and follow-through needed for confident next-step action.
Why it matters: It communicates that signed does not always mean ready.
Related terms: Secure Outcome, Completion Record, Workflow Evidence
Workflow Evidence is the structured proof showing that important document events and downstream actions occurred.
Why it matters: It supports review, export, audit, and follow-through confidence after completion.
Related terms: Completion Record, Outcome Readiness, Protected Record
Document Outcome is the real-world result of a document workflow after signing activity is complete.
Why it matters: It includes not only signature completion, but also delivery, proof, follow-through, and downstream readiness.
Related terms: Secure Outcome, Outcome Management, Document Completion
Outcome Management is the practice of managing what happens after a document is sent and signed.
Why it matters: It includes visibility, follow-up timing, evidence, artifacts, and next-step execution.
Related terms: Document Outcome, Outcome Workspace, Completion Record
Document Completion is the full successful process of moving from secure send to usable outcome.
Why it matters: Peekop uses this idea more broadly than traditional e-sign systems, which often treat signature alone as completion.
Related terms: Signed, Secure Outcome, Outcome Management
Completion Visibility is the ability to see where a recipient is in the path from delivery to signed outcome.
Why it matters: It helps the sender understand whether a document was only sent, opened, actively started, completed, or moved into follow-through.
Related terms: Viewed, Signing Started, Signal Center
Follow-Up Timing Intelligence is the ability to understand when outreach is most useful based on live signing visibility signals.
Why it matters: In Peekop's model, Signing Started is often the most useful timing signal before completion.
Related terms: Signing Started, Signal Center, Completion Visibility
Recipient-Specific Link is a protected signing link created as part of a signing request for the intended recipient.
Why it matters: It is a delivery and access artifact attached to the request, not the source of signing authority by itself.
Related terms: Signing Request, Verified Access, Protected Signing Session
Protected Signing Session is the signing environment entered after Verified Access is established and before protected signing actions occur.
Trusted Completion is the completed signature state with sufficient trust signals to support reliable outcome handling.
Protected Record is a durable evidence-bearing record of what happened across the document workflow.
Evidence Ready is the state in which the supporting proof for a document outcome is available for review, export, or downstream use.
Signing Started means a verified recipient has moved beyond viewing and has begun actively completing the document.
Verified Access is the moment the intended recipient confirms the email tied to the signing request and enters the protected signing session.
No. Viewed means the document was opened. Signing Started means the recipient began interacting with the signing process.
A Completion Record is the structured proof of who engaged, when the document was viewed, when signing began, when completion happened, and what outcome artifacts exist.
Outcome Workspace is the post-sign surface where senders review completion details, evidence, artifacts, and recommended next steps.
Signed means the signature step is complete. Secure Outcome means the workflow has also moved into evidence, artifacts, and next-step follow-through.
Follow-up timing matters because senders make better decisions when they know whether a recipient only opened the document or actually began completing it.
Use these pages to go deeper into the document journey, follow-up timing, and outcome model behind Peekop.