ScopeQueue Carrier estimate in, justified supplement package out.

Drip Edge in Georgia: The Code Version, and the Exact Date It Changed

· 10 min read

The rejection reads the same way every time. Drip edge was not required when this roof was built. No date, no code edition, no citation. Just the sentence.

Sometimes it is true about the original roof. It is almost never a reason to strike the line from a replacement. But you cannot make that point with a general statement about codes — you need the version Georgia is actually on, and the date it changed. Here it is, with the rules those dates come from named at the bottom.

Is drip edge required by code in Georgia?

Yes. Georgia's residential code requires a drip edge at the eaves and at the rake edges of asphalt shingle roofs. The requirement lives in Section R905.2.8.5.

Two things make Georgia simpler than most states. First, the residential code is one of Georgia's mandatory state minimum standard codes. Under O.C.G.A. § 8-2-25, those codes apply across the state: a city or county may enforce them, but does not have to adopt them first for them to be in force. Whether your county runs an inspection department or not, the same text governs the work. Second, Georgia has not amended this section. In both the 2018 and the 2024 editions as adopted here, R905.2.8.5 carries the model IRC language unchanged — the text an inspector in Whitfield County reads and the text an inspector in Glynn County reads are the same text.

Local governments can go further, but not quietly. The same statute lets a local government impose requirements that are not less stringent than the state code where local climatic, geologic, topographic, or public safety factors justify it, and it requires the proposed amendment to go to the Department of Community Affairs for review before adoption. A stricter local rule is therefore possible, and it is a matter of record. Check for one before assuming the state floor is also the ceiling. Your jurisdiction's climatic and geographic design criteria sit in Section R301.2, near the front of the code, and that is where a county-specific number usually shows up.

The timeline, with the date nobody publishes

Georgia adopts a code edition, then issues amendment packages against that same edition for several years before moving to a new one. The rule that carries the residential code has been retitled again and again as those packages landed — 2014 amendments, then 2014 and 2015, then 2014 and 2015 and 2018 — all against one base edition. That is why "Georgia's code" can be described three different ways in the same year and all three can be defensible. What matters for drip edge is the base edition, because the drip edge section did not exist before the 2012 IRC.

January 1, 2014 is the date. The original version of the state rule that carries the residential code adopted the 2012 IRC with 2014 Georgia amendments; it was filed November 13, 2013, effective January 1, 2014. That is the day drip edge became a code requirement for one- and two-family dwellings in Georgia.

Two details in that list come up in rejections. First, Georgia went from the 2006 edition to the 2012 edition, and the rule record shows no Georgia adoption of the 2009 IRC. If someone tells you the requirement arrived with the 2009 code, that may be fair about the model code somewhere else, but it has no bearing on a Georgia roof: Georgia was still on the 2006 edition through 2013.

Second, the 2006 edition genuinely did not require it. The International Code Council classifies R905.2.8.5 as an addition in the 2012 edition — a new section, not a rewritten one. Its published commentary on that change says a roof drip edge was not previously required for asphalt shingle installation unless the roofing manufacturer's installation instructions called for it. That last clause matters, and it comes back below.

What the section actually requires

This is the text in the edition now in force. Read it closely, because the eave and the rake are not the same operation:

That last line separates a real drip edge scope from a token one. The sequence reverses between the two locations, which makes them two different steps landing at two different points in the install order. An estimate carrying a single undifferentiated drip edge quantity has not described the work — it has described a material.

A wording note if you are working an older roof. The 2012 edition said "eaves and gables." Later editions say "eaves and rake edges." Same thing: the code council's commentary on that section identifies the sloped edges the code text called gables as the rake edges. Do not let the older word start an argument about whether rakes were covered.

Rake footage is the line that quietly disappears

This is the most common quiet loss on a Georgia drip edge line, and it is not a rejection — it is an omission nobody argues about because nobody notices it.

Eave length and rake length are different numbers, and their ratio swings hard with roof geometry. A pure hip roof has no rakes at all. A simple gable runs roughly comparable eave and rake footage. A cut-up roof with gabled dormers can carry far more rake than the elevation suggests, because each dormer adds two short rakes and little or no eave. If the estimate shows one line labeled "Drip edge" with one linear-foot number, a desk reviewer cannot tell whether rakes are inside it — and neither can you, three weeks later, defending it.

