The Problem

Solar developers aren't losing the Investment Tax Credit because projects fail in the field. They're at risk of losing it because of a regulatory deadline that has nothing to do with construction quality and everything to do with paperwork sequencing.

Under the One Big Beautiful Bill Act, signed in July 2025, the federal government dramatically compressed the runway for solar and wind tax credits that the Inflation Reduction Act had extended through 2032. The new rule: solar and wind projects must begin construction by July 4, 2026 to remain eligible for the 30% Section 48E Investment Tax Credit, or be fully placed in service by December 31, 2027. Miss both deadlines, and the credit isn't reduced. It's gone. There's no gradual phase-down.

The mechanics that determine whether a project "began construction" in the eyes of the IRS are not casual. For most solar projects above 1.5 MW, the old 5% cost safe harbor (long the easy path) that no longer applies. Developers must now satisfy the Physical Work Test: documented, continuous physical construction activity, on-site or off-site under binding contract, with inventory purchases no longer counting. On top of that, new Foreign Entity of Concern (FEOC) rules disqualify projects that receive "material assistance" from prohibited suppliers, with a Material Assistance Cost Ratio (MACR) threshold that requires verified, documented supply-chain sourcing, with a clawback period that now extends to ten years if a project is later found non-compliant.

This is the pattern that keeps showing up across clean energy work: the hardware is rarely the failure point. The failure point is coordination: tracking which legal test applies to which project, when documentation has to be locked, who owns supplier certification, and what happens if a permitting delay pushes a project past the line.

Why This Is an Operations Problem, Not Just a Legal One

Every developer racing this deadline has access to the same legal guidance. Law firms and EPCs have published extensively on the Physical Work Test, the MACR threshold, and the safe harbor mechanics. That's not the bottleneck. The bottleneck is operational: most teams are tracking this across spreadsheets, email threads, and individual project managers' memory, for a regulatory requirement with a ten-year audit exposure if it's wrong.

That's a workflow and systems problem before it's a tax problem.

Where Context Engineering Changes the Outcome

This is the kind of situation a context-engineered operational system is built for. Not because the system "knows tax law," but because the actual risk is in coordination, documentation, and deadline tracking across a portfolio, not in any single legal question:

  1. Portfolio-level deadline tracking. A live system that flags, per project, which BOC (beginning-of-construction) path applies: Physical Work Test vs. small-project safe harbor, and surfaces which projects are at risk of missing July 4 before it's too late to act.
  2. Supplier documentation chain-of-custody. Given the ten-year clawback window on FEOC violations, the MACR documentation a developer collects today needs to be retrievable and defensible a decade from now. A structured intake workflow standardizes what's collected at the point of supplier contracting, instead of reconstructing it under audit pressure later.
  3. Continuous-construction evidence trail. The Continuity Safe Harbor requires showing uninterrupted progress, not just a start date. A structured workflow that logs physical work activity as it happens, rather than relying on after-the-fact narrative reconstruction, making the difference between a defensible filing and a vulnerable one.
  4. Decision triage, not document generation. The highest-leverage move isn't a tool that drafts compliance memos. It's a system that tells a development team, every week, which 3–5 projects in their pipeline need an action this week to stay inside the safe harbor, so attention goes where the deadline risk actually is.

Illustrative Outcome (Modeled, Not Actual)

Note: This is a projected outcome based on the mechanics above, not a reported result from any real engagement.

For a mid-size developer with 15–20 projects in active development, a portfolio-level tracking and documentation system of this kind would typically be expected to:

Who This Is For

Solar and wind developers and EPCs with active multi-project pipelines who are inside the July 2026 compliance window and do not currently have a centralized system tracking BOC status, supplier documentation, and continuity evidence across projects.