The design criteria, material specs, and special inspection requirements that govern the whole structural set, and how to catch them when they drift out of sync with the plans.
The structural general notes sheet is usually the first S-series sheet in the set, and it's also the one most people skip straight past to get to the framing plan. That's a mistake. The general notes carry the design criteria the entire structural design was built on: the loads, the material strengths, the code edition, the special inspections required. When a plan reviewer or a field team finds a conflict between what the notes say and what the plans show, it's usually because nobody checked the notes against the current drawings after the design changed.
This guide breaks down what belongs on a structural general notes sheet, why it drifts out of sync with the rest of the set, and how to check it before the sheet goes out the door.
A structural general notes sheet states the design criteria (loads, wind and seismic parameters, soil bearing), material specifications (concrete strength, rebar and steel grades), the adopted code edition, required special inspections, and deferred submittals that govern the entire structural set. Reading it correctly means checking every value against the current plans and calculations, not just reading it as boilerplate carried over from the last project.
Six categories of information make up most general notes sheets:
Firm-specific formats vary, but a note category missing entirely, rather than just formatted differently, is worth flagging on any set you're reviewing.
General notes get written once, usually early, and rarely get revisited line by line every time the framing plan or foundation design changes. A soil bearing value entered at schematic design based on a preliminary geotechnical report can go stale once the final geotechnical report comes back with a different number. A seismic design category can shift after a code update mid-project and never get updated in the notes even though the calculations were rerun. None of these are dramatic errors on their own, but each one is exactly the kind of internal inconsistency a plan reviewer is trained to catch, and each one generates a correction letter that pushes the permit timeline back a review cycle.
Checking each of these by hand across a full set, especially on a resubmission where only part of the design changed, is exactly the kind of cross-reference work that's easy to skip under deadline pressure and easy for automated cross-referencing to catch consistently instead.
General notes apply to the whole sheet or the whole set and are listed once, usually on the first structural sheet. Keynotes are numbered callouts pointing at one specific location on one specific detail, referencing a legend for the full text. Reviewers sometimes look for a design criterion in the keynote legend when it actually lives in the general notes, or vice versa. For the full distinction between the two and where each belongs, see keynotes vs. general notes.
General notes are one piece of a larger structural set that includes framing plans, foundation plans, sections, and connection details. For the full picture of how to read the rest of that set, see how to review construction drawings, which covers the discipline-by-discipline review process this checklist fits into. For how AI review specifically handles the structural discipline, including cross-checking general notes against plans automatically, see AI for structural engineering.
Practitioner insight
“The general notes sheet is the one page nobody re-reads after the first draft. I've seen a soil bearing value sit in the notes for six months after the geotech report came back different, because the plans got all the revision attention and the notes sheet didn't get touched. It's boring to review, which is exactly why it needs a checklist instead of a skim.”
Source: Conversations with structural engineers and QA/QC leads at structural engineering firms about recurring plan check correction patterns, synthesized from Helonic's structural-discipline interviews, Q2 2026.
Manas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.
How this page was researched: Checklist categories reviewed against common structural plan check correction patterns and IBC Chapter 17 special inspection requirements, focused on the general notes to plan-and-calculation consistency gaps that recur most often on resubmissions.
Last reviewed by Manas Gandhi · July 2026
Related references for structural drawing review.
A full breakdown of framing plans, foundation plans, and sections.
How the two note types differ and where each is used on a sheet.
The abbreviation reference general notes legends are built from.
Where structural RFIs come from and how earlier review cuts the count.