Review Overview
Review cross-checks a set of engineering documents against each other. You gather plans, specifications, and reports into a package, run Review Package, and get one list of findings. Each finding quotes the page it came from, so you can verify it and decide what to do.
Review is built for the discrepancies that cause RFIs and change orders: a sheet the index does not list, a callout that points nowhere, a specification section that is cited but missing, two printed statements about the same item that cannot both be true.
Review reports the conditions it detected. An empty findings list is not a certification that a set is clean. A reviewer makes the final call.
Open Review
Open a project workspace and select Review in the header. The panel opens beside chat. Packages belong to the project, so every workspace in the project shows the same packages.
Use + at the top of the panel to create a package, or pick an existing one from the list. The tabs change with the package:
| Tab | What it is for |
|---|---|
| Setup | Choose documents, set their roles, pick Criteria Sets, and start the review |
| Findings | Work through what the review found |
| Backcheck | Appears only when the package continues an earlier one. Checks whether earlier findings were addressed |
| Manage | Counts, charts, a pivot, recent activity, and exports |
Everyone with access to the project can read the panel. Changing a package, a finding, or a deliverable needs write access to the project.
What a Review Looks For
Checks on every run
| What it looks for | What it means in practice |
|---|---|
| Drawing index vs the sheets | An index row with no matching sheet, or a sheet the index does not list. If no drawing index could be read, the review says so rather than inventing one |
| Duplicate sheet numbers | The same sheet number printed on more than one page. That can be a legitimate reissue. Different titles on those pages are treated as more serious |
| Inconsistent titles | One sheet whose pages print materially different titles |
| Missing referenced sheet | A sheet or detail callout whose target is not in the package |
| Malformed detail callout | A detail reference that does not give both a number and a target |
| Undefined keynote | A keynote called out on a sheet that does not define it |
| TBD / TBC | Placeholder language left on a sheet |
| Title-block revision | A revision or date that disagrees across pages of the same sheet |
| Unprocessed sheets | Drawing pages that did not make it into the sheet register |
| Cited section missing from the manual | A section cited in the manual or on a sheet that the manual's contents and headings do not contain |
| Named schedule not on the drawings | The manual says a named schedule is on the drawings, and no sheet prints it |
Detail, sheet, and specification review
The review also reads details, sheets, and specification sections. It raises a finding only when it can quote the text behind it.
| What it looks for | What a finding means |
|---|---|
| Conflicts inside a detail, sheet, or section | Two printed statements about the same item disagree |
| Specification item not on the drawings | A physical item a specification section requires, and the sheet search did not show it |
| Printed dimensions that do not fit | Lengths, elevations, openings, counts, or slopes in one detail or sheet that cannot all be true. Engenerate does the arithmetic |
| Cited standards | A value the package prints disagrees with a standard it cites |
| Missing bid basis | Work whose amount depends on a condition that exists before the contractor starts, with no quantity, limit, allowance, unit price, or owner-decision mechanism |
| Criteria | Items you require to be printed, design rules, and numeric limits, from the Criteria Sets you select |
Design reports and calculations
Files with the Design report or Calculations role get a first-pass read. This is a screen for leads, not an engineering check of the design.
| What it looks for | What a finding means |
|---|---|
| A local concern in a report or calculation | Something in one part of the document that looks wrong on its own, with a quote |
| The same fact with two different numbers | One quantity, such as a flow, elevation, or capacity, stated differently in two places in the report |
| A stated threshold the printed number fails | A limit the report or one of your Criteria Sets states, and a printed value that does not meet it |
| Report versus drawings and specifications | A value or claim in the report that a plan sheet or the specifications print differently, with a quote from each side |
The review compares values after converting units within the same kind of quantity, for example flow, length, velocity, force, stress, unit weight, and area. The report-versus-drawings check needs a report that states the value. A number that appears only on the drawings is not checked, and neither is a number that exists only inside a drawing image with no text to quote.
A first-pass read can miss a concern. A later run does not close these findings by itself, so set Resolution when you are done with one.
Cited standards are looked up in your package's Reference standard files first, then your organization library, then the Engenerate Library, and then the web. A web answer can miss a clause or misread a table. Treat web-sourced findings as leads and check the standard.
Severity and type
Severity (High, Medium, Low, Info) is coordination impact: how likely the item is to cause an RFI, a change order, or rework if nobody acts. It is not a safety ranking.
Type is a separate label:
| Type | Meaning |
|---|---|
| Substantive | Worth sending. A missing sheet or section, a real conflict, an undefined keynote, a placeholder, or anything that would change what a bidder prices or builds |
| Administrative | Paperwork only: a submittal, an approval, a schedule format. A bidder would not build something different |
| Editorial | A section citation that is stale or malformed and that is not a missing section |
What Review Does Not Do
- It does not certify that a set is clean or that a design is correct.
- It does not certify a design. The read of design reports and calculations is a first pass that finds leads. A concern it misses is accepted.
- It does not check pay items, measurement and payment, or compare one addendum with another. The Bid schedule and Addendum roles exist, but those comparisons are not built.
- It does not prove that every requirement in the specifications appears on the drawings.
- It does not cross-check schedule tables cell by cell for sizes, classes, and quantities.
- It sees only keynotes written as "KEYNOTE n". A bare bubble with no label is not read.
- It does not draw boxes on the sheet. A finding points to the page and marks the quoted words.
- It is not a structural, MEP, fire, accessibility, or building-code compliance review.
Next
- Packages — create a package, add documents, run the review, and issue it
- Findings — work the list
- Backcheck — follow findings from one package to the next
- Manage and Reports — dashboard, exports, RFIs, reports, and comment logs