Contracts

Contracts are the agreements behind your services: term dates, renewal terms, notice periods, and contract value.

They live at /contracts, with /contracts/review for the Pending Approval queue.

What a contract record holds

Each contract captures:

• Name and contract number
• Client, provider, and account
• Type: MSA, Order Form, Co-term, Addendum, or Terms & Conditions
• Status
• Start and end dates, and term in months
• Auto-renew and notice period
• MRC, NRC, and total contract value (TCV)
• Notes

A progress bar on the record shows how much of the term has elapsed.

How contracts get added

Contracts can be added manually or extracted automatically from a document your provider attaches, for example a signed order form or master service agreement. A parsed contract appears immediately in your main Contracts list, badged Pending approval.

The Pending Approval queue

/contracts/review. A contract created from a parsed document is already in your list and its data is already saved, but it first needs a quick human check. That check happens here.

Open a pending contract, review the extracted fields, then:

• Approve it to clear the pending state and mark it reviewed.
• Reject it to remove it if it was parsed in error.

Any user in your organization with access can approve, so this is not restricted to admins. Approving does not change visibility, since the contract is already visible in your list before approval; it simply clears the pending state.

Linking contracts to services

Every service in your inventory can be linked to its governing contract so its cost and lifecycle can be checked against what you actually agreed to. See Service inventory.