Reported Status Across Time

LESSON

Technical English: Verb Tenses and Engineering Status

020 20 min beginner

Reported Status Across Time

By the end of this lesson, you will be able to...

  • Convert a live status sentence into a reported status sentence.

  • Explain why is warming up often becomes was warming up after said.

  • Choose when to keep the original tense because the status is still current.

Idea in one sentence: Reported status separates what someone said earlier from what you know now, so the reader can see both the source and the time frame.

Core Insight

In the previous lesson, active voice helped you show who did what:

The gateway rejected the request.

Now the problem changes.

Sometimes you are not directly describing the system. You are reporting what another person, team, dashboard, or log message said earlier.

Original status at 09:10:

The cache is warming up.

Later update at 09:30:

The team said the cache was warming up.

The important change is small:

is warming up -> was warming up

This is reported status.

You are not saying, "I can prove the cache is warming up right now." You are saying, "At an earlier time, the team described the cache as warming up."

That distinction matters in technical work. It protects the reader from confusing a past report with current evidence.

The trade-off is precision versus simplicity. Reported status is more careful, but it adds one extra time layer. The reader has to track both the original event and the later report.

The Small Situation

Imagine a deployment channel during a slow rollout.

At 09:10, the platform team posts:

The cache is warming up.

At 09:30, you write an incident summary for the support team.

You could write:

The cache is warming up.

That sentence sounds current. It sounds like you know the cache is warming up now.

But maybe you have not checked the cache at 09:30. You only know what the platform team said at 09:10.

A safer sentence is:

The platform team said the cache was warming up.

Now the reader sees the source and the time distance.

This sentence does three jobs:

This is not just grammar polish. It is evidence hygiene.

Plain to Precise

Plain meaning:

Reported status means you repeat someone's earlier status in your current sentence.

In this scenario:

The platform team said at 09:10:

The cache is warming up.

You report at 09:30:

The platform team said the cache was warming up.

Technical name:

This is reported speech, sometimes called indirect speech. In technical updates, we can call it reported status because the thing being reported is a system state, symptom, plan, or observation.

The key mechanism is the time shift:

present continuous -> past continuous
is warming up -> was warming up

The shift does not mean the cache stopped warming up. It means the warming-up status was part of the earlier message.

The Naive Idea

The naive idea is:

Just copy the original sentence.

That can work when you quote exactly:

The platform team wrote, "The cache is warming up."

The quotation marks show that these are the team's exact words.

But most technical updates do not quote every message. They summarize.

Without quotation marks, copying the original tense can accidentally make the old status sound current:

The platform team said the cache is warming up.

This sentence can be correct if the cache is still warming up and you want to say the status remains true.

But if you only know what the team said earlier, it is safer to write:

The platform team said the cache was warming up.

The naive copy breaks because the reader cannot tell whether you are reporting old information or confirming current state.

Reported status gives the reader that separation.

The Reporting Mechanism

Use this small mechanism:

source + reporting verb + reported status

Example:

The team said the cache was warming up.

Source:

The team

Reporting verb:

said

Reported status:

the cache was warming up

The reporting verb matters.

said means someone communicated it.

The team said the cache was warming up.

reported sounds a little more formal and often points to an incident channel, ticket, or status page.

The team reported that the cache was warming up.

confirmed is stronger. It says the source checked and verified something.

The team confirmed that the cache was warming up.

Do not use confirmed just because it sounds professional. Use it only when there was real confirmation.

Small words carry evidence weight.

A Worked Status Timeline

Let's trace the status across time.

Input at 09:10:

Platform team: The cache is warming up.

Transition:

You write a summary at 09:30. You want to include the platform team's message, but you do not want to make a new claim about the current cache state.

Intermediate state:

You have an old source message. You do not yet have fresh evidence.

Decision:

Use reported status with a past reporting verb and a shifted tense.

Output:

The platform team said the cache was warming up.

Now compare the choices:

Original at 09:10 Report at 09:30 What the report means
The cache is warming up. The team said the cache was warming up. They described an ongoing state earlier.
The gateway rejected the request. The logs showed the gateway had rejected the request. The rejection happened before the log review.
We are deploying the worker. The release owner said they were deploying the worker. The deployment was in progress when they spoke.
The alert shows user impact. The on-call engineer said the alert showed user impact. The alert showed impact in that earlier report.

Notice the path:

original status -> later report -> shifted tense -> clearer evidence boundary

The naive failure is:

The platform team said the cache is warming up, so support told users the cache is warming up now.

That may be true, but the grammar hides a question:

Did anyone check the cache again?

If nobody checked again, the safer update is:

At 09:10, the platform team said the cache was warming up. We are checking whether the cache is still warming up now.

This version separates old report from current investigation.

When to Keep the Original Tense

Backshifting is common, but it is not automatic.

You can keep the original tense when the status is still true, still planned, or still important as a current fact.

Example:

The team said the cache is warming up.

This can be fine if you have fresh evidence or if the team is giving a current update.

Another example:

The status page says the API is degraded.

Here, says is present. You are pointing to a current source. The reported status can stay present:

The API is degraded.

Compare:

At 09:10, the status page said the API was degraded.

Now the source is in the past. The degraded state belongs to that earlier report unless you add current evidence.

The small question is:

Am I reporting an old message, or am I making a current claim?

Old message:

The team said the cache was warming up.

Current claim:

The team says the cache is warming up.

Both are useful. They do different jobs.

Reported Status and Evidence

Reported status is not only about people.

Tools can "say" things in technical English, but choose the verb carefully.

Good:

The dashboard showed that error rate was rising.
The logs showed the gateway had rejected the request.
The alert said checkout latency was above the threshold.
The status page reported that the API was degraded.

These sentences make the evidence source visible.

They also keep the time frame visible.

If the dashboard showed error rate was rising at 09:10, that does not prove error rate is rising at 09:30. It proves what the dashboard showed at 09:10.

This is why reported status is useful in incident timelines. It lets you write:

At 09:10, the dashboard showed that error rate was rising. At 09:18, the release owner paused the rollout. At 09:30, the team confirmed that error rate had returned to baseline.

Each sentence has a source, a time, and a status.

Lesson 021 will combine several tenses in one incident timeline. This lesson gives you the reporting tool you need before that.

Fast Conversion Frames

When you are tired during an incident, do not start from a grammar rule. Start from the original message and ask what kind of source you have.

For a team message:

Original: The cache is warming up.
Report: The team said the cache was warming up.

For a dashboard:

Original: Error rate is rising.
Report: The dashboard showed that error rate was rising.

For logs:

Original: The gateway rejected the request.
Report: The logs showed the gateway had rejected the request.

For a current status page:

Original: The API is degraded.
Report: The status page says the API is degraded.

The last example keeps present tense because the source is current: says.

This is the practical rule:

past source -> usually shift the status back
current source -> often keep the status current

The rule is not perfect, but it is a useful first pass. It keeps your update honest until you have better evidence.

That honesty matters when another team is making decisions from your summary.

Trade-offs and Limits

Reported status improves evidence clarity.

It helps when you are summarizing Slack messages, status pages, logs, dashboards, or handoff notes.

It costs a little extra attention because the reader must track two times:

It does not prove that the old status is still true.

You can see the boundary when the reader asks:

Is that still happening now?

If the answer is "we do not know yet," say so:

The team said the cache was warming up at 09:10. We are checking whether it is still warming up now.

If the answer is "yes, we have fresh evidence," make the current evidence visible:

The team said the cache was warming up at 09:10, and the dashboard still shows cache warmup traffic now.

The trade-off is useful. Reported status is more careful than a simple current claim, but it prevents old information from pretending to be fresh evidence.

Common Confusions

Confusion: Was Means the Status Is Finished

Why it is tempting:

Past forms often describe finished events.

Better model:

In reported status, was warming up can mean "this was the status in the earlier report." It does not always mean the warming finished.

The team said the cache was warming up.

The cache may still be warming up. The sentence simply does not claim that by itself.

Confusion: Said and Confirmed Mean the Same Thing

Why it is tempting:

Both verbs introduce information from a source.

Better model:

Said reports communication. Confirmed reports verification.

The team said the cache was warming up.
The team confirmed that the cache was warming up.

Use confirmed only when the team actually checked.

Confusion: Reported Status Is Only for People

Why it is tempting:

Grammar books often use people as examples.

Better model:

Technical sources can report, show, indicate, or log information.

The logs showed the gateway had rejected the request.
The dashboard showed that error rate was rising.

The source can be a person, a team, a dashboard, a log, or a status page.

Check Your Understanding

Check: You saw this message at 09:10: The cache is warming up. At 09:30, you do not have fresh evidence. Which report is safest?

A. The team said the cache was warming up.
B. The team said the cache is definitely warming up now.
C. The cache is warming up, no source needed.

Think first, then reveal.

Answer: A. It reports the earlier status without turning it into a fresh current claim.

Check: Which sentence uses a stronger evidence verb?

A. The team said the cache was warming up.
B. The team confirmed that the cache was warming up.
C. The team maybe had cache thoughts.

Think first, then reveal.

Answer: B. Confirmed means the team verified the status, so it is stronger than said.

Practice

Convert each original status into a reported status.

Original messages:

The cache is warming up.
The gateway rejected the request.
We are deploying the worker.
The alert shows user impact.

Possible reported versions:

The team said the cache was warming up.
The logs showed the gateway had rejected the request.
The release owner said they were deploying the worker.
The on-call engineer said the alert showed user impact.

Now add one current-evidence sentence:

The team said the cache was warming up at 09:10. The dashboard still shows cache warmup traffic now.

This small pair is powerful. The first sentence reports the earlier message. The second sentence tells the reader what you know now.

Daily Practice Lines

Repeat these three lines during the day:

The team said the cache was warming up.
The gateway rejected the request.
The request is rejected when the token is invalid.

The first line practices reported status.

The second line reviews active voice.

The third line reviews passive voice.

Resources

Key Takeaways

PREVIOUS Active Voice for Actions and Accountability NEXT Mixed Tenses in Incident Timelines