The high-pile storage permit, start to finish
What the submittal contains, which of the three parties owns which part of it, and how to find out what your layout triggers before a customer has accepted the quote. This page carries no thresholds on purpose — the number that governs your project is the one your authority applies, and it is not the same everywhere.
Why this page has no thresholds in it
Search this topic and you will find pages confidently naming a height above which you need a permit. The trouble is that the figure moves: model codes carve out exemptions that some authorities adopt and others do not, plenty of jurisdictions apply a different height to fixed racking than to movable, and a few require a permit for fixed racking at any height at all. A single number, printed without its jurisdiction, is confidently wrong somewhere.
What does generalize is the process: what a package has to contain, who signs which part of it, and what order the questions arrive in. That is what this page covers, and it holds regardless of which authority you are filing with.
Three parties, three jobs, no substitutions
Most confusion about rack permitting comes from collapsing three separate roles into one. They are separate, and each has something the others cannot supply.
The dealer or integrator prepares
You own the layout, the storage arrangement, the commodity information from your customer, and the assembly of the package itself. This is the part that has historically taken the longest and the part software actually shortens: the drawing, the takeoff, the placards and the checklist all come out of the same layout object rather than being assembled by hand.
The engineer of record reviews and stamps
A licensed engineer verifies the structural design and stamps it, and where the authority requires it a fire-protection engineer signs the fire features and the sprinkler design serving the arrangement. Nothing a layout tool produces is a stamped design; the bill of materials is a budgetary estimate for that engineer to verify before anything is ordered. The saving is in what reaches their desk — a complete, dimensioned, internally consistent package instead of a sketch and a spreadsheet — not in skipping the review.
The authority having jurisdiction decides
The AHJ applies the locally adopted code, decides whether a permit is required and on what conditions, and issues it. They may also require special inspections during installation. No checklist, and no vendor, can make this determination on their behalf — which is why the only sound use of a pre-flight is to find the questions early, then take them to the authority.
What the submittal package contains
A permit reviewer is checking that the arrangement you describe is the arrangement that will be built, and that the features protecting it match. In practice that means a package rather than a drawing. This is what FloorCast3D writes out of a finished layout as a single ZIP:
- Main drawing PDF
- The plan sheets a reviewer reads first.
- CAD drawing (DXF)
- The vector drawing, opened by every CAD seat a plan checker or engineer is likely to have.
- CAD drawing (DWG)
- The same drawing in native format, when a converter is available on the machine; the DXF always carries it regardless.
- 3D model and browser viewer
- For anyone who wants to look at the arrangement without a CAD seat.
- Budgetary BOM / quote
- The itemized takeoff behind the number, as a spreadsheet.
- Permit & code pre-flight
- The checklist described on this page, as plain text.
- Rack capacity placards
- Draft placards for the installation — marked not-for-posting whenever the capacity data behind them is incomplete.
- Preliminary request forms
- The prefilled forms that start the conversation with the authority.
- Package manifest
- The contents record, stating for every artifact above whether it was included or omitted.
The last item is the one worth insisting on from any tool. A package that quietly drops an artifact because something failed to generate looks complete on the cover and is not, and the person who discovers the gap is usually the reviewer. A manifest that states, per artifact, whether it was included or omitted makes a degraded package visibly degraded — and the same record carries the geometric check on the layout itself, so a package built from a drawing with overlapping rows says so in writing rather than presenting clean paperwork for an unbuildable arrangement.
Every package is stamped preliminary: layout review and budgeting only, not for construction. If you would like to read a real one before installing anything, download the sample submittal package and hand it to your engineer — it is the same output, generated by the product.
How the pre-flight findings are organized
A flat list of code findings is nearly useless in a sales conversation, because the item that delays a filing and the item that merely tidies a drawing look identical. FloorCast3D sorts findings into six categories and prints them in the order below, worst-consequence first, each carrying the trigger, the reasoning, and the code section where one applies.
[PERMIT]
Whether a permit is expected at all, and which one.
The finding that changes the schedule. It is first because everything downstream assumes you are filing.
[ENGINEERING]
Where a stamped design, calculations or special inspections come into it.
This is what puts a licensed engineer on the critical path, so it wants to surface during the quote, not after acceptance.
[ANCHOR]
Base-plate anchorage expectations for the installation.
Anchorage is decided by the local authority and the slab, and it is routinely the item nobody priced.
[FIRE]
Fire-protection features the storage arrangement implicates.
Almost always the costliest surprise, and the one most likely to be settled by the fire-protection engineer rather than the rack supplier.
[DESIGN]
Layout choices that will read poorly to a plan checker.
Not a blocker, but cheaper to fix on screen than in a correction letter.
[NOTE]
Context, sources, and the checklist admitting what it has not verified.
A checklist that never says "confirm this locally" is a checklist that is guessing.
What a tool can compute, and what it must ask you
This is the honest boundary of any automated code check, and the thing to interrogate a vendor about. Whatever is in the geometry can be computed from the geometry: how tall the rack is, where the top of the highest load lands, the ratio the design gets checked against. The layout knows all of it, so the check is as good as the drawing.
Everything else cannot be computed at all, because it is not in the drawing — what the customer intends to store and how hazardous it is, how much it weighs, how much storage area the arrangement adds up to for the authority’s purposes, and whether the rack is new or used. FloorCast3D surfaces those as checklist reminders for the rep to confirm rather than resolving them silently, and the pre-flight says so in its own closing line. A tool that returns a confident verdict on the second group is answering a question it has no way to see.
The same discipline applies to the reference data behind the check. FloorCast3D bundles jurisdiction data for every US state and the District of Columbia, with metro-level detail where a local authority differs from the state baseline, and it resolves the job site from its ZIP code. When the site resolves to a known permitting authority the sheet names it; when it does not, the sheet says there is none on file and to confirm locally, rather than printing a state default that would read as a resolved answer. Findings drawn from research the tool has not verified are labeled as unverified on the sheet itself.
Run it during the layout, not after the handshake
The expensive version of this process is the familiar one: quote the racking, win the job, and discover during plan review that the arrangement needs a permit nobody scoped, engineering nobody priced, or fire features that change the building. Each of those lands after the number has been agreed, which is the worst moment to raise any of them.
Running the check while the layout is still a drawing changes the conversation from a correction letter into a design choice, because the layout can still move. Sometimes the finding is worth designing around and sometimes it is simply worth pricing honestly — but both are decisions, and you only get to make them while the drawing is still cheap. The rack types guide covers which storage systems the layout could move to, and the rack layout guide covers the geometry that most often has to change.
Frequently asked
What is a high-pile storage permit?
It is the approval a local authority requires before storage above a certain height goes in, granted on the basis of a submittal that shows the storage arrangement, the commodities, the aisles and the fire-protection features serving them. The height and commodity conditions that trigger it are set locally and vary between jurisdictions, which is why the useful question is never "what is the threshold" but "what does my AHJ apply, and what do they want to see".
What goes in a rack permit submittal package?
A dimensioned plan of the storage arrangement, the CAD drawing behind it, an itemized bill of materials, capacity placards for the installation, prefilled preliminary request forms, and a code checklist working through what the layout triggers — plus a manifest stating what the package does and does not contain. FloorCast3D writes all of it as one ZIP from the layout, for a licensed engineer to review and stamp.
Who signs a high-pile storage permit application?
Three parties own different parts and none can do another one’s job. The dealer or integrator prepares the submittal. A licensed engineer of record reviews and stamps the structural design, and where the authority requires it, a fire-protection engineer signs the fire features. The authority having jurisdiction decides the permit. Software prepares the package; it does not stamp it and it does not approve it.
Can rack layout software tell me if I need a permit?
It can tell you what your layout triggers, and it should tell you plainly what it cannot see. Anything geometric — the height of the rack, the top of the loads, the ratio the design is checked against — is computed from the layout. Anything that is not in the drawing, such as the weight and commodity class of what you intend to store, the storage area, and whether the rack is new or used, cannot be computed and is surfaced as a question for a human to confirm. A tool that answers the second group without asking is guessing.
What happens if the pre-flight and my AHJ disagree?
The AHJ is right. A pre-flight is a screening pass against bundled reference data so a trigger surfaces early in a deal, and it says so on its own first line — advisory, not a substitute for AHJ review or a PE stamp. Use it to avoid the expensive surprise, then confirm every finding with the local authority before you rely on it.
When in the deal should the permit check happen?
Before the quote is accepted, not after. Permit exposure, engineering and fire features are the three items most likely to move a number materially, and all three are cheapest to raise while the layout is still a drawing. The reason to run the check during the layout is that it changes what you quote, not just what you file.
Run the pre-flight on your own layout
Draw the zones, set the job site, and read what the layout triggers — sorted worst-first, cited, and honest about what it could not check for you. The whole submittal package comes out as one ZIP. The free trial key is the whole product for 14 days — no card, and everything it generates is marked as a trial copy until you subscribe.