State Verbs for Metrics, Config, and Knowledge

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

• choose state verbs for metrics, config, and knowledge in technical updates.

• explain why shows, contains, needs, and knows usually do not need present continuous.

• revise a live incident update so it separates evidence from work in progress.

Idea in one sentence: State verbs describe what the system, dashboard, config, or team has as a condition or fact, not an action currently moving.

Core Insight

The previous lesson used present continuous for live work:

We are investigating elevated latency.
The platform team is rolling back the deploy.

Those sentences show movement. Someone is doing something now.

But not every present-time sentence should move.

Look at this update:

The dashboard shows a spike in errors.

The dashboard is not actively "showing" in the same way a team is actively investigating. The sentence describes evidence that is visible now. It is a state or condition.

That is why technical English often uses simple present with state verbs:

The dashboard shows a spike in errors.
The config contains the old endpoint.
The service needs a restart.
The team knows the likely cause.

These sentences are about what is true, visible, known, present, or needed. They help the reader inspect the situation without pretending that every noun is performing an action.

The Small Situation

Imagine the same checkout incident from lesson 003.

At 10:12, users report slow checkout. At 10:15, the team starts investigating. At 10:19, the team starts rolling back the deploy.

During the incident, you also need to report evidence:

The dashboard shows a spike in errors.
The config contains the old database host.
The logs include timeout errors.
The rollback needs manual approval.

These sentences are not live work. They are observations and conditions.

Now compare them with live work:

Sofia is checking database metrics.
The platform team is rolling back the deploy.
We are watching error rate.

The difference matters. Evidence tells the team what is visible. Work-in-progress tells the team what is being done.

If you mix them, the update becomes odd:

The dashboard is showing a spike in errors.
The config is containing the old database host.

The first sentence is possible in casual English, but it often sounds heavier than needed in a technical status update. The second sounds wrong because contain is a state verb. A config contains a value; it is not "containing" as an active task.

The Naive Idea

A naive idea is:

If the information is current, I should use present continuous.

That idea helped in lesson 003, but it breaks here.

Current does not always mean moving.

The metric is current:

The dashboard shows elevated latency.

The config is current:

The config contains the old endpoint.

The team's knowledge is current:

The team knows the likely cause.

But these are not actions in progress. They are states.

So the better question is:

Is something happening, or is something true?

If something is happening, present continuous may fit:

We are investigating elevated latency.

If something is true, visible, present, known, or needed, a state verb often fits:

The dashboard shows elevated latency.

Plain to Precise: State Verbs

Plain meaning:

A state verb describes a condition, relationship, possession, knowledge, need, or appearance.

In this scenario:

The dashboard shows a spike in errors.

Technical name:

Shows is a state-like verb in this update. It tells the reader what evidence is visible.

Plain meaning:

A moving action describes work that is happening now.

In this scenario:

Sofia is checking database metrics.

Technical name:

This is present continuous. It uses is checking because checking is active work.

The useful distinction is not "now versus not now." The useful distinction is:

state versus activity

A Worked Incident Update

Here is a rough update:

The dashboard is showing errors. The config is containing the old endpoint. We investigate it.

The reader can guess the meaning, but the time frames are messy.

Now trace the update step by step.

Input:

metrics + config value + team action + approval requirement

Transition question:

Is this information a state, or is it work in progress?

Intermediate state:

• use simple present for visible evidence and conditions
• use present continuous for active work

Output:

The dashboard shows a spike in errors. The config contains the old endpoint. We are investigating the config change. The rollback needs manual approval, and Alex is requesting it from the release owner.

The naive failure is treating every current detail as an is ...ing sentence. That makes state sound like motion and makes the update harder to scan.

Combining the First Four Patterns

At this point, you have four useful present-time tools.

First, you can describe normal behavior:

The worker runs every five minutes.

Second, you can describe stable ownership:

The API owns the order state.

Third, you can describe live work:

We are investigating elevated latency.

Fourth, you can describe visible evidence or a condition:

The dashboard shows a spike in errors.

Real status updates often need more than one of these at the same time.

Here is a rough update:

The worker runs every five minutes. The dashboard shows errors. We are investigating. The config contains the old endpoint.

This is mostly clear, but it still feels like a pile of facts. A better update orders the sentences by what the reader needs first:

The dashboard shows a spike in checkout errors. We are investigating the config change. The config contains the old endpoint, and the API owns the order state.

The first sentence gives evidence. The second sentence gives live work. The third sentence gives a relevant condition and a stable ownership fact.

This order helps because the reader first sees the signal, then the action, then the system context.

You can also write a calmer runbook sentence:

The API owns the order state. The worker reads that state and publishes billing events. The dashboard shows billing error rate.

That sentence does not describe an incident. It describes how the system normally fits together.

The words are simple, but the time frames are different. That is the point. Good technical English lets the reader see whether each sentence is about design, evidence, state, or live work.

When you revise a status update, do not ask only "Is this grammatically correct?" Ask:

What job is this sentence doing?

If the job is system design, present simple facts help. If the job is live coordination, present continuous helps. If the job is evidence, state verbs help. If the job is current condition, is healthy, is blocked, or a similar state sentence may help.

This gives you a small editing loop:

1. Find the technical noun.
2. Decide the sentence job.
3. Choose the verb pattern.
4. Remove words that do not change the reader's decision.

