Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It covers the screens you work in every day. For what Coverbase reads each document into, see the Contract components guide. For running clause reviews, see the Contract Guardian guide. For the dates behind reminders, see Contract dates and reminders. For raising a new contract and getting it approved and signed, see Contract intake and approval. To turn a folder of contracts you already hold into records, see Contract Assembly.
The contracts module has two screens: the list page, where you see the whole portfolio at once, and the contract record, where you work one agreement. This guide covers what each part shows and what you can change.

​
The contracts list page

Contracts list page with attention cards, toolbar, and contract table

The contracts list page: the attention cards, the toolbar, and the contract table.

Two sections stack down the page: the attention cards, then the list. The list has two views, a table and a renewal runway, and a toggle on the toolbar switches between them. Beside the page title are three links: Configuration for lifecycle stages and reminders, Guides for this documentation, and Reports for the dashboards built on the portfolio.

​
Attention cards

Attention cards showing notice deadlines, renewal decisions needed, missing renewal details, and reviews needed

The four attention cards. The line under each figure is the part that cannot wait.

Four cards sit in one row. Each is a queue that needs someone to act, and the line under the figure says how urgent it is. Click a card to filter the list below to exactly those contracts. Click it again to clear the filter. Each card is a saved view, so the filter it applies can be edited like any other, and the three review queues folded into Reviews needed are still available on their own from the view selector.
Reviews needed counts contracts, not problems. A contract with an open clause and a value conflict is one review, because the list the card opens can only show it once.

​
The toolbar

Under the cards, one row holds the controls for the list: Search, the view selector (All contracts and your saved views), Filter, display options for the table’s columns, the toggle between the table and the renewal runway, and Preview. On the right, Actions opens exports, notifications, uploads, bulk create, Start a review for a clause review, and, where your workspace has it, Import contracts and View import batches for Contract Assembly. New contract creates one. The view toggle and Preview remember your choice in this browser. They do not change anything for your colleagues.

​
The contract table

The table opens on the renewal story, left to right: Contract, Vendor, Status, Notice due, Renewal decision, Renewal, Renewal term, Current term end, Relationship owner, Contract value, and Updated. Columns marked AI hold values Coverbase extracted from the documents rather than values someone typed. The column picker offers the rest: Term start, Effective date, Initial term, Termination notice, Contract length, Action date, Renewals applied, Contract type, Committed amount, and every contract component. A value nobody has recorded reads Not recorded. It turns orange where the gap is yours to close: a contract that renews automatically with no Renewal term will roll forward on a term nobody wrote down. A contract renewed by agreement has no renewal term, so that cell reads Not applicable. Every row ends in a menu with the same four actions:

​
Previewing contracts

Contract list with one row highlighted and a panel on the right showing the vendor, the contract name, its summary, and its renewal terms

Preview mode. The selected contract is highlighted in the list and shown beside it.

Click Preview in the toolbar to look through contracts without leaving the list. A panel opens beside the table, or beside the runway, and shows the first contract. While preview mode is on:
  • Click any row to show it in the panel. You do not need to close the panel first, and the rest of the page stays usable.
  • The contract you are previewing stays highlighted in the list.
  • Use the up and down arrows at the top of the panel, or the up and down arrow keys on your keyboard, to move to the previous or next contract. They follow the list as you have filtered and sorted it, and continue onto the next page. The panel shows where you are, for example 2 of 230.
  • Click Open contract at the bottom of the panel to open the full record.
The panel shows the vendor first. If the contract is an order form, SOW, or amendment under another agreement, that agreement comes next, and you can click it to open it. Then come the contract name, type, and status. Below that are the details that do not fit in a column: the summary or description, the term and renewal dates, the contract value and payment terms, owners, services, documents, and notes. On a narrower screen, the panel opens over the right side of the list instead of beside it. The rows it does not cover still work the same way. To leave preview mode, click Preview again or close the panel. With preview mode off, clicking a row opens the contract as usual. Holding Cmd or Ctrl while you click opens it in a new tab in either mode.

