Section 179D After June 30, 2026: What Project Teams Should Recheck

Section 179D changed on June 30, 2026, and that date is now behind project teams reviewing commercial building work. The key question is not simply whether a project is complete. Teams should check when construction began, what property and work are involved, what records support the timeline, and whether other requirements apply. This article offers a project review framework, not tax advice or a determination that any facility qualifies.

Discuss your energy project

What changed for Section 179D after June 30, 2026?

The U.S. Department of Energy states that Section 179D does not apply to property whose construction begins after June 30, 2026. That makes the construction-start date a key point for teams assessing a project’s potential tax treatment. The date alone does not establish eligibility: the property, project facts, applicable rules, and required documentation still matter.

For projects already in progress, do not assume that a planned completion date, purchase date, contract signature, or equipment installation date answers the construction-start question. Those dates can describe different events. Ask a qualified tax professional to determine which facts and legal standards apply to the project and what evidence is appropriate. The Department of Energy’s Section 179D overview describes the deadline and program at a high level.

In practical terms, the deadline calls for careful triage rather than a quick yes-or-no answer. A project team can help by making the underlying facts easier to review: identify the property, define the work, build a reliable chronology, and preserve the records that explain each event. A tax adviser then determines how the relevant law applies. Keeping those roles distinct helps avoid turning a planning assumption into a conclusion.

It is also important to date the discussion. The Inflation Reduction Act of 2022 is relevant background for energy tax provisions, but a discussion based on that law before the later change may not describe the rule that applies after June 30, 2026. When reviewing an old slide deck, estimate, article, or project memo, note its publication date and ask whether its assumptions remain current. Do not carry an earlier incentive assumption forward without checking it.

Which projects need a closer timeline review?

Prioritize projects where the date is uncertain or where the work changed over time. A project team may have approved a scope before the deadline but delayed mobilization. Another project may have begun some work while later phases were added or substantially revised. A third may involve multiple buildings or separate work packages. These examples are prompts for review, not conclusions about how the law treats a particular project.

• Approved but not clearly started:

  Locate dated records that show what actually happened, not only the original authorization or intended schedule.

• Phased or expanded work:

  Identify the separate buildings, systems, phases, and scope changes. Ask whether each should be evaluated on its own facts.

• Delayed or paused work:

  Build a timeline of activity before and after the deadline, including any restart or revised scope.

• Multiple parties involved:

  Compare owner, contractor, designer, and finance records so the dates and descriptions align.

Keep the review grounded in evidence. A schedule entry may help explain a sequence, but the project team should not treat one document as a legal test. Have a tax adviser assess the significance of the evidence under current requirements.

When authorization and field activity do not line up

Projects often have a long path from an internal decision to work at a site. A capital request may be approved in one month, the contract may be signed later, a notice to proceed may follow, and mobilization may occur on a different date. That sequence can be useful context, but the team should not select the most favorable date and assume it controls. Record each milestone as a separate event, with the source and the person who can explain it.

For example, suppose a project schedule shows an anticipated start in June, but the site log first records contractor activity in July. Do not erase or reinterpret either record. Ask the project manager what the June entry represented, whether it was a forecast or actual work, and whether there are other contemporaneous records. The tax adviser can decide whether the distinctions matter under the applicable standard. This kind of fact reconciliation is more reliable than a retrospective statement that simply declares a start date.

When there are multiple buildings, phases, or systems

A campus-wide program can contain different work packages: one building may be getting controls upgrades, another may have a separate lighting scope, and a third may have work deferred. A single project name or overall budget may conceal those differences. Create an inventory that identifies each building or property, the systems included, the work package, the responsible project lead, and the known dates. Keep the inventory factual and ask an adviser how to group or evaluate the work.

Scope changes deserve particular attention. A change order may add equipment, alter design details, remove a building, or shift work to a later phase. Preserve the original scope and each dated revision instead of replacing earlier files with the newest version. A reviewer needs to see what was planned at each point, what changed, and when the project team approved or carried out the change. A project described as one continuous effort may still contain distinct factual components, but the legal treatment must be determined by an appropriate adviser.

