Remember, Forget, and Regret Patterns

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

• Classify remember, forget, and regret patterns by timeline and meaning.

• Distinguish a past action from a future obligation in deployment and postmortem notes.

• Write short technical sentences that say whether an action happened, was missed, or is being judged after the fact.

Idea in one sentence: With these verbs, the form after the verb changes the timeline: a memory of an action, a task still to do, or a judgment about an action already done.

Core Insight

The deployment checklist says:

Remember to rotate the key after the deploy.

The next morning, the team asks what happened. One engineer writes:

I remember rotating the key after the deploy.

These sentences contain the same technical action, rotate the key, but they place it at different points in time. The first sentence points forward from the reminder. The second points backward from the engineer's memory.

That difference matters in engineering communication. A checklist tells someone what still needs to happen. A postmortem describes what happened. A status message may also judge a past decision:

We regret disabling the alert during the deploy.

The words after remember, forget, and regret help the reader reconstruct the timeline. They are small grammar choices with a large practical effect.

The Small Situation

A team is deploying a new authentication service. The deploy has three important actions:

1. rotate the signing key after the new service is healthy;
2. confirm that the rollback command still works;
3. keep the expiration alert enabled until the deploy is complete.

At 14:00, before the deploy, the release owner posts:

Remember to rotate the signing key after the new service is healthy.

At 14:20, the service is healthy. The owner rotates the key. At 15:00, the team writes a short postmortem because one alert was disabled too early.

The team now needs to express four different meanings:

• a task was still in the future;
• an action happened and someone recalls it;
• a required action did not happen;
• a past action happened, but the team now considers it a mistake.

The naive idea is to treat doing and to do as interchangeable after these verbs. They are not interchangeable here. The choice changes what the reader believes about time and responsibility.

The Naive Idea

Compare these pairs:

Remember to rotate the key.
Remember rotating the key.

The first is a reminder. The rotation is a task that should happen later, or at least after the moment of the reminder.

The second is a report about memory. The rotation is already a past event, and the writer says that the event is in their memory.

Now compare forget:

We forgot to confirm the rollback command.
I forgot rotating the key during the last deploy.

The first sentence says the team failed to complete a required task. The second says the rotation happened, but the speaker does not remember doing it. The second meaning is possible, but it is less common and can sound awkward. In a formal postmortem, I forgot that I had rotated the key is often clearer.

The same action can therefore be present in two sentences while the event itself changes position:

future task -> remember to rotate
past memory -> remember rotating
missed task -> forget to rotate
past action not remembered -> forget rotating

What The Pattern Adds

In plain English, the pattern tells the reader which side of the action the writer is standing on.

Remember to do: keep a future task in mind

Plain meaning:

Do not lose this task before the right moment arrives.

In the deployment:

Remember to rotate the signing key after the new service is healthy.

The rotation has not been presented as complete. The sentence is useful in a checklist, a handoff, or a pull request comment.

Technical name:

Remember to do is a memory of an obligation or next action. The action is expected after the reminder.

Other examples:

Remember to re-enable the alert after the test.
Remember to record the migration version in the release note.
Remember to check the rollback command before closing the incident.

Remember doing: recall a past action

Plain meaning:

The action happened, and I can recall that event.

In the deployment:

I remember rotating the signing key after the new service was healthy.

This sentence belongs in a status update or an investigation. It does not ask anyone to rotate the key now. It reports a memory of a completed action.

Technical name:

Remember doing describes memory of a past experience or action.

Other examples:

I remember checking the rollback command before the deploy.
She remembers reviewing the alert rule with the on-call engineer.

Forget to do: fail to complete a task

Plain meaning:

The task was expected, but it did not happen because nobody kept it in mind.

In the deployment:

We forgot to confirm the rollback command.

The sentence says the confirmation did not happen. It does not say that the team confirmed it and lost the memory later.

Technical name:

