Contract Hub

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.

• 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

• 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.

1. 1Open /contracts and search the Contract Action Catalog for the job you need.
2. 2Use the command center when you want lifecycle posture, approval pressure, and work-queue priority.
3. 3Create or inspect a contract packet, then use the date picker for expiry, effective, and termination dates.
4. 4Review obligations and set due dates from the obligation ledger.
5. 5Use the approvals and SLA panels to route decisions and record evidence.
6. 6Open Document Sign or PDF Studio only when a contract needs signature or document processing.

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.

Which contract actions are recorded?

High-risk approval and lifecycle actions are both audited and permission checked, so the record of who advanced a contract and when is kept alongside the check that they were allowed to.