Message guideFor care teamsAny market

What to tell a homeowner when the repair date is unknown

After handover, many repairs wait on someone else: a supplier, a contractor, a technical adviser or an access arrangement. This guide helps the care team give an honest update while the repair date is still open.

Short answer

A useful update names the case, states what you have verified and where it came from, says plainly what is still unknown, and names the next action and the person taking it. It ends with the date and time of the next update, which is a commitment your team controls. Give a repair date only once it is confirmed, or label it as an estimate and say what it depends on. “We do not know yet” is honest and useful when it comes with the action that will find out.

Separate the repair date from the next update

Three dates appear in almost every waiting case, and each commits the team to something different. When they blur together, an update turns into a promise nobody can keep.

Three dates and what each one commits you to
DateWhat it meansWhat it commits the team toHow to word it
Agreed visitA time when a contractor or the team will attend, agreed with whoever provides access.Attending, or rearranging with notice. It does not promise that the repair will be finished at that visit.“The fitter will attend on [date] between [time] and [time].”
Repair targetThe deadline your team set after reviewing the report, or a revised one. It may depend on parts or another party.Working towards it and saying early if it will move. Call it a target or an estimate until the work and the visit are confirmed.“Our target for the repair is [date]. It depends on [dependency].”
Next updateWhen you will next contact the homeowner, whether or not anything has changed.Contacting the homeowner by that time with the latest position. This one is entirely within your control.“I will update you by [next update date and time].”

While the repair date is open, the next update carries the weight, because it is the one commitment you can always keep. Give it a day and a time, not “soon” or “next week”. The aftercare process guide keeps the visit apart from the repair deadline for the same reason.

An unconfirmed target is not a guarantee. If a date depends on a delivery, a contractor or an assessment that has not happened yet, say so in the same sentence as the date.

Gather the facts before writing

Check the record and the dependency before you draft anything: the message can only be as accurate as what you have verified. Collect these points first.

  • Last verified information. What you know, who told you and when. “Contractor, by phone, 7 October” is more useful than “we understand”.
  • Pending dependency. The part, access arrangement, assessment or decision the work is waiting for.
  • Who is following up. The person or team chasing that dependency, and when they last did.
  • Effect on the homeowner. What they cannot use, or have to work around, while they wait.
  • Anything the homeowner needs to do. Confirm access, send a photo, keep an area clear. If nothing, say so.
  • Next update. A date and time the responsible person can meet.

Where a point is unknown, record it as unknown. Do not guess a delivery or attendance date to fill the gap; a guessed date is the one the homeowner will remember. Keep these facts under the same case reference in your defect register or portal, so the next person can see what was checked.

Give the homeowner one clear contact, even when a contractor holds the next action. The Canadian Home Builders’ Association’s guidance for new homeowners asks buyers to know their key contact and the response time they can realistically expect, and notes that builders may have to arrange service calls around subcontractors’ availability. That three-party dependency is exactly why the homeowner should not have to chase two people.

Four messages for work that is waiting

Each message below stands on its own, so you can paste it into an email, a portal message or a text. Replace the placeholders in square brackets. Each one relies on an internal action; send it only when that action is in place.

Waiting for a part

Message 1 · Waiting for a part

Case [case reference]: [known position: what has been ordered, and from whom]. The supplier has not yet confirmed delivery, so we cannot book the repair visit yet. I am sorry that [affected item] is still out of use. [Responsible contact] is checking with the supplier, and I will update you by [next update date and time], even if there is no news.

Behind it: the record names the supplier or contractor contact, the date of the last check and the next chase, scheduled before the promised update so there is something current to report.

Arranging access

Message 2 · Arranging access

Case [case reference]: the contractor is ready to [next action] and needs access to [area]. They can attend on [option 1] or [option 2]. Please reply with the option that suits you, or suggest another time, and tell us who will let them in. [Responsible contact] will then confirm the visit. If we have not agreed a time by [next update date and time], I will contact you again.

