# How to Compare a New Home Design Approval Path Before Plan Freeze

Source: https://brictale.com/build/design/compare-new-home-design-approval-path-before-plan-freeze
Published: 2026-10-05
Audience: Homeowner
Published by Brictale, a consumer home-intelligence publication. https://brictale.com

## Short answer

Before freezing a new detached-home plan, make one row for every competing requirement and label its jurisdiction, source, responsible person, evidence, review gate and handoff. Resolve items that can change the site, envelope, structure, life-safety path or required review first. Leave finish selections and trade coordination for later only when the architect, builder and authority confirm they do not reopen an earlier gate.

---

# How to Compare a New Home Design Approval Path Before Plan Freeze

Before freezing a new detached-home plan, make one row for every competing requirement and label its jurisdiction, source, responsible person, evidence, review gate and handoff. Resolve items that can change the site, envelope, structure, life-safety path or required review first. Leave finish selections and trade coordination for later only when the architect, builder and authority confirm they will not reopen an earlier gate.

This guide is for a homeowner in the United States who is in schematic design or design development for a new detached single-family home. It is not permit-ready drawing advice, structural sizing, a multifamily Fair Housing Act determination or legal advice. Austin, Texas appears as a named process example because its public residential-review page clearly shows the sequence; Austin rules are not national rules. Your actual city, county, state, tribal authority, utility, subdivision, overlay administrator and lender or program administrator may control different parts of the decision.