What records should a project team gather?

Start by assembling a concise project file. The goal is to give reviewers a consistent picture of the work, its timing, and the people responsible for key decisions. Avoid rewriting records after the fact. If a document is incomplete or inconsistent, flag the gap and explain what is known rather than filling it with assumptions.

1. Chronology:

   Collect dated approvals, notices to proceed, contracts, work orders, meeting notes, site logs, invoices, and schedule updates that may help establish the sequence of events.

2. Scope history:

   Keep the original project description alongside change orders, revised drawings, equipment substitutions, and phase additions.

3. Property details:

   List the buildings and systems involved, the owner or relevant parties, and the work performed or planned. Do not assume similar buildings have identical facts.

4. Efficiency documentation:

   Preserve technical specifications, calculations, design records, commissioning or performance information, and any other documents your tax adviser requests.

5. Open questions:

   Record missing dates, conflicting descriptions, and decisions that need confirmation. Assign an owner and a due date for each question.

For facilities with multiple project files or disconnected records, a simple evidence index can save time. Use columns for document name, date, source, project phase, and the question it may help answer. Keep privileged or sensitive materials in the appropriate controlled location and follow your organization’s retention practices.

Build the file in a repeatable sequence

A manageable review does not require copying every record into a new folder at once. Start with a short project description that names the property, the general purpose of the work, the systems involved, and the internal project owner. Keep the description neutral. For example, say that a controls project covered Building A and Building B, rather than stating that it meets a tax requirement. Add a version date so the team knows when the summary was prepared.

1. Set the boundaries:

   Determine which property and work package the review covers. If the project contains several buildings or phases, make separate entries where facts differ.

2. Collect records by source:

   Ask facilities, procurement, finance, design, construction, and operations teams for records they maintain. Capture where each file came from and whether it is an original, a copy, or a later summary.

3. Record event dates:

   Extract dates from the records, but do not decide in advance which date is legally decisive. Note the event described, such as approval, purchase, site access, installation, or a schedule forecast.

4. Compare descriptions:

   Check whether the project name, building, equipment, and phase descriptions are consistent. Preserve differences and ask the relevant author to explain them.

5. Mark uncertainty:

   Use clear labels such as confirmed by a dated record, reported by a project participant, or still unverified. Do not present a recollection as documentary proof.

6. Route the package:

   Give the indexed material and unresolved questions to a qualified tax adviser. Use the adviser's request list to determine what additional documentation is needed.

One workable index has fields for record ID, file name, document date, date received, source, project or phase, event described, and follow-up question. A separate chronology can then point to those record IDs. This is helpful when two files say different things: the chronology shows the conflict, while the index lets the reviewer inspect the underlying records without searching a shared drive from scratch.

For instance, a planning presentation may refer to a project as starting in May, while a contractor report first describes site work in July. The index should include both records and identify the difference. It should not silently convert the planning milestone into actual work or remove the contractor report. The project lead can supply context, and the tax adviser can assess whether the difference affects the analysis.

What should the timeline capture?

Capture events before, on, and after June 30, 2026, where records exist. Include the event date and the date the record was created if those are different. For example, a meeting note written in July might describe a June event. That is not necessarily a problem, but the record should be labeled accurately. Distinguishing the event from the document date avoids presenting a later recollection as if it were contemporaneous.

Useful timeline entries can include internal approval, design milestones, bid or procurement steps, contract execution, notice to proceed, site access, mobilization, delivery, installation, inspection, commissioning, pause, restart, and completion. This is not a list of legal tests. It is a practical way to make the project history visible. The adviser can identify which events are relevant and request further evidence if needed.

Where the evidence is incomplete, write down the gap and the next step. A note might say that the first available site log is dated July 8 and that the project manager is checking archived contractor reports. That is more transparent than inferring activity from a later invoice or assuming that no earlier activity occurred. If a record cannot be found, note which systems or people were checked and when, following internal information-handling practices.