Forget to do describes a missed obligation. This is the most useful forget pattern for checklists and incident notes.

Other examples:

The worker forgot to renew its lease.
We forgot to update the runbook after changing the flag.

Forget doing: lose the memory of a past action

Plain meaning:

The action happened, but the speaker no longer remembers doing it.

In the deployment:

I forgot rotating the key during the last deploy.

This can mean that the rotation happened but the speaker has no memory of the event. Because the form is less common, a clearer technical sentence is often:

I forgot that I had rotated the key during the last deploy.

Use forget to do when you mean that the task was missed. Use forget doing, or the clearer forget that I had done, only when the action happened but the memory is missing.

Regret doing: judge a past action negatively

Plain meaning:

The action happened, and now the speaker wishes it had not happened or sees it as a mistake.

In the postmortem:

We regret disabling the expiration alert during the deploy.

The alert really was disabled. The team is not announcing a future action. It is evaluating a past decision.

Technical name:

Regret doing describes negative judgment about a past action.

You may also see regret to say, regret to report, or regret to inform in formal messages:

We regret to report that the rollback did not complete.

That pattern is different. It introduces bad news that the writer is about to communicate. It does not mean that the writer regrets performing the report. For the deployment lesson, keep the main contrast clear: regret doing looks backward at an action; regret to report introduces information.

A Worked Deployment Timeline

Let us follow the same release from the reminder to the postmortem.

The input is one deployment checklist. Each pattern moves the reader to a different point on the timeline. The intermediate question is always the same:

Did the action happen?
If it happened, is the writer recalling it or judging it?
If it has not happened, is the writer giving a reminder or reporting a missed task?

The output is a sentence that carries its own time signal. That is more useful than a sentence that is merely grammatical.

So far, the key map is:

remember to do -> future obligation
remember doing -> memory of a past action
forget to do -> missed obligation
forget doing -> past action is not remembered
regret doing -> negative judgment about a past action

What This Changes In Technical Writing

Without this distinction, a release note can force the reader to guess:

Remember rotating the key.

Is this a reminder to rotate it, or a question about whether someone recalls the rotation? The sentence does not fit the intended checklist meaning.

For a checklist, write:

Remember to rotate the key after the deploy.

For a status report, write:

I remember rotating the key after the deploy.

For a missed step, write:

We forgot to rotate the key before the certificate expired.

For a postmortem judgment, write:

We regret delaying the rollback while we investigated the alert.

The pattern also makes ownership clearer. Remember to gives the reader a task. Forgot to names a missing action. Remember doing records a person's memory, which is useful evidence but not the same as a log entry. Regret doing records a judgment, not an objective system state.

Trade-offs and Limits

The main trade-off is temporal precision versus writing speed. This distinction buys temporal precision, but it costs a small amount of attention. The writer must decide whether the action is future, completed, missed, remembered, or judged.

It also does not prove that the action happened. If someone writes:

I remember rotating the key.

the sentence reports a memory. A deployment log or key-management audit is stronger evidence. Grammar can clarify the claim, but it cannot validate the system state.

The forget doing pattern has another boundary: it is grammatically possible but less natural in many technical contexts. Prefer forget to do for a missed task and forget that I had done when you need to say that a completed action is no longer remembered.

Finally, regret doing expresses a judgment. Different engineers may judge the same decision differently. In a postmortem, pair the sentence with evidence:

We regret disabling the alert because it delayed detection by eight minutes.

The signal at the boundary is the follow-up evidence: logs for whether an action happened, and an explicit reason for why a past decision is being criticized.

Common Confusions

Confusion: Remember to do means the action is already complete

Why it is tempting:

The sentence contains the action, so a learner may treat it like a status update.

Better model:

Remember to rotate puts the action in the task list. Use remember rotating to report a remembered past action.

Confusion: Forget doing and forget to do describe the same failure

Why it is tempting:

Both sentences contain forget, and both can sound negative.

