Why the Lag Must Match the Decision
In longitudinal studies, covariates and treatments are recorded repeatedly. A data table may place a treatment and a covariate in the same row, or label a covariate as “lagged,” but neither convention establishes whether the covariate was measured before the treatment decision. The relevant question is more precise: what covariate information was measured before the particular treatment decision being studied?
This timing matters because a covariate that precedes a treatment decision may help explain why that treatment was chosen. A covariate measured after the decision cannot be treated as a pretreatment covariate for that decision merely because it appears in the same row or is called a baseline value. It may instead have been affected by treatment. Conversely, a value measured after one treatment can precede and help guide the next treatment decision.
Temporal order is necessary for deciding whether a measurement can serve as a pretreatment covariate, but it is not sufficient to establish that the covariate is a confounder. Confounding also concerns relationships among the covariate, treatment, and outcome. The narrower task here is to get the ordering right before making those further judgments.
Specify the Decision Time and the Measurement Window
Let \(d_t\) denote the time of the treatment decision \(A_t\). A covariate measurement may be a single observation at time \(m\), or a summary of observations collected over a window from \(s\) through \(e\). For a single observation, compare \(m\) with \(d_t\). For a window summary, compare the whole window with the decision time. A summary calculated from observations on both sides of the decision is not wholly pretreatment.
If a measurement is recorded as occurring at exactly the decision time, the available timestamps may not establish the order. Do not silently treat a tie as “before.” Check the study protocol or finer-grained timestamps; if the ordering remains unknown, mark it as unresolved. Similarly, a window that includes post-decision observations cannot be made pretreatment simply by shifting its label to an earlier row.
It is also useful to distinguish measurement time from recording or reporting time. A value measured before a decision may have been entered into a database afterward. If the target is the timing of the underlying covariate, use the measurement time. If the question is what information was available to the treatment decision-maker, also check when the value became available. These are different questions: a pre-decision sample whose result was not yet known may describe a pretreatment biological state without having guided that decision.
Worked Example: A Biomarker Before One Decision and After Another
Consider a hypothetical study of treatment decisions for asthma. The first dose decision, \(A_1\), occurs Monday at 09:00. A biomarker is measured Monday at 08:00, with a value of 18 units. A second dose decision, \(A_2\), occurs the following Monday at 09:00. The biomarker is measured Friday at 16:00, with a value of 24 units.
For \(A_1\), the Monday measurement time is \(08{:}00\), and the decision time is \(09{:}00\). Thus \(08{:}00 < 09{:}00\): the value of 18 units is pretreatment for \(A_1\), provided the measurement was available in time if the question concerns information used by the clinician.
For \(A_2\), the Friday measurement is after the first decision but before the second: Friday at 16:00 is earlier than the following Monday at 09:00. The value of 24 units is therefore post-treatment for \(A_1\) and pretreatment for \(A_2\). Calling it simply “post-treatment” without naming the decision would lose this distinction.
A table could label the Friday measurement as a value “during period 1.” That label does not make it pretreatment for \(A_1\); its timestamp shows otherwise. The same value can still be relevant as pretreatment information for \(A_2\).
Why Row-Based Lag Labels Can Mislead
A row index is an organizational choice, not a causal clock. In one study, \(L_t\) may mean a covariate measured immediately before \(A_t\). In another, the same symbol may denote a measurement collected at the end of the interval after \(A_t\). A lag label such as \(L_{t-1}\) is informative only when the study’s measurement schedule defines what that index means.
For a sequence of treatment decisions, the same measurement may occupy different positions relative to successive decisions. For example, a covariate measured after \(A_t\) but before \(A_{t+1}\) is post-treatment for \(A_t\) and pretreatment for \(A_{t+1}\). If \(A_t\) can affect that covariate, treating it as a baseline confounder for \(A_t\) misstates the ordering. Treating it as “post-treatment” for all later decisions makes the opposite mistake.
This ordering is one reason the earlier material on treatment-confounder feedback and lagged outcomes matters: treatment can affect a later covariate, which can then influence a subsequent treatment decision. Correctly locating the covariate in time does not itself determine the appropriate causal analysis. It prevents the more basic mistake of assigning it to the wrong side of a decision.
Worked Example: A Summary Window That Crosses the Decision
Suppose a hypothetical symptom score is measured daily, and a treatment decision \(A_t\) is made Wednesday at 12:00. The scores are 4 on Monday at 08:00, 6 on Tuesday at 08:00, 8 on Wednesday at 08:00, and 12 on Wednesday at 16:00. A table reports one four-observation average for the period.
The reported average is
But the Wednesday 16:00 measurement is after the Wednesday 12:00 treatment decision. Therefore the four-observation average includes a post-decision value and is not wholly pretreatment for \(A_t\).
If the intended covariate is the average of scores observed strictly before the decision, use the first three measurements:
The value 6 is the mean of the available pre-decision scores in this example. It is a different summary from 7.5, and it has a different temporal status. The difference between the averages does not show that treatment caused the later score; it shows why including that later score changes the covariate window and makes the summary partly post-decision.
A Practical Rule for Choosing Covariate Lags
Choose the lag by starting with the treatment decision, not by starting with the columns in a data table. The aim is to identify the covariate history that genuinely precedes that decision. Then record how the measurement window was constructed and whether the information was available at the relevant time.
Identify the actual time \(d_t\) at which \(A_t\) was assigned, initiated, or changed. Do not assume that a nominal visit date identifies the decision time.
Use the time the value was measured, and identify the start and end of any window used to summarize repeated measurements.
A value measured before \(d_t\) can be pretreatment for \(A_t\). A value measured after \(d_t\) is post-treatment for \(A_t\). A window that crosses \(d_t\) needs to be split, redefined, or explicitly treated as temporally mixed.
If the question concerns what guided the decision, verify when the value became available to the decision-maker as well as when it was measured.
State whether the value is pre- or post-treatment for \(A_t\), and repeat the assessment for later decisions rather than carrying the label forward.
This rule is a timing check, not a recipe for causal identification. A correctly timed covariate may still fail to control confounding, and a post-treatment measurement may have a role in a more involved longitudinal analysis. The rule simply prevents temporal misclassification before those questions are addressed.
Justification: Why an Overlapping Window Is Not Pretreatment
The classification follows from the meaning of “measured before the decision.” If a summary uses any observation taken after the decision, then the summary is a function of information that did not exist as an observed value before that decision. It cannot be described as a summary of only the pretreatment covariate history.
To see this, let \(W\) be a summary of measurements \(X_1,\ldots,X_k\), collected at times \(m_1,\ldots,m_k\). If at least one \(m_j\) satisfies \(m_j>d_t\), then \(W\) depends on a post-decision measurement \(X_j\). Therefore \(W\) is not determined solely by measurements with times earlier than \(d_t\). For an average, this is explicit:
This establishes the temporal classification; it does not establish that the treatment changed \(X_j\). The post-decision value could be affected by treatment, by other events, or by neither. The essential point is that it was measured too late to serve as a purely pretreatment summary for that decision.
Worked Example: The Same Weekly Value for Two Dose Decisions
In a hypothetical study, a clinician makes dose decisions every Tuesday at 10:00. A kidney-function measurement is collected Thursday at 15:00, two days after one decision, and is recorded as the covariate value for that week. The next dose decision is the following Tuesday at 10:00.
For the Tuesday decision just before the Thursday measurement, compare the times: Tuesday at 10:00 is earlier than Thursday at 15:00. The measurement is post-treatment for that Tuesday decision. It should not be relabeled as a pretreatment value for that decision merely because a data table places both in the same weekly row.
For the next Tuesday decision, Thursday at 15:00 is earlier than Tuesday at 10:00 in the following week. The same measurement is pretreatment for this next decision. If the value was entered into the clinical record on Friday, the measurement still precedes the next decision. Whether it could have guided the first decision is a separate question, and the timing shows that it could not have done so because it had not yet been measured.
Thus, the correct classification is not “Thursday values are always post-treatment” or “weekly values are always pretreatment.” It is “this Thursday value is post-treatment for the earlier Tuesday decision and pretreatment for the later Tuesday decision.”
Common Mistakes and Why They Matter
- Assuming the row order determines causal order. A covariate and treatment displayed in one row may have been measured hours or days apart. Check timestamps and protocol-defined windows.
- Calling a value pretreatment because it is labeled “lagged.” A lag is only meaningful relative to the decision time and the study’s indexing convention. Verify what the lagged value actually measures.
- Using the end of a window without checking its beginning. A window ending before a decision is wholly earlier; a window that starts before and ends after it contains measurements from both sides.
- Giving a covariate one permanent status. A variable can be post-treatment for one decision and pretreatment for the next. State the decision to which each label refers.
- Equating temporal precedence with confounding. “Measured before treatment” does not by itself mean “confounder.” The covariate must also have the relevant relationships to treatment and outcome.
- Assuming a post-decision value must be treatment-affected. Timing allows the possibility of a treatment effect on the value but does not prove one. Avoid inferring causal effects from timestamps alone.
A wrong lag can therefore change the causal interpretation of an adjustment variable. A genuinely pretreatment confounder may be mistakenly treated as post-treatment and omitted from a conventional adjustment set. Conversely, a treatment-affected covariate may be mislabeled pretreatment and adjusted for as if it preceded the treatment. The direction and size of any resulting bias are not determined by the timing error alone; they depend on the causal relationships and analysis.
Check Your Understanding
For each question, identify the relevant treatment decision before classifying the covariate.
- A covariate is measured at 08:30, and a treatment decision occurs at 09:00. What timing information would you check before calling it pretreatment?
- A two-day covariate average includes one measurement before and one after a treatment decision. Why is the average not wholly pretreatment for that decision?
- A measurement occurs after \(A_t\) but before \(A_{t+1}\). Classify it relative to each decision.
- A value is measured before a decision but entered into the database afterward. Which timestamp matters for the underlying covariate’s temporal status, and what additional time matters if you ask what information guided the decision?
- Why does establishing that a covariate preceded treatment not, by itself, establish that it is a confounder?