What a 156-page hotel, restaurant, and waterfront review surfaced
Groundbook reviewed one mixed-use hospitality drawing set against four uploaded 2025 California code volumes—and returned 132 potential issues spanning life safety, accessibility, structure, commercial-kitchen systems, energy, and drawing-set quality.
Project details have been anonymized. Findings are potential issues for professional verification, not final code or engineering conclusions.
Counts describe this anonymized review only. They do not establish the source project's compliance, safety, or final issue disposition.
One set, several occupancies, and a shoreline edge
Hotels, restaurants, retail spaces, waterfront structures, and public access routes place very different requirements next to one another. The coordination burden lives at those boundaries.
Many disciplines shared the same conditions
Architectural, civil, structural, mechanical, plumbing, electrical, energy, dock, and elevator information all appeared in the 156-page drawing package.
Hospitality and commercial kitchens raise the stakes
Sleeping-unit separations, accessible guest rooms, egress, alarms, cooking exhaust, make-up air, and fire suppression each depend on information repeated across plans, schedules, details, and notes.
Project requirements extended beyond the drawings
The review connected drawing evidence to uploaded volumes of the 2025 California Building, Mechanical, and Energy Codes instead of treating code checks as a separate page-by-page exercise.
Six patterns across the 132 potential findings
These generalized examples show the kinds of questions Groundbook returned to the project team with source context for verification.
Hotel entry doors were scheduled without the required rating
Sleeping-unit doors opening into an interior lobby were marked unrated even though the surrounding separation called for protected openings.
If unresolved: Door procurement and the fire-partition strategy could proceed from incompatible requirements.
Life safety · architecturalGuard and handrail loads fell below the adopted requirement
Architectural notes specified a lower design load, while structural details directed the requirement back to those notes without stating the governing load.
If unresolved: Public waterfront and hotel-deck railings could be detailed or fabricated from incomplete design criteria.
Architecture ↔ structureA grease exhaust fan was detailed over combustible support
The commercial-kitchen exhaust fan was shown on a wood platform without a documented clearance or a noncombustible support condition.
If unresolved: The support assembly could require redesign after equipment coordination or code review.
Kitchen exhaust · mechanicalKitchen exhaust and outside-air intake were too close on the roof plan
The drawing showed a separation appropriate to one exhaust rule, but the outside-air intake had a different requirement for Class 4 kitchen exhaust.
If unresolved: Rooftop equipment could need relocation or a documented alternative calculation.
Mechanical · code coordinationDeferred fire-protection work was not fully listed
Project notes and approval conditions required sprinkler, alarm, and waterfront standpipe systems, but the set's deferred-submittal list named only a different system.
If unresolved: Required design packages and approval responsibilities could remain unclear during permitting.
Architecture · fire protectionEnergy forms, schedules, notes, and indexes drifted apart
The review found differences in insulation, door and window products, space classifications, code editions, detail references, sheet indexes, and unfilled specification placeholders.
If unresolved: Reviewers, bidders, and trades could rely on different versions of the project's requirements.
Energy · multidisciplinaryThe important questions crossed pages, disciplines, and codes
The review did not establish that any downstream outcome occurred. It organized the source-backed questions that qualified professionals could investigate first.
Mixed occupancies changed the governing requirements
Hotel rooms, restaurant and bar spaces, retail areas, and public waterfront routes brought different fire, egress, accessibility, ventilation, and energy rules into the same set.
The same fact appeared in several document forms
Requirements repeated across plans, schedules, details, notes, specifications, energy forms, and approval conditions. Groundbook checked whether those versions agreed.
Severity separated design questions from cleanup
Four high-priority findings could be reviewed before 69 medium-priority coordination questions and 59 lower-priority documentation items.
Every finding came back with its source context
Reviewers could move from the issue summary to the relevant drawing and uploaded code language instead of reconstructing the comparison from scratch.
Potential impacts are based on the issue type, not on verified outcomes from this anonymized project.
Read the drawing set and the code sources as one connected system
The review followed information across documents, grouped related symptoms into findings, and returned the evidence for a qualified reviewer to decide.
- 1Map the complete set
Classify sheets, disciplines, details, schedules, notes, approval conditions, and code sources.
- 2Connect repeated requirements
Follow hotel, restaurant, retail, waterfront, structural, and building-system information wherever it reappears.
- 3Check drawings against sources
Compare the project evidence with the uploaded 2025 California code volumes.
- 4Return a prioritized queue
Group potential issues by root cause, severity, discipline, and supporting context.
132 questions to verify—not 132 automatic verdicts
The output expands review coverage while preserving professional judgment and accountability.
What this result means
- Groundbook surfaced 132 potential issues worth professional review.
- Four higher-priority findings can be investigated before document cleanup.
- The review covered both full-set coordination and uploaded code sources.
- Each finding included the project context used to produce it.
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.
- Unverified savings, prevented RFIs, or project outcomes can be attributed to the review.
The review is specific. The public story is not identifying
This case study uses a generalized project description, aggregate results, and summarized finding patterns. It excludes source-document screenshots and details that could identify the project, its location, or its participants.
- No address or location
- No project name
- No people or firm names
- No permit or project IDs
- No filenames
- No sheet numbers
- No revision dates
- No exact design values
About this hotel and restaurant plan review
What did Groundbook AI review in this case study?
A 156-page architectural, civil, structural, mechanical, plumbing, electrical, energy, dock, and elevator drawing set for a mixed-use waterfront hospitality project. The set was checked against four uploaded 2025 California code volumes.
How many potential issues did the review surface?
132 potential issues for professional verification: 4 high severity, 69 medium severity, and 59 low severity.
What kinds of potential issues did the review surface?
Fire and life-safety documentation gaps, commercial-kitchen exhaust questions, accessibility and egress conflicts, structural design criteria omissions, energy-model coordination issues, and drawing-set QA/QC problems.
Does Groundbook AI replace professional plan review?
No. Groundbook supports qualified professionals with a systematic first pass and traceable source context. Responsible architects, engineers, contractors, reviewers, and authorities verify every finding and retain responsibility for decisions.
How was project privacy protected?
The public case study omits the address, project name, firms, people, identifiers, filenames, sheet numbers, dates, screenshots, and exact design values. It uses a generalized project description, aggregate results, and summarized finding patterns.
Continue from the 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.