
The short answer
Ask for a written explanation of the missed work and a recovery plan tied to remaining tasks. Document the pattern before making decisions about remedies or changing contractors.
In this guide
- Separate a missed day from an unresolved dependency
- Request a remaining-work plan
- Keep communications factual
- Escalate the conversation in stages
- Keep a delay log that can support a decision
- A useful written request for recovery information
- Follow through on the decision
- Decision checklist
- A recovery-plan conversation
Separate a missed day from an unresolved dependency
Ask what is preventing the next scheduled task: materials, inspection, an owner decision, trade coordination or crew availability. These are different problems with different solutions. Record the explanation and the expected next event. Avoid debating only whether a delay is reasonable; first establish what actually needs to happen for work to resume.
Request a remaining-work plan
Ask for a short sequence identifying the next tasks, who performs them and the dates the contractor currently expects. Include decisions or access you owe. A revised end date without intermediate commitments gives you little way to track progress. The plan should make it possible to see whether the next promised step happened and to update dependencies when it did not.
Keep communications factual
Write down promised attendance dates, actual attendance and meaningful work completed. Save texts and emails. A daily record does not need emotional commentary or speculation about other customers. Describe the effect on your household accurately, including inaccessible rooms or additional arrangements, and preserve receipts for relevant actual costs without assuming they are automatically recoverable.
Escalate the conversation in stages
Send the contractor a concise written summary and request a specific response. Refer to the contract’s notice and dispute provisions before formal action. If work appears abandoned or there are serious safety concerns, review CSLB’s complaint process and obtain advice about your circumstances. Do not assume hiring a replacement immediately or stopping every payment has no contractual consequences. See CSLB consumer guidance for the applicable official information.
Keep a delay log that can support a decision
Use a small table with date, planned task, actual activity, explanation received and next promised action. Include days when work proceeds normally, not only failures. A selective record can hide the true sequence and make a later discussion less useful. Note your own selection delays, access restrictions and requested changes alongside contractor-controlled events. Preserve the original messages rather than replacing them with a summary alone.
At the next project meeting, use the log to identify the current obstacle and ask who owns the next action. If the contractor promises to return on a date, request the intended task and crew rather than accepting a token visit as full recovery. If the response remains vague, state the question again in writing and review the notice process in the agreement. The goal is to decide on evidence whether the job is recovering, needs a revised plan or requires outside assistance. A calendar full of anger does less work than a clear chronology of commitments and results.
A useful written request for recovery information
A practical message identifies the last agreed task, the date it was expected and what remains incomplete. Ask for the reason, the next action, the person responsible and the current forecast. You can say that you need this information to plan access or temporary living arrangements without threatening a remedy you have not reviewed.
When the answer arrives, distinguish a firm commitment from a tentative estimate. Record the dependency attached to a tentative date. If delivery is the obstacle, ask what confirmation exists and whether unaffected work can proceed. If labor allocation is the issue, ask what work the returning crew will perform and how long it is expected to remain.
Review the response against the contract and your log at the next check-in. A revised schedule is useful only if it becomes the shared working plan. Repeatedly replacing one unsupported completion date with another does not improve your information. If communication continues to fail, the organized record will support a more informed discussion with an adviser or the appropriate complaint resource. It will not by itself establish which legal remedy is available, but it gives that review a factual starting point.
Follow through on the decision
Keep the current schedule somewhere both parties can identify. Label it with its issue date and retain earlier versions. If the contractor sends an informal update, ask whether it replaces the prior forecast or only describes one task. This avoids a later dispute about which completion date everyone was using.
Decision checklist
- Record the promised task, actual progress and explanation received.
- Ask who owns the next action and what event unlocks it.
- Request a remaining-work forecast rather than another unsupported finish date.
- Review contract notice provisions before choosing any formal dispute response.
A recovery-plan conversation
Hypothetical example. Suppose the painter cannot start because cabinet installation remains incomplete. Ask which cabinet items are outstanding, their delivery status, who will install them and when painting can reasonably follow. If the contractor instead says the crew is on another job, ask for a definite return commitment and the revised sequence. The written record should capture the actual explanation rather than a generic delayed label.
Related questions
Can I demand a penalty for every missed day?
That depends on the agreement and applicable law. Document the facts and obtain contract-specific advice rather than inventing a penalty after the event.
Does every delay mean abandonment?
No. Establish communication, activity and dependencies before applying that label.
Official sources
Why readers ask this question
These public discussions informed the topic. Individual experiences are not permit rules, verified prices or professional advice.