Module guide
Contract Hub
Contract lifecycle, approvals, SLAs, renewal packets, and legal evidence.
Overview
Contract Hub is a standalone contract lifecycle workspace. It manages contract packets, legal review, approval queues, work items, obligations, renewal reminders, clause remediation, lifecycle transitions, and PDF evidence handoff without requiring CRM or signing work.
Highlights
The capabilities worth knowing before you dive in.
- Contract packet builder with amount, expiry, PDF evidence, approval, and SLA controls
- Searchable Contract Action Catalog for packets, renewals, approvals, obligations, redlines, evidence, and optional handoffs
- Lifecycle header editing for effective and termination dates through the shared date picker
- Obligation ledger with a due-date picker, completion proof, reminders, and decision actions
- Approval and SLA surfaces for legal, finance, security, procurement, and executive review
- Each cataloged contract action names its user control, validation rule, app API route or standalone module boundary, and MCP target
- Optional handoff to Document Sign and PDF Studio for signing packages or source-PDF evidence
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Date-only fields use the Atlas date picker and preserve the existing API payload shape.
- Contract Hub can create CRM activities and PDF evidence links, but those are optional integrations.
- High-risk approval and lifecycle actions are audited and permission checked.
How to use it
The primary workflow, start to finish.
- Open /contracts and search the Contract Action Catalog for the job you need.
- Use the command center when you want lifecycle posture, approval pressure, and work-queue priority.
- Create or inspect a contract packet, then use the date picker for expiry, effective, and termination dates.
- Review obligations and set due dates from the obligation ledger.
- Use the approvals and SLA panels to route decisions and record evidence.
- Open Document Sign or PDF Studio only when a contract needs signature or document processing.
FAQ
- Why are contract dates pickers instead of plain inputs?
- Enterprise contract dates must be deliberate, accessible, and consistent. The picker prevents browser-native timezone and formatting drift.
- Does Contract Hub require a CRM deal?
- No. Deal context can help revenue workflows, but contract work can stand alone.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?