Better model:

Forgot to confirm means the confirmation did not happen. Forgot confirming means the confirmation happened but is not remembered. When the second meaning matters, forgot that I had confirmed is often clearer.

Confusion: Regret to report means regret about a past report

Why it is tempting:

Regret usually carries a negative feeling, so the reader may connect it to an earlier action.

Better model:

Regret doing judges a past action. Regret to report is a formal way to introduce bad news now.

Check Your Understanding

Check: The release owner is writing a checklist item before the deploy. Which sentence fits?

A. Remember rotating the key after the deploy.
B. Remember to rotate the key after the deploy.

Think first, then reveal.

Answer: B. The key rotation is a future obligation, so the checklist uses remember to rotate.

Check: The key was rotated, and an engineer is reporting a memory of that event. Which sentence fits?

A. I remember to rotate the key after the deploy.
B. I remember rotating the key after the deploy.

Think first, then reveal.

Answer: B. Remember rotating looks backward at a completed action. The first sentence sounds like a present reminder or routine, not a report about a past event.

Check: The team did not confirm the rollback command. Which sentence is precise?

A. We forgot to confirm the rollback command.
B. We forgot confirming the rollback command.

Think first, then reveal.

Answer: A. The confirmation was a required task and it did not happen. The doing version would suggest that the confirmation happened but was not remembered.

Practice

Write one sentence for each situation. Keep the technical noun visible and choose the pattern from the timeline.

1. Before a migration, remind the owner to check the rollback script.
2. After the migration, report that you can recall checking the script.
3. Report that the team missed the step of updating the runbook.
4. Write a postmortem sentence saying that the team now judges removing the alert as a bad decision.
5. Rewrite this ambiguous sentence for a checklist: Remember checking the certificate expiry.

Model answer:

1. Remember to check the rollback script before the migration. This is a future task.
2. I remember checking the rollback script before the migration. The check happened and is remembered.
3. We forgot to update the runbook after the migration. The required update did not happen.
4. We regret removing the alert during the migration. The removal happened and is now judged negatively.
5. Remember to check the certificate expiry. The checklist needs a future obligation, not a memory of a past action.

A strong answer does three things:

• chooses to do for a future task or missed obligation;
• chooses doing for memory or judgment about a past action;
• makes the technical timeline visible in the surrounding words.

Daily Practice Lines

Repeat these short lines, then change one technical noun:

Remember to rotate the key after the deploy.
I remember rotating the key after the deploy.
We forgot to confirm the rollback command.
We regret disabling the alert during the deploy.
Try increasing the timeout before changing the client.

Try substitutions such as key -> certificate, rollback command -> migration check, or alert -> cache. Keep the meaning stable while the noun changes. The last line reconnects this lesson to the previous contrast: try increasing proposes an experiment, while these remember, forget, and regret patterns locate an action in time or evaluate it.

Connections

Lesson 006 used try doing and try to do to distinguish an experiment from an attempted goal. This lesson uses a related habit: ask what job the action has in the sentence before choosing the form.

The next lesson, Used To, Be Used To, and Get Used To, changes the focus from one event in a deployment timeline to past habits, present familiarity, and a process of adaptation.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Verb patterns - Compare verbs that take doing and to do with different meanings.
• [ARTICLE] Cambridge Dictionary Grammar: Infinitives - Review how infinitives express tasks, intentions, and formal announcements.
• [ARTICLE] Microsoft Writing Style Guide - Apply direct wording to checklists, status notes, and postmortems.

Key Takeaways

• Use remember to do for a future obligation or checklist task.
• Use remember doing for memory of an action that already happened.
• Use forget to do when a required task was missed; use forget doing carefully when the action happened but is not remembered.
• Use regret doing to judge a past action negatively; regret to report introduces bad news now.
• The patterns clarify a timeline, but logs and audit records are still stronger evidence than a person's memory.