Completion Dates on a Home Improvement Contract
By Seamless Home Team, Solar fulfillment operations · September 9, 2026
Quick answer
Most home improvement statutes require the contract to state approximate commencement and completion dates, and a contract without them is defective in the same way as one missing a cancellation notice. The dates are described as approximate rather than guaranteed, which is what makes them workable — but approximate is not unlimited, and in several states failing to commence or to complete within a reasonable time without lawful excuse is the statutory definition of contractor abandonment, which is a licensing violation independent of any harm to the homeowner. Residential PV solar makes this genuinely difficult because most of the elapsed time is controlled by third parties: the plan review queue, correction cycles, an HOA committee's meeting calendar, an interconnection review, an inspection booking and finally the utility's permission to operate. The workable answer is not a vague date or an optimistic one. It is a date built from measured cycle times for that jurisdiction with the third-party dependencies named in the contract as the conditions they actually are, plus a documented change procedure when a dependency slips. What converts delay into exposure is silence, not duration.
A home improvement contract has to say when the work will start and when it will finish. That requirement exists in most states, it is unremarkable on a kitchen remodel, and it sits awkwardly on residential solar — because a solar project's elapsed time is mostly not the contractor's to control.
Between signature and a working system there is a plan review queue, a possible correction cycle, sometimes an architectural review committee that meets monthly, an interconnection review, an inspection booking, and finally a utility issuing permission to operate. A contractor with crews standing by can still be four months from completion for reasons that have nothing to do with capacity.
None of which removes the requirement. And in several states, delay that becomes unreasonable is not a customer-service problem — it is abandonment, which is a licensing violation.
What the date commits you to
The statutory language is usually approximate commencement and completion dates. That word is doing real work, and it is worth being precise about what it does and does not give you.
What it gives you: the dates are not guarantees. Residential home improvement contracts do not normally carry the liquidated-damages machinery that utility-scale construction uses — as what an EPC is sets out, that apparatus belongs to a different kind of contract entirely.
What it does not give you: unlimited time. The date establishes the reference point against which delay is judged reasonable or unreasonable. It is what a licensing board compares the actual timeline against if a complaint arrives.
And "to be determined" does not satisfy the requirement. A contract that appears to state dates while stating nothing is a defective contract in the same way as one missing a cancellation notice.
Abandonment is the consequence people do not expect
The formulations differ by state, but the common shape is: failing to commence within a stated period after the agreed start date, or failing to complete within a reasonable time, without lawful excuse and without the homeowner's agreement. Several states set an explicit number of days of inactivity.
Three features make this different from an ordinary breach:
- It is a licensing violation, administered by the board rather than a court.
- It does not require proven financial harm. The conduct is the violation.
- Lawful excuse is a genuine defence — a project waiting on a plan review is not an abandoned project.
There is a second clock running in parallel and it is easy to forget: the permit itself expires if work does not commence or is suspended for a set period, which is a separate consequence with a separate owner — see who is responsible when a solar permit expires.
Where the time actually goes
A defensible date has to be built from the real components. These are the ones that consume the calendar, and only one of them is inside the contractor's control:
| Stage | Controlled by | Notes |
|---|---|---|
| Survey and design | The contractor | The one genuinely controllable stage |
| Association review | The committee | Its meeting calendar can add a month on its own |
| Plan review | The jurisdiction | Use the observed turnaround, not the published one |
| Correction cycle | Both | The single largest variance; assume a probability, not zero |
| Interconnection review | The utility | Runs in parallel, on its own clock |
| Install scheduling | The installer | Backlog from notice to proceed |
| Inspection | The jurisdiction | Booking lead time, plus re-inspection risk |
| Permission to operate | The utility | After everything else, and frequently the longest single wait |
Two of these are systematically underestimated. The correction cycle is not a rare event, and a cycle is rarely just the day it takes to fix a drawing — it is the resubmission queue at the other end, which is measured in weeks in a busy jurisdiction. And the HOA committee's meeting calendar turns a nominal thirty-day review into a wait for the next meeting plus the review, which is why a submission landing the day after a meeting has lost four weeks before anyone reads it.
The project timeline estimator exists to build this figure from jurisdiction, association status and financing type rather than from optimism.
Writing a date that holds up
Three moves, in order:
1. Build the number from measured cycle times. Observed plan review turnaround for that specific jurisdiction, a realistic correction probability, the association's meeting calendar, the utility's review and PTO turnarounds, the installer's current backlog. This is AHJ research, not estimation, and it is reusable across every project in that jurisdiction.
2. Name the dependencies as conditions, specifically. A term identifying plan review, association approval, interconnection review, inspection and permission to operate as steps outside the contractor's control is accurate and defensible. A blanket clause excusing any delay for unspecified circumstances is neither, and it is likely to be read as an attempt to avoid the requirement rather than as a term. Specificity is what makes a condition survive.
3. Have a documented change procedure and use it. When a dependency slips, the date moves by an agreed instrument rather than by drift. That is the same change-order discipline that applies to scope and price, applied to schedule.
The financing consequence
There is a reason the completion date is not merely a compliance term, and it is the reason a long delay can kill a project outright rather than just annoy a homeowner.
Credit approvals expire. Lender stipulations go stale. A funding stipulation cleared in month one can need re-clearing in month four, and a long enough delay means the whole approval is re-run — at pricing, and against a credit profile, that may have moved. On third-party-owned products the approval window and the milestone conditions have their own timetables again.
So the date is tied to whether the project funds, not only to whether the homeowner is happy. That is the strongest internal argument for building it honestly: an optimistic date does not make a project faster, and it removes the early warning that would have let somebody re-approve the financing before it lapsed.
What actually prevents the complaint
Not a better date. Visibility.
The pattern in nearly every delay complaint is identical: a milestone passed, nobody told the homeowner, and the next contact was initiated by them. Homeowners tolerate long timelines they understand and escalate short ones they cannot see. This is the same mechanism described in why solar projects stall after the sale — the work produces no signal when it stops, because it never produced a signal when it started.
A status the homeowner can see without asking does more for this problem than any drafting, and it happens to be the same record that makes the lawful-excuse defence available.
Where Seamless Home fits
Seamless Home is a licensed contractor running design, permitting, engineering and project management as inside operations, with installation performed by vetted installing partners engaged as its subcontractors. On projects where it is the contractor of record, the completion date in the homeowner agreement is its obligation, and the third-party dependencies behind it are the ones it tracks.
Practically that means the date is built from jurisdiction cycle times rather than from a target, the dependencies are named rather than disclaimed, association and permit milestones are tracked to written outcomes, and the homeowner is not the party who discovers a slip. Coverage is confirmed per service area rather than promised as blanket availability.
Nothing here is legal advice. Whether dates are mandatory, what period defines abandonment, and what constitutes lawful excuse are all state law and vary.
The bottom line
Approximate start and completion dates are a mandatory term in most home improvement statutes, and omitting them makes the contract defective. Approximate is not unlimited: in several states, unreasonable delay without lawful excuse is statutory abandonment, a licensing violation that needs no proof of harm. Solar makes the requirement hard because most of the calendar belongs to a plan reviewer, a committee and a utility — so build the date from measured cycle times, name those dependencies specifically rather than disclaiming everything, move the date by a documented change rather than by drift, and give the homeowner a status they can see. Duration is survivable. Silence is what becomes a complaint.
Frequently asked questions
Does a home improvement contract have to state a completion date?
In most states, yes. Approximate commencement and completion dates are one of the recurring mandatory terms, alongside the contractor's licence details, the price, the payment schedule and the cancellation notice. A contract that omits them is defective, and the consequences follow the same pattern as any other omission — most often nothing until a dispute, sometimes an extended cancellation right, and in several states an impaired ability to enforce the contract. Writing 'to be determined' is not a way of satisfying the requirement; it is a way of not satisfying it while appearing to.
Is the date a guarantee?
No, and the statutory language is usually careful about that. The term is approximate dates, not guaranteed dates, and residential home improvement contracts do not normally carry the liquidated-damages machinery that utility-scale construction uses. What the date does is establish a reference point. It tells the homeowner what to expect, it starts the clock against which delay is judged to be reasonable or unreasonable, and it is the thing a licensing board will compare the actual timeline against if a complaint is filed.
What counts as abandonment?
It is defined by state statute and the formulations vary, but the common shape is failing to commence work within a stated period after the agreed start, or failing to complete within a reasonable time, without lawful excuse and without the homeowner's agreement. Several states set an explicit number of days of inactivity. The important features are that it is a licensing violation rather than only a contract breach, that it does not require the homeowner to prove financial loss, and that lawful excuse is a real defence — a project waiting on a plan review is not an abandoned project. What removes the defence is failing to document the excuse or failing to communicate it.
How do you write a realistic completion date for a solar project?
Build it from measured cycle times rather than from a target. For the specific jurisdiction: observed plan review turnaround, not the published one; the probability and cost of a correction cycle; whether an association review applies and when that committee meets; utility interconnection review time; inspection booking lead time; and the utility's permission-to-operate turnaround. Add the installer's current backlog from notice to proceed. The resulting figure is usually longer than a sales team would like and considerably shorter than the outcome when nobody plans for the correction cycle. Then name the dependencies in the contract as conditions rather than burying them in a disclaimer.
Can the contract just make everything conditional?
It can and should identify genuine third-party dependencies, but a blanket condition that excuses any delay for any reason is likely to be read as an attempt to avoid the requirement rather than as a term. The distinction that holds up is specificity: naming the plan review, the association approval, the interconnection review, the inspection and the permission to operate as conditions outside the contractor's control is accurate and defensible. Stating that completion is contingent on unspecified circumstances is neither, and it does not satisfy a statute that asked for a date.
What actually turns a delay into a complaint?
Silence, far more reliably than duration. Homeowners tolerate long timelines they understand and escalate short ones they cannot see. The pattern in almost every delay complaint is the same: a milestone passed, nobody told the homeowner, and the next contact was initiated by them. That is also what removes the lawful-excuse defence in practice — a contractor who can produce a dated record of a correction notice and the resubmission is describing a delay, while one who cannot is describing an absence. The operational fix is a status the homeowner can see without asking, not a better date.
Who is exposed when a project runs long, the seller or the installer?
Both, differently. The licensing exposure sits with the licence holder, which is normally the contractor of record. The commercial and reputational exposure sits with whoever promised the date, which is frequently the sales organisation, and the homeowner will call them regardless of who holds the paper. Financing adds a third dimension: credit approvals expire, lender stipulations go stale, and a long enough delay can require the whole approval to be re-run at numbers that have since changed. So the date is not only a compliance term — it is the term most closely coupled to whether the project funds at all.