Contract Hub

Contract Hub is the contract lifecycle workspace. It has an Overview page and pages for Renewals, Spend and Compliance, a clause library, and three workspace pages: Dashboard for contract health and the lifecycle lanes, Work queue for legal review, approval queues, work items, obligations and renewal reminders, and Create and policies for contract packets and approval SLA policies. The New contract wizard saves a draft on its own. A packet made with the packet builder on the Create and policies page is a contract out for signature, and the builder also creates a CRM account and deal, a signing envelope for one signer and a PDF record.

• Contract packet builder with account, deal, signer, PDF name, amount and expiry
• Overview, Renewals, Spend and Compliance pages with contract value, expiring contracts, the renewal rate and open, overdue and blocked obligations
• 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 queue and approval SLA policies with deadlines, reminders and escalation, for CRM, e-signature, PDF and delegated-access approvals
• Clause library and redline comparison for reviewing contract wording
• Links 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.
• A packet created on the Create and policies page is a contract. The Overview, Renewals, Spend and Compliance pages count it as out for signature, and it becomes active when every signer has signed. The packet also creates a CRM account and deal and a signing envelope, so those records appear in Sales CRM and Document Sign.
• Each contract action needs the contracts permission for it (view, create or update). Approval decisions are recorded with who made them and when.
• The workspace used to be one page. Its old address now opens the Dashboard, or the Work queue when a link names a work item or an approval, so existing links and bookmarks still arrive.
• A contract out for signature leaves that state when its signing request ends unsigned. If the request is withdrawn or a signer declines, the contract returns to draft so it can be revised and sent again. If the request expires, the contract moves to expired. Each change is recorded on the contract's history.

1. 1Open /contracts and read the Overview page for contract value, expiring contracts and the renewal rate.
2. 2Use the Renewals page for contracts expiring within 30, 60 and 90 days, and the Compliance page for open, overdue and blocked obligations.
3. 3Open Create and policies to create a contract packet, then use the date pickers for expiry, effective and termination dates. Open the Dashboard for contract health and the seven lifecycle lanes.
4. 4Review obligations and set due dates from the obligation ledger.
5. 5Open the Work queue to decide approvals, and Create and policies to set approval SLA deadlines, reminders and escalation.
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. The New contract wizard saves a draft contract on its own. The packet builder on the Create and policies page creates its own CRM account and deal for the packet, so you do not need an existing deal.

Which contract actions are recorded?

Each contract action needs the contracts permission for it, and approval decisions are recorded with who made them and when.