​
The renewal runway

Renewal runway with one lane per contract showing the notice deadline, the required notice span, and the current term end

The renewal runway. Each row is a contract, drawn on a year of days from today.

Switch the toggle to the runway and the same rows are drawn as a calendar: one lane per contract, on a year of days from today. Filters, search, sorting, and paging carry over from the table. Each lane carries three things, named in the legend: Today is the circled day at the left, with a line down every lane. Hover a mark to read its date, and click a row to open the contract. The row menu is the same one the table has. A lane with no notice date says Notice due date not recorded where the mark would be, with a dotted line up to the term end. A notice date that has already passed sits on today as a filled mark, and its hover gives the date it fell on. A term end more than a year out runs off the right edge.
The notice deadline is the last day you can act, and it always comes before the term end. Read the lanes by their hollow circles first: that is the column of dates you are working to.
To find the contracts that cannot renew, click the Missing renewal details card, or filter on Auto-renews is Automatic and Renewal Term is empty. Those are the ones that will be marked expired instead of rolling forward.

​
The contract record

Contract record showing the header, the facts row, the tabs, and the Overview with its right rail

A contract record: the header and its facts, the tabs, and the Overview.

Open a contract from the table, the runway, or a search result. The top of the record says where the contract stands before you open a tab.

​
The header and the facts row

The header carries the vendor’s logo, the contract name, its type, and its status. Hover the logo for the vendor’s website and risk analysts, and click it to open the vendor. Click the name to rename the contract, and click the status to move it to another stage. On the right are Copy link, a button for the next step, and Actions, which holds Configure lifecycle, Configure reminders, and Archive. The next-step button names what the contract is waiting on: Continue clause review while a clause review has flagged clauses nobody has triaged, otherwise Submit for approval, View approval, Send for signature, or Track signature, following the Workflow tab. Under the name, one row of facts: Value, Term, Renewal, Notice Due, Owners, and Vendor Risk. Nothing in the row is an editor. An empty fact links to the Terms card, where the value is edited, and Owners links to the Team card. A warning icon beside Term means the term dates disagree with the documents.

​
The tabs

Findings open from the Findings card on the Overview and take a tab of their own only while they are open.

​
The Overview tab

The main column runs from what needs a decision to what the contract says:
  1. Reading documents, only while Coverbase is still reading files on the contract
  2. Needs Attention, described under What needs attention
  3. Summary, the AI read of the agreement
  4. Terms, the one place the contract’s own facts are edited
  5. Documents, the files on the contract nested under what they amend, each marked with its role. Upload and All documents and what they say open the Documents tab.
The right rail holds Team (relationship owners and watchers), Reviews, and Custom Fields. Vendor, Risks, Findings, and Related (the contract this one renews, and other contracts buying the same category) join them when those parts of Coverbase are on for your organization.

​
What needs attention

Everything on the contract that blocks a step or wants a decision sits in one list, with the action beside each line: The card is not shown when there is nothing to do.

​
The terms card

Terms card showing the date track, the term and renewal values, the renewal decision row, and the reminders row

The Terms card: the dates on a track, the values under it, the renewal decision, and the reminders.

Dates, term lengths, renewal, notice, cost, and the contract’s description are edited here and nowhere else. A Term 4 badge beside the title means the contract has renewed three times.
  • The track places the dates in order: Effective, Term start, Term end, Notice due, Internal action, and Audit date. Click a date to edit it. The + beside the track brings back a date you hid. What each date means, and which ones Coverbase calculates, is in Contract dates and reminders.
  • The grid under it holds Effective date, Term start, Term end, Initial term, Auto-renews, Renewal term, Notice period, Notice due, Contract value, Payment terms, Services, and Description. Click any value to edit it. A value marked derived was calculated from the others, and a small document icon marks a value read from a document. Yearly breakdown in the card header splits the contract value year by year.
  • Renewal decision shows the decision recorded for the current term and who recorded it. Record decision (or Change decision) opens the four choices, Not decided, Renew, Terminate, and Under review, with a note for why and who you asked, and the contract’s Renewal Notes. The decision is a column on the contracts list and a filter across the portfolio, so “which renewals has nobody decided yet” is a question you can answer without opening records one at a time.
  • Reminders says how many reminder emails are scheduled and whether they are inherited from the global settings or set for this contract. Click it to see the schedule. Admins see Configure.
