The sloped glass roof over the dining room is tempered glass, with no screen or laminated lite beneath it.
The permit drawings for enclosing a restaurant patio with a sloped glass roof and curtain walls were checked before submission, and the overhead glazing, the structural design basis, the code data and the fire protection scope are not ready for plan review.
Restaurant patio glass enclosure
Architectural permit drawings for a patio enclosure at an existing restaurant: code and area data, demolition plans, plans, elevations and sections of the glass roof and curtain walls, a glazing schedule and details, read against one another and the building, fire and energy code sections the review cited.
What the review compared
The review read the architectural permit drawings for enclosing an existing restaurant patio with aluminum-framed curtain walls and a sloped glass roof: code and area data, demolition plans, the enclosure plan, elevations, sections, a glazing schedule and details. Its instructions asked for missing or inconsistent information, drawings checked against specifications, missing compliance before permit and conflicts across disciplines. Code checking was enabled.
Where the set is not ready for plan review
The glass roof is the center of the project and the least resolved part of it. It is tempered glass over a dining area with nothing below it, it has no roof, snow or wind loads, and the elevations and section disagree on its height. Around it, the code sheet prints an altered area larger than the building, the title blocks certify to an outdated code edition and are unsigned, and the new room has no occupancy, occupant load, sprinkler or alarm scope, door schedule or energy compliance path. The glazing schedule and its own basis of design describe different glass.
What to verify next
The architect should settle the overhead glazing makeup and the roof geometry, have the structural design criteria added or the glass roof listed as a delegated design, and complete the code data for the enclosed room before submission. Examples that cite a requirement follow the building, fire and energy code sections the review cited; every example is a question for the architect, the engineer and the building department.
12 selected examples from the review
Twelve distinct findings, summarized for professional verification.
Tempered glass overhead with nothing below
The sloped roof glass is tempered, with no screen or laminated inner lite shown.
Why it matters: A broken lite could fall onto diners below.
What to check: Use a laminated inner lite or add screens.
ArchitecturalNo design loads for roof or footing
No sheet gives roof, snow or wind loads, soil bearing or footing reinforcing.
Why it matters: The roof and footing cannot be checked to a known load.
What to check: Add the design criteria and reinforcing.
StructuralAltered area larger than the building
The code sheet’s altered area is over three times the building area it lists.
Why it matters: As printed, the whole restaurant falls under new-building rules.
What to check: Recalculate both areas from the drawings.
ArchitecturalSprinkler and alarm work unassigned
The sprinklered building gains a roofed room; no sprinkler, alarm or deferred submittal is listed.
Why it matters: That work can drop out of bids and the permit.
What to check: Add it to the scope or defer it.
Fire Protection · ElectricalNo occupant load for the new room
The enclosure and the dining room exiting through it have no occupancy or occupant load.
Why it matters: Exits, hardware and egress lighting cannot be checked.
What to check: Add a code plan with loads and exits.
Architectural · ElectricalCertified to an outdated code, unsigned
Every title block certifies to a code edition no longer enforced; signature lines are blank.
Why it matters: The set cannot be accepted for permit.
What to check: Cite the adopted codes, then seal and sign.
ArchitecturalRoof heights differ by view
Elevations and a section through the same end give different wall and roof heights.
Why it matters: Roof slope and attachment height are unsettled.
What to check: Fix both heights and align every view.
ArchitecturalClear glass scheduled, tinted unit specified
The schedule calls clear tempered glass; the basis of design is a tinted low-e unit.
Why it matters: Bidders may price plain glass.
What to check: Name each type’s full insulating unit.
ArchitecturalEnergy compliance path missing
The heated glass room has no stated compliance path or framed-assembly U-factor.
Why it matters: The energy review cannot be completed.
What to check: State the path and assembly values.
ArchitecturalNew doors have no schedule
The legend’s door schedule sheet number is blank; both new doors lack size and hardware.
Why it matters: Exit doors cannot be checked or ordered.
What to check: Issue a schedule for both doors.
ArchitecturalIndex lists sheets never issued
The sheet index lists many more sheets than the set, including trades with no work.
Why it matters: Reviewers cannot tell what scope exists.
What to check: Match the index to the issued sheets.
ArchitecturalRafter spacing label wider than drawn
A detail prints a wider rafter spacing than the roof plan and the detail draw.
Why it matters: Rafters laid out to the label would overrun the roof.
What to check: Correct the label and dimension the plan.
ArchitecturalReview scope and priorities
The review organized the questions by severity, discipline, and source context so the responsible designers could investigate them.
Architectural, Structural, Fire Protection, and Electrical
Check the findings with the responsible discipline designers.
High, Medium, and Low priorities
Selected examples retain their assigned priority.
Drawing coordination and code checking
Code checking was enabled alongside the review of plans, schedules, details, and notes.
Findings connected to their source context
Groundbook links each finding to the sheets it came from so the responsible designer can confirm or dismiss it.
Potential impacts describe the issue type. They are not verified outcomes from this project.
Follow the information across the complete set
Groundbook reads the documents you upload and reports where they disagree, where a reference does not resolve, and where a required value is absent.
See how a full set is reviewed or how interfaces are coordinated.
- 1Map the complete set
Identify sheets, disciplines, details, schedules, and notes.
- 2Connect repeated information
Follow tags, references, and requirements wherever they reappear.
- 3Check drawings and code references
Read the detected code references alongside the drawing evidence.
- 4Return findings for verification
Organize potential issues by severity, discipline, and supporting context.
Questions for professional verification
The output supports the responsible designers as they review the source documents and decide what needs to change.
What this result means
- Groundbook surfaced potential issues for professional review.
- Severity helps prioritize which questions to investigate.
- The findings describe coordination, completeness, and code-reference questions in the uploaded set.
- Each finding includes source context for verification.
What it does not mean
- Every potential finding is a confirmed error or violation.
- The project was unsafe, unbuildable, or ultimately noncompliant.
- Groundbook replaced the responsible professionals or authority.
- A correction was made, or any cost or delay was avoided.
About this review
Is this a real review?
Based on a Groundbook review completed in November 2026. Findings are summarized.
Are these findings confirmed defects?
No. Each one is a potential issue for the responsible designer to verify against the source documents. Groundbook reports what the documents say and where they disagree. It does not make design decisions, certify compliance, or replace the authority having jurisdiction.
How long did the review take?
Turnaround runs from 20 minutes to 24 hours depending on project size.
Which codes were checked?
Code checking was enabled for this review. Groundbook detects the codes a set references, reads the codes and amendments that governments publish online, and uses licensed codes only where a license allows it.
Can I see a full report?
Yes. The sample plan review report shows all 79 findings from one review of a drawing set and its specifications, with the cited excerpts.
Continue from the case study
Explore the source-linked examples in the sample plan review report, or browse every published case study.
Give the next drawing set a connected first pass
Upload the project, choose the checks that matter, and receive structured potential findings with source context.