How can teams compare documents without drawing a tax conclusion?

A useful review separates observable facts from interpretation. It can help to keep a factual timeline and an adviser question log side by side. The timeline records what documents and participants say. The question log identifies what needs legal or tax analysis. This structure supports a careful conversation without making a project manager responsible for interpreting tax law.

• Fact:

  A purchase order is dated May 12, 2026. Record that date and what the purchase order covered.

• Context:

  A meeting note dated May 20 describes an expected July installation. Record the forecast and the document date.

• Conflict or gap:

  A later report says work occurred in June, but the underlying site record has not been located. Identify the source and the missing support.

• Question for adviser:

  Ask which facts and legal standards determine the relevant construction-start analysis for this property and scope.

This format is deliberately neutral. It neither dismisses a record nor treats it as conclusive. A tax professional can identify the significance of each item, request additional evidence, and explain whether the facts support any further analysis. The project team's job is to make that assessment possible by providing a complete and accurate account.

When documents use broad terms such as project start, construction, implementation, or installation, do not assume all authors meant the same thing. Ask what activity the term referred to in that specific document. An engineer may use a milestone label for schedule planning, while a finance memo may use the same phrase to refer to budget authorization. Preserve the wording, then add a plain-language note that identifies the author or project role and the context where known.

How should teams handle phased, paused, or revised work?

Changes over a project's life can make a single start-date summary misleading. A project may start with an initial scope, pause because of procurement or access issues, and later resume with a revised design. Another project may proceed in one building while a second is postponed. Rather than compressing this into one narrative, represent the project as a sequence of documented events and decisions.

For phased work, create a short fact sheet for each phase. Identify the location, equipment or systems, planned activity, current status, and the records associated with it. Cross-reference shared documents, such as a master contract or campus plan, but note which portions relate to which phase. If a phase was added later, preserve the change approval and the prior scope description. The aim is to show the project's evolution, not to make an eligibility determination.

For a pause, note when the pause was communicated, the reason recorded at the time, what work had occurred, and when the team considered or executed a restart. If the reason is unknown, say so. Do not fill the gap with an assumption that a pause either preserved or changed a project's treatment. Ask the adviser whether the pause, restart, or subsequent changes are relevant under current requirements.

For scope revisions, maintain a change log with the date, description, author or approving role, impacted property or system, and linked records. A short entry such as revised controls sequence for Building B may be more useful than a vague note that the project was updated. If the revision was discussed in a meeting but formal documentation followed later, retain both records and distinguish their dates. Again, the adviser determines the legal effect.

These practices help operational teams as well as tax reviewers. A current scope record can expose a procurement mismatch, clarify which equipment was actually installed, or explain why an original schedule no longer matches field reports. The same discipline is useful even if a project ultimately does not pursue a potential tax benefit.

How can teams avoid confusing a deadline check with eligibility?

A favorable answer about timing is not a complete eligibility review. Section 179D has program requirements beyond the construction deadline, and the project's precise facts matter. Teams should avoid treating a general article, an old estimate, or an informal discussion as a current tax conclusion. The Inflation Reduction Act of 2022 is relevant background for changes to energy tax provisions, but an older article about the law should not be used as current tax advice.

Separate the work into three questions:

• What is known?

  State verified facts about project scope, dates, ownership, and documentation.

• What needs interpretation?

  Ask a qualified tax professional to assess the applicable statutory requirements and the effect of the records.

• What action follows?

  Determine whether to gather more evidence, revise a project assumption, or stop relying on a potential benefit in planning until it is verified.

This separation helps facility and finance teams discuss project economics without treating a possible deduction as guaranteed savings. If a potential benefit is part of an approval model, label it as unconfirmed until an appropriate review supports its use.

Keep the financial model honest while review is underway

A capital-planning model may include a tax assumption because decision makers want to understand possible scenarios. That does not mean the assumption is established. Label the amount or treatment as pending review, identify the date of the estimate, and state which project facts or program rules remain unverified. If the project approval depends on that assumption, make the dependency visible to the approving group rather than burying it in a footnote.