A contract set to auto-renew with no renewal term cannot renew. Renewal needs both: the setting that says it renews, and a term to renew into. With only the first, the contract is marked expired on the term end its paperwork names, which can be years in the past.Needs Attention says so when it applies, and the renewal editor warns you as you set it. Filling in Renewal term clears it. The next nightly run then renews the contract and puts its status back.
Warning that the contract is set to auto-renew but no renewal term is recorded

The warning shown on a contract set to auto-renew with no renewal term recorded.

If a contract renews while you are recording a decision about the term that ended, the save is refused and you are told the term moved. That is deliberate: the decision was about the old term, and the new one deserves a fresh look. Read the new term, then record the decision again.

​
Saving, and undoing a save

Description and Payment terms save when you click away. There is no Save button for them, so the confirmation is the toast that appears in the corner: “Description saved” or “Payment terms saved”. Contract value, Services, and the renewal notes also save as you leave them. The date and renewal editors open in a panel with their own Save. The Description and Payment terms confirmations carry Undo. Click it and the field goes back to the value it held before that save.
Undo is offered for one save at a time. Once you edit the same field again, the earlier offer disappears, because putting back a value from two edits ago would throw away the edit in between. Finish an edit, check the confirmation, then move on.
If a save fails, the toast says so and names the field. The value stays in the box, so you can click away again to retry rather than retyping it.

​
The vendor card

Vendor card showing other contracts, status, owners, risk tier, and assessment dates

The vendor card. Who the counterparty is, what else they are paid, and how they were rated.

The top of the right rail answers the questions that decide how carefully the rest of the page should be read. The same 90 day notice period is routine on a design tool and a board-level problem on the vendor holding your customer data. Click the vendor name to open the full vendor record.
Unavailable in the risk tier or last assessment row means the lookup failed, not that the vendor is unrated or never assessed. Reload the page. If it keeps saying Unavailable, the vendor record itself will tell you.

​
The documents tab

Documents tab showing the file table above the contract components and document insights cards

The Documents tab: the files, then what the documents say, then document insights.

The Documents tab opens on Files: every document on the contract, with every action on a row. Upload new files below the list, or use Link Existing Contract Documents to add paper already on the vendor. When you upload, Coverbase reads each new file against what the contract already holds and asks you to confirm what it does before anything is saved, for example whether it replaces a document or adds to the contract. Below the files sit What the documents say, the contract components read by component or by document, and Document Insights.

​
Read the workspace from MCP or the API

You can read the list page and the contract record from an MCP client or with an API key. An MCP client reads with query_engagements_contracts(kind="contract_home_summary"), query_engagements_contracts(kind="contract_attention_queues"), query_engagements_contracts(kind="contract_runway"), query_engagements_contracts(kind="contracts"), query_engagements_contracts(kind="contract_detail") and query_engagements_contracts(kind="contract_detail_context"). It edits a contract with mutate(entity="contract", action="update"). The API routes are GET /v1/contract-home-summary, GET /v1/contract-attention-queues, GET /v1/contract-savings-report, GET /v1/contract-records/{contract_id}/detail-context and the Contract records API. See Contract components, value and spend. Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field. Archiving a contract needs contract:archive:org, which service accounts do not hold.

​
What’s next

Contract Guardian guide

Build a clause set, run a review against the documents you choose, and work the results.

Contract dates and reminders

What each date on the timeline means, which ones Coverbase calculates, and who gets the reminder emails.

The contract Spend tab

What a contract costs, line by line, and across its renewals.

Contract Assembly

Import a folder of contracts you already hold and confirm what Coverbase proposes.