Frequently asked questions

Recensa is a document assurance platform for finished Word and PDF documents. You upload a document, run a Document Check, and get a structured Issue Ledger and a Proof Report so you can decide what to fix before you sign, send, file, submit, or publish.

Document assurance is a final, structured review pass on a finished document—distinct from drafting, live editing, or signing. It organizes findings in an Issue Ledger and Proof Report so you decide what matters before the document goes out.

Yes — that's the core use. Recensa runs a final review on your finished document and flags issues worth checking before you sign, send, file, submit, or publish. It surfaces what to look at; you make the final call.

Proofreading usually targets surface grammar and spelling. Document assurance is document-level: consistency, cross-references, missing pieces, and—with supporting files—whether claims match sources you provide. You get a proof record, not just inline edits.

Recensa can flag inconsistencies, unclear or conflicting language, formatting issues, mismatched details (names, dates, amounts, cross-references), and—with supporting files—claims that do not match the sources you attach.

Yes — including names, dates, defined terms, amounts, and cross-references within the document.

It can flag likely gaps and mismatches—for example, exhibits referenced but not present. You confirm whether each flag is material.

Yes — Recensa performs formatting-aware review of headings, lists, captions, and similar structure. It is not a layout or graphic design tool.

Recensa is not legal advice, not a guarantee of correctness, not live internet fact-checking, and does not replace your final review or professional judgment.

Recensa runs an independent, multi-perspective check over your finished document and merges the findings into one Issue Ledger, so inconsistencies are caught by cross-checking rather than a single AI's opinion. It looks for conflicts like defined-term mismatches, dates and numbers that don't agree across sections, and broken cross-references, and presents each as a reviewable item. You decide what matters—nothing changes without you.

Yes. Apply Fixes produces source-grounded corrected outputs you review before accepting—included with a Source Check (Full) (one credit) and not part of the free Internal Check (Quick). Corrected output is oriented to Word document workflows; your live capabilities and limits are shown in the app.

A Document Check is a single review run over your uploaded document. It produces the Issue Ledger and Proof Report for that run.

The Issue Ledger is one merged list of findings you work through—duplicates collapsed, anything the check was uncertain about flagged for you, and a clear note if a check couldn't finish fully.

A Proof Report is an exportable record of what was reviewed and what was found—useful for sign-off context. It is structured proof, not a chat transcript.

Apply Fixes (source-grounded edits) generates proposed changes and corrected outputs you can inspect before you use them, mainly for Word workflows. You still verify every change — Recensa never silently rewrites your file.

No. Proof-report mode never edits your file. Apply Fixes only proposes changes you review, and Recensa produces new outputs rather than overwriting your original.

Yes — you disposition each issue and decide what to accept, ignore, or handle yourself. Nothing changes without your review.

Yes. Recensa reviews finished Word (DOCX) and PDF documents up to about 40 MB. Corrected-file outputs from Apply Fixes are Word-centric; PDF inputs run the same assurance pipeline with export paths aligned to your review.

Main documents: Word (DOCX) and PDF. Supporting files for source checks: PDF, Word (DOCX, with limited .doc support), text, and Markdown.

Yes, on Recensa Pro. Scanned or image-only PDFs are read using OCR, which extracts the text so the check can review it. OCR works best on clean scans—very poor or low-resolution scans may be declined, and because recognition isn't perfect, you should verify findings against the original. Searchable PDFs and Word files don't need OCR and are always supported.

Recensa produces redline-style and annotated review outputs you can read alongside the Issue Ledger, but it does not generate native Word Track Changes. You apply changes in your own editor after reviewing them.

No — Recensa creates new outputs (reports, corrected copies, exports). Your original upload stays untouched.

Yes — you can export the Proof Report and other reviewed outputs. Download locally or save back to Google Drive, Dropbox, or OneDrive as new files when you connect a provider.

Yes — Recensa can flag inconsistencies, risky or unclear language, and mismatches worth reviewing in a contract. It is not legal advice, and you should rely on qualified counsel for legal judgment.

