## TL;DR
No-news updates work when they say what you checked, not just that you are checking. "We reviewed the logs again this morning, no new errors since 2am, the team is still tracing the payment queue" beats "we are still working on it." Honest process detail is the news.

## The query

```text
how to write a status update when there is no news yet
```

## Use this when

- An investigation is dragging past your promised update time
- Engineering has nothing new to report
- A customer asked "any update" and the answer is honestly no
- You committed to daily updates on a long-running ticket

## Not for

- Incident status pages (those have their own templates)
- Updates where there IS news (just share the news)
- Proactive outreach with nothing pending
- Closing a ticket that stalled

## Steps

### 1. Say the no-news part in the first line

Dont bury it. "No fix yet" or "Nothing new to report" up front respects the reader's time and paradoxically builds trust, because it proves you will say it straight.

Expected output: the update's first sentence states the situation plainly.

### 2. Describe what happened since the last update

List the actual work: "The team re-ran the failed jobs at 9am, checked the database logs, and ruled out the payment provider." Activity is information even when the outcome is nothing.

Expected output: two to three concrete actions named with times.

### 3. Name what is happening next and when

"We are now tracing the queue worker" plus "I will update you by 5pm, with news or without." The next check-in time matters more than the next technical step.

Expected output: a named next step and a committed next-update time.

### 4. Keep it short enough to read on a phone

Three short paragraphs max. A no-news update that is long reads as defensive. Say the thing, say the work, say the next time. Done.

Expected output: updates under 120 words.

### 5. Send it on schedule even when it hurts

The promised update time is the product. Sending "nothing new" at 5pm as promised beats sending "fixed!" at midnight after silence. Reliability of communication is what the customer scores.

Expected output: zero missed update commitments on open tickets.

## Ready-to-use template

```text
Quick update: no fix yet, but here is where things stand.

Since this morning we [action 1 with time], [action 2 with time],
and ruled out [thing you ruled out]. So far [one-line current state].

Next, the team is [next step]. I will update you again by [time],
with news or without.
```

## Variant phrasings

### what to say when a ticket has no update

Steps 1 and 2. Lead with the honesty, follow with the work log.

### no news status update for customers

The template as-is. It works for tickets, email, and chat.

### how to update a customer when engineering is silent

Step 2 is the hard one here. If engineering gave you nothing, say what you asked them and when you will chase again. "I asked the team at 2pm and I am checking back at 4" is still process detail.

## Why it happens

Silence feels like abandonment to a waiting customer, and agents avoid no-news updates because they feel like admitting failure. But the customer is not scoring your progress, they are scoring whether anyone is paying attention. A scheduled, honest "nothing yet" proves attention. The updates that damage trust are not the empty ones, they are the missing ones.

## Edge cases

- The customer replies angrily to a no-news update: that is normal. Acknowledge, dont defend: "Fair, this is taking too long. Here is what I am doing about the wait itself."
- Engineering truly has no info for days: say that, and add what you are doing instead, like pulling in a second team or widening the search.
- The ticket is low priority and you want to stop updating: say so honestly. "This is queued behind higher-impact work, I will update you when it moves" beats silent neglect.
- Multiple customers asking about the same issue: write the update once, reuse it. Consistency across tickets prevents "but you told them something different."
- The news is bad (it will take weeks): deliver it plainly with the reason. Bad news with a reason preserves trust; vague delay destroys it.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Oloo7E-I45ANnPFyNUfKYg