Planning
A useful ADU construction-cost estimate is a range, not a single number
What an early ADU budget should include, what can move it, and how to test low, likely, and high costs.
Planning information only. Confirm local requirements and review financing, tax treatment, scope, and costs with the appropriate professionals.
Early in an ADU project, the construction-cost input is often a guess. Unfortunately, it may also be the assumption with the most power to change the result.
A single polished number can create false confidence. A planning range is more honest and more useful.
Why the range matters
A single total looks precise even when the site has not been inspected, utilities have not been located, and the scope is incomplete. A low, likely, and high range makes the uncertainty visible.
The range also makes the next step clearer. If the ADU only works at the low end, the project needs more validation before you rely on it. If it still works at the high end, you have more room for surprises.
Describe the project before estimating it
Useful early inputs include:
- ADU type, such as detached construction, an addition, or a conversion
- total conditioned square footage and unit layout
- number of stories and finish level
- city and state or ZIP code
- slope and construction access
- existing structure or demolition conditions
- sewer or septic conditions
- electrical capacity and utility-run distance
- whether design, engineering, permits, appliances, and landscaping are included
- an explicit contingency
These do not replace plans or a site visit. They make the first estimate less generic.
Separate what is included from what is unknown
A planning estimate should state its scope. It should also show:
- line items
- assumptions
- unknowns
- exclusions
- contingency
- source links
- confidence and the reason for that confidence
- the date of the estimate
Without those details, two estimates with the same total may describe very different projects.
Treat contingency as part of the model
Contingency is not a prediction that something will go wrong. It acknowledges that an early estimate cannot see everything. Site conditions, utility work, structural requirements, code changes, finish selections, and schedule changes can move cost.
Test more than one contingency level and keep it visible. Do not bury it inside a total that looks exact.
Put the range into the financial decision
The next step is not choosing the likely number and forgetting the rest. Run at least three evaluations:
- likely cost with expected rent and schedule
- high cost with conservative rent or a delay
- a revised case based on a real builder estimate
Watch how the cost changes peak cash required, monthly cash flow, and longer-term gain. This sensitivity check is more informative than debating whether the first estimate is “right.”
Turn a quote into a comparable budget
Ask each builder to mark every line as included, excluded, or an allowance. A low bid with substantial exclusions is not necessarily the low-cost option. Record who supplied the number, when it was prepared, whether the site was inspected, and what would cause a revision.
Keep financing costs and cash reserves visible beside the construction budget. Do not count the same contingency twice by adding it to a total that already includes it. Separate committed spending from optional finish upgrades so you can see which choices remain available if costs rise.
Take the uncertainty to the right person
A designer or contractor can help narrow scope and site unknowns. The utility provider can clarify connection requirements. The local authority can explain the applicable permit process; for California projects, the HCD program page is a starting point for current state guidance. None of these sources is a substitute for a project-specific bid.
Use the resulting low, likely, and high cases in a with-and-without ADU cash-flow comparison. This article describes a budgeting method, not an announcement of an automated estimating feature or a promise about what construction will cost.