Framing review
A deck framing plan should explain the structure quickly. The goal is not to decorate the drawing; it is to make joist spans, beam spans, supports, openings, stairs, and connection intent obvious.
Framing drawings should show enough structure to review whether the deck layout is reasonable before construction starts.
Joist size, spacing, direction, and unsupported spans
Beam size, beam type, and post spacing
Ledger location or freestanding support strategy
Cantilevers, dropped beams, and bearing points
The unusual parts of a deck are where plan mistakes tend to hide. Give them enough attention in the drawing package.
Clipped corners, bump-outs, bump-ins, and multi-bay transitions
Stair openings, intermediate landings, and stair bearing points
Rail post locations, guard openings, and stair rail transitions
Roof, door, and house-wall conditions that affect framing
Good notes tell the reviewer and crew what still needs field verification. They should not overclaim that the software has approved every structural decision.
Verify local code, permits, inspections, and field conditions
Follow manufacturer installation instructions for connectors and decking
Confirm footing depth and bearing with local requirements
Use licensed engineering review where required by law or site conditions
Checklist
Use this as a working review list. It should support field judgment, not replace local code review, inspection requirements, or professional engineering where required.
Every joist bay has clear dimensions and support conditions.
Beam and post layouts match the current deck geometry.
Cantilevers and unsupported spans have been checked against the selected criteria.
Stair and landing framing is visible enough to build and review.
Connection details are included or referenced.
The plan notes make field verification responsibilities clear.
Questions
Clear dimensions, visible support paths, labeled framing members, readable elevations, and standard details make review faster.
It is better to separate framing and decking views when possible. Each view has a different job and can become cluttered if everything is shown together.
Turn the checklist into a connected deck model with plan views, elevations, takeoffs, and previews.