Project-Level Reviews

Last updated: September 23, 2026

Background

Project-Level Reviews bring checklist-style reviews up from the single-document level to the whole project. Instead of reviewing one document at a time and manually reconciling the results, you apply a review template to a project, and each review item is answered across all relevant documents — surfacing how each document addresses the item and flagging where documents conflict, corroborate, or leave gaps. Rather than opening a document and reviewing it, you work through a set of issues, and the system surfaces the relevant document(s) for each one — the document follows the review, not the other way around. This is especially useful for reconciling risk across an entire bid package, prime contract and subcontract set, or preconstruction document set, without having to run the same review repeatedly and cross-reference results by hand.

Things to Consider

  • Point-in-time, not a living review. Adding a new document to the project does not automatically re-run the review or flag affected items — you'll need to re-run the review manually to include it.

  • Reviews are user-initiated only. There's no background processing or auto-refresh of results.

  • Single project only — there's no cross-project analysis or aggregation.

  • Document limits exist. Analyzing many documents at once is computationally heavy, so very large document sets may exceed what a single review can handle. If you are encountering issues, reach out to your Customer Success Manager to modify your review to focus the topics or the documents to review.

  • Don't "staple" documents together.  Upload documents individually and let the review do the cross-document work. The one exception is versions of the same document — upload those as versions, not as separate new documents.

  • Mobile is triage-scoped. You can view results, answer items, comment, and action tasks on mobile, but the side-by-side document viewer is desktop/tablet only.

  • No real-time collaborative editing. Collaboration happens asynchronously through comments, @mentions, and tasks.

  • Downloads are simple for now. The download button produces a basic PDF with no options.

  • No self-service template authoring. Project-level review templates are created by the Document Crunch team. Org and team admins can view and provision copies of available templates, but can't build new ones from scratch.

  • Users with Editor and Admin permissions can run a project-level review

Steps

Apply a review to a project

  1. Open the project and go to the Review tab.

  2. Click the template dropdown and choose + Apply a new review, then select the project-level review template you want to use.

  3. The review runs against all of the project's documents.

Work through review items

  1. Browse review sections in the left panel (e.g., Contract Documents, Owner, Performance, Warranty, Subcontractors). The Needs Attention and Pinned views collect items that need your eyes.

  2. Each item shows the review question, an answer selector (Yes / No / Needs Review), and an AI Summary with citations to every source document, down to the page and section.

  3. Use the copy, helpful/not helpful, comments, and tasks options directly from the item to take action without leaving the review.

Tip: Answers, comments, and tasks are visible to everyone with access to the project, and they persist across re-runs — so the review becomes a running record of your team's decisions, not just a one-time report.

Compare sources side by side

  1. Click any review item (or citation) to open the document drawer from the right.

  2. Use the L / R buttons next to each source to load documents into the left or right pane.

  3. Scroll and zoom each document independently — highlighted passages show the language behind the summary.

  4. Close the drawer to return to the summary view.

Pin, task, and download

  1. Pin any item to add it to the Pinned list, which also shows tasks associated with pinned items.

  2. Assign tasks from the review itself or from the pinned list.

  3. Click Download to export the review as a PDF.

FAQ

  • How is a project-level review different from running the same checklist on each document?

    • One review runs across all of a project's documents at once and reconciles the results — surfacing how each document treats an item and flagging conflicts or gaps between them. This is analysis a per-document review can't do on its own.

  • Should I still combine my documents into one PDF before uploading?

    • No. Upload documents individually and let the review handle the cross-document synthesis. Versions of the same document are the exception — upload those as versions.

  • Can my teammates see my answers?

    • Yes. Answers, comments, and tasks are visible to everyone with access to the project.

  • If I add a new document to the project, does the review update automatically?

    • Not yet. Reviews are point-in-time — re-run the review to include a newly added document.

  • Can I see the actual contract language behind a summary?

    • Yes. Every summary cites its sources by document, page, and section. Click a citation to open the document drawer and compare sources side by side with the relevant language highlighted.

  • Can I build my own project-level review template?

    • Not yet. Templates are authored by Document Crunch. Org admins can copy available templates, configure them, and publish them to their teams — reach out to your Customer Success Manager to discuss reviews for your specific workflows.

  • Where do I find project-level reviews in the app?

    • In the Review tab in the project.

  • Does this work on my phone?

    • For triage, yes — you can view results, answer questions, comment, and action tasks. The side-by-side document viewer is desktop/tablet only.

  • Who can run a project-level review?

    • Users with Admin or Editors level permissions.