No. Recensa is document assurance, not legal advice, and it does not replace a lawyer. It helps you spot issues worth reviewing so you can decide what matters and when to consult counsel.

No. Recensa can help you prepare for and tighten a review, but it does not provide legal advice or replace professional judgment.

Yes — as finished documents Recensa can run an assurance pass on NDAs, MSAs, leases, vendor agreements, and similar files. The same non-advice limits apply.

Yes — it can flag undefined or inconsistent terms, mismatched dates or amounts, and referenced-but-absent exhibits for you to confirm.

Yes — for consistency, missing sections, and—with supporting files on Pro—alignment to a referenced SOW or brief you attach.

Finished DOCX or PDF files such as proposals, SOWs, board memos, client packets, vendor or procurement documents, and compliance packets.

Yes — a final pass for inconsistent names or dates and missing attachments before a document goes to a client.

Yes — through the pilot. You give us your requirement list (a compliance matrix, a Section L breakdown, however you keep it) and we trace each item to a file, section, or package entry. Presence is not compliance: we tell you an item is there or that we can't find it; whether it substantively satisfies the requirement is your call.

Yes — deterministically, against the rules you specify. Filename length and characters, PDF format, duplicate attachments, page and title limits. Your NOFO governs; we don't guess at program-specific requirements.

No. Recensa checks the finished package and reports what it finds. It can't fix SAM.gov registration, deadlines, or eligibility — it reads what is on the page and leaves submission to you.

It can flag citation and reference inconsistencies and — with supporting files — whether claims match the cited sources you provide. You verify every flag.

No. It's on nobody's side — that's the point of an independent check, and also its limit. It reports contradictions, broken references, and missing items against your own requirement list; it does not score persuasiveness or predict whether you'll win.

Supporting files are evidence you attach—PDF, Word, text, or Markdown—so the check can compare your main document against them. Source checks are a Pro capability.

Yes, when source checks are enabled on Pro — findings can be grounded in the files you provide.

No. Recensa checks against the supporting files you provide, not the open internet. Without sources it can still flag internal inconsistencies, but it cannot verify external claims.

You still get internal-consistency review for that run. Cross-document grounding is not available without supporting files.

A single AI pass has blind spots. An independent, multi-perspective check surfaces what one pass misses instead of hiding it behind one polished answer.

Independent perspectives cross-check the same document, and disagreements are surfaced for you rather than averaged away.

No. Recensa improves review discipline and visibility, but it does not guarantee correctness and does not replace your final review. You make the final decision.

Yes — like any AI system, Recensa can miss issues or surface ones that don't hold up. That's why findings are presented for your review and the final decision stays with you.

Treat the Issue Ledger as a prioritized checklist. Spot-check critical items against the source document and your own judgment.

Ignore or disposition it — you decide what matters. Nothing changes in your file without your action.

Yes—wherever the review can locate it, each flagged issue in the Issue Ledger is aligned to the specific section of your document it refers to, so you can jump straight to the passage instead of hunting for it. Anchoring is best-effort: most issues are tied to their location, but when a finding spans multiple places or the source can't be pinpointed, Recensa still reports the issue and leaves the final judgment to you. Nothing is hidden because it couldn't be anchored.

See the Data security page for how uploads are processed and which AI providers are used. Only upload what you are permitted to share.

Recensa does not use your documents to train its own models. To run a review, your content is processed by third-party AI providers under their own terms, which we do not control. We also keep a de-identified quality record of how each review performed — its structure and scoring, not the text of your document. See the Data security and Privacy pages for details.

By default, your uploaded files and generated outputs are scheduled for automatic deletion about 7 days after a review completes — and about 24 hours when you run a review in sensitive mode. These windows are configurable for enterprise deployments. Deletion timing can vary slightly with system load, so it is not instant at completion. See the Data security page for full details.

