Two scopes, written by different people, for different purposes
A scope of loss looks backwards. It asks what existed, what the event did to it, and what it would take to return the property to the condition it was in. That is a coherent question and it has a defensible answer.
A scope of work looks forward, and it asks something else entirely: what will the building department permit us to construct, on this building, under the code that is in force now. Most of the time the two land close enough that nobody notices the difference. When they separate, the separation was decided by a code section long before anybody wrote an estimate.
Owners meet that gap in a plan review comment, weeks after the number everyone has been working from was set, and it reads as a contractor moving the goalposts. The code put those goalposts where they are. The estimate was written before anybody checked.
The code classifies the work before it regulates it
Florida governs work on existing buildings through its own volume, the Florida Building Code, Existing Building, currently the 8th Edition (2023). The volume is organised around a distinction that decides most of these arguments: repairs are one thing, alterations are another, and the code sorts the work into a category before it says anything about what the work has to satisfy.
Repairs sit in Chapter 4, and the baseline there is more generous than owners expect. Where damage is less than substantial structural damage, Section 406.2.1 permits the damaged elements to be restored to their predamage condition. Putting back what was there is a real, code-sanctioned answer, which is exactly why the exceptions feel arbitrary when one lands. Section 406.1 sits above all of it and does not care about extent at all: dangerous conditions get eliminated regardless of how much or how little was damaged.
Alterations are classified in Chapter 6, and the classification turns on a phrase worth memorising. A Level 1 alteration is the removal and replacement, or the covering, of existing materials, elements, equipment or fixtures with new ones that serve the same purpose. Same purpose is the hinge. Add or eliminate a door or a window, reconfigure or extend a system, install additional equipment, and the work is a Level 2 alteration where the work area is at or below 50 percent of the building area; above that, it is Level 3. Each level carries the chapters below it, so classification is cumulative rather than a menu.
So the question that sets the scope is which category the work falls into, and what that category drags in behind it. Severity is one input to that, and on many jobs it is not the deciding one.
Why does a claim-funded repair cost more than putting back exactly what was there?
Because the permit is issued against the code in force now, and the code classifies the work before it regulates it. Restoring damaged elements to predamage condition is permitted for an ordinary repair. Once the replacement cannot serve the same purpose, or the extent crosses a threshold, current provisions attach, and everything they add is scope that must be priced and approved.
The delta is produced upstream of any estimate. It is not a contractor’s judgement about what the building deserves, and no amount of negotiating with the estimate changes it, because the document it comes from is the permit rather than the proposal.
It is also uneven across one building. A bedroom put back exactly as it was may attract nothing, while the same event’s damage to an envelope assembly or a distribution system pulls current requirements onto work that looks, to the owner, like the smaller half of the job.
For a lender, a board or a partner, the framing that survives scrutiny is that the code delta is a condition of the permit. Treated that way it is auditable. Treated as an overrun it invites a question nobody can answer with a receipt.
Four triggers, and only one of them is about how bad the damage was
The code delta shows up through a handful of distinct mechanisms, and they behave differently enough that it is worth knowing which one is operating before anyone argues about the number.
The first is product availability. An assembly is permitted here on the strength of a current approval, and in the High-Velocity Hurricane Zone that documentation is the whole basis on which an opening or a roof assembly is allowed to exist. A window, a shutter, an anchor schedule or a roofing system that was legal on the day it went in may have no approved equivalent left in the catalogue. There is nothing to put back in kind, so the replacement is a current-code assembly by default, and it frequently brings substrate, fastening or structural attachment work with it. Product approval in the HVHZ is the mechanism doing that work, and it moves scope on repairs far more often than owners anticipate.
The second is a threshold measured by area. Roofing is the familiar example: Section 706.1.1 holds that not more than 25 percent of the total roof area or roof section of an existing building may be repaired, replaced or recovered in any 12-month period unless the entire roofing system or section conforms to current code. Section 553.844(5), Florida Statutes, carves an exception out of that for a system or section already built, repaired or replaced under the 2007 Florida Building Code or a later edition, where only the repaired, replaced or recovered portion must comply. Which side of that line a property falls on is a documentary question about the roof’s own history, which means the permit record either answers it or the owner pays for the assumption.
The third is extent, and it is the only one that turns on severity. Where a building has taken substantial structural damage, Section 406.2.2 sends the lateral force-resisting system to evaluation before anyone repairs it, and Section 406.2.3 requires gravity load-carrying components that sustained it to be rehabilitated to the dead and live load provisions of the Florida Building Code, Building. The second half of that section is what catches owners out: undamaged components receiving load from rehabilitated ones get rehabilitated as well, where the rehabilitation design requires it. Rehabilitation follows the load path rather than the water line. Whether a building is in that condition is a structural engineer’s determination, and it becomes engineering scope the moment somebody asks the question.
The fourth has nothing to do with the damage at all. In a flood hazard area, the substantial improvement and substantial damage tests compare the cost of the work against the market value of the structure, and crossing 50 percent brings the whole building to current flood provisions rather than only the part that was hit. A modest repair on a low-value structure can cross that line while a much larger one on a valuable structure does not, which stops looking strange once you see that the test measures value and not damage. Flood zone designation governs the answer, and the determination is the floodplain administrator’s.
Who determines what, and the line we do not cross
Every one of those triggers is decided by somebody, and the somebody is never the person writing the damage estimate.
The building official determines how the work classifies and what the permit will require, and the vehicle for that determination is plan review. An engineer of record determines whether damage is substantial structural damage. The floodplain administrator makes the substantial improvement call. None of those roles is advisory, and none of them is reachable by discussion with a contractor.
Our own boundary matters here as much as theirs. Unique Construction is a Florida Certified General Contractor, not a public adjuster. We document existing conditions, produce a scope and an estimate for the work we would perform, build it under permit, and coordinate the construction alongside whoever the owner has retained to handle the claim itself. We do not deal with a carrier on an owner’s behalf, interpret a policy, or tell anyone what a claim will or will not pay. That belongs to the owner and their own advisers, and the separation protects them as much as it does us.
That division is what produces a clean document. A construction scope describing only construction, with each code-driven item traceable to the section behind it, works for every reader it reaches afterwards. Fold somebody’s guess about what will get funded into the same pages and no reader can rely on any of it.
How should a code-required upgrade be documented so it survives review by a lender, a board or an auditor?
Keep it on its own line. The code-required work is separated from the damage repair in the estimate and in the schedule of values, each item carrying the code section or plan-review comment that produced it, with the approved plans and any engineer’s letter attached. Scope that grows with no such record behind it reads as an estimating miss.
A merged line item is the version that fails. Months later, when somebody asks which part of a number was the repair and which part the code required, a single blended figure cannot answer, and the person asking is usually the person deciding whether to release money.
The citation is doing more than tidying. It makes the item verifiable by a reader who was never on site and has no reason to take anybody’s word: the section exists, the comment is in the review record, and the two describe the same work.
Where an owner is funding one part of a project from one place and another part from somewhere else, that separation is the only thing that keeps the two apart at reconciliation. Build it at estimate time. Reconstructing it afterwards from memory and photographs is a different and much worse job.
The delta arrives late, and the lateness is the expensive part
The order in which these documents get produced is what turns a paperwork problem into a schedule problem.
Damage gets scoped early, while the loss is fresh and before anyone has applied for anything. The permit application comes later. Plan review comes later still, and that is the first moment the code delta is stated by the only party whose statement counts. By then the scope everyone has been discussing is weeks old, the schedule has been built on it, and on plenty of jobs funds have already moved against it.
A revision cycle follows. Comments go back to whoever prepared the drawings, the designer or the engineer amends the package, somebody resubmits, and every trade sequenced behind the approval waits. On an occupied building, or one carrying a construction loan or a lease commencement date, the delta itself is rarely what hurts. The float it consumes is, and no change order records that.
That cycle compresses if the code review happens at scope time rather than at review time. Classify the work. Test the area thresholds against what the scope actually touches. Confirm an approved product exists for anything in the envelope. Check the flood hazard designation and pull the permit history. Ask the engineer, early and in writing, whether the extent is likely to trigger an evaluation. All of it is desk work, all of it is available before a single wall opens, and each answer converts a future plan-review surprise into a line item somebody has already seen. How review and inspection actually run in Miami-Dade and Broward is the other half of that preparation.
What belongs in the file before anything gets closed up
The record for this kind of work has to satisfy readers who arrive years apart and want different things from it. Assembled once, at the time, it satisfies all of them:
- Existing conditions photographed before any demolition or mitigation, with enough context in frame to establish location rather than only condition
- The permit history for the assembly in question — the roof, the openings, the service — because threshold exceptions are decided on what was previously permitted, not on what the material looks like
- Each code-required item on its own line, naming the section or the review comment that produced it
- Plan review comments and the approved drawings retained together, so the scope change and its cause travel as one document
- Any engineer’s evaluation or letter, kept with the structural line items it authorises rather than filed separately
- Inspection approvals recorded against the permit, closing the loop between what was authorised and what was verified
That file is what makes the property financeable, sellable and insurable later, and it is also the only thing that tells a future buyer’s inspector why the building has newer work in one place and original work beside it. A property whose permit record has holes in it pays for them at the worst possible moment, which is during somebody else’s due diligence.
If a loss has landed on a property you own or manage and the repair scope is still being written, request a proposal and we will walk it, classify the work against the current code, and name what the permit is going to require before the number gets committed to.