Present Continuous for Live Incidents and Work in Progress

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

• write present continuous sentences for work that is happening now.

• separate stable system facts from live investigation, mitigation, and change.

• revise an incident update so the reader sees what is currently moving.

Idea in one sentence: Present continuous tells the reader that an action, investigation, or change is in progress now, not just normally true.

Core Insight

In lesson 001, you separated normal behavior from current state:

The worker runs every five minutes.
The worker is stopped.

In lesson 002, you used present simple for stable facts and ownership:

The API owns the order state.
The worker publishes billing events.

Now we need a third kind of present-time sentence:

We are investigating elevated latency.

This sentence is not a habit. It is not a stable system fact. It is live work. The team is doing something now.

That is the main job of present continuous in technical updates:

subject + am/is/are + verb-ing

Use it when the reader needs to see an action in progress:

We are investigating the error spike.
The team is rolling back the deploy.
The worker is retrying failed jobs.
The database is recovering after the restart.

The grammar makes movement visible.

The Small Situation

Imagine an incident channel at 10:12.

Users are seeing slow checkout requests. The dashboard shows elevated latency. The API still owns the order state. The worker still publishes billing events. Those stable facts did not change.

But the team is active:

We are investigating elevated latency.
Sofia is checking the database connection pool.
The platform team is rolling back the last deploy.

These sentences answer a different question from the previous lessons.

They do not answer:

What does the system normally do?

They do not answer:

Which component owns the state?

They answer:

What is happening now?

That question matters during incidents because people need to coordinate. If one person is checking the database, another person should not silently do the same work. If the team is rolling back, support can tell users that mitigation is in progress. If nobody is investigating, the update should not pretend that work is happening.

The Naive Idea

A naive idea is:

I can use present simple for any present-time update.

That creates confusing incident messages.

Compare these two sentences:

We investigate elevated latency.
We are investigating elevated latency.

The first sentence sounds like a habit or policy. It means:

When latency is elevated, our team investigates it.

That may be true, but it does not tell the reader that work is happening now.

The second sentence says:

The investigation is active now.

That is the sentence you usually want in a live incident update.

The same contrast appears with system actions:

The worker retries failed jobs.
The worker is retrying failed jobs.

The first sentence describes normal worker behavior. The second sentence describes a current action. The queue may be draining now.

Plain to Precise: Work in Progress

Plain meaning:

Work in progress means an action has started and has not finished yet.

In this scenario:

We are investigating elevated latency.

Technical name:

This is present continuous. It uses am, is, or are plus an -ing verb.

Plain meaning:

A live incident update tells other people what is happening now during a problem.

In this scenario:

The team is rolling back the deploy.

Technical name:

This is also present continuous. It shows an active mitigation, not a stable design fact.

The important question is:

Is this action currently in progress?

If yes, present continuous is usually a good choice.

A Worked Incident Timeline

Look at one incident update sequence.

The input is evidence from the incident: metrics, assignments, deploy state, and queue depth.

The transition is your question:

Is the action still happening now?

The intermediate state is the sentence choice:

• present simple for habits and stable facts
• present continuous for active work
• state language for current condition

The output is an update the team can coordinate around.

The naive failure is leaving the update too general. "We investigate latency" may describe a team habit, but it does not tell anyone what is happening in this incident.

What Present Continuous Makes Visible

Present continuous is useful because it shows movement.

It can show investigation:

We are investigating elevated latency.
Mina is comparing API logs with database metrics.
The support team is collecting affected user examples.

It can show mitigation:

The team is rolling back the deploy.
The worker is retrying failed jobs.
The database is recovering after the restart.

It can show temporary change:

We are routing traffic away from us-east-1.
The cache is warming after the flush.
The deploy pipeline is waiting for manual approval.

It can show coordination:

Alex is updating the status page.
Sofia is checking the connection pool.
The platform team is watching error rate.

The sentence does not need to be long. It needs one visible actor, one am/is/are, and one useful -ing action.

The Update Shape: Actor, Action, Evidence

A strong live update often has three pieces:

actor + present continuous action + evidence or target

The actor says who is doing the work:

We are investigating elevated latency.
Sofia is checking the database connection pool.
The platform team is rolling back the deploy.

The action says what is moving:

investigating
checking
rolling back
retrying
watching
routing

The evidence or target says where the work is aimed:

elevated latency
the database connection pool
the last deploy
failed jobs
error rate
traffic away from us-east-1

This shape prevents a common weak update:

We are working on it.

That sentence is sometimes acceptable as a quick acknowledgement, but it does not help the team coordinate. It hides the action and the target.

Prefer:

We are investigating elevated latency in checkout.
Sofia is checking database wait time.
The platform team is watching error rate during the rollback.

These sentences are still short, but they are more useful. They tell the reader who is active, what is happening, and where to look for the next update.

This does not mean every update needs a person name. Sometimes the actor is a component:

The cache is warming after the flush.
The worker is retrying failed jobs.
The deploy pipeline is waiting for approval.

The same pattern works. Something is in motion now.