Teams can distinguish a base case from a scenario that includes an unconfirmed benefit. The base case should show the project economics without assuming an unverified tax outcome. A separate scenario can show what the model would look like if an adviser later confirms a treatment, with assumptions clearly listed. This is a planning method, not a tax calculation. Have the finance team and tax adviser determine the appropriate inputs and presentation for the organization.

For example, a facility manager might want to compare an efficiency project with and without an assumed deduction. The responsible approach is to label the second case as illustrative, identify who is responsible for verifying it, and avoid presenting the potential amount as a guaranteed source of savings. If the review changes the assumption, update the model and preserve the prior version so decision makers can see what changed and why.

Use consistent language in meeting notes, budgets, and executive summaries. Phrases such as potential treatment subject to project-specific tax review are clearer than statements that the project qualifies. Avoid terms that make an unverified benefit sound certain. A short caveat does not replace professional analysis, but it can keep internal communication aligned with what is actually known.

What common review pitfalls should teams avoid?

Several preventable habits can make an otherwise useful project review less reliable. The first is treating a familiar milestone as a legal answer. Teams may be accustomed to using contract execution, purchase order release, or mobilization as shorthand for a project start. Those terms may be useful operationally, but they describe different events. Write down what happened and when; let a qualified adviser determine which facts matter for the tax question.

A second pitfall is collecting only the records that support the date the team expects to find. A balanced file should include records that appear to point in different directions, along with an explanation of what each one says. Do not omit a schedule revision because it complicates the story or elevate one site note simply because it is convenient. Reviewers can assess a conflict only if they can see it.

A third pitfall is relying on a document label without reading the underlying context. A file called construction start may contain a forecast, a retrospective summary, or a generic phase marker. Confirm the author, the purpose, and the event described. Where the record does not make those points clear, ask the author or project participant for context and preserve that explanation as a separate note rather than editing the original.

Another common problem is mixing buildings or phases in a single folder without clear identifiers. If a campus has several projects underway, an invoice or site report may be assigned to the wrong work package. Use consistent project and building identifiers in the chronology, index, and source folder. If one record applies to multiple locations, say so and explain how the team knows. This reduces the risk that a reviewer mistakes evidence from one scope for evidence about another.

Finally, avoid overstating the value of missing records. A missing document does not itself prove that an event did or did not occur. Record what was searched, who conducted the search, and what sources remain available. Then ask whether additional corroborating information exists and whether it is appropriate to use. These simple controls help keep the review credible even where the historical record is imperfect.

Who should take part in the review?

The right group depends on the project's size and organizational structure, but a useful review usually brings together people who hold different parts of the record. A facility or energy lead can explain the operational scope. A project manager can reconstruct decisions and milestones. Procurement or legal staff may hold contracts and change documents. Finance can explain how the project was modeled. A qualified tax professional can assess the legal and tax questions.

Do not assume every participant needs every document. Assign a coordinator to maintain the index, control versions, and route questions to the appropriate owner. The coordinator should not resolve legal questions by consensus. Instead, use the meeting to confirm what is known, identify conflicts, and agree on who will provide the missing record or obtain professional advice.

Before the meeting, circulate a concise agenda and a factual summary. Ask participants to bring source records rather than relying only on memory. During the meeting, note which statements are supported by a document, which are recollections, and which remain unresolved. Afterward, distribute an action list with a responsible person and due date for each open item. A short, disciplined meeting is more useful than a long discussion that ends with an undocumented conclusion.

A practical review meeting agenda

1. Confirm the scope:

   Agree on the property, buildings, systems, phases, and project records being reviewed.

2. Walk through the timeline:

   Review each event and its supporting record, especially where a date is close to June 30, 2026, or differs across sources.

3. Review changes and interruptions:

   Identify scope revisions, pauses, restarts, substitutions, and deferred work.

4. List evidence gaps:

   Assign someone to search for each missing or conflicting record and set a follow-up date.