Behind it: the record shows who can agree access (the homeowner, a tenant or building management), the contact route offered and what still needs confirming. If no reply has arrived, the record says “access not yet agreed”, not “owner unresponsive”.

Seeking technical advice

Message 3 · Seeking technical advice

Case [case reference]: before deciding on the repair, we have asked [assessor or team] to assess [the question, for example where the water is coming from]. We do not have their view yet, so we cannot say what work is needed or when. [Next action, for example their inspection on a confirmed date]. I will update you by [next update date and time] with any findings or, if none have arrived, what we are doing to get them. I will give an expected reply date only if they have provided one.

Behind it: the record names the assessor, the exact question sent, the date it went and any reply date they have given. Do not offer a likely cause in the meantime; a guessed diagnosis is hard to withdraw.

Changing a repair target

Message 4 · Changing a repair target

Case [case reference]: we had aimed to complete the repair by [previous target]. We will not meet that date because [verified reason]. [Only if agreed: Our new target is [new date], which depends on [dependency].] The visit on [visit date] is [still going ahead / cancelled, and we will arrange a new one]. I am sorry for the change. [Responsible contact] is [next action], and I will update you by [next update date and time].

Behind it: the record shows who reviewed the change and why, which visit it affects, the revised plan and the date the homeowner was told. Keep the previous target in the history instead of overwriting it.

Improve a vague update

A useful update gives the homeowner a specific next step and a time for the next message. The fictional case below shows a first draft and the version that was sent.

Fictional example

Replacement kitchen drawer front

EX-U01

Example development · Apartment 7 · Kitchen

Report and assessment

  1. 1 OctOwner reports a split drawer front and sends two photos
  2. 2 OctTeam reviews the report and decides the front needs replacing
  3. 5 OctJoinery contractor is asked to source a matching front from the kitchen supplier

Waiting for the supplier

  1. 7 OctContractor confirms by phone that the front is ordered; delivery is not confirmed
  2. 8 OctCoordinator rewrites the first draft and sends the update, promising the next by 13 Oct, 12:00
  3. 13 OctDelivery still unconfirmed; update sent at 11:20, with the next due 16 Oct, 12:00

Fictional example. The case, dates and wording illustrate the method; they do not come from a real developer.

First draft (not sent)

Hi, just to let you know we are looking into this and will be in touch soon.

Sent version · 8 October

Case EX-U01, kitchen drawer front: the joinery contractor confirmed yesterday that a replacement front has been ordered from the kitchen supplier. The supplier has not yet confirmed a delivery date, so we cannot book the fitting yet. I am sorry the drawer is still damaged. The contractor is chasing the supplier, and I will update you by 12:00 on Tuesday 13 October, whether or not we have a date. If anything changes with the drawer in the meantime, reply to this message.

What the edit added, and what it left unknown
ElementFirst draftSent version
CaseNot namedReference and item
Verified position“Looking into this”Front ordered, confirmed by the contractor the day before
What is unknownNot statedThe delivery date, so no fitting date yet
Next action and whoNot statedThe contractor is chasing the supplier
Next update“Soon”12:00 on Tuesday 13 October
Homeowner’s partNoneReply if the situation changes

The sent version still has no arrival date, because nobody had one. It is more useful because the homeowner knows what is happening, who is doing it and when they will hear next.

What to do when the promised update is due

Send the promised update on time, even if nothing has changed. Work through these steps first.

  1. 1Check the record for the last verified position and what the previous message promised.
  2. 2Ask the dependency owner (supplier, contractor or assessor) for their current position, ideally the day before the update is due.
  3. 3Send a factual update: what you checked, what has or has not changed, and what happens next.
  4. 4Record the message, the new position and the next update you promised.

Someone has to own this. A spreadsheet or template will not prompt anyone, so the care team needs a named person who reviews open promises every working day, or a regular check built into its own routine. If homeowners use a homeowner portal, send updates there so the conversation stays with the case. Either way, record each promise next to the case.

