> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Check drawing readiness

> Build a drawing-package check against your issue requirements, then review sheets and resolve exceptions.

Check a drawing package against the practice's issue requirements before publishing it. Start with a small set of sheets and define what each should contain. This example uses room sheets with a plan, reflected ceiling plan and four elevations.

## Define the check

Open your own project and supply a drawing checklist or register. Identify the sheets, expected views, naming rules, permitted scales and required sheet information. Include exceptions, such as an elevation that is intentionally omitted.

Make each rule specific. For example, require one room plan, one RCP and four elevations on each selected room sheet, with scales set by your drawing standard. Explain how views should be matched to their room and sheet.

## Build the checking automation

Start a new chat with the intended Revit document connected. For example:

> Create an automation to review the selected sheets against this drawing checklist. Check required sheet information, naming, view scales and whether the expected views are placed. Create or update a Revit QA view with the findings by sheet. Preserve the existing sheet layouts. Separate model-data checks from items that need visual inspection.

Ask for a sheet selector, expected scale and a named Revit QA view. This example checks sheet number and name, the six required views, their scales and their room identity. Open **Run with parameters**, marked **1**, to review the inputs.

![Created room-sheet checking automation with Run with parameters marked 1.](https://mintcdn.com/ideatura/_Z9qqM2bzwrb1rIY/images/qa-qc/drawing-created.svg?fit=max\&auto=format\&n=_Z9qqM2bzwrb1rIY\&q=85\&s=ab43dd6912f01f6ac06b6ca268e9aaaa)

## Test a small scope

Choose **1** the room sheet, **2** its expected scale and **3** the QA-view name, then select **4 Run**. Here, entering **50** checks for 1:50. Compare the findings with your own check; a view must be placed on the intended sheet, not just present in the Project Browser.

![Sheet selector, expected scale 50, QA output name and Run button.](https://mintcdn.com/ideatura/_Z9qqM2bzwrb1rIY/images/qa-qc/drawing-controls.svg?fit=max\&auto=format\&n=_Z9qqM2bzwrb1rIY\&q=85\&s=6d2faab1e19937f299a29e9617a28978)

Check that intentional exceptions are recognised and that unrelated sheets remain outside the report.

## Review the findings

Keep the chat summary brief. The Revit QA view below confirms one plan, one RCP and four elevations at 1:50 for room 108. Sheet information and room identity passed; visual review remains. Running it again updated the same QA view.

![Native Revit QA view confirming six views at 1:50 with visual review still required.](https://mintcdn.com/ideatura/_Z9qqM2bzwrb1rIY/images/qa-qc/drawing-result.svg?fit=max\&auto=format\&n=_Z9qqM2bzwrb1rIY\&q=85\&s=dbf62b7a959263703364c7f19ab993f7)

Open the actual sheets and inspect overlapping annotations, clipped content, view-title spacing and readability at issue scale. Correct names, scales and view counts do not establish that the drawing layout is ready to issue.

## Correct and recheck

Approve a specific correction, such as placing a missing elevation or updating one sheet's information. Preserve the accepted layout and annotations elsewhere. Use [Review and recover](https://docs.ideatura.ai/v2/essentials/how-to-talk-to-ai.md#correct-the-part-that-needs-changing) if an attempt leaves partial work.

Rerun the checklist and visually inspect the affected sheets. Record unresolved items, then save the checked automation for the next drawing review. A clear report supports the architect's issue review; it does not replace that review.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.