Break it out. Eave LF on one line, rake LF on another, each traceable to a marked-up roof diagram or a labeled photo. Two lines can each be checked against the diagram; one blended line cannot be checked against anything. Our list of commonly missed roofing line items and the rejections that follow them walks through the other quantities that behave this way, and the companion piece on why "it wasn't there before" is not a denial covers what a defensible drip edge photo set looks like.

Answering "it wasn't required back then"

Check the date before you argue

If the roof was permitted on or after January 1, 2014, the statement is simply wrong about that roof, and the fastest answer is a permit record rather than a paragraph of reasoning. Pull the permit date from the county. If the roof went on in 2017, drip edge was required at original installation, and the premise of the rejection is gone before the argument starts.

The absence of a requirement does not carry forward

For genuinely older roofs, this is the point that matters, and it is worth stating precisely because it is easy to state sloppily.

A 2009 roof built without drip edge complied with the code in force in 2009. That is not in dispute. What the age of the roof establishes is that the existing assembly was permitted to remain — it does not establish that a new assembly may be built to 2009 rules. The code addresses reroofing in a section of its own for exactly this reason: a tear-off to the deck followed by a new shingle installation is new roofing work, and new work is built to the edition in force on the day it is performed.

Put another way: "the old roof was legal" is a true statement about the past. It is not a specification for the future.

The manufacturer's instructions are a second, independent path

The code separately requires roof coverings to be installed according to the manufacturer's installation instructions. That is the same requirement the code council pointed to when it noted that before 2012 a drip edge was required only where those instructions called for one. Where the product you are installing calls for a metal edge, that requirement stands on its own and does not depend on which code edition anyone thinks applies.

This is often the strongest argument available on an older roof, and the one most often left out — because making it properly means attaching the installation instruction sheet for that specific shingle, not a general claim that manufacturers usually require one. Print the page. Circle the line.

Keep the code argument and the ordinance-and-law argument apart

These are two different arguments answering two different questions, and blending them into one paragraph is how people lose both at once.

The code argument is about scope. It says: the work being performed requires a drip edge at eaves and rakes, therefore the drip edge is part of what it costs to replace this roof, therefore the line belongs in the estimate. It is a statement about the physical work and the code that governs it. It stands or falls on the code edition, the date of the work, and the measured quantities — nothing else.

The ordinance-and-law argument is about coverage. It asks whether increased cost arising from the enforcement of a law or ordinance is addressed by the policy — which depends on that specific policy, its endorsements, and its limits. That question belongs to the policy and to the adjuster, not to a general article and not to a contractor's estimate.

The separation is practical, not pedantic. Write "this is required by code, so it is covered under ordinance and law," and you have fused two claims into one object that can be rejected once. A reviewer who concludes the ordinance-and-law piece does not apply to that policy now has a clean reason to strike the whole paragraph — and your scope point, which never depended on coverage terms, goes down with it. Two paragraphs under two headings can be accepted or declined independently. One paragraph cannot.

Cite the edition in force on the day of the work

A small thing that costs disproportionate credibility: writing "2018 IRC" on a file for work performed in 2026. Georgia moved to the 2024 edition on January 1, 2026. A reviewer who catches a stale edition in your citation has been handed a reason to read the rest of the file skeptically — and you spent that credibility on a detail that took ten seconds to get right.

For work happening now, cite the 2024 edition with Georgia amendments. For earlier work, cite whatever was in force then; the list above gives you the boundaries.

What belongs in the file

None of that compels a particular outcome. What it changes is what the person on the other end is reading: a dated, measured, citable description of work, instead of a line item with a number beside it.

Where these dates come from

This article is general information about published building code adoptions in Georgia. It is not legal advice and it is not an interpretation of any insurance policy. Code editions and local amendments change; verify the code in force in your jurisdiction on the date of your work, and consult a qualified professional about any specific claim, contract, or policy.

This is what ScopeQueue does with a file

You can work through all of this by hand, and plenty of good contractors do. ScopeQueue reads the carrier estimate and your photographs and drafts the same file for you to check — with the reason written under each item, and the code section left blank wherever it cannot be verified.

Try it on one file — free

More