Until, Since, From, and For in Timelines

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

• Mark a timeline's starting point, duration, interval, and end boundary.

• Distinguish the open-ended view of since from the bounded range introduced by from.

• Write an incident update that tells a reader when a state began, how long work lasted, and when the team could close the incident.

Idea in one sentence: Since anchors a state to a starting point, from opens a named range, for measures duration, and until closes a continuing state at an end boundary.

Core Insight

At 09:00, a deployment increases traffic to a slow database. The queue grows until workers catch up. A useful incident update needs more than a list of timestamps:

The queue has grown since the deploy.
Workers processed the backlog for three hours.
They processed jobs from 09:30 until 12:15.
The incident stayed open until the queue returned to zero.

Since tells us where the current state began. For tells us how long an activity lasted. From ... until ... gives the activity's bounded interval. The last until marks the condition that allowed the incident to end. These phrases draw different lines on the same timeline.

The Small Situation: A Queue Incident

The payments queue has this evidence:

09:00  cache deploy starts
09:20  queue depth begins to rise
09:30  extra workers start
12:15  backlog reaches zero
12:30  incident is closed

The on-call engineer must answer four questions:

1. When did the current problem begin?
2. How long did the recovery work last?
3. What exact range did the extra workers cover?
4. What boundary allowed the team to stop watching the incident?

The first draft says:

The queue has grown from the deploy for three hours until recovery.

This combines a start point, duration, and endpoint without showing which phrase controls which part of the timeline. We can make each relation visible instead:

The queue has grown since the deploy.
The extra workers ran for three hours.
They processed jobs from 09:30 until 12:15.
The incident stayed open until the backlog reached zero.

The Naive Idea: Treat All Time Phrases as “From”

Spanish desde, durante, and hasta can tempt us to build every sentence with from, for, or until without checking the timeline's shape:

The queue has grown from the deploy.       # sounds incomplete for a state continuing now
The workers ran since three hours.         # mixes a start point and a duration
The incident stayed open for the queue was empty. # duration phrase before a clause

The repair starts with a question:

Where did the current state start?       -> since + starting point
What amount of time did it last?         -> for + duration
What range did the activity cover?       -> from + start + to/until + end
How long did it continue before stopping? -> until + end boundary

The Four Main Jobs

since: a starting point linked to the present state

Use since when a state or situation began at a past point and is still relevant now:

The queue has grown since the deploy.
The service has been slow since 09:00.
We have seen duplicate events since the migration.

Since answers “From what point has this state been true?” It commonly appears with the present perfect (has grown, has been, have seen) because the state reaches from the past toward the present.

The starting point can be a time, event, or clause:

The alert has remained open since 09:20.
The alert has remained open since the queue started growing.

Do not use since when you only want to name a completed range in the past:

The workers processed jobs from 09:30 to 12:15.

That range has two boundaries. Since 09:30 would make the reader expect a state that continues to the present.

from: the opening boundary of a named range

Use from to mark where an interval begins, usually with to or until to identify where it ends:

The extra workers ran from 09:30 to 12:15.
The report covers data from Monday until Friday.
Traffic was sampled from the first request to the final retry.

From presents a range as an object the reader can inspect. It can also introduce a source in movement (the request moved from the browser), but this lesson uses its temporal meaning.

Compare the incomplete and complete versions:

The workers ran from 09:30.          # the endpoint is missing or understood elsewhere
The workers ran from 09:30 to 12:15. # the interval is explicit

If the endpoint matters for an operational decision, state it. An unclosed from phrase leaves the reader guessing whether the activity is still running.

for: a measured duration

Use for before an amount or length of time:

The workers ran for three hours.
The queue remained above the limit for 20 minutes.
The team replayed the request for ten minutes.

For measures the size of the interval. It does not identify its starting clock point:

The workers ran for three hours.       # duration
The workers ran from 09:30 to 12:30.   # start and end

Both can describe the same activity, but they answer different questions. If the incident report must align with logs, use the range. If the reader only needs the cost or persistence, use the duration.

