What you get for each insight
Every extracted value arrives with:The value
YYYY-MM-DD; numbers strip currency symbols and separators.A verbatim source quote
A page citation
A confidence and a rationale
Where insights show up
On the document itself
On the document itself
On the contract record
On the contract record
Inside the contract AI summary
Inside the contract AI summary
In exports
In exports
When extraction runs
- Automatically, on upload. When a new document finishes processing, Coverbase extracts every enabled insight whose document types match that document.
- On demand, per document. Open a document’s Insights tab and choose Refresh all. Use this after you add or reword an insight, since existing documents were processed against the old definition.
- On demand, per insight. Re-extract a single insight from the row’s actions after you tighten its description.
- In bulk, across history. A new insight starts empty on every document you already hold. Configuration → Document Insights → Document types shows exactly how many, and a backfill re-extracts them. See Backfilling history.
Creating an insight
Go to Configuration → Document Insights. You need the org-settings update permission to reach this page.Create a group first (optional but recommended)
Add the insight and name it for a human
Write the description
Pick the type
Pick the mode
Scope it to document types
Try it on a real document before you roll it out
Extract vs Synthesize
This is the setting people get wrong most often.Extract: a single, typed answer
Synthesize: a written summary
The decision table
Yes/No insights
Write a Yes/No description as the question, and say what counts as Yes. “Do we have audit rights?” reads Section 8.3, answers Yes, and cites the clause. Where the answer turns on nuance (notice periods, conditions), the quote carries the nuance and the value stays filterable.The same question, both ways
Take one requirement (do we have the right to run a penetration test?) and see how the mode changes what you get.- Extract
- Synthesize
Yes, quoting “Customer may, no more than once per twelve (12) month period and upon thirty (30) days’ prior written notice, conduct penetration testing of the Services.” on page 14, confidence high.Good when you want to sort your portfolio by which vendors you can test. The nuance about notice periods lives in the quote; the filterable answer lives in the value.Quick rules
- If you want one value you could sort or filter on (a date, a number, a name, Yes or No), use Extract.
- If you would have to read a paragraph and then say a sentence back, use Synthesize on a Text insight.
- Every Yes/No, Number and Date insight is Extract. Synthesize takes Text only.
- A Number or Date you would have to work out is still Extract; put the working in the description.
- When you cannot decide on a Text insight, start with Synthesize. You get an answer with a quote attached, and you can tighten to Extract later once you have seen how the language reads.
Concise and Detailed answers
Every insight also has an Answer format, set on its Definition tab. It decides how long the stored value is.Writing descriptions that work
The description is the prompt. Treat it like an instruction to a sharp new analyst who has never seen your contracts and will not ask follow-up questions. A description that performs well usually has four parts:Define the thing precisely
Name the aliases
Say what to do about edge cases
Say what not to return
- Weak
- Strong
A starter library
There is no packaged template for insights the way there is for clause sets. Insight definitions are yours to write, because they encode what your program tracks. Use this as the copy-and-adapt starting point. Group them, scope them to your contract document types, and delete anything you will not use.Group: Contract basics
Scope to MSA, order form, SOW, terms of service, software license agreement.Group: Renewal and exit
Scope to MSA, order form, terms of service.Group: Risk and liability
Scope to MSA, DPA, security addendum.Group: Data protection and security
Scope to DPA, MSA, security addendum, SCC.Group: Service levels and AI
Scope to SLA, MSA, AI addendum.Auditing coverage
Writing an insight is the easy half. Knowing whether it worked across your whole corpus decides whether anyone trusts the field. Configuration → Document Insights answers that. Three tabs over the same data:Insights: is each definition healthy?
Insights: is each definition healthy?
Document types: is this type well covered?
Document types: is this type well covered?
Extractions: is this specific value right?
Extractions: is this specific value right?
Two kinds of blank
A missing value means one of two opposite things:Backfilling history
A backfill re-extracts documents you already hold, so a new or reworded insight applies to your whole corpus instead of only to what arrives next.Scope it
Choose what to re-run
Read the estimate
Watch it run
The insight workbench
Click an insight on Configuration → Document Insights to open its workbench. Everything about one insight lives here: what it extracted, how to test a change, its definition, the fields it fills, its history, and the changes waiting for a reviewer. The header shows the insight’s name, whether it is on, its current version (Version 3, for example), and whether it fills fields automatically or asks a reviewer first. Test, Re-run and Export start from here.Teaching an insight with examples
A description tells Coverbase what to look for. An example shows it. Add examples on the Definition tab when the description is right but the answers keep coming back in the wrong shape, or when one kind of wording keeps tripping it up. Each example has three parts:- Document Excerpt. The passage the answer comes from, pasted from a real document (up to 4,000 characters).
- Expected Answer. What the insight should return for that passage. Leave it empty when the passage does not answer the question, which is how you teach an insight not to guess.
- Why This Is the Answer (optional). One sentence on why that is the answer, such as “The amendment in Exhibit C replaces the Net 30 term.”
Testing a change before you save
The Test tab runs your edited definition, including unsaved changes and examples, against documents you choose. Nothing is saved and no field is filled.Pick documents
Run the test
Compare
Applying a change
When you save an edit that affects extraction (the description, type, mode, answer format, display format, document types, or examples), the insight moves to a new revision and Coverbase asks which documents should use it. Renaming an insight, turning it on or off, reordering it, or moving it to another group does not create a revision.Marking values correct or incorrect
A verdict records that a person checked a value against the document. On the Values tab, mark a value Correct or Incorrect, one at a time or by selecting several rows. You can clear a verdict if you change your mind. When you mark a value Incorrect, you can enter the right answer. The corrected value replaces the extracted one, is treated as set by hand, and is never overwritten by a later re-run. It also flows to any field the insight fills, following that field’s rules. Verdicts do three things for you:- They tell you which insights to fix. Filter to Incorrect to see where a definition goes wrong, then fix it and re-run those documents with Selected documents.
- They become examples. Choose Save as example on a correction.
- They build the dataset for your decision model.
Seeing one document type at a time
The Document types tab on Configuration → Document Insights shows coverage for each type. Click a type to open a grid of every document of that type down the side and every insight that applies to it across the top. Use it to read an MSA’s insights side by side across vendors, or to spot the one document where a value is missing. On Configuration → Document types, each type shows how many insights apply to it and links to those insights.Retiring an insight
Three actions, easy to confuse:Promoting an insight to a custom field
An insight lives on a document. Your team works from vendor, contract, and assessment records. Promotion carries the value across.Open the insight's Fields tab and choose Promote to custom field
Set the gates
Choose what happens when the field already has a value
Backfill the field
Filling built-in contract and document fields
Besides custom fields, an insight can fill fields Coverbase already has on contracts and documents. Choose them on the insight’s Fields tab.Fill automatically or ask a reviewer
The Fields tab also sets what happens when the insight finds a value for a field.The audit trail
Every insight keeps a full record on its History tab. Definition Changes. Each version of the definition is listed with what changed, who changed it, and when. Open one to see the definition and examples exactly as they were. Value Changes. Every change to a value is recorded and never edited afterwards:- Extracted, or extracted again by a re-run, with the revision that produced it
- Set or cleared by hand
- An unverified answer accepted
- Marked correct or incorrect, a verdict cleared, or a value corrected
- Written to a field
- A review requested, approved, or rejected
The decision model
The Model tab on Configuration → Document Insights lets you build a model tuned to your organization’s documents from the answers your team has checked. You never need one: insights work without it.Build the dataset
Evaluate
Train
Activate
Sharing a library between orgs
Insight definitions can be exported as a JSON file (names, descriptions, types, modes, and document-type scope, with no values and no ids) and imported into another org. This runs through the Coverbase API rather than a button in the dashboard. An import matches on the insight’s stable key. Existing definitions are skipped unless the import explicitly opts into overwriting them, so reimporting a shared library never silently reverts local prompt tuning. The Export on a single insight’s page is different: it downloads that insight’s extractions as a workbook (document, vendor, value, confidence, grounding, page and quote).Reviewing and correcting values
The AI drafts; a reviewer checks the evidence before anyone relies on it.Check the quote before you trust the value
Check the quote before you trust the value
Accept an answer whose evidence was not verified
Accept an answer whose evidence was not verified
Re-extract after you change a definition
Re-extract after you change a definition
Export for analysis
Export for analysis
Manage insights from MCP or the API
You can define, test, backfill and review insights from an MCP client or with an API key, as well as in the dashboard. An MCP client reads withquery_platform(kind=...) (document_insight_configs, document_insight_config_detail, document_insights, document_insight_pending_changes, document_insight_stats, document_insight_backfills). It writes with mutate(entity="document_insight_config", action=...), mutate(entity="document_insight_value", action=...), mutate(entity="document_insight_example", action=...), mutate(entity="document_insight_backfill", action=...) and mutate(entity="document_insight_pending_change", action=...).
The API routes sit under /v1/document-insights, /v1/document-insight-values and /v1/document-insight-backfills. See Create and manage document insights.
You can also read coverage, value history, the inbox and accuracy checks, compare and export values, open evidence images, run an insight on one document, and delete an archived insight. An MCP client reads these with query_platform(kind=...) (document_insight_coverage, document_insight_value_query, document_insight_pivot, document_insight_config_events, document_insight_value_events, document_insight_snippets, document_insight_inbox, document_insight_model_scorecard, document_insight_preview) and writes with mutate(entity="document_insight_config", action=...) (test, export, delete), mutate(entity="document_insight_extraction", action=...) (run, start_preview) and mutate(entity="document_insight_pending_change", action="bulk_resolve"). Bulk approval and rejection of pending changes is in MCP only. See Delete a document insight and the sections after it.
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.
Creating or changing an insight, its examples, targets, groups or backfills needs org_settings:update:org. API keys do not hold it, so use a key created by a person whose role holds it. Reviewing values needs only vendor:update:org. Even with the right key, archiving or restoring an insight, unlinking a custom field, retiring a decision model and deleting an example, group, target or value stay with a signed-in user.
Troubleshooting
The insight comes back empty on documents that clearly contain the answer
The insight comes back empty on documents that clearly contain the answer
- It never ran on that document. If the insight was created after the document was processed, it has never been attempted there. Check the coverage matrix: a stale badge means backfill, not a broken definition.
- A type that does not fit the question. A Number or Date insight only stores a value that parses as one, and a Yes/No needs a question with a yes-or-no answer. Match the type to the question, or use a Text insight.
- Wrong document-type scope. If the insight is not scoped to the type that document was classified as, it never ran. Check the document’s type on its detail panel, and check the insight’s document types (or its group’s).
- The description names the wrong thing. The model looked for what you described and did not find it. Add the aliases the clause hides under.
A Yes/No insight keeps failing
A Yes/No insight keeps failing
The value is right but the page number looks wrong
The value is right but the page number looks wrong
The number came back as text
The number came back as text
Nothing extracts on a scanned or image-only PDF
Nothing extracts on a scanned or image-only PDF
The insight is right for one document type and noisy on another
The insight is right for one document type and noisy on another
I changed an insight but old documents still show the old answer
I changed an insight but old documents still show the old answer
A field change is waiting but no one was asked to review it
A field change is waiting but no one was asked to review it
I don't see Configuration → Document Insights
I don't see Configuration → Document Insights