The trade-off is that you may write two or three short sentences instead of one impressive long sentence. In incident work, that is usually a win. Short sentences let each time frame stay clean.

One quick test helps:

Can the subject choose, move, check, retry, roll back, or request something?

If yes, an action pattern may fit:

Sofia is checking the dashboard.

If no, a state verb may fit:

The dashboard shows a spike.

The dashboard provides evidence. Sofia performs the action. That difference is small, but it makes the update easier to trust. It also helps the next responder decide whether to inspect data or coordinate people. Good status language points attention at the right kind of work.

Common State Verbs in Technical Updates

Use shows for visible evidence:

The dashboard shows a spike in errors.
The graph shows higher database wait time.
The alert shows real user impact.

Use contains or includes for contents:

The config contains the old endpoint.
The logs include timeout errors.
The response contains an empty user id.

Use has for possession or current condition:

The service has three unhealthy pods.
The request has a missing tenant id.
The queue has many failed jobs.

Use needs for requirements:

The rollback needs manual approval.
The worker needs a restart.
The migration needs a smaller batch size.

Use knows, sees, or believes for team knowledge, but be careful:

The team knows the likely cause.
Support sees reports from three customers.
We believe the deploy changed the connection pool behavior.

Believe is weaker than know. Use it when the evidence is not final.

Common Confusions

Confusion: Is showing is always wrong

Why it is tempting:

This lesson says shows is often better for dashboards and evidence.

Better model:

Is showing can be natural when you want to emphasize temporary behavior:

The dashboard is showing old data after the cache flush.

But for a normal evidence sentence, simple present is cleaner:

The dashboard shows a spike in errors.

The trade-off is weight. Present continuous can add temporary emphasis, but it can also make a simple evidence sentence feel noisy.

Confusion: Know and believe mean the same thing

Why it is tempting:

Both describe what is in someone's head.

Better model:

Use know when the evidence is strong:

We know the rollback reduced error rate.

Use believe when the evidence is partial:

We believe the config change caused the timeout spike.

This helps avoid overclaiming during an incident.

Confusion: Every state sentence is safe

Why it is tempting:

State verbs sound calm and factual.

Better model:

A state sentence can still be wrong, stale, or too strong. Add evidence or a time marker when needed:

The dashboard currently shows a spike in errors.
The latest logs include timeout errors.
We believe, but do not yet know, that the config change caused the spike.

Check Your Understanding

Check: Which sentence is the clearest evidence update?

A. The dashboard is showing a spike in errors. B. The dashboard shows a spike in errors. C. The dashboard is investigating a spike in errors.

Think first, then reveal.

Answer: B. Shows reports visible evidence directly. A can be possible, but it is heavier. C is wrong because the dashboard is not investigating.

Check: Which sentence should use present continuous?

A. The config contains the old endpoint. B. The rollback needs manual approval. C. Alex is requesting approval from the release owner.

Think first, then reveal.

Answer: C. Alex is doing an action now. A and B describe states.

Trade-offs and Limits

State verbs help because they make evidence, contents, needs, and knowledge easy to scan. They keep the update calm and direct:

The dashboard shows a spike.
The config contains the old endpoint.
The rollback needs approval.

The trade-off is that state verbs can sound more certain than your evidence supports. If the evidence is weak, do not hide uncertainty:

The logs suggest a timeout problem.
We believe the config change caused the spike.

This lesson does not mean present continuous is forbidden with every state-like verb. Sometimes you may emphasize temporary behavior:

The dashboard is showing stale data after the cache flush.

But use that extra weight on purpose. If the sentence only reports evidence, simple present is usually clearer.

You can see the boundary by asking:

Am I reporting what is visible or true, or am I reporting what someone is doing?

Practice

Revise each update.

1. The config is containing the old endpoint.
2. The dashboard is showing a spike in errors.
3. We know the deploy caused the issue. The evidence is still partial.
4. Alex requests approval now. Alex is actively doing it in the incident.

Model answers:

1. The config contains the old endpoint.
2. The dashboard shows a spike in errors.
3. We believe the deploy caused the issue.
4. Alex is requesting approval now.

Your answer may include more context, but it should keep the state/activity boundary clear.

Daily Practice Lines

Say or write these lines during the day:

The dashboard shows a spike in errors.
We are investigating elevated latency.
The API owns the order state.

Then replace one state verb:

shows -> contains -> includes -> has -> needs -> suggests

Keep evidence as evidence. Keep active work as active work. Do not make every current detail an is ...ing sentence.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: State verbs and action verbs
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/state-verbs-and-action-verbs
  • Focus: Compare verbs that describe states with verbs that describe actions.
• [ARTICLE] Cambridge Dictionary Grammar: Present simple
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/present-simple-i-work
  • Focus: Notice how present simple describes facts and states.
• [REFERENCE] Microsoft Writing Style Guide: Be clear and concise
  • Link: https://learn.microsoft.com/en-us/style-guide/welcome/
  • Focus: Prefer direct evidence sentences that help the reader inspect the situation.

Key Takeaways

• Use state verbs for evidence, contents, needs, and knowledge: shows, contains, has, needs, knows.
• Use present continuous for active work: We are investigating elevated latency.
• Do not force every current detail into is ...ing.
• Choose careful knowledge verbs: know for strong evidence, believe for partial evidence.