The truss layout says the floor carries no roof load, while its girders carry walls that hold up the roof.
The supplier’s floor truss layout and truss design drawings for a two-story house were checked against the engineer’s structural drawings and the architectural set, and the loads, beams and connections the trusses depend on are missing from the structural design.
House floor truss submittal load path
A floor truss layout and engineered wood truss design drawings for a two-story single-family house, checked against the structural design drawings and the architectural permit drawings supplied as references, and the residential code sections the review cited.
What the review compared
This was a later review of the house in the two-story house roof load and shear wall study, with the supplier’s floor truss layout and truss design drawings as the documents checked and the structural and architectural drawings as references. Its instructions asked for conflicts across plans, schedules, sections and details, load transfer and connection information, and typical details checked against actual conditions. Code checking was enabled.
Where the truss package and the structure part ways
The trusses were designed, but the structure around them was not. The layout calls for beams the engineer never sized, girders print reactions of several tons onto bearings with no post, and every hanger and one uplift tie are left to others. The girders were also run with a lighter floor load than the trusses they carry, under a note that says the floor carries no roof load while upper walls bear on it. Above the floor, a shear wall stands over the open kitchen and the two-story foyer wall is framed as a typical wall.
What to verify next
The engineer of record should give the truss designer the line loads of each upper bearing wall, size the layout’s beams and the posts under heavy girder bearings, and add a hanger and tie schedule; the truss designer should then rerun the affected girders. Examples that cite a requirement follow the residential code sections the review cited; every example is a question for the engineer, the truss designer and the building department.
12 selected examples from the review
Twelve distinct findings, summarized for professional verification.
Girders carry walls the note ignores
The layout says the floor carries no roof load; two girders carry walls under rafters.
Why it matters: The girders are too light, or the note is wrong.
What to check: State the wall loads and confirm the girders.
StructuralTwo layout beams the engineer never sized
The truss layout calls for two long multi-ply beams the structural plan omits.
Why it matters: Beams carrying a girder and five trusses are undesigned.
What to check: Size both beams, with posts and footings.
StructuralHeavy girder reactions land on nothing
Girder reactions of several tons bear where the structural plan sizes no post or stud pack.
Why it matters: The supports cannot be built or inspected to a design.
What to check: Size a post and footing under each.
StructuralHangers left to others
Truss drawings require hangers and an uplift tie by others; no sheet specifies them.
Why it matters: The framer would choose hangers for heavy hung girder ends.
What to check: Add a hanger and tie schedule with model, fasteners and capacity.
StructuralUpper shear wall over the kitchen
A second-floor shear wall stands over the open kitchen, with nothing below.
Why it matters: Its shear and overturning have no path to the foundation.
What to check: Move the wall or design the transfer.
Structural · ArchitecturalTwo-story foyer wall framed as typical
A foyer wall open to above uses the typical stud size and spacing.
Why it matters: Its height exceeds what the cited table allows without engineering.
What to check: Design the tall wall and check similar walls.
StructuralHold-downs at one end only
Three interior shear walls have a hold-down only at the end meeting an exterior wall.
Why it matters: Wind from the other side lifts an unrestrained end.
What to check: Call hold-downs at both ends and specify their anchors.
StructuralGirders designed for a lighter floor
Two girders use a lower floor dead load than the trusses hanging from them.
Why it matters: Their printed deflections and forces are understated.
What to check: Rerun the girders with the floor dead load used elsewhere.
StructuralPatio ceiling beam has no size
A long beam over the open patio carries ceiling joists but has no size label.
Why it matters: It cannot be priced, ordered or framed.
What to check: Label its size, grade and end connections.
StructuralGrade beam depth stated two ways
Foundation notes give interior grade beams a shallower depth than the beam details.
Why it matters: An estimator reading the notes would price shallow beams.
What to check: Correct the note or refer depths to the engineer’s details.
Structural · ArchitecturalFill depths about four times the plan
Beam details print fill and slab-step heights about four times the plan values.
Why it matters: Excavation and fill quantities cannot be read reliably.
What to check: Correct the dimensions in the beam details.
StructuralTruss layout names another address
The truss layout title block gives a different street number from the title sheet.
Why it matters: Permit and delivery records may not match the right lot.
What to check: Have the supplier correct the address and reissue.
StructuralReview scope and priorities
The review organized the questions by severity, discipline, and source context so the responsible designers could investigate them.
Structural and Architectural
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.