Remember the purpose meaning from lesson 007:

The dashboard is for the on-call review. # purpose
The dashboard was open for three hours.  # duration

The surrounding noun phrase tells the reader which for relation is active.

until: a continuing state up to an end boundary

Use until to say that an action or state continued and stopped at a point, event, or condition:

The incident stayed open until the backlog reached zero.
Workers retried the jobs until the database recovered.
The queue remained above its limit until 12:15.

The phrase after until can be a time (until 12:15), a noun phrase (until recovery), or a clause (until the backlog reached zero). The important idea is continuation up to the boundary.

Compare before from lesson 008 with until here:

Before recovery, the queue was still high.       # earlier than recovery
The queue stayed high until recovery.            # continued up to recovery

Before locates an event on one side of a reference. Until describes persistence that reaches the reference boundary.

Open-Ended and Bounded Timelines

This is the central contrast:

The queue has grown since the deploy.

The sentence looks from the starting event toward now. The current state is open-ended unless another sentence closes it.

The workers processed the backlog from 09:30 until 12:15.

This sentence gives a closed interval. The reader can place both endpoints on a log timeline.

The workers processed the backlog for three hours.

This sentence gives the interval's length, but not necessarily its clock position.

Use the form that matches the evidence the reader needs. An incident handoff may need all three:

The queue has grown since the deploy.
The extra workers processed the backlog from 09:30 until 12:15, for three hours.

The first sentence explains the current state. The second gives start, end, and duration for the recovery action.

A Worked Timeline: From Alert to Closure

Start with the input: the deployment event and the first queue-depth alert.

deploy at 09:00 -> queue rises at 09:20 -> workers scale at 09:30

Describe the current state:

The queue has grown since the deploy.

This tells the incident channel that the growth is connected to a start point and remains relevant now.

Add the bounded worker activity:

The extra workers processed jobs from 09:30 until 12:15.

Now the operation has a clear start and end. Add its cost:

They processed the backlog for three hours.

Close the incident with a condition rather than an arbitrary clock time:

The incident stayed open until the backlog reached zero.

The complete trace is:

input: deploy at 09:00
  -> since the deploy: queue growth remains visible
  -> from 09:30: extra workers begin recovery
  -> until 12:15: backlog processing continues to the end boundary
  -> for three hours: recovery duration is measured
output: close the incident when the backlog reaches zero

The naive summary would be:

The queue grew for the deploy until three hours.

It is unclear whether the deploy is a starting point, a duration, or a purpose. The repaired version gives every time phrase one job.

Three Records, One Timeline

Operational evidence often gives slightly different clocks. The deployment system may report a start at 09:00, the queue metric may show its first rise at 09:20, and the worker log may begin at 09:30. Do not flatten those events into one vague “start.” Keep their relations visible:

The queue has grown since the deploy at 09:00.
The queue has remained above its limit since 09:20.
The extra workers processed jobs from 09:30 until 12:15.
They ran for three hours according to the worker logs.

The first two since phrases attach different current states to different evidence points. The from ... until phrase describes the bounded worker activity, while for three hours reports its measured duration. If the clocks disagree, the sentence should preserve the disagreement until the team resolves it; precise prepositions should not manufacture certainty.

This is also why a timeline can contain several valid anchors:

The incident has been open since 09:20, but the recovery job ran from 09:30 until 12:15.

The incident and the recovery job are different objects with different temporal shapes.

Try changing only one anchor in this pair:

The service has been slow since the deploy.
The service was slow from the deploy until the rollback.

The first sentence presents slowness as a state that reaches the reporting moment. The second presents a finished interval with a start and an end. If the rollback has not happened yet, the second sentence would be premature; choose the open-ended form instead. A small change in preposition changes what the reader believes about the incident's current state.

Active Check: Choose the Timeline Shape

Check: The queue began growing at the deploy and is still above normal. Which sentence matches that evidence?

A. The queue has grown since the deploy.

