Tail: Log Print Footer Data, Calibration Records, and WCSB Log Quality Control

The tail is the last page or pages of a wireline or logging-while-drilling print, the section appended at the end of the curve display that carries the supporting information about the well, the recording parameters, and the calibration of the measurements. Where the main body of a well log shows the depth tracks and the petrophysical curves such as gamma ray, resistivity, density, and neutron porosity, the tail is the documentation that proves those curves can be trusted. A complete log tail typically records the well identification and legal location, the operator and logging contractor, the run number and the logged interval with its top and bottom depths, the casing and bit sizes, the mud type, weight, resistivity, and temperature at measured points, the maximum recorded temperature, the depth reference and its elevation, the tool string serial numbers and the spacing of each sensor, the logging speed, the time-since-circulation, and most importantly the before-survey and after-survey calibration data for each tool. Those calibrations, the shop master calibration, the wellsite before calibration, and the after calibration run when the tools come back to surface, let a petrophysicist verify that a density tool was reading a known limestone or aluminum standard correctly, that a gamma ray tool matched its reference source, and that no drift occurred over the run. In the Western Canadian Sedimentary Basin, where decades of logs across the Cardium, Viking, Mannville, and Montney are correlated well to well, the tail is the audit trail that lets an analyst decide whether a thirty-year-old density log can be compared directly against a modern one or whether an environmental correction is needed. The tail is also where regulatory and contractual metadata lives. Alberta Energy Regulator submission requirements, governed historically under requirements that flow from the Oil and Gas Conservation Rules and modern digital submission standards, depend on the header and tail content being complete and accurate, and the LAS (Log ASCII Standard) digital file mirrors much of this tail information in its parameter and well-information sections. A log delivered without a readable tail, or with missing after-survey calibrations, is effectively unverifiable, which is why mudlogging and wireline crews treat the tail as a deliverable in its own right rather than an afterthought. The header at the front of the log and the tail at the back bracket the data and together form the legal and technical provenance of the measurement, and disputes over log quality, reprocessing, or invoice acceptance almost always begin with someone reading the tail to see exactly how the survey was acquired and whether the calibrations hold.

Key Takeaways

  • Proof, Not Just Paperwork: The tail is the documentation at the end of a log print that proves the curves are trustworthy. It carries well identification, recording parameters, tool serial numbers and spacings, logging speed, and the before-and-after calibration records that let a petrophysicist confirm each tool read known standards correctly across the run.
  • Calibration Audit Trail: Shop master, wellsite before-survey, and after-survey calibrations in the tail let an analyst detect tool drift. If a density tool no longer reads its aluminum or limestone standard after the run, the after-survey calibration in the tail flags it, and the affected interval can be reprocessed or rejected rather than misinterpreted.
  • Enables Cross-Well Correlation: In the WCSB, logs spanning decades across the Cardium, Viking, Mannville, and Montney are correlated together. The tail tells the analyst the mud properties, temperature, and environmental conditions needed to decide whether an old log compares directly to a modern one or needs correction first.
  • Regulatory and Digital Mirror: AER log submission depends on complete header and tail content, and the LAS digital file reproduces much of the tail in its well-information and parameter sections. A log with a missing or unreadable tail is effectively unverifiable and may be rejected on submission or invoice review.
  • Brackets the Data With the Header: The header at the front and the tail at the back together form the legal and technical provenance of the measurement. Quality disputes, reprocessing requests, and billing questions almost always start by reading the tail to see exactly how the survey was acquired.

What the Tail Actually Records

A typical WCSB wireline tail lists the operator and service company, the AER well licence and legal location, the run number, the logged interval top and bottom in metres, casing and bit sizes, and a mud report giving type, density in kg per cubic metre, resistivity at a stated temperature, and the maximum recorded bottomhole temperature. It then details the tool string: each sensor's serial number, the spacing between detectors, the logging speed in metres per minute, and the time since circulation stopped, which governs invasion and temperature corrections. The calibration block follows, pairing each measured response against a known reference so the analyst can confirm the tool was in specification both before going downhole and after returning to surface.

Why Petrophysicists Read the Tail First

An experienced analyst opening an unfamiliar log checks the tail before trusting a single curve. A density log acquired in a heavy barite mud, a neutron run at high temperature, or a survey logged too fast all carry corrections that only the tail discloses. If the after-survey calibration shows a gamma ray tool drifted, the analyst knows a shale baseline shift is instrumental, not geological, and avoids miscorrelating a Mannville coal or a Montney organic-rich interval. Because petrophysical decisions on net pay, porosity, and water saturation flow from these curves into reserves bookings and completion designs, the few minutes spent reading the tail protect millions of dollars of downstream decisions.

Fast Facts

When logs were delivered only as paper prints, the tail was literally the trailing footage of film or paper that came off the camera last, after the curves were recorded uphole, which is how it earned its name. Even today, with logs stored as LAS digital files and viewed on screen, the convention persists: the well information, parameters, and calibration sections live at the structural end of the file, and a petrophysicist auditing a forty-year-old WCSB log will still hunt for that final page of calibration tails before deciding whether the porosity curve can be believed.

The tail is one bookend of a Well Log, complementing the header that opens the print, and together they document the survey. Its calibration content directly supports trust in the Gamma Ray Log and other curves, since a drift flagged in the tail can invalidate an interval. Much of the tail is reproduced in the LAS File, the Log ASCII Standard format that carries the well-information and parameter sections an analyst reads before processing the digital curves.

Real-World WCSB Scenario: A Density Mismatch in a Pembina Cardium Correlation

A geologist correlating a new Cardium horizontal well near Pembina against a 1980s vertical offset found the density-derived porosity reading about three porosity units higher on the old log, enough to change the net-pay estimate and the landing target. Before flagging a geological change, the team pulled the old log tail and found the after-survey density calibration noted a small standard offset and a heavy barite mud, conditions that bias the apparent porosity. Re-applying the proper barite and standoff corrections, a few hours of a petrophysicist's time billed near CAD 1,200, brought the two logs into agreement.

The reconciliation kept the horizontal landing in the genuine Cardium sand rather than steering it toward an artifact of an uncorrected old log. Without the calibration record preserved in the tail, the discrepancy would have looked like real reservoir variation, and a misplaced lateral can cost a seven-figure completion its best production, underscoring why the tail is treated as core deliverable across WCSB logging programs.