Skip to main content

Object Glossary

This glossary defines the main terms used across the portal, the SpotDraft UI, and public API integrations.

Core records​

  • Contract: the central public API record for contract creation, retrieval, status, uploads, downloads, and related operations
  • Contract ID: the system-generated contract identifier returned by SpotDraft
  • Reference ID: the SpotDraft-facing contract number used to identify a contract in the repository
  • Title: the contract name shown in the repository and used by humans to recognize the record
  • Contract type: the configured agreement category referenced by public contract-type endpoints and by several contract operations
  • Template: the public object used to generate a contract from structured request data
  • Document: the file artifact attached to a contract, whether generated by SpotDraft or uploaded from an external source
  • Template contract: a contract generated from a SpotDraft-managed template and structured source data
  • Third-party paper: an externally drafted contract file uploaded into SpotDraft for review or signature
  • Executed contract: a contract that has already been fully signed and is stored in the repository
  • Supporting document: a reference file uploaded alongside a contract
  • Related record: another contract or external record linked to the current contract for context

People and organizations​

  • Creator party: your organization, acting as the SpotDraft workspace side of the contract
  • Creator party organization: the parent company or legal name of your organization
  • Creator party entity: the business unit, signing entity, or legal entity from your organization that is party to the contract
  • Counterparty / party: the external organization or individual on the other side of the agreement
  • Counterparty point of contact: the main counterparty representative responsible for review, information collection, or negotiation
  • Business user: the internal user who creates, owns, or is assigned to the contract from the business side
  • Legal user: the internal user who reviews legal language, negotiates terms, or accepts or rejects changes
  • Approver: a user who approves a contract through configured or ad hoc approval flows
  • Signatory: an individual authorized to sign on behalf of a party
  • Recipient: a contract participant surfaced by recipient-related public APIs
  • Receiver: an internal or external stakeholder who receives a finalized contract copy
  • Reviewer: a non-signer participant who reviews or comments on a contract
  • Admin: a member of the admin team who can configure workspace settings and can grant themselves contract access through product permissions

Structured integration data​

  • Metadata: structured values attached to a contract and used by integrations or downstream business logic
  • External metadata: identifiers or machine-readable values written specifically to correlate SpotDraft with another system
  • Contract data: structured field data stored on a contract and updated through contract-data APIs
  • Key pointers: structured values exposed through key-pointer APIs for retrieval or update
  • Questionnaire response: structured response data exposed through questionnaire APIs
  • Intake-form response: structured response data associated with contract intake flows
  • Tags: color-coded or categorized labels used to organize contracts
  • Opportunity details: CRM or deal context visible when a supported integration is enabled

Lifecycle statuses​

  • Status: the current lifecycle stage of a contract
  • Draft: a template-based contract has been created but not yet shared with the counterparty
  • Redlining: the contract is under counterparty review or negotiation
  • Signing: the contract is approved for signature or already in the signature flow
  • Executed: all required signatories have completed signing
  • On hold: the contract is paused and may be resumed later
  • Voided: the contract is no longer active, usually because the deal stopped or a duplicate was created
  • Deleted: the contract has been deleted from active repository views

Repository filters and task views​

  • Pending with counterparty: a filter or state indicating the counterparty has a pending review or signing action
  • Assigned to me: a task-oriented view for contracts that need the current user's review, approval, signature, signature setup, or other action
  • Task: an assigned action that a user needs to complete in the contract workflow
  • Repository: the searchable contract store that contains active and completed contract records, documents, metadata, and related context

Approvals​

  • Pre-send approval: an approval step that runs before a contract is shared for review
  • Pre-sign approval: an approval step that runs before a contract is sent for signature
  • Ad hoc approval: a contract-specific approval requested outside the configured workflow

Lifecycle and automation terms​

  • Webhook event: an asynchronous notification that a contract lifecycle change occurred after the initiating API request returned
  • Webhook HMAC key: the shared secret retrieved from the webhook API and used to verify webhook payload signatures
  • Embedded signing: a public flow where signing or counterparty interaction is surfaced via embedded endpoints
  • Reconciliation job: a scheduled repair process that checks for missed or delayed downstream updates without replacing webhooks as the primary signal
  • Counterparty review: the stage where the non-SpotDraft side is reviewing, commenting on, or negotiating the agreement
  • Execution milestone: a useful integration term for the point at which the agreement is fully signed and final downstream fetches usually become relevant

Contract actions​

  • Download: retrieve a contract document or download link
  • Upload version: upload a new version of a contract document
  • Preview: inspect the current contract version
  • Send for counterparty review: share the contract with the counterparty for review and redlines
  • Request internal review: send the contract to an internal legal reviewer
  • Request internal approval: request an ad hoc or workflow approval
  • Mark for execution: mark a version as ready to be signed
  • Set signing order: configure the sequence in which signatories receive the contract
  • Send for signatures: send the final contract to signatories
  • Put on hold: pause the contract workflow
  • Void: end the contract workflow without completing it

Workspace setup terms​

  • Workflow: the configured sequence for creating, reviewing, approving, signing, and storing a contract
  • Questionnaire: configured questions used to collect structured data for template generation or routing
  • Intake form: configured questions used when a contract or request enters SpotDraft
  • Access control: workspace, team, role, and contract-level permissions
  • Task center: the UI area where users see assigned contract tasks
  • DraftMate for admins: the Microsoft Word add-in flow used to prepare standardized templates
  • DraftMate for users: the Microsoft Word add-in flow used to collaborate on contracts

Public reference​

For broader product terminology, SpotDraft also publishes a help-center glossary:

How to use the glossary​

Use these definitions consistently when:

  • naming metadata keys
  • documenting integration assumptions
  • mapping webhook handlers to business events
  • aligning upstream and downstream systems on the same contract lifecycle vocabulary
  • Use Platform 101 for the architecture-level orientation.
  • Use Data Model for the first-class API entities and configuration boundaries.