![Decision map showing a homeowner comparing two designs through jurisdiction, code, household, program and trade gates before plan freeze](https://brictale.com/images/home/build/design/compare-new-home-design-approval-path-before-plan-freeze/approval-path-overview.webp)

### Originality brief

**Current answers:** Most available answers are generic permit checklists, code summaries, accessibility explainers or single-jurisdiction application instructions. **Missing decision:** They rarely show what a homeowner must resolve before plan freeze when two design options trigger different local reviews, household needs, energy programs or consultant handoffs. **Original contribution:** This guide’s *Jurisdiction-Labeled Approval-Path Comparison Worksheet* compares options row by row using a named authority, evidence owner, review gate, handoff and next decision, with a modeled Austin, Texas example and sensitivity branches. **How to check it:** Recreate the rows for the actual property, open each linked authority or program source, confirm the adopted code and site triggers, and require the responsible person to accept the evidence before freezing the affected drawing input.

The practical question is not “Which plan looks better?” It is “Which plan creates the cleaner verified path through the next gate?” A good comparison makes a late conflict visible while both options are still cheap to change. It also prevents a common category error: treating a household preference, a voluntary energy target, a designer’s assumption and an enforceable local requirement as if all four had the same authority.

## 1. Decide what an approval path includes before comparing plans

An approval path is the sequence of decisions, evidence and handoffs that allows one design option to proceed, not a promise that an authority will approve it. Compare each option across local land-use rules, adopted technical codes, voluntary programs, household needs, site constraints, professional design responsibilities and later trade coordination. The option with fewer unresolved gates is usually the safer plan-freeze candidate, even when it is not the cheapest or most attractive option.

### Start with the decision you actually need to make

At schematic design, owners often ask a question that sounds simple but contains several decisions:

* Can the footprint move six feet to preserve an existing tree?
* Can a larger south-facing window wall fit the energy target without changing the mechanical concept?
* Can the primary entry, bathroom and bedroom remain on one level for a household member who may use a mobility aid?
* Can a garage, porch, roof form or conditioned attic be deferred to later drawings?
* Can two layouts follow the same permit and inspection path?

These are not only design questions. Each may trigger zoning, overlay, tree, floodplain, historic, energy, utility, fire, drainage, accessibility or internal coordination work. The homeowner’s decision is to identify which differences are “freeze now” differences and which are “coordinate later” differences.

Write the decision in one sentence before anyone scores the options:

> We will choose the option whose unresolved requirements can be verified by the responsible person before the next design gate, without relying on an unconfirmed local exception or a later field fix.

That sentence does not tell you which option wins. It tells you what winning means. If your most important outcome is preserving a mature tree, a tree review is not an inconvenience to subtract from the score. It is a first-order design input. If your most important outcome is an accessible main level for a particular household member, a generic statement that “the plan is accessible” is not evidence. The architect needs the actual household brief, dimensions and route assumptions.

### Separate six kinds of requirements

Use these labels in your comparison sheet. They are not interchangeable.

1. **Jurisdiction rule.** A local or state requirement with an identified authority, adopted text or official application instruction. Examples can include a setback, overlay, floodplain process, tree ordinance, historic review or permit submittal requirement. The actual authority and current version must be recorded.
2. **Adopted technical code.** A building, residential, energy, electrical, plumbing, mechanical, fire or other code adopted and amended for the project’s jurisdiction. A model code printed in a book is not automatically the law where your house will be built.
3. **Voluntary program or finance condition.** A certification, incentive, tax, lender, utility or builder requirement that may be important but is not automatically the local building code. A program can become practically mandatory for your deal if you choose it or your contract makes it a condition; label that contract or financing source.
4. **Household requirement.** A need or preference such as a no-step entry, a quiet bedroom, a future caregiver room, a home office, storage, daylight, a low-energy target or a view. The household owns the priority, while the design professional translates it into a buildable brief.
5. **Professional assumption.** A proposed interpretation by an architect, designer, engineer, energy consultant, builder, surveyor or other specialist that still needs confirmation. “The city will probably accept this” is an assumption until the authority’s current rule or written response supports it.
6. **Later coordination item.** A decision that can safely remain open because it will not change a reviewed site relationship, code path, opening schedule, structural concept, service route, equipment space, inspection evidence or contract scope. The phrase “later” must name an owner and a gate; otherwise it is simply an untracked risk.

This classification is the first protection against false certainty. The U.S. Department of Energy explains that the United States has no single national building or energy code and that states or local governments may adopt a model code, a modified model code or their own code. Once adopted, the code becomes law in the particular jurisdiction. That is why a national explanation can help you ask better questions but cannot answer whether your house complies. Read the [DOE explanation of local code adoption](https://www.energy.gov/cmei/buildings/articles/energy-codes-101-what-are-they-and-what-does-role) alongside the actual authority for your property.

### Define plan freeze narrowly

“Plan freeze” should not mean that every faucet, cabinet pull and paint color is final. It should mean the design decisions that other people must use as fixed inputs are stable enough to issue the next coordinated set. For a new home, that commonly includes:

* legal lot, address, jurisdiction and applicable overlays;
* building footprint, height, stories and conditioned floor area;
* primary access, parking, driveway and service connections;
* setbacks, easements, right-of-way relationships and site disturbance;
* flood, drainage, tree, historic, fire or other specialty-review triggers;
* structural grid and major spans, without attempting structural sizing here;
* window and door locations that affect envelope, egress, daylight, privacy and energy assumptions;
* equipment rooms, shafts, chases, intake and exhaust locations;
* household accessibility or visitability priorities;
* the selected energy-code path and any separate certification or incentive;
* the people responsible for unresolved evidence and the date of the next gate.

The freeze question is therefore binary for each row: either the input is verified and can be handed off, or the option remains conditional and must not be represented as final. A plan may be aesthetically complete and still not be ready for this kind of freeze.

### What not to infer

Do not infer that a preliminary conversation is approval. Do not infer that a voluntary program is code. Do not infer that a plan that works in one city works in another. Do not infer that a house designed for one household automatically satisfies every accessibility standard. Do not infer that a deferred item is harmless because a trade can “figure it out in the field.” Each inference can create a different kind of late redesign.

The next decision is whether you have enough jurisdiction and household inputs to compare options at all. If the property, project type, priority hierarchy or candidate changes are still unknown, stop scoring and collect those prerequisites first.

## 2. Build the jurisdiction record before you score a design

The jurisdiction record should be complete enough that a second person can tell who has authority over each question and which document would prove the answer. Record the property location, project type, adopted codes, overlays, specialty triggers, program commitments, household priorities, professional team and next review gate before debating which plan is “simpler.”

### Required inputs

Create one project header and one evidence row for each competing requirement.

**Project header**

| Input | What to record | Why it changes the comparison |
|---|---|---|
| Site jurisdiction | City, county, state or tribal authority, parcel or legal description, address status | The place that adopted and enforces the relevant rule |
| Project type | New detached single-family home, number of stories, approximate area and accessory structures | Different project types can use different review tracks |
| Design stage | Schematic design or design development, drawing date and version | Shows whether a question is suitable for preliminary review or must be documented in the next set |
| Household priorities | Ranked needs, including mobility, aging, caregiving, quiet, work, storage and energy goals | Prevents a code question from silently overriding a human need |
| Candidate changes | Option A, Option B and the exact geometry or system difference | Gives reviewers a finite comparison rather than a vague concept |
| Team | Owner, architect or designer, builder, surveyor, engineer, energy professional and authority contact | Assigns responsibility instead of leaving “someone” to verify it |
| Commitments | Lender, utility, incentive, certification, subdivision, HOA or contract conditions | Identifies requirements that are not local code but may still govern the project |
| Next gate | Household brief approval, concept review, schematic sign-off, DD coordination or authority question | Stops the team from using the wrong evidence at the wrong time |

**Requirement row**

| Field | Prompt |
|---|---|
| Decision ID | Give the conflict a short name, such as TREE-01 or ENTRY-02 |
| Candidate options | State the specific change, with dimensions, orientation and affected rooms |
| Requirement type | Jurisdiction rule, adopted code, program, household, assumption or later coordination |
| Authority or source | Name the local office, adopted code, program administrator or household decision-maker |
| Exact question | Ask what must be true, not whether the whole plan is “okay” |
| Required evidence | Survey, site plan, tree inventory, flood information, code citation, energy model, accessibility diagram, written program checklist or trade coordination sketch |
| Responsible person | Name one owner of the evidence, even when several people contribute |
| Review gate | State when the answer is needed and what cannot proceed without it |
| Handoff | Name the next person who receives the verified answer |
| Status | Unchecked, assumption, submitted, comment received, verified, conditional or deferred |
| Next decision | State the action if the answer is yes, no or conditional |

The worksheet is deliberately more demanding than a permit checklist. A checklist asks whether a document exists. This worksheet asks who owns the document, what decision it unlocks and which later person must trust it.

### Verify the actual authority, not a search-result summary

Start with the official site for the authority that can say yes or no. Search results can reveal a useful phrase, but they can be outdated, incomplete or detached from the adopted ordinance. Capture the page title, URL, access date, effective date or code edition if shown, and the exact scope. If an official page directs you to another department, follow that handoff and record the destination.

For Austin, the [Residential Plan Review page](https://www.austintexas.gov/development-services/residential-plan-review) says that its division reviews new construction and related work for single-family, duplex or two-family houses and additional buildings on one lot, and identifies Austin’s Land Development Code, the 2024 International Residential Code and local technical-code amendments as part of that local review context. That statement is useful because it names both project scope and sources. It does not establish which code applies in your city, county or state.

Ask your actual authority these questions before plan freeze:

1. Which office receives the first question about this property and project type?
2. Which state and local codes are adopted on the date we expect to submit?
3. Are there zoning districts, overlays, subdivision restrictions, easements, right-of-way limits or design standards that change the footprint or exterior?
4. Which flood, drainage, tree, historic, fire, utility, transportation or environmental screens occur before or alongside building review?
5. Is there a preliminary consultation, zoning question channel, code-question channel or pre-application meeting?
6. What drawings and site information make that conversation answerable?
7. Does the authority issue a written response, comment log, case number or other record we can carry into the next gate?
8. If the footprint, window schedule, roof, grading, tree impact or equipment changes later, which review must be reopened?

Austin’s page is a useful example of why these questions matter: it lists additional reviews such as floodplain proximity, historic applicability, technical residential building-code review, tree ordinance compliance, zoning and overlays, plus other department reviews. The page also states that the applicant is responsible for verifying property-specific information such as deed restrictions or restrictive covenants. Use that as a model for your question list, not as a portable set of Austin thresholds.

### Assign the evidence owner before the meeting

The homeowner owns the decision and the project record. That does not mean the homeowner should produce every technical answer. A sensible allocation looks like this:

* **Homeowner:** legal property information in hand, household priorities, budget or financing commitments, program choices, tolerance for redesign and the final decision to proceed.
* **Architect or qualified designer:** coordinated design options, code questions framed at the right level, space and route diagrams, plan revisions and the consequences of each choice.
* **Surveyor:** boundary, topography, easements or other survey deliverables within the survey scope.
* **Engineer or specialist:** structural, civil, geotechnical, flood, tree, historic, energy or other professional analysis when required by the site or project.
* **Builder:** constructability, sequencing, scope, allowances, trade coordination, site logistics and feedback about what a proposed option changes in the field.
* **Authority:** interpretation or review within its jurisdiction and published process; it does not replace the design team’s responsibility to coordinate the work.
* **Program verifier or administrator:** program-specific documentation and certification requirements, if the homeowner has committed to that program.

The owner should not ask a building department to select between two uncoordinated designs. Give the authority a short, neutral question with the relevant site facts and two clearly drawn options. Give the design team the written response and preserve the drawing version it addressed.

### The next decision: research, ask or design

Each row should end in one of three actions:

* **Research:** the answer is already published by the responsible authority or program and can be quoted with a scope and date.
* **Ask:** the published material does not resolve the site-specific question, so the owner or authorized agent asks the responsible authority in writing or through the official meeting process.
* **Design:** the question is not an authority interpretation but a professional coordination problem, so the architect, engineer, builder or verifier tests it against the selected path.

If a row cannot be assigned to one of those actions, it is not ready for scoring. That is a signal of missing ownership, not permission to mark it “probably fine.”

![Annotated worksheet diagram linking a property question to authority, evidence owner, review gate, handoff and next decision](https://brictale.com/images/home/build/design/compare-new-home-design-approval-path-before-plan-freeze/jurisdiction-evidence-ledger.webp)

## 3. Use the jurisdiction-labeled approval-path comparison worksheet

The worksheet’s job is to make two designs comparable without pretending that a score is a permit decision. Use the same rows, evidence standard and next-gate test for every candidate. A plan wins the worksheet only when its high-impact rows are verified or have a named conditional path with an explicit owner and date.

### Original contribution: Jurisdiction-Labeled Approval-Path Comparison Worksheet

**Summary.** This worksheet compares competing design changes through an evidence-and-handoff trail. It exposes whether the conflict is a local rule, adopted code, voluntary program, household requirement, professional assumption or later trade item. It produces a recorded next decision rather than a vague preference.

**Method.** For each candidate design change, record the site jurisdiction, project type, household priority, candidate options, governing source, responsible person, required evidence, review gate, handoff and next decision. The worked example uses illustrative Austin, Texas inputs and a five-point homeowner weighting model; sensitivity tests add flood, tree, historic, energy-program and accessibility branches. Then test the rows for completeness and keep the local compliance path separate from voluntary, household and later-coordination inputs.

**Limitations.** This is an editorial planning tool, not a permit determination, code opinion, accessibility certification, engineering analysis or legal advice. Austin is only an example; the homeowner and local design professionals must verify the current authority, adopted code, overlays, programs and site facts for the actual property. The worksheet cannot know whether a site is in a floodplain, contains regulated trees, lies in a historic district or is governed by a local program. Recheck the actual authority, adopted code, current program version and site evidence before relying on any row.

### Worked illustrative example: preserve the tree or preserve the service yard

The following is intentionally modeled. It is not a record of a real property, permit application, cost estimate or test.

Assume a homeowner is planning a new detached single-family home in Austin, Texas during design development. The initial concept inputs are:

* lot: 0.18 acre, represented in the base drawing as approximately 78 feet wide by 100 feet deep;
* home: one detached house, approximately 2,200 square feet of conditioned area, two stories;
* existing condition: one mature tree shown on the concept plan near the northeast side of the proposed footprint; whether it is regulated is not yet verified;
* household priority: a step-minimized primary entry, a first-floor full bathroom, a quiet home office and a protected outdoor area;
* program question: the homeowner is considering DOE Efficient New Homes certification but has not signed a builder or verifier commitment;
* candidates: Option A shifts the footprint 6 feet west to avoid the tree; Option B keeps the footprint centered, retains a wider west service yard and assumes the tree can be removed or impacted after review;
* decision gate: freeze the footprint, exterior openings, entry route and primary service zones before the coordinated design-development set.

The homeowner should not begin by awarding points for “tree” or “service yard.” First convert the differences into evidence rows.

| ID | Difference | Requirement label | Question | Evidence owner | Freeze gate | Handoff / next decision |
|---|---|---|---|---|---|---|
| TREE-01 | A avoids the tree; B may impact it | Jurisdiction rule, pending site fact | Is the tree regulated, and what activity would affect it? | Owner with arborist or Austin tree reviewer; architect maps footprint | Before footprint freeze | If regulated, request the applicable tree review path and revise the site plan; if not, retain written basis and continue |
| ZON-01 | A moves toward the west side; B stays centered | Jurisdiction rule | Do both footprints meet setbacks, overlays, easements and any lot-specific limits? | Architect, owner and local zoning contact | Before site-plan freeze | Send dimensioned options to zoning or plan review; select only an option with documented dimensions or a named exception path |
| ENTRY-01 | A shortens the west approach; B keeps a wider approach | Household requirement plus site/grade coordination | Which entry route better serves the household priority and can it be built within the site and local requirements? | Homeowner and architect; civil or accessibility specialist if needed | Before floor-plan and grading freeze | Approve the route diagram and carry slopes, thresholds and drainage questions to the responsible professional |
| ENERGY-01 | A changes glazing and west wall area; B keeps the base window pattern | Adopted code plus optional program | Which energy-code path applies, and is DOE certification a project commitment? | Architect, builder and energy verifier if program is selected | Before window and envelope schedule freeze | Record code path separately from program checklist; model or document the chosen path |
| SERV-01 | A narrows the west service yard; B preserves it | Professional assumption / later coordination | Do equipment, utility, maintenance and construction-access routes still work? | Architect and builder; utility contacts where applicable | Before equipment and site logistics freeze | Issue a coordination sketch; if a clearance or route fails, reopen the footprint decision |
| HIST-01 | Exterior massing and new construction may differ by district | Jurisdiction rule, only if triggered | Is the property in a historic district, overlay or other historic-review condition? | Owner and local historic office; architect supplies concept elevations | Before exterior massing freeze | Obtain the applicability answer and add the correct reviewer to the handoff |

This table shows why “Option B is simpler” is not a sufficient conclusion. Option B may preserve a wider service yard, but it carries an unverified tree assumption. Option A may solve the tree question but create a setback or equipment coordination problem. The useful comparison is not a preference score; it is the count and severity of unresolved gates.

### A transparent illustrative scoring model

If the household wants a provisional comparison while evidence is being collected, keep the model simple and visible. Use a 0-to-5 rating for how well each option serves a household priority, then subtract a gate penalty for an unresolved requirement that could force redesign.

Let:

`Provisional score = (priority weight × option rating) summed across priorities − unresolved gate penalty`

Use weights that add to 100 points. For the modeled example:

| Priority | Weight | Option A rating | Option B rating | Why the rating is only an assumption |
|---|---:|---:|---:|---|
| Preserve mature tree if regulated | 30 | 5 | 1 | Based on the drawn footprint, not a verified tree survey or authority decision |
| Maintain service and construction yard | 20 | 2 | 5 | Based on concept dimensions, not trade layout or utility confirmation |
| Support household entry and first-floor needs | 25 | 4 | 3 | Based on a schematic route, not final grades or professional accessibility review |
| Keep energy-path flexibility | 15 | 3 | 3 | No energy model or program enrollment has been completed |
| Keep exterior massing and privacy goals | 10 | 3 | 4 | Household preference only; no historic applicability confirmed |
| **Total weighted rating** | **100** | **350 / 100 = 3.50** | **290 / 100 = 2.90** | **Illustrative only** |

The arithmetic for Option A is `30×5 + 20×2 + 25×4 + 15×3 + 10×3 = 350`, or `3.50` on a five-point scale. Option B is `30×1 + 20×5 + 25×3 + 15×3 + 10×4 = 290`, or `2.90`. Those numbers do not mean Option A is approved. They only make the homeowner’s provisional priorities inspectable.

Now add an unresolved-gate penalty. Suppose the homeowner sets the penalty at 0.75 points for a high-impact assumption and 0.25 for a lower-impact assumption. Option B’s unverified tree-impact path receives 0.75, while Option A’s west-yard coordination question receives 0.25. The adjusted results are:

* Option A: `3.50 − 0.25 = 3.25`.
* Option B: `2.90 − 0.75 = 2.15`.

The result is still not a permit conclusion. It tells the team which question is worth resolving first: TREE-01. If a verified tree review shows that Option B can proceed with no removal or impact permit, its penalty may fall. If a survey shows the tree’s critical root zone overlaps Option A’s excavation or staging, Option A’s rating must be revisited. The model is useful because it tells you what evidence would change the decision.

### Sensitivity test: change the review environment

The worksheet must survive reasonable branches. Test one added condition at a time, rather than hiding several new assumptions in one score.

**Branch 1: flood review is added.** The footprint, finished-floor concept, site grading, access and documentation may need a different review sequence. Do not guess the flood elevation or design response from a map screenshot. Assign the owner to obtain the authority’s current floodplain or drainage requirements and have the qualified design professional incorporate verified site information. Both options remain conditional until the added review confirms that their footprint and grade relationships can proceed.

**Branch 2: tree review is added.** The tree is no longer a background landscape preference. It becomes a review gate with a site plan, tree information and protection or impact question. Austin’s tree page says regulated trees require a permit to remove or impact, including activity that may disturb a critical root zone, and it describes a pre-plan consultation option. That is an Austin process fact, not a rule for every U.S. city. [Austin’s trees-on-residential-property guidance](https://www.austintexas.gov/development-services/trees-residential-property) should be read only for the Austin example; use your local arborist or environmental authority elsewhere.

**Branch 3: historic review is added.** Exterior massing, demolition, materials, windows and site visibility may become more consequential than the interior layout. Add the historic authority to the evidence owner list and freeze the elevations only after applicability and submission expectations are recorded. Do not use “new construction” as a reason to skip a historic screen; the trigger may depend on district, landmark, existing structure or local overlay.

**Branch 4: the energy program becomes a commitment.** A voluntary program becomes a project requirement because the owner signed a contract, expects an incentive, chose a certification target or agreed to a lender or builder condition. The energy-program checklist now has its own review gate and verifier handoff. It still must be kept separate from the adopted local energy code. DOE’s [Efficient New Homes Single Family Version 2 page](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-single-family-version-2) lists eligible single-family homes, duplexes and townhouses and the program documents; DOE’s separate [Efficient New Homes Program Requirements page](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-requirements) states the third-party verification requirement and publishes the effective-date table tied to permit date. Confirm the applicable version, location boundary, permit-date rule and verifier role with the program administrator.

**Branch 5: an accessibility need becomes more specific.** A household request for a step-minimized entry, wider clearances, a first-floor bathroom or future adaptability should be placed in the household brief and translated into a dimensioned route by the design team. Do not call it a federal Fair Housing Act requirement for a detached house without checking the project type. HUD and DOJ’s guidance places the Fair Housing Act design and construction requirements on covered multifamily dwellings, including buildings with four or more dwelling units built for first occupancy after March 13, 1991; that federal boundary does not turn every detached single-family home into covered multifamily housing. [the current HUD/DOJ accessibility guidance](https://www.justice.gov/crt/media/1457641/dl?inline=) is the source for this scope, while other laws, funding conditions and local rules may still matter.

### What the sensitivity test is supposed to reveal

If one added review changes the winning option, that is not model failure. It means the original decision was sensitive to an unverified condition. Mark the decision “conditional,” name the evidence, and move the review earlier. If an added branch changes nothing because both options face the same gate and the same evidence, keep the common gate in the project record but let the homeowner compare the actual design differences.

The next decision is whether the unresolved row belongs in an authority conversation, a professional analysis or a household choice. That determines the next handoff.

## 4. Resolve the local rule first: Austin process example and nationwide translation

For a real project, use your own authority’s published process; for the Austin example, the homeowner should sequence preliminary questions, preparation, application, review, corrections, permit issuance and inspections while preserving the written record. The process is not a single “approval path” in the abstract. It is a chain of gates with different owners, documents and consequences.

### Austin’s published sequence

Austin says an owner or agent may request a Preliminary Plan Review meeting before submitting a permit application to discuss preliminary design or construction issues. The city also states that the meeting is intended to identify items that should be addressed or modified before construction plans are submitted, and that it does not guarantee approval. Use this as a pre-freeze question channel, not as a permit or design certification. [Austin’s Preliminary Plan Review description](https://www.austintexas.gov/development-services/residential-plan-review) supports that limited interpretation.

For the Austin example, translate the page into this homeowner sequence:

1. **Prepare the project header.** Confirm the property, project type, lot status, known overlays, existing structures, tree or flood questions, household priorities and the two candidate options.
2. **Choose the question set.** Ask only questions that the authority can answer at this stage: review applicability, required documents, code edition, zoning relationship, specialty review trigger and whether the two alternatives follow different paths.
3. **Request the appropriate preliminary conversation.** Give the authority a concise plan set or concept diagram that labels Option A and Option B. Record meeting date, participants, drawing version, questions, answers and unanswered items.
4. **Prepare the formal application inputs.** The city’s page says to use the appropriate application, checklists and requirements to determine documentation. Do not assume the preliminary discussion substitutes for these materials.
5. **Submit the application and preserve the accepted set.** Record the application number, submitted plan version, fees if relevant to your project management, and every supporting document.
6. **Track plan review comments.** Austin says the applicant receives approval notification or a Master Comment Report after reviews, and that rejection comments must be addressed before approval.
7. **Respond with a coordinated update.** The page says responses should describe how and where each comment was addressed, revised plans should highlight changes, the full plan set should be submitted, and unresolved comments can result in rejection or additional fees.
8. **Recheck discipline handoffs.** If a change affects a previously approved discipline, tell intake staff so the plans can be redistributed for review. This is why a “small” footprint or window change can reopen a larger path.
9. **Reach permit issuance and inspections.** Austin describes permit issuance after reviewer approval, activation before construction and inspections after the applicable permit is activated.
10. **Record post-approval revisions.** The city states that revisions are required for changes to approved design after approval and before final inspection, subject to the applicable process.

These are Austin’s published process statements, not a guarantee of timing or outcome. The [city’s residential review page](https://www.austintexas.gov/development-services/residential-plan-review) currently publishes the sequence, review-time information and revision expectations, but a homeowner should not use a posted turnaround as a promise to a lender, builder or move-in schedule. A review clock is not the same as a complete design, a permit or an inspection pass.

![Side-by-side comparison of two illustrative footprints showing tree, service yard, entry, energy and historic review consequences](https://brictale.com/images/home/build/design/compare-new-home-design-approval-path-before-plan-freeze/option-freeze-comparison.webp)

### Translate the example to another jurisdiction

Use the same sequence but replace every Austin label with the actual authority:

* **Preliminary conversation:** Does the city, county or state offer a pre-application, zoning inquiry, plan consultation or code-question process? Is it advisory, binding, written, paid, public or limited to an owner or authorized agent?
* **Adopted code:** Which code editions and local amendments apply on the expected application date? Are residential and commercial paths different? Does a state agency control the energy code while a city controls zoning and building permits?
* **Specialty review:** Which agency owns floodplain, stormwater, trees, historic resources, fire, driveway, utility, septic, coastal, wildfire or environmental review?
* **Evidence:** Does the authority require a survey, topographic information, tree survey, elevation certificate, energy compliance report, energy model, geotechnical report, historic photographs, drainage plan or other document before it can answer?
* **Revision path:** If a reviewer comments on one discipline, how are changes redistributed to other disciplines? Does the authority require a complete resubmittal or accept a marked revision set?
* **Inspection and field change:** Which changes require a formal revision, deferred submittal, field approval or new inspection? Who can authorize each kind of change?

The answer should be written in your project record. If a local staff member gives verbal guidance, ask whether it can be confirmed in the official portal, a written email, a comment log or a cited section. A verbal “should be okay” can be a useful lead, but it should remain labeled as an assumption until the authority’s process turns it into a record.

### Keep design questions small enough to answer

Bad question: “Will this house be approved if we move it west?”

Better questions:

* “For a new detached single-family dwelling on this parcel, does the proposed west wall location meet the currently applicable setback and overlay controls shown on the attached site plan?”
* “Does the existing tree condition shown in the attached survey trigger a tree review or permit before excavation, and which document does the authority require?”
* “If the south window area changes from Option A to Option B, which energy-code compliance path and documentation must the design team submit?”
* “Does this project type fall within the authority’s residential review, and which separate review groups must see the plan before the main review is complete?”

The smaller questions make the next handoff inspectable. They also prevent an authority from accidentally appearing to approve parts of the design it was never asked to review.

### The next decision: freeze, revise or escalate

At the end of local-rule review, choose one:

* **Freeze the affected input:** the authority or professional record is clear, the drawing matches it and the handoff owner accepts it.
* **Revise the option:** the evidence changes the footprint, exterior, route, equipment or schedule; update the comparison and rerun affected rows.
* **Escalate to a qualified professional:** the question requires a licensed architect, engineer, surveyor, arborist, energy professional, accessibility specialist or attorney within the appropriate jurisdiction.
* **Keep the option conditional:** the issue cannot be resolved yet, but the team can safely advance unrelated work without representing the conditional input as final.

Never let “conditional” become a silent fourth option. Put an expiry or decision date next to it and define what may not proceed before the answer.

## 5. Separate mandatory review, voluntary program, household need and later handoff

The cleanest comparison assigns a different evidence owner to every category. A local authority can interpret its rule; a program verifier can interpret its certification; a design professional can coordinate drawings; a household can set priorities. None of these roles should impersonate another.

### Use a four-lane responsibility table

| Lane | Example question | Primary owner | Evidence that can travel to the next gate | What it does not prove |
|---|---|---|---|---|
| Local rule or adopted code | Does the site or project trigger a zoning, flood, tree, historic, fire or building-code review? | Owner and design professional with the authority | Current official page, adopted section, portal record, written response, accepted plan or comment resolution | It does not prove a different jurisdiction’s rule or guarantee final approval |
| Voluntary program or finance condition | Are we committing to DOE Efficient New Homes, a utility incentive or a lender condition? | Owner, builder and program administrator or verifier | Current program version, signed commitment, checklist, model or verifier instructions | It does not automatically become local code |
| Household requirement | Does the main level work for our mobility, care, work, noise or storage needs? | Homeowner with architect or qualified designer | Ranked brief, room and route diagram, dimensions, option decision and agreed compromises | It does not establish compliance with a federal or local accessibility law |
| Later professional or trade coordination | Will the equipment, framing, conduit, duct, utility route or finish fit after the major geometry is fixed? | Architect, builder and relevant trade or engineer | Coordinated detail, equipment cut sheet, service diagram, responsibility matrix and inspection evidence | “We will solve it later” does not prove the space or path exists |

This table is a control against authority drift. For example, the homeowner may choose a high-performance envelope. The architect and energy professional may model it. The builder may sequence air sealing and insulation. A qualified tester may provide a result if the adopted code or program requires one. The local official may accept specified documentation. A homeowner blog cannot collapse those steps into “high-performance homes are required to do X.”

DOE’s code-compliance overview explains that design and construction professionals carry important compliance responsibilities, local building officials typically review plans and conduct field inspections, and qualified third parties may provide test documentation for some requirements. Use the [DOE compliance overview](https://www.energy.gov/cmei/buildings/articles/building-energy-code-compliance) to understand the role separation, then confirm the exact local evidence path.

### Distinguish “required by code” from “required for our chosen program”

Put the source beside the requirement, not at the end of a paragraph. A row should say one of the following:

* “Required by [named jurisdiction and adopted code section].”
* “Required by [named program version] because the owner elected certification.”
* “Required by [named lender, contract, utility or incentive document].”
* “Chosen by the household; the design team will determine how to document or coordinate it.”
* “Recommended by a professional; verify whether it is a code, program or design choice.”

For example, DOE’s [Efficient New Homes program](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program) is voluntary and is not intended to be adopted as a minimum building energy code; its versioned requirements and third-party verification pathway still matter if the owner chooses certification. It does not by itself tell you that your municipality has adopted every DOE program requirement as its energy code. Conversely, a local energy code does not by itself mean that your house is certified under a DOE program. Keep two columns: **local compliance path** and **optional or contractual performance path**.

The same distinction applies to ratings, labels, tax credits and utility incentives. If an incentive matters to the budget, put its administrator, deadline, version and evidence in the worksheet. If the owner is only exploring it, mark it “not committed” and show what would change if the decision is made later. A program that affects window specifications, equipment space, solar readiness, ventilation, duct routing or inspection evidence should be decided before those parts are frozen.

### Treat accessibility as both a household priority and a scope question

A homeowner may choose a more accessible home because it supports current mobility, aging in place, caregiving, visitors or future resale. That is a legitimate design priority even when no federal law applies to the detached house. The design team should turn it into observable requirements: route from parking or sidewalk, entry threshold, clear passage, turning spaces, bathroom layout, bedroom location, controls, lighting, storage and future reinforcement or adaptability.

Separately, ask whether a legal accessibility requirement applies to this project. HUD and DOJ’s [covered-multifamily accessibility guidance](https://www.justice.gov/crt/media/1457641/dl?inline=) states that the Fair Housing Act design and construction requirements cover newly constructed multifamily housing with four or more units intended for first occupancy after March 13, 1991, and describes features such as accessible routes, doors, controls, bathroom wall reinforcement and usable kitchens and bathrooms. Those statements are relevant to the federal multifamily boundary, not a universal detached-home rule.

The question for the local authority or professional should therefore be: “Which law, code, funding source, use, project type or household need creates this requirement here?” Do not ask only “Is accessibility required?” That wording invites an overbroad yes or no and can miss a local visitability ordinance, a public or common-use area, federal funding condition, state rule or the homeowner’s own non-negotiable need.

### Handoffs need an acceptance test

A handoff is complete when the next person can use the information without reopening the previous decision. Add an acceptance test to every major row:

* **Architect to authority:** correct jurisdiction, project type, drawing version, dimensions, specific question and supporting site information.
* **Authority to architect:** written applicability answer, cited source or comment, required document and any conditions or limits.
* **Architect to builder:** updated plan set, revision cloud or change log, affected scope, detail responsibility and decisions that may not be changed in the field.
* **Energy professional to design team:** selected code/program path, model inputs, assumptions, required envelope or equipment changes and verification plan.
* **Builder to trades:** current drawings, equipment or product information, clearances, routes, sequencing, inspection hold points and change procedure.
* **Household to team:** ranked priorities, accepted compromises, unresolved concerns and the exact next decision date.

If the recipient says “I did not know that was a condition,” the handoff was incomplete. If a trade says “we assumed the earlier sketch was still current,” the change log failed. A plan-freeze record is valuable precisely because it gives later people a way to distinguish a deliberate decision from an abandoned assumption.

### The next decision: accept the tradeoff or change the brief

Every comparison has a point where two good goals conflict. A wider service yard may reduce tree disturbance. A larger south-facing window may support daylight but alter the envelope calculation, shading design and HVAC assumptions. A no-step route may require a different grade, drainage response or entry location. A historic review may constrain exterior expression while the household wants a different massing.

Do not hide the conflict inside a technical score. Write the tradeoff in household language, identify the authority or professional evidence needed, and obtain an explicit owner decision. The next handoff should say what was chosen and what was not chosen. That record is more useful than a neutral-sounding plan set that leaves the team guessing.

## 6. Compare energy and accessibility without mislabeling requirements

Treat energy and accessibility as separate decision surfaces: identify the adopted local requirement, identify any chosen program or funding condition, then translate the household outcome into coordinated design inputs. The correct comparison does not assume that an energy program is code or that a detached-home preference is a federal accessibility mandate.

### Energy: code path first, performance target second

The local energy-code question comes first because the authority enforces the adopted code for the project. Ask for the code edition, compliance path, required forms or software, inspection evidence, testing requirements and any local amendments. Record who prepares the compliance documentation and who verifies field conditions.

Then decide whether the homeowner is also pursuing a performance target. That target might be a DOE program, a utility incentive, a lender condition, a tax-credit eligibility path, a builder standard or simply a household goal. Each can change the design, but each has a different source and evidence trail.

DOE’s [Efficient New Homes Single Family Version 2 page](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-single-family-version-2) lists eligible buildings and the national and California program documents. The separate [DOE Efficient New Homes Program Requirements page](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-requirements) states that certification requires a third-party verifier and explains that the effective program version is selected using the permit-date table. DOE’s [program FAQ](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-faqs) describes the handoff: builders review and register, a rater performs post-construction site testing and inspections, and the rater’s documentation goes through oversight approval. Record the program version, location boundary, permit or eligibility date, verifier, modeled inputs and required evidence.

For the comparison, list design inputs rather than slogans:

* window orientation, area and shading assumptions;
* wall, roof, floor and foundation assemblies at the level the design team can actually document;
* air-sealing and ventilation strategy;
* heating, cooling and water-heating concept, including space and service routes;
* lighting, appliances, solar-ready or electric-vehicle-ready features if required by the chosen path;
* duct, plumbing and electrical routing that affects framing and chases;
* testing, inspection and verifier evidence;
* operating assumptions that belong to the homeowner rather than the code.

Do not freeze a window schedule by comparing glass adjectives alone. The window decision may affect solar gains, shading, wall area, structural openings, views, privacy, egress, daylight, furniture layout, HVAC loads and program documentation. Ask the architect and energy professional which inputs are sensitive enough that changing them after the model or compliance report will require rerunning the path.

### Energy sensitivity example

Return to the illustrative Options A and B. Suppose both currently use the same window performance assumption, but Option B adds 80 square feet of west glazing to preserve the wider service yard and improve a room’s view. That 80 square feet is not automatically “bad” or “noncompliant.” It is a model input that may alter the compliance calculation, shading need, cooling concept or program checklist.

Record:

* baseline west glazing: 40 square feet;
* Option B west glazing: 120 square feet;
* change: `120 − 40 = 80 square feet`;
* unresolved question: does the selected local code path or chosen program remain satisfied with the revised orientation, window properties and shading design?
* responsible person: architect or energy professional, with builder input on product availability and installation;
* evidence: updated energy compliance calculation or program model, revised window schedule and shading detail;
* freeze gate: before window order, exterior elevation freeze and any dependent mechanical sizing;
* next decision: retain, shade, resize or select Option A.

The numbers above are illustrative inputs, not performance claims. The article does not calculate a house’s energy use from them. A real model needs climate, geometry, assemblies, openings, equipment, schedules and the applicable calculation method. DOE’s [whole-building energy-modeling overview](https://www.energy.gov/cmei/buildings/about-building-energy-modeling) lists building geometry, materials, lighting, HVAC, water heating, renewable generation, controls, operating assumptions and local weather as model inputs used to calculate loads and energy use; a quick glazing-area comparison cannot substitute for that model.

### Accessibility: design for the household, verify the legal scope

For a detached house, begin with the household outcome, not a label. Ask:

* Who needs the route now, and who may need it later?
* Is the required route from the property boundary, parking, garage, sidewalk or another arrival point?
* Which rooms must be usable on the first floor?
* Which clearances, turning areas, thresholds, controls, storage and bathroom arrangements matter to the person who will use them?
* What site slope, drainage, snow, heat, handrail or door hardware conditions affect the route?
* Which dimensions must be verified by the architect or qualified accessibility professional rather than estimated from a sketch?

Then check the legal and program boundary. If the project is a covered multifamily dwelling, a different federal analysis may apply. If the project receives federal assistance, is a public accommodation or falls under a state or local law, additional requirements may apply. If it is a detached single-family home for the homeowner, the household may still choose a more usable layout, but the federal multifamily rules should not be misrepresented as a blanket detached-home mandate.

Also distinguish “visitability” from every other accessibility concept. A local visitability ordinance can be narrower or broader than a household’s accessibility brief, and a code may address specific elements without delivering the whole experience the household needs. The correct row names the actual authority, law or household goal.

### When a later specialist can safely enter

An accessibility specialist, energy professional or trade can join after the schematic comparison only if the upstream inputs are stable enough for useful review. Do not defer them past the point where the footprint, grades, openings, shafts, bathrooms, equipment rooms or structural grid are frozen if their advice could change those inputs.

Use a “consultant entry test”:

1. Is the site jurisdiction and project type verified?
2. Is the household outcome stated in observable terms?
3. Are the two candidate options dimensioned and versioned?
4. Is the selected local or program source current and in scope?
5. Does the consultant have enough information to test the actual choice?
6. Is the consultant’s output a recommendation, a required document, a certification or a design input?
7. Which earlier rows would reopen if the answer changes?

If the answer to any of the first four is no, the specialist should usually enter earlier. If the answer to the last two is unclear, the team has not defined the handoff.

### The next decision: keep, modify or reject the candidate

At this stage, the team should be able to explain every material difference between the options in one of four ways:

* verified local requirement;
* chosen program or finance condition;
* explicit household priority;
* coordinated professional consequence.

If a difference has none of those explanations, remove it from the score or label it as a preference. If a supposedly minor change affects multiple rows, treat it as a compound change and rerun the comparison. A plan that wins only because its consequences are unrecorded is not ready to freeze.

## 7. Run the freeze gate and hand off a defensible decision record

Freeze a design option only when high-impact inputs are verified, conditional items have owners and dates, the next reviewer can identify the current set, and the homeowner has accepted the remaining tradeoffs. The output should be a short decision record that another professional can inspect without rereading every conversation.

### Plan-freeze checklist

Use this checklist at the end of schematic design or design development. Mark each item **verified**, **conditional**, **deferred with owner**, or **not applicable with reason**.

**Jurisdiction and scope**

* [ ] Property jurisdiction, parcel or legal description and project type are recorded.
* [ ] The authority that controls zoning, building, energy and specialty reviews is named.
* [ ] Adopted code editions and local amendments are recorded from current official sources.
* [ ] Any state, county, tribal, utility, subdivision, HOA, lender or program condition is separated from local code.
* [ ] The team has checked for flood, drainage, tree, historic, fire, wildfire, utility, septic, transportation and other site-specific triggers applicable to the actual property.

**Design inputs**

* [ ] Footprint, stories, approximate area, height, access and parking are dimensioned.
* [ ] Setbacks, easements, overlays and site constraints are drawn or assigned to a responsible professional.
* [ ] Primary entry and household-priority routes are diagrammed.
* [ ] Major window and door locations are stable enough for energy, privacy, egress and coordination review.
* [ ] Equipment rooms, shafts, chases, intake, exhaust and utility service zones are reserved.
* [ ] The structural or civil professional has the inputs needed for the next level of work, without treating this guide as structural design.

**Evidence and review**

* [ ] Each material row has one responsible evidence owner.
* [ ] Each local-rule claim links to the actual authority or adopted source.
* [ ] Each voluntary-program claim identifies the program version and verifier or administrator.
* [ ] Each household need is expressed as a decision or measurable design input, not a generic label.
* [ ] Each deferred item states what cannot change before its later gate.
* [ ] Authority responses, meeting notes, comment logs and drawing versions are stored together.
* [ ] The team knows which change would reopen each previously reviewed discipline.

**Homeowner decision**

* [ ] The homeowner has selected the option or recorded why it remains conditional.
* [ ] Accepted compromises are written in plain language.
* [ ] The budget owner and builder understand scope changes that follow from the selection.
* [ ] The next decision date and next handoff recipient are named.
* [ ] The homeowner understands that this record is not a permit, inspection approval or professional sign-off.

### Common failure cases and recovery actions

**Failure 1: The team freezes the plan from a model code summary.**

What happened: A national article or old code book was treated as the local rule. The footprint, window or energy path was selected before the authority and adopted amendments were confirmed.

Interpretation: The evidence has the wrong scope.

Recovery: Reopen the jurisdiction record. Ask the actual authority or qualified local professional which code and amendments apply on the intended application date. Recheck only the affected rows first: footprint, envelope, openings, fire, accessibility, drainage and specialty reviews. Do not restart every design decision automatically. The [DOE code-adoption explanation](https://www.energy.gov/cmei/buildings/articles/energy-codes-101-what-are-they-and-what-does-role) is a useful reminder that this answer belongs to the particular jurisdiction.

**Failure 2: A preliminary meeting is described as approval.**

What happened: The team heard that a concept looked workable, then treated it as guaranteed.

Interpretation: Advisory information was promoted to a final determination.

Recovery: Preserve the meeting record, identify the exact unanswered questions and obtain the formal source, application response or review comment that controls the next gate. Austin expressly says its Preliminary Plan Review does not guarantee approval, which illustrates the boundary. [Austin’s published preliminary-review process](https://www.austintexas.gov/development-services/residential-plan-review) supports that distinction.

**Failure 3: A voluntary energy target quietly becomes “code.”**

What happened: A builder, lender or homeowner selected a program, but the design team did not separate its checklist from the local energy-code submission.

Interpretation: Two paths were merged, so the team cannot tell which evidence is required by which source.

Recovery: Make two rows: local code compliance and program certification. Identify the program version, contract or incentive condition, verifier, required calculations, inspections and deadlines. Check whether the current design satisfies both or whether one path can be dropped without breaching a commitment.

**Failure 4: The tree, flood or historic question appears after the footprint is frozen.**

What happened: The site was treated as a blank canvas. A specialty review later changed the buildable area, grading, exterior or construction staging.

Interpretation: The site trigger was not screened during comparison.

Recovery: Freeze no more than the unaffected interior work. Assign the site professional and authority question immediately. In Austin, the city publicly identifies floodplain proximity, historic applicability and tree ordinance compliance as possible additional review areas; the exact thresholds and departments elsewhere must be checked independently. [Austin’s residential review triggers](https://www.austintexas.gov/development-services/residential-plan-review) support that limited local example.

**Failure 5: “Accessible” is used without a household route.**

What happened: A generic label replaced the actual needs of the person who will use the house, or a federal multifamily rule was assumed to govern a detached home.

Interpretation: Household design and legal scope were both under-specified.

Recovery: Rewrite the household brief as a route and room requirements, then ask the architect or qualified specialist for a dimensioned design review. Separately identify whether the project has multifamily, funding, public-use or state/local accessibility triggers. Do not rely on a generic blog checklist as proof.

**Failure 6: The builder receives an old plan set.**

What happened: A later coordination change was discussed by text or in a meeting but was not carried into the controlled set.

Interpretation: The handoff lacked version control and an acceptance test.

Recovery: Issue one current set, a change log and a short list of decisions that cannot be changed in the field without reopening review. Ask each affected professional and trade to acknowledge the scope. If a change affects a previously approved discipline, follow the local revision process rather than relying on an informal markup.

**Failure 7: The score hides a hard gate.**

What happened: Option B won a weighted matrix because it scored well for cost or floor area even though its tree, flood or setback path was unresolved.

Interpretation: A conditional failure was treated as a small preference loss.

Recovery: Separate hard gates from preferences. If a row could make the option unbuildable, require written confirmation or a qualified professional’s path before allowing the option to compete on softer priorities. Use penalties only to prioritize work, never to override a missing legal or technical answer.

### Safety boundaries during design coordination

The design stage can appear low-risk because the work is mostly drawings and conversations, but the decisions can direct hazardous work. Do not enter excavations, inspect unstable structures, climb roofs or trees, open energized equipment, disturb suspected contamination or enter confined spaces to collect evidence for this worksheet. Have qualified professionals handle structural, electrical, excavation, tree, flood, geotechnical, fire-protection and other hazardous work within the relevant rules.

A remote article cannot diagnose or direct homeowner evidence collection around pressurized gas, water, hydronic or hydraulic systems. If you suspect a leak, observe abnormal pressure or see a relief device discharge, stop and keep clear; use the applicable qualified professional, utility or emergency process for the system and jurisdiction. Do not investigate, disconnect, repressurize, reset or alter the system to improve the worksheet record. If there is immediate danger, follow emergency instructions and contact emergency services. A photo or written description from a safe location can help the responsible professional decide what to inspect, but it is not a substitute for that professional’s evaluation.

A remote article cannot assess a site’s soil, flood elevation, tree stability, utility location, structural condition, electrical hazard, grade, moisture, contamination or construction access. Photos and sketches can help a professional prepare a question; they cannot replace a survey, inspection, test, permit review or field verification. The safest homeowner action is to collect records from a safe location, identify the uncertainty and ask the responsible professional what evidence is needed.

### Prepare the next handoff packet

Give the next person a compact packet, not a conversation transcript:

1. **Decision cover sheet:** project name, property, jurisdiction, drawing version, date, homeowner decision and unresolved conditions.
2. **Two-option comparison:** the exact changes, dimensions, household priorities, provisional scoring assumptions and sensitivity branches.
3. **Jurisdiction record:** authorities, adopted-code sources, program sources, specialty triggers and question log.
4. **Evidence ledger:** each claim, source URL, access date, scope, responsible person and status.
5. **Marked plan set:** site, footprint, entry route, major openings, equipment zones, tree or flood information and affected elevations.
6. **Comment and response log:** question, response, drawing location, responsible person and next action.
7. **Handoff list:** recipient, information provided, acceptance test and date for confirmation.

![Plan-freeze handoff record connecting verified inputs and conditional items to architect, builder, authority and next gate](https://brictale.com/images/home/build/design/compare-new-home-design-approval-path-before-plan-freeze/freeze-handoff-record.webp)

The packet should let the builder price the chosen scope, let the architect coordinate the next set, let the energy professional identify model inputs, let the authority answer a bounded question and let the homeowner see which tradeoffs were accepted. If it cannot do those things, the decision is not yet durable.

### The final decision

Choose **freeze** when the option’s site, project type, major geometry, household priorities, local review triggers and chosen code or program paths are verified enough for the next coordinated set. Choose **revise** when evidence changes the footprint, exterior, route, equipment or review group. Choose **hold** when the missing answer could reopen a hard gate and no safe unrelated work can advance. Choose **escalate** when the decision requires a licensed or jurisdiction-qualified professional.

The most useful output is not a claim that one plan is universally best. It is a record that says: this property is in this jurisdiction; these are the requirements and chosen goals; these people own the evidence; this option was selected for these stated reasons; these conditions remain; this is the next gate; and this is the person who must verify it. That is how a homeowner prevents plan freeze from becoming a hidden transfer of risk to the permit reviewer, builder or trade.

For the next stage, keep the comparison record with the current drawing set and revisit it whenever the footprint, openings, grading, services, energy path, household brief or program commitment changes. New homeowner decisions can then be added to Brictale’s broader [home-building decision library](/blog) without losing the original jurisdiction, evidence or handoff trail.

## Evidence

- Austin Development Services says its Residential Plan Review division reviews new construction and related work for single-family, duplex or two-family houses and additional buildings on one lot, using Chapter 25-2 of the Land Development Code, the 2024 International Residential Code and Chapter 25-12 Technical Codes with local amendments. [Residential Plan Review | Austin Development Services](https://www.austintexas.gov/development-services/residential-plan-review). Scope: Austin, Texas residential plan review; local process example only, not a national rule or a determination for another jurisdiction.. Accessed: 2026-09-08.
- Austin describes a Preliminary Plan Review meeting as a way for an owner or agent to discuss preliminary design or code issues before construction plans are submitted, and states that the meeting does not guarantee approval. [Residential Plan Review | Austin Development Services](https://www.austintexas.gov/development-services/residential-plan-review). Scope: Austin, Texas preliminary review process; the existence and effect of a comparable meeting elsewhere must be confirmed locally.. Accessed: 2026-09-08.
- Austin's published residential process lists preparation, application, plan review, correction updates, permit issuance and inspections; it says rejection comments must be addressed and later changes to an approved design may require revisions. [Residential Plan Review | Austin Development Services](https://www.austintexas.gov/development-services/residential-plan-review). Scope: Austin, Texas residential permit sequence; timing, forms and revision rules vary by authority and project.. Accessed: 2026-09-08.
- Austin identifies additional review triggers that can include floodplain proximity, historic applicability, tree ordinance compliance, technical residential building code review, zoning and overlays, and other department reviews. [Residential Plan Review | Austin Development Services](https://www.austintexas.gov/development-services/residential-plan-review). Scope: Austin, Texas triggers as displayed on the current city page; thresholds and departments are not portable to another jurisdiction.. Accessed: 2026-09-08.
- Austin states that regulated trees on residential property require a permit to remove or impact, including work that may disturb a tree's critical root zone, and provides tree review and pre-plan consultation steps. [Trees on Residential Property | Austin Development Services](https://www.austintexas.gov/development-services/trees-residential-property). Scope: Austin, Texas tree ordinance process; the homeowner must identify the equivalent tree authority and rules for the actual site.. Accessed: 2026-09-08.
- DOE explains that the United States does not have one national building or energy code; states or local governments may adopt a model code, a modified model code or their own code, and an adopted code becomes law in the particular jurisdiction. [Energy Codes 101: What Are They and What is DOE’s Role? | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/articles/energy-codes-101-what-are-they-and-what-does-role). Scope: U.S. explanation of code adoption; it does not identify the adopted code for a particular property.. Accessed: 2026-09-08.
- DOE describes code compliance as involving design and construction professionals, local building officials, field inspections and, for some tests, qualified third parties whose documentation may support a local official's compliance determination. [Building Energy Code Compliance | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/articles/building-energy-code-compliance). Scope: DOE overview of common energy-code compliance roles; exact responsibility and accepted evidence depend on the adopted code and authority.. Accessed: 2026-09-08.
- DOE's Efficient New Homes Single Family Version 2 page identifies eligible single-family homes, duplexes and townhouses and publishes the national and California program requirement documents for that program version. [DOE Efficient New Homes Single Family Version 2 | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-single-family-version-2). Scope: DOE Efficient New Homes Single Family Version 2 program eligibility and documents; it does not establish local code or permit requirements.. Accessed: 2026-09-08.
- DOE describes the Efficient New Homes program as voluntary and says it is not intended to be adopted as a minimum building energy code. [DOE Efficient New Homes Program | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program). Scope: DOE program status; a project contract, lender, incentive or owner decision can still make participation a practical project condition.. Accessed: 2026-09-08.
- DOE's Efficient New Homes Program Requirements page states that all DOE Efficient New Homes must be certified by a third-party verifier and directs readers to recognized certification organizations for more details. [DOE Efficient New Homes Program Requirements | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-requirements). Scope: DOE Efficient New Homes certification; third-party verification is a program requirement and does not by itself replace the local building permit or local code compliance.. Accessed: 2026-09-08.
- DOE's Efficient New Homes Program Requirements page says that the program version required for certification is determined by the effective-date table and the home's permit date, with the corresponding program document defining the permit date for the building type. [DOE Efficient New Homes Program Requirements | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-requirements). Scope: DOE Efficient New Homes program-version timing; it does not determine a local jurisdiction's permit requirements or guarantee tax-credit eligibility.. Accessed: 2026-09-08.
- DOE's Efficient New Homes FAQ says builders should review the program requirements, register as partners and find a rater; after construction, the rater performs site testing and inspections to check that the as-built home matches the modeled design and meets mandatory requirements, then submits documentation for oversight approval. [DOE Efficient New Homes Program FAQs | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/doe-efficient-new-homes-program-faqs). Scope: DOE Efficient New Homes program workflow; the FAQ describes program roles and does not assign local code, permit or contract responsibilities for a particular project.. Accessed: 2026-09-08.
- DOE's whole-building energy-modeling overview says a building energy model uses inputs including geometry, construction materials, lighting, HVAC, water heating, renewable generation, component efficiencies, control strategies, operating schedules and local weather to calculate loads, system response and energy use. [About Building Energy Modeling | U.S. Department of Energy](https://www.energy.gov/cmei/buildings/about-building-energy-modeling). Scope: DOE description of whole-building energy modeling; the overview does not perform a model or establish compliance for a particular house.. Accessed: 2026-09-08.
- HUD and DOJ guidance says the Fair Housing Act's design and construction requirements apply to covered multifamily dwellings, defined in the guidance as buildings with four or more dwelling units built for first occupancy after March 13, 1991; the guidance separately asks whether the requirements apply to detached single-family homes and states the covered-multifamily boundary. [Accessibility (Design and Construction) Requirements for Covered Multifamily Dwellings Under the Fair Housing Act | U.S. Department of Justice and HUD](https://www.justice.gov/crt/media/1457641/dl?inline=). Scope: Federal Fair Housing Act design/construction boundary; other federal, state, local, funding, public-accommodation or household-specific requirements may apply.. Accessed: 2026-09-08.
- HUD and DOJ's covered-multifamily guidance describes Fair Housing Act design and construction features including an accessible entrance and route, sufficiently wide doors, accessible routes through dwellings, accessible controls, bathroom wall reinforcement and usable kitchens and bathrooms. [Accessibility (Design and Construction) Requirements for Covered Multifamily Dwellings Under the Fair Housing Act | U.S. Department of Justice and HUD](https://www.justice.gov/crt/media/1457641/dl?inline=). Scope: Covered multifamily housing under the Fair Housing Act; the guidance is not a universal detached-home design mandate and is not a substitute for local accessibility review.. Accessed: 2026-09-08.