Yes. Every job has a 'Delete this job now' control that immediately and permanently removes your uploaded files and all generated outputs for that job—this can't be undone. Separately, jobs are scheduled for automatic deletion about 7 days after completion (about 24 hours in sensitive mode). Deletion from Recensa doesn't extend to the third-party AI providers that processed your document, whose handling is governed by their own no-training API terms. For deletion questions beyond an individual job, email privacy@recensa.ai.

Anything you are not authorized to share, or that your policies or regulations prohibit. You control what you submit.

An Internal Check (Quick) is free — one every day, no card required. A Source Check (Full) costs one credit; credits come in one-time packs — a Try Pack at $18 for 3 checks ($6 each) and a Starter Pack at $50 for 10 checks ($5 each). There's no subscription. An External Check (Deep) is coming soon. Your live balance and remaining free checks are shown in the app.

Yes — an Internal Check (Quick) is free, one every day, with no card required.

A free Internal Check (Quick) is a fast confidence read, once a day. A Source Check (Full) (one credit) adds source cross-checks, reviewer agreement, a sealed Proof Report, and Apply Fixes. An External Check (Deep) is coming soon; your live limits are shown in the app.

Apply Fixes (source-grounded edits) is included with a Source Check (Full) (one credit); it isn't part of the free Internal Check (Quick).

Supporting files and source checks are part of a Source Check (Full) (one credit).

Yes — main documents are limited to about 40 MB. Supporting files let you attach multiple evidence files per Source Check (Full). Check the app for your current limits.

Team and Enterprise/API options are available by contacting us. Today Recensa runs on individual accounts with pay-per-check credits; reach out and we'll set up team access.

Yes — run a free Internal Check (Quick) on a single document any day, or spend one credit for a Source Check (Full).

There's no subscription, so there's nothing to cancel. You buy credits only when you want them, and unused credits stay in your account.

No — everything for individual use is self-serve. Run a free Internal Check (Quick) or buy a credit pack in the app; no sales call, no subscription. Team and Enterprise/API are the only options handled by contacting us.

Apply Fixes (source-grounded corrected edits) and supporting files for source checks are part of a Source Check (Full) (one credit). The free Internal Check (Quick) is a fast confidence read; your live balance and limits are shown in the app.

Yes—Recensa fits teams that want structured, independent document review without an enterprise sales cycle, sitting between free single-pass tools and enterprise-only platforms. It's self-serve: run free Internal Checks (Quick) or buy pay-per-check credits in the app, with no subscription; Team and Enterprise/API are the only options handled by contacting us. You run independent, multi-perspective Document Checks on finished Word or PDF files and receive an Issue Ledger and Proof Report, with your live limits shown in the app.

ChatGPT is a general chat assistant. Recensa is a structured Document Check with a merged Issue Ledger and proof exports—a proof layer, not a transcript.

A single model gives you one answer. Recensa adds an independent, multi-perspective check, merge logic, and packaged exports on a finished file.

Grammarly polishes writing as you type. Recensa does document-level assurance on a finished file with a proof record.

Adobe helps you edit and manage PDFs. Recensa is an independent proof pass before you rely on or send the file.

DocuSign handles agreement workflow and signing. Recensa is the review and proof checkpoint before you sign or send.

Those are vertical contract-review suites. Recensa is a horizontal document assurance layer for finished DOCX and PDF, with the same non-advice limits.

It can flag language issues, but its value is document-level assurance and proof output—not grammar suggestions alone.

No — it reviews a single finished document for issues and produces a Proof Report, rather than diffing two files side by side.

Upload or import from a connected cloud drive, choose your review focus, run a Document Check, review the Issue Ledger and Proof Report, then apply fixes with a Source Check (Full) or export.

Yes. After you connect a provider, you can import your main and supporting files from Google Drive, Dropbox, or OneDrive and save reviewed copies back as new files. Recensa doesn't manage your whole drive, overwrite originals, or edit Google Docs in place — export Google Docs to PDF or Word first.

Yes — DOCX is a first-class input and the primary target for corrected-file outputs from Apply Fixes.

Yes — run the proof pass before you sign or send. Recensa complements those tools rather than replacing them.