There is no single national standard for naming structural calculations. Each permitting authority sets its own filename rule, and some set none. Your safest approach is to build a clean internal convention, then rename the final PDF to match whatever the local building department publishes. This guide shows what Oregon, Nevada and several California jurisdictions actually require, and how to keep your calc package consistent from first draft to resubmittal.
TL;DR
- Naming rules come from the permitting authority, not from a national code. Check the jurisdiction's electronic plan review page before you export.
- Real examples differ: Roseville wants
Structural_Calcs.pdf, Henderson wants permit number, document type and version, and Oregon suggests a numeric prefix such as040-STRUCTURAL CALCS.PDF. - Keep file names short, unique and free of special characters. Keep a separate calc PDF from the plan set.
- Inside the package, name wall lines, segments and revisions the same way on every page so reviewers can cross-check against the drawings.
- Keep the exact file you submitted. Some cities reject resubmittals whose file name does not match the original.
Table of Contents
- Two kinds of naming: the file and the contents
- What a calc package contains, and why it matters for naming
- What permitting authorities actually require
- A file naming convention you can use as a default
- Naming inside the calculations
- Common naming mistakes
- Our perspective
- Generating consistently named reports with ShearWise Pro
- A pre-upload checklist
- FAQ
- Sources
Two kinds of naming: the file and the contents
"Naming conventions" means two different things in a calc package, and both get reviewed.
File naming is what the reviewer sees in the upload portal: the PDF name, its order in the folder, its version. Jurisdictions regulate this directly.
Internal naming is what the reviewer sees on the pages: wall line labels, segment IDs, hold-down tags, load case names, revision marks. Few agencies regulate this, but a plan checker reading your calcs against the framing plan will notice instantly if a wall is called "W3" on the drawing and "Line C" in the calcs.
This article covers both. File naming is rule-driven. Internal naming is a matter of discipline.
What a calc package contains, and why it matters for naming
Naming is easier when you know what is being named. NCSEA describes a normal calculation package as the design basis, project data, loads, framing locations, analysis-model assumptions, gravity and lateral designs, foundations and miscellaneous structural items. It also recommends that packages be well documented, supported by sketches or loading diagrams, and consistent with the drawings, design criteria and firm standards.
That last point is the whole case for a naming convention. If sections, sketches and member tags follow one pattern, consistency with the drawings is easy to show. If you want a fuller walkthrough of the package itself, see our guide on what a structural calculation package is. For package structure and professional documentation habits more broadly, this piece on end bearing plate design shows how a single detail gets documented.
What permitting authorities actually require
The examples below come straight from agency pages. They show how much the rules vary.
| Jurisdiction | Pattern or guidance | Notes |
|---|---|---|
| Oregon (statewide ePermitting) | Short descriptive names, optional three-digit prefix, for example 040-STRUCTURAL CALCS.PDF | Prefix controls review order; avoid special characters; keep names unique |
| Henderson, Nevada | Permit number, document type, version, separated by underscores, for example Permit#_StrucCalcs_v#.pdf | Resubmittals become v2, v3 and so on |
| Roseville, California | Structural_Calcs.pdf | Underscores replace spaces; no date or project number in the name |
| Mill Valley, California | Street name and number, permit number, document type | Structural Calcs is the document type example |
| Vacaville, California | YYYY.MM.DD_Structural Calcs for a first submittal | Opposite of Roseville on dates |
Oregon
The Oregon Building Codes Division recommends separate files for each document group, short descriptive filenames, and optional three-digit prefixes to control the order of review. Its examples include 040-STRUCTURAL CALCS.PDF and 050-GEOTECH REPORT.PDF. The same page warns against special characters, reusing non-unique filenames, and including MEP plans with the main structural permit files.
For calculations from more than one discipline, Oregon's electronic document requirements call for separate PDFs by discipline, with modifiers such as ENG CALC, ARCH CALC, BEAM CALC or LAT CALC. A lateral package for a two-story wood house could therefore reasonably be a standalone LAT CALC file.
Nevada
Henderson's submittal instructions use a three-part format: the full permit number, a document type and a version, separated by underscores. The example given is BSFD2020012345_Arch_v1.pdf, and later resubmittals are numbered v2, v3 and so on. The same document lists Permit#_StrucCalcs_v#.pdf or Permit#_StructuralCalcs_v#.pdf for structural calculations, depending on permit type, and asks that calcs go in a separate file from the plan set, with plan sets broken down by discipline, sheet numbers and bookmarks.
Las Vegas takes a different approach in its residential submittal guideline, which says engineering and calculations are required when applicable. The excerpt we reviewed does not prescribe a filename pattern, so confirm the current rule with the department before you upload.
California
California has no statewide filename rule, and the cities disagree with each other.
- Roseville's electronic plan review requirements set the sample name Structural_Calcs.pdf, replace spaces with underscores, and say not to include the date or project number. They warn that ignoring the format may trigger resubmittal requests or delay review.
- Mill Valley's permit submittal instructions use street name and number, then permit number, then document type.
- Vacaville's submittal guidance lists a date-first pattern, YYYY.MM.DD_Structural Calcs, for a first submittal.
- Another California city's document submission standards require filenames to match the City's established conventions and use separate files for calculations, specifications, reports and studies.
The lesson is blunt: a name that is correct in Roseville (no date) breaks the rule in Vacaville (date first). Never reuse a filename from one city's job on another's without checking.
Bakersfield
If you work in Bakersfield, start at the City's Development Center, which points to electronic plan review and the construction application checklists. That page does not state a structural-calculation filename convention, so rely on the current electronic plan review submittal guide and checklists for your permit type. We cover the local portal workflow, including its file name length limit, in Bakersfield structural ePlan reviews.
A file naming convention you can use as a default
When the jurisdiction gives you a pattern, use it exactly. When it gives you nothing, use a default that satisfies the common denominators in the rules above: short, descriptive, unique, no special characters, versioned.
- Document type first, in plain words.
Structural_CalcsorLateral_Calcs. Use underscores instead of spaces, which is what several of the agencies above ask for. - Identifier second, only if allowed. Add the permit number or address when the city's pattern includes it. Skip it where, like Roseville, the city says no.
- Version last.
_v1,_v2. Henderson numbers resubmittals this way, and it is a clear habit even where nobody requires it. - Characters. Letters, numbers, underscores and hyphens. Avoid %, +, $, # and anything else that might break an upload system.
- Length. Keep it short. Some portals cap file name length, so shorter is always safer.
Example defaults:
Structural_Calcs_v1.pdffor a generic first submittalLateral_Calcs_v2.pdffor a lateral-only resubmittal040-STRUCTURAL CALCS.PDFwhere Oregon-style ordering prefixes apply
Separate files, separate disciplines
Every source above separates calculations from the plan set. Henderson asks for structural calcs as a separate file. The California standards cited above split calculations, specifications and reports into different files. Oregon wants separate PDFs by discipline when more than one is submitted. Do not append calcs to the drawings, and do not mix energy calcs, soils reports and structural calcs in a single PDF.
File size matters too. Keep each trade PDF within the portal limit; our note on keeping each trade PDF under 50 MB explains how to plan for it.
Naming inside the calculations
The reviewer's job is to trace a number on the drawings back to a calculation. Your internal names make that trace fast or slow.
Wall lines and segments
Pick one label for each wall line and use it everywhere: framing plan, shear wall schedule, calcs, hold-down schedule. For example, label lines by story and direction: 1-A, 1-B for first-floor lines running one way, 1-1, 1-2 for the other, and 2-A and so on for the second floor. Label full-height segments within a line as 1-A.1, 1-A.2. Whatever scheme you choose, write the key on the first page of the lateral section.
Hold-downs and straps
Give each hold-down a tag that ties to its wall segment, such as HD-1A.1, and show the tag in the calc and on the plan. Do the same for transfer straps between stories. If the drawings use a different tag, the calcs should use that tag, because the drawings are the contract documents.
Load cases and criteria
Name the design basis items once, early, and reuse the names: roof dead load, floor dead load, wind, seismic. Cite the code edition and the source of each assumption the same way every time. This is the "design basis" section NCSEA lists first in a normal package.
Sheet and page references
Number the calc pages sequentially and use section prefixes, for example L-1 to L-14 for lateral pages and G-1 onward for gravity. Add PDF bookmarks that mirror those sections. Reviewers in Henderson and Roseville both ask for bookmarks on plan sets, and the same habit helps with calcs.
Revisions
When a review comment forces a change, increment the version in the file name and mark the changed pages with a revision tag and date. Keep a short revision log on page one. If a reviewer asks what changed between v1 and v2, the answer is on the cover page.
Common naming mistakes
- Reusing a name from another jurisdiction. The Roseville and Vacaville examples above contradict each other on dates.
- Special characters and spaces. Oregon warns against special characters, and Roseville asks for underscores in place of spaces.
- Non-unique names. Oregon advises unique filenames. Two files called
Calcs.pdfin one permit are an error waiting to happen. - Renaming on resubmittal. Roseville says resubmittals may be rejected unless the filename exactly matches the original submittal filename. Keep a copy of the file as submitted and check the name and sheet order before you upload.
- Bundling disciplines. Oregon warns against including MEP plans with the main structural permit files.
- Unsigned calcs. Henderson's commercial building checklist requires structural calculations to be digitally stamped and signed by the registered design professional. Our guide to electronically signing structural calculations walks through it.
- Mismatched labels between drawings and calcs. This is the most common reason for a plan check comment that has nothing to do with engineering. See also our list of common California structural drawing omissions.
Our perspective
We build ShearWise Pro for one kind of project: 1-story and 2-story wood-framed buildings. In that work, naming problems rarely come from a lack of care. They come from re-typing. A wall line gets one label in the layout, another in the calc sheet, and a third in the hold-down schedule, because each was entered by hand at a different time.
The fix is to enter the structure once and let every output draw from it. That is why we organize the calculation around wall lines, openings, full-height segments, hold-down forces, transfer straps, roof information and story drift checks, and generate the PDF report from the same data. The labels on page 3 are the labels on page 12.
We also hold a firm view on file names: the jurisdiction's rule wins. A report can be perfect and still bounce from an upload portal over an underscore. Export the report, then name the file to the local pattern, every time.
— Evalin
Generating consistently named reports with ShearWise Pro
ShearWise Pro is an online shear wall calculator and report platform for engineers, architects, designers, drafters, contractors and builders working on 1- and 2-story wood-framed projects. You organize wall lines, openings, segments, hold-downs and straps in one project, then export a clean PDF report for review coordination. You can see how it works in the shear wall software overview, and check the calculations against worked cases in the validation library.
The trial includes three watermarked reports at $0. After that, Professional Monthly is $29 per month and Professional Annual is $250 per year. Start with the three-report trial and run a real project through it.
A pre-upload checklist
- Open the jurisdiction's current electronic plan review page and find the naming rule for calculations.
- Name the file to that pattern. If there is no pattern, use
Structural_Calcs_v1.pdfstyle. - Confirm the calcs are a separate PDF from the plan set and from other disciplines.
- Remove special characters and spaces from the name.
- Check that wall line, segment and hold-down labels match the drawings.
- Add bookmarks that mirror the calc sections.
- Apply the digital stamp and signature where the authority requires it.
- Check the file size against the portal limit.
- Save a copy of the exact file you submit, so a resubmittal can keep the same name or the next version number.
For what reviewers look for once the file is open, see our checklist of shear calc reviewer requirements and our broader guide to permit structural calculations.
FAQ
What are structural calcs?
Structural calcs are the written record of the structural analysis and design for a building. A normal package covers the design basis, loads, framing, lateral and gravity design, and foundations. Permit reviewers use them to check that the drawings match the engineering.
Is there a standard file name for structural calculations?
No. Roseville asks for Structural_Calcs.pdf, Henderson uses permit number, document type and version, and Oregon suggests short descriptive names with an optional numeric prefix. Always follow the local authority's current instructions.
Should I put the date in the file name?
Only if the jurisdiction asks. Vacaville lists a date-first pattern for a first submittal, while Roseville says not to include the date. Use version numbers such as v1 and v2 when the city allows them.
What file name should I use for a Bakersfield submittal?
The City's Development Center page points applicants to electronic plan review and the application checklists but does not state a calc filename convention. Follow the current submittal guide for your permit type, and contact the Development Center if it is unclear.
Do I need to keep the original file after submitting?
Yes. Roseville may reject a resubmittal unless the filename exactly matches the original. Keeping the submitted file lets you check the name and sheet order before you upload revisions.
Sources
- Drawing Packages & Calculations, NCSEA
- File naming standards for electronic plans, Oregon Building Codes Division
- Electronic document requirements, Oregon Building Codes Division
- Henderson, Nevada submittal instructions
- Henderson, Nevada commercial building checklist
- Las Vegas residential submittal guideline
- Roseville electronic plan review document submittal requirements
- Mill Valley permit submittal instructions
- Vacaville submittal guidance
- Document submission standards, lcf.ca.gov
- Bakersfield Development Center