Homeowner update record

Add one row each time you send an update, under the same case reference you use in your register or portal. Fill in “Actual update” when the promised update goes out, so a missed promise is visible at a glance. The example rows follow case EX-U01.

Case referenceMessage dateKnown positionSource and when checkedPending actionWaiting onResponsible personPromised next updateActual updateRepair target and status
EX-U018 Oct 2026Replacement drawer front ordered; delivery not confirmedJoinery contractor, phone, 7 OctGet a delivery date from the supplierKitchen supplier, via the joinery contractorCare coordinator13 Oct, by 12:0013 Oct, 11:20Not set; waiting for delivery
EX-U0113 Oct 2026Delivery still unconfirmed; supplier has not repliedJoinery contractor, email, 13 OctChase the supplier; book fitting once delivery is confirmedKitchen supplierCare coordinator16 Oct, by 12:00Not yet dueNot set; waiting for delivery

Scroll sideways to see every column.

Download the record (CSV)Opens in Excel, Numbers or Google Sheets. The example rows are fictional; delete them before use.

This is an editorial aid for any spreadsheet or system. It does not send reminders; someone in the team has to check the promised dates.

If the delay comes from a visit that did not go ahead, record the visit outcome first: see what to record when a repair visit fails.

When routine updates are not enough

Some changes need a decision, not another update. Review the case under your team’s process when any of these happens.

  • The effect on the homeowner changes, for example a room or appliance can no longer be used.
  • The condition gets worse, or the homeowner reports something new.
  • A commitment has been missed, including a promised update.
  • The homeowner, the contractor or your team disagree about what the work covers.

Communication is part of following a repair through, but it is not evidence that a condition is safe or resolved. A homeowner who stops replying has not necessarily accepted the delay.

In the UK, the New Homes Ombudsman Service reported in September 2026 that cases were more likely to escalate where developers’ responses had been slow or their communication weak. Treat that as context for taking updates seriously, not as proof that a well-written message prevents a dispute.

Where this applies

For customer care and aftercare teams at residential developers who coordinate repairs with contractors and suppliers after handover. The method works in any market and with any tool. It does not set response times or notice periods: check your contractual and statutory obligations, including warranty terms, with your adviser.

About the author · Toveta

Has built software for property developers since 2016, from CRM systems to listing portals.

Sources

  1. New Homes Quality Board. New Homes Ombudsman Service reports rise in complaint volumes and resolutions as awareness among customers continues to grow. United Kingdom, 4 September 2026; context on escalation, not evidence that a message prevents disputes
  2. Canadian Home Builders’ Association. After Buying a New Home. Canada; homeowner guidance on contacts and expectations, sets no update frequency

Spotted an error or an outdated source? Email info@wisemonks.com and we will correct the page.

Frequently asked questions

How often should we update a homeowner?

There is no single right interval. Agree a rhythm that suits the case and its effect on the homeowner, then meet every date you give. A clear next-update time matters more than a fixed frequency.

What if the contractor has not replied?

Tell the homeowner what you last verified and when, and what your team is doing to get an answer. Stay the single contact rather than passing the homeowner on to the contractor.

Can we give an estimated repair date?

Yes, if you label it as an estimate and say what it depends on. State what has been confirmed, such as the order, and what has not, such as delivery or the visit.

What if there is still no change at the next update?

Send the update anyway, with the date of your latest check, the dependency still outstanding and your next step to move it. If the same message keeps going out, treat that as a reason to review the case.

Choose what Toveta may use on this device. You can come back and change this at any time. The cookie policy lists each cookie.

NecessaryLoads the site securely and remembers this choice.
Always on
AnalyticsGoogle Analytics 4. Shows us how the site is used.
AdvertisingLinkedIn Insight Tag. Measures our LinkedIn campaigns.