5. Ask tax questions:

   Give the qualified adviser the factual file and ask what legal requirements, additional documents, or analysis are needed.

6. Agree on interim communications:

   Decide how project status and unconfirmed assumptions will be described in budgets, approvals, and leadership updates.

Keep minutes focused on facts and actions. If the adviser provides a conclusion, record it through the organization's normal professional-advice process and do not paraphrase it beyond what the adviser intended. For sensitive communications, follow counsel's guidance about handling and distribution. A project file should be complete enough for review while respecting applicable confidentiality and retention policies.

How can a team close out its first review pass?

Before sending materials to an adviser, run a short quality check. Confirm that the file has a clear project name, a scope summary, and a list of properties or work packages covered. Check that the chronology includes the records closest to the key dates and that each entry points to a source. Confirm that the scope history shows major additions, removals, substitutions, pauses, and restarts rather than only the latest plan.

Then check whether a reviewer can tell the difference between fact, recollection, and interpretation. A dated work order is a source record. A project manager's explanation can add context, but should be identified as a recollection or follow-up statement when that is what it is. A statement that a project qualifies is an interpretation and should not appear in a project team's factual summary unless it is quoting an appropriately scoped professional conclusion. Clear labels make the file easier to review and reduce accidental overstatement.

Next, review the outstanding-items log. Each open item should identify the missing fact or record, the person responsible for following up, the expected next action, and a target date. If an item cannot be resolved, leave it visible and tell the adviser. Do not remove it from the list simply because locating the record is difficult. The adviser may be able to explain whether another source is useful or whether the gap limits the analysis.

Finally, define how the team will use the result. The review may lead to a request for further documentation, a more detailed tax analysis, a revision to internal planning assumptions, or a decision not to pursue the question. Record the decision and the source of the guidance, using the organization's normal process. A project team should not infer a final answer from silence, an old spreadsheet, or an informal comment in a meeting.

What should teams do next?

Set a short review meeting with the facility lead, project manager, finance representative, and tax adviser. Bring the project chronology, scope history, and list of unresolved questions. Ask the adviser to identify which facts are material, what additional records are needed, and whether the project's timing and other facts warrant further eligibility analysis.

Energy project discussions also benefit from a clear view of efficiency measures, costs, and decision points. Profitable Green Solutions describes its energy-efficiency project advice separately from tax determinations. For more educational material, browse the company's energy articles. Any tax or rebate question should be reviewed against current program rules and the specific project facts.

For a project lead, an efficient first pass can be completed in several manageable steps. First, write a neutral scope description and identify the buildings and systems. Second, gather the key dated records from the people who created or maintain them. Third, build a chronology that distinguishes event dates from record dates. Fourth, note contradictions and missing information without trying to settle the tax question. Fifth, have a qualified tax professional review the materials and specify the next analysis required.

That process also creates a useful decision trail. If the project team later updates its schedule, modifies a phase, or revises a financial assumption, it can explain what changed and which records support the update. If the adviser says more information is needed, the team has a defined list rather than a general request to investigate. If no further action is warranted, the file still supports accurate project planning and communication.

Call to discuss an eligibility conversation

Frequently asked questions

Does work completed after June 30, 2026 automatically qualify?

No. Completion after the date does not establish qualification. The Department of Energy describes the cutoff in terms of when construction begins, and other program and project requirements still need review.

Does signing a contract before the deadline prove construction began?

Not by itself. A contract date is one record in a project timeline, but teams should ask a qualified tax adviser what facts and legal standards determine the relevant construction-start date.

What if different project records show different dates?

Preserve both records, identify what event each one describes, and note who created it. Ask the people closest to the work to explain the difference, then give the records and explanation to a qualified tax professional. Do not choose one date solely because it is more favorable.

Can a project team use an old Section 179D article to make a decision?

Use older material only as background. Tax provisions and program requirements can change, so confirm the current rules and the facts of the specific project with a qualified tax professional before relying on a potential benefit.

A careful timeline and well-organized project file help teams ask better questions, but they do not replace a project-specific tax review.