Grounding
Grounding checks the claims in a document against your reference library. It shows which claims your sources support, which disagree with them, and which aren't in your library yet, so you can fix the document or the library before you publish.
Before You Start
- Open a document, then select the Grounding icon (a shield) on the right edge. On a phone it's one of the document's panel tiles.
- Grounding works on documents in Content and in projects. It isn't offered on Blueprint drafts or items in your reference library. On a scratchpad, the panel asks you to convert it into a document first.
- Running a check needs the Admin or Creator role.
- A check uses Studio Credits, and availability depends on your plan. See Pricing.
Check a Document
- Open the Grounding panel.
- Select Check grounding. The panel saves your latest edits first, then shows Checking grounding… and its steps. A check usually takes a minute or two.
- Read the meter at the top: X of Y claims grounded, with counts for each result below it. A claim counts as reviewed once every finding on it is dismissed or resolved. If the check was incomplete, claims it couldn't confirm are counted together as not confirmed.
To run it again later, select Re-check at the top of the panel.
Review Conflicts
Claims under To review disagree with the material the document was built from. Each card shows This draft next to the source it conflicts with. Select the source name to open it. Depending on the conflict, the card offers:
- Fix in this document opens the AI Assistant with a fix ready. Review it, then send it.
- Review suggested fix appears instead when the suggested fix changes the context item rather than the document. It shows the Current Content and Suggested Update. Select Accept Change to apply it.
- Update the context item instead opens the context item in a new tab, with an instruction for the AI Assistant ready to change it to match your document. It isn't offered when the card says the claim disagrees with your material about a company.
- Dismiss — Not a Real Conflict removes the card.
When two of your own context items disagree, Grounding follows the newer one. If your document matches only the older item, the card says Outdated: this draft matches an older context item that a newer one contradicts. It shows the Older and Newer context items with their dates, so you can update the document to match the newer one. This is different from the Outdated status at the top of the panel, which means the check itself needs a re-check.
Add Missing Claims to Your Library
Claims under Not in your reference library yet have no support in your library. When several claims are missing, they share one card with one picker. When only one is missing, the card covers that claim.
- On the card, open the Choose context item to update: list. Marcora suggests an item where it finds a good fit.
- Pick an item, or search your reference library for another.
- Select Run update. Marcora updates the item in the background, and the card shows Updating with a Watch link.
When the update finishes, the card disappears and the panel shows Outdated. Select Re-check to see the added claims as supported. If the claims are still missing afterward, the card says why: Marcora didn't change the item, or the update didn't finish.
If no item is a clear fit, the card says so. To save a claim on its own, select Save this claim as new reference material (with several claims, each button names its claim), then Save claim. This creates a Team item named after the claim, with nothing else from the document.
With several missing claims, the panel offers two shortcuts at the top:
- The update button (for example Update the 3 affected context items) runs every suggested update at once.
- Add this document to your reference library saves the whole document as a new context item. You can't remove it from the app afterward.
With fewer missing claims, the same action is at the bottom of the panel as Add current document to your reference library.
To skip the missing claims, select the X on the card. It dismisses every claim on that card.
How It Works
- What it reads: first, what the document was built from (your reference library, Brand Foundation, its project and anything used while drafting). Then your other collections, which can support a claim but never raise a conflict. See What this check reads in the panel.
- Claims about your company are checked against material about your company, and only your Brand Foundation and context items Marcora has confirmed as yours can flag a conflict about your company. Marcora needs your company overview to confirm them. Claims about another company, such as a competitor, are checked against your material about that company, which can also flag a conflict. When the check can't flag conflicts against your context items, the panel says why: there's no company overview (select Open Brand Foundation to add it), none of your context items are confirmed as yours, or some aren't confirmed yet.
- When two of your own context items disagree, the one whose content changed more recently wins. A claim that only the older item supports is flagged Outdated. A claim that matches the newer item isn't flagged just because the older one disagrees. If the items' dates are within an hour of each other, or one has no date, Grounding doesn't choose between them.
- Grounded claims cite their source. Select one to open it, including a project brief. Notes are claims another collection disagrees with, not conflicts.
- Couldn't be confirmed means the check was incomplete, and the panel says why. "Still indexing" means your other collections are still being prepared: re-check when it's done. "Could not be indexed" means a source failed. Re-checking alone doesn't clear it: edit or split the material, save it, then re-check (see Reference materials that need attention under Troubleshooting).
- Outdated means the document or its sources changed, access to a source changed, or the last check used fewer sources than you can see. If you created the document, one banner at the top of the results says which, with its own Re-check button.
- Extracted claims lists every claim pulled from the document.
- Studio Credits: any estimate the panel shows is a range, not a promise. If a check costs more than you have, it finishes and your balance stops at 0. If your team's reference library hasn't been prepared yet, the estimate also says Initial reference-library preparation is free. The check itself still uses Studio Credits, and later changes to your reference library may use them too.
- A finding you dismissed stays dismissed when you re-check, as long as the claim and the source it was checked against haven't changed. If either changes, the finding comes back for review.
- Between your document and your library, Grounding shows a conflict but doesn't decide which side is right.
Permissions
| Role | What they can do |
|---|---|
| Admin, Creator | Run checks |
| Collaborator | Can't use grounding |
A Collaborator who opens the panel sees Grounding isn’t available for your role. Only the person who created the document sees the cards and their actions. Everyone else sees the meter, the Extracted claims list and Details are visible to the document's creator. If a document uses private sources, only you can see its check, and sharing the document doesn't share those sources. When you check one of your own Private documents, the check also reads your Only me context items. Results that others can see never use or cite anyone's Only me items.
Troubleshooting
The check won't start and says someone has the document open for editing. Another person holds the edit lock. Re-check once they're done.
It says to wait for the assistant to finish. The AI Assistant is still changing the document. Wait for it, then re-check.
The grounding check didn't finish. Select Try again. If you edited during the check, the retry uses your latest saved content.
The panel lists Reference materials that need attention. Marcora couldn't prepare those materials for the check. Each one shows a reason:
- Too large to prepare as one context item: split it into smaller context items.
- Preparation stopped after 3 failed attempts: correct its text.
Select Edit next to the material (or select its name to view it), make the change and save, then select Re-check. Re-checking without changing the material won't retry it. Only the person who created the document sees this list.
Some items couldn't be read within this check's limit. The check covered only part of your reference library, and the panel lists what it skipped under Not read in this check.
The panel says it can't flag conflicts. Add your company overview in Context Hub > Brand > Company Overview (or select Open Brand Foundation), then select Re-check. If it says some context items aren't confirmed as yours yet, re-check later.
The panel shows an upgrade or credits message instead of a check. Your plan or balance doesn't cover grounding. See Pricing.
Re-check is unavailable because your team doesn't have enough credits. You can still read the last check's results. The panel shows how many credits the check may need and how many you have. An admin can select Add credits or See plans (on a trial, See plans), then select Re-check. On older plans the panel says Grounding needs at least 50 credits. and shows View credits.
Related
- Content: where your documents live
- Context Hub: your reference library, where added claims go
- AI Assistant: applies Fix in this document
- Projects: the project brief a check can cite
- The
check_content_grounding,get_grounding_resultandapply_finding_fixMCP tools do the same jobs from Claude or ChatGPT.