B. The queue has grown for the deploy.

C. The queue has grown from three hours.

Think first, then reveal.

Answer: A. Since the deploy names the starting event of a state that reaches the present.

Check: The workers started at 09:30 and stopped at 12:15. Which sentence gives both boundaries?

A. The workers ran since three hours.

B. The workers ran for 09:30 until 12:15.

C. The workers ran from 09:30 until 12:15.

Think first, then reveal.

Answer: C. From ... until ... opens and closes the interval. For would measure its duration, not name the clock boundaries.

Common Confusions

since versus from

The service has been slow since the deploy.       # past start to now
The service was slow from 09:00 until 10:00.       # bounded past interval

Use since when the current state is the focus. Use from when the range itself needs two endpoints.

for versus since

The alert has been open since 09:20.  # start point
The alert has been open for 40 minutes. # duration

A report can include both if the reader needs to calculate or verify the interval.

until versus before

Before recovery, the queue was high.
The queue stayed high until recovery.

The first places a fact before an event. The second says the state continued to the event.

from versus the movement source

The request moved from the browser to the gateway. # spatial source
The report covers data from Monday to Friday.       # temporal start

The same word marks a source in different dimensions. The surrounding nouns and endpoint (to, until) tell the reader which map to use.

for purpose versus for duration

The dashboard is for the on-call review. # intended use
The dashboard was open for three hours.  # length of time

Do not select for by translation alone. Identify whether the phrase names a target or measures time.

Trade-offs and Limits

The central trade-off is temporal precision versus reading load. Adding since, from, until, and for lets an investigator align prose with logs, but four anchors can make a short update heavy. Include the start, end, or duration that changes the next decision; omit redundant measurements when the evidence is already obvious.

These forms also have limits:

• Since suggests a state that reaches the present, but the tense must support that interpretation.
• From without an endpoint can leave a range open or incomplete.
• For gives duration without a clock position; it cannot replace a required start or end timestamp.
• Until marks a boundary, but it does not prove that the boundary condition was actually observed.
• Temporal order and duration do not establish causation. Metrics, logs, and event records still have to support the incident explanation.

Use a closed range when auditability matters, an open-ended since statement when current status matters, and a duration when cost or persistence matters.

Transfer Challenge: Repair an Incident Timeline

An engineer writes:

The queue has grown from the deploy for two hours.
Workers have processed jobs since 09:30 until recovery.
The incident stayed open for the backlog reached zero.

Rewrite the update so it expresses:

1. queue growth beginning at the deploy and continuing to the present;
2. a worker interval with a start and end boundary;
3. the duration of that worker activity;
4. an incident boundary defined by a recovery condition.

Model answer:

The queue has grown since the deploy.
Workers processed jobs from 09:30 until recovery, for three hours.
The incident stayed open until the backlog reached zero.

The exact duration can change with the evidence. What matters is that since, from ... until, for, and the final until each describe a different part of the timeline.

Daily Practice Lines

Repeat these three lines during the day:

The queue has grown since the deploy.
Workers processed jobs from 09:30 until recovery.
The alert stayed open for three hours.

For spaced review, connect the timeline to lesson 008:

While the workers drained the queue, the incident stayed open until the backlog reached zero.

The sentence combines overlap (while) with the end boundary (until).

Resources

• [ARTICLE] Cambridge Dictionary Grammar - Reference for since, from, for, until, and time expressions.
• [ARTICLE] MDN HTTP Overview - Technical context for request events, retries, and operational timelines.
• [ARTICLE] Microsoft Writing Style Guide - Guidance for concise incident updates and explicit temporal boundaries.

Key Takeaways

• Use since for a starting point connected to a current state: has grown since the deploy.
• Use from to open a named range, usually with to or until to close it.
• Use for to measure duration, not to identify a start timestamp.
• Use until for an action or state that continues to an end boundary or recovery condition.
• Make the timeline as precise as the next operational decision requires, and keep evidence separate from grammar.