1308 S College St, Seattle, WA 98144, US
Editorial Desk: Mon - Fri 08:00 - 18:00 EST
Log Context Sheet

Why the Baseline Session Matters

You cannot prove something changed unless you wrote down what it looked like before.

2026-04-21 Marcus Vance 6 min read
CASE PROTOCOL CONTEXT REVIEW
REVIEW FOCUS: Reference Session Before Any Change
VEHICLE STATE: Fully stock, no pending modifications
SHEET OUTCOME: Baseline File Committed to Archive
Why the Baseline Session Matters
Executive Summary & Scope

The Reference Point Every Later Log Depends On

Every follow-up recording quietly assumes a baseline exists. When the intake arrived, the first session was logged while the car was still fully stock — not to find a problem, but to give every future file something to be compared against.

Key Facts & Session Baseline
  1. Session Purpose: Reference capture, not fault investigation
  2. Vehicle State: Stock intake, stock calibration, 91 octane
  3. Baseline Length: 3 drives across two days, mixed load
  4. Outcome: Baseline archived; intake change deferred until it existed
Reviewed against the Log Context Sheet standard
Examine Full Sheet
Log Context Sheet

1. The Question

Did the reported hesitation appear after the repair, or was it present before?

A workshop replaced a worn ignition component and the customer reported a mild hesitation two days later. The follow-up log showed a transient that looked suspicious — but there was no pre-repair baseline to compare it against. The entire dispute hinged on a recording that did not exist.

The dispute had two honest sides and no referee: the customer felt something new, the workshop saw nothing wrong in their work, and the log showed a transient that was real but unmoored. 'New' is a comparison claim, and there was only one side of the comparison.

Every post-repair question is secretly a two-session question. Whatever the vehicle did before the work is the denominator; without it, every after-log reads worst-case.

2. The Vehicle State

Mid-size SUV, 2017 model year, naturally aspirated V6, 112,000 km. Coil-on-plug ignition service performed. No baseline log was captured before the repair order was signed off.

Nothing about the pre-repair behaviour — trims, idle stability, transient response — was on file.

At 112,000 km, an engine has habits — learned adaptations, wear-in behaviours, quirks that never quite trigger codes. Those habits were exactly what the follow-up log was being asked to judge, and none of them were on record.

A baseline does not need the vehicle to be healthy; it needs the vehicle to be described. Even a flawed baseline — one that captures the pre-repair quirks honestly — is worth more than none.

3. The Conditions

The follow-up recording was taken on a humid morning during a cold commute. The owner had never logged the vehicle before the repair, so every session after it was the first of its kind.

'Different' is impossible to demonstrate without 'same.'

Cold humid mornings produce their own transients: enriched mixtures, higher idle targets, different adaptation behaviour. The hesitation the customer felt could be the repair, the weather, or their intersection — and the file alone could not say.

Conditions documentation would not have fixed the missing baseline, but it would have narrowed the suspects. As it stood, every plausible explanation remained on the table.

4. The Recorded Window

The recorded window covered the first twelve minutes after a cold start, including the hesitation event the customer described at a merge ramp.

The event was captured cleanly — the missing piece was everything that happened before the repair.

The twelve-minute cold-start window was well chosen for the symptom — it captured the merge-ramp event cleanly. The failure was temporal, not technical: the window opened after the repair, and the comparison it needed lived before it.

No window choice inside a single session can substitute for a second session. When the question is 'did this change?', the recorded window that matters most is often the one nobody opened.

5. The Observation

The transient in the follow-up log was real and repeatable within the session. What could not be established was whether it was new.

The workshop documented the repair carefully and documented the vehicle's prior behaviour not at all.

The transient repeated within the session, which proved it existed — and nothing more. Repeatability inside one log cannot distinguish 'new fault' from 'old habit,' because both look identical in isolation.

This is where unbaselined reviews stall: the data is real, the concern is legitimate, and the one piece of evidence that would resolve the dispute was never created.

6. The Follow-Up Question

Collect a fresh baseline on a second, comparable morning after re-learning adaptations — and start treating 'record the baseline first' as a step in the job, not an afterthought.

Two comparable sessions finally answered what one dispute could not.

The resolution came from reconstructing the comparison properly: a second cold morning, matched conditions, after adaptation re-learn — giving the 'after' side the honest baseline it should have had as a 'before.'

The procedure change that survived the dispute is the real lesson: 'record the baseline' is now a line item on repair orders, not a favour the customer might think to request.

What was happening when this data was recorded? If the sheet cannot answer that, the log is not evidence yet — it is just a file.
— Marcus Vance, LogContext Journal
Field Notes

Key Takeaways Box

01

You Cannot Skip the Baseline

Any “after” log compared against memory or another car is a guess. The baseline is the only honest reference.

02

Baseline Quality Sets the Ceiling

A rushed 5-minute idle capture cannot support a later comparison. The reference session deserves the same care as the event session.

03

Record More Than You Need

Baseline PIDs that look boring become critical later. Channels are cheap before the change and impossible to recover after.

Parameters

Session Specifications

Baseline Sessions 3 drives / 2 days
Vehicle Modifications None at capture
Ambient Range 18–21°C, dry
Follow-Up Action Log again after intake install
Peer Discussion

Comments & Verification Notes

No peer comments recorded yet. Be the first to submit a technical note.

Leave a Peer Review Comment

Thank you! Your comment has been submitted and is awaiting moderation.
Standard

Review Guidelines

Comments are reviewed against the Log Context Sheet standard. Please keep observations tied to the recorded window, vehicle state, and conditions — not to tuning advice.

Peer-Verified Workflow
Reference

A Log Context Sheet is the journal's standard review format: Question, Vehicle State, Conditions, Recorded Window, Observation, and Follow-Up Question. It keeps every conclusion tied to what was actually happening while the data was recorded.

Newsletter & Dispatch

Stay Informed on Verified Diagnostic Methodology

Receive quarterly white papers, protocol updates, and raw log interpretation frameworks directly from our engineering desk.