When the Sentence Should Change

Present continuous is temporary. That is part of its meaning.

During a live incident, keep checking whether the action is still true:

We are investigating elevated latency.

This is useful while the investigation is active.

When the team finds the cause, change the sentence:

We found that database wait time increased after the deploy.

When mitigation starts, use present continuous again:

We are rolling back the deploy.

When mitigation finishes, change the sentence again:

The rollback is complete.

This habit keeps the update honest. It also protects the reader from old information. A stale present continuous sentence can be misleading because it still sounds alive.

A Tiny Decision Test

Before writing the sentence, ask:

Would this still be true as a runbook fact next week?

If yes, use present simple:

The worker retries failed jobs.

Now ask:

Is someone or something doing this right now?

If yes, use present continuous:

The worker is retrying failed jobs.

This test is small, but it prevents many confusing status updates.

Common Confusions

Confusion: Present continuous always means something is broken

Why it is tempting:

Many incident updates use present continuous because incidents contain live work.

Better model:

Present continuous means the action is in progress. The action may be good, bad, neutral, planned, or unexpected:

The team is deploying the fix.
The cache is warming.
We are testing the rollback plan.

The tense shows activity, not automatically danger.

Confusion: Present simple and present continuous are interchangeable

Why it is tempting:

Both can talk about present time.

Better model:

They answer different questions:

The worker retries failed jobs.

This describes normal behavior.

The worker is retrying failed jobs.

This describes work happening now.

During an incident, the difference changes what the reader believes.

Confusion: Every -ing sentence is present continuous

Why it is tempting:

The -ing form is visually obvious.

Better model:

Present continuous needs am, is, or are plus the -ing verb:

We are investigating.
The worker is retrying.
The teams are coordinating.

Without am/is/are, the sentence may be incomplete:

We investigating elevated latency.

That sentence is missing are.

Check Your Understanding

Check: Which sentence says the work is happening now?

A. We investigate elevated latency. B. We are investigating elevated latency. C. The API owns the latency dashboard.

Think first, then reveal.

Answer: B. are investigating shows live work in progress. A sounds like a general habit. C is an ownership fact.

Check: The rollback has finished. Which update should you avoid?

A. The rollback is complete. B. The team is rolling back the deploy. C. Latency is back to normal.

Think first, then reveal.

Answer: B. Present continuous says the rollback is still in progress. If the rollback is complete, use a completion sentence instead.

Trade-offs and Limits

Present continuous helps because it makes live work visible. It reduces coordination confusion during incidents, deploys, investigations, and migrations.

The trade-off is that it creates an expectation of current activity. If you write We are investigating, the reader believes someone is actively working on the problem now. Do not use it to sound reassuring if nobody is assigned.

It also does not prove progress. This sentence:

We are investigating elevated latency.

does not mean the team has found the cause. It only says the investigation is active. Add evidence when you have it:

We are investigating elevated latency. Database wait time increased after the 10:05 deploy.

You can see the boundary when the action has stopped, finished, or become a stable fact:

The rollback is complete.
The worker runs every five minutes.
The API owns the order state.

Those sentences need other patterns. Present continuous is for the moving part.

Practice

Revise each update so the time frame is clear.

1. We investigate the error spike. The team is working on it now.
2. The platform team rolls back the deploy. The rollback is in progress now.
3. The worker retries failed jobs. You are describing normal worker behavior in a runbook.
4. Sofia checks database metrics. Sofia is doing this now during the incident.

Model answers:

1. We are investigating the error spike.
2. The platform team is rolling back the deploy.
3. The worker retries failed jobs.
4. Sofia is checking database metrics.

Notice that number 3 stays present simple. Not every technical sentence should become present continuous. Choose the tense from the reader's question.

Daily Practice Lines

Say or write these lines during the day:

We are investigating elevated latency.
The API owns the order state.
The worker runs every five minutes.

Then replace one action:

investigating -> rolling back -> checking -> retrying -> watching -> routing

Keep the actor visible. Keep am/is/are before the -ing verb. Keep the sentence honest about whether the action is still happening.

If the action finishes, write a new sentence instead of leaving the old one in place. Technical status ages quickly, and present continuous ages fastest. That is why live updates need frequent small corrections. Old action words can create fresh coordination mistakes.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Present continuous
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/present-continuous-i-am-working
  • Focus: Notice how am/is/are + -ing marks actions happening around now.
• [ARTICLE] Cambridge Dictionary Grammar: Present simple
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/present-simple-i-work
  • Focus: Compare stable facts and habits with present continuous actions.
• [REFERENCE] Microsoft Writing Style Guide: Be clear and concise
  • Link: https://learn.microsoft.com/en-us/style-guide/welcome/
  • Focus: Use direct updates that tell the reader what is happening and what is complete.

Key Takeaways

• Use present continuous for live work: We are investigating elevated latency.
• Use am/is/are + -ing when an action is currently in progress.
• Do not use present continuous after the work is complete.
• During incidents, present continuous helps the team see who is doing what now.