WorkflowDrilling, Wells & Decommissioning

Daily Drilling Report Review

Daily drilling report review that checks each hour against the rig's own data, then asks the person who wrote it while they still remember the night.

See the demo Book a demo

Read the night from 05:14 to the 07:30 call ↓

The problem

A shut-in phoned in at night can still reach the well database as reaming

The company representative closes the report around crew change, after a long tour at the choke or on the floor. Lines get carried in from the driller's tour sheet, hours go missing or overlap, and a code can say reaming while the bit sat still and the pits climbed.

The superintendent reads the reports by eye before the call, mostly the summary. Nobody holds the hours against the rig's own data. When a lost-time study or an offset review finds the bad line months later, the writer is on another rig and the answer is a guess.

Built forDrilling superintendentsCompany representativesDrilling data analystsOperations geologistsDrilling managers

The Problem Today

Each rig's report is typed at the end of a long tour, and a wrong code stays until nobody remembers what happened.

2,920: daily reports a year from eight rigs, each hour coded by hand our estimate
Daily: summary of well activities asked on one regulator's form published

Checked by eye today

Hours
Codes
Mud weights
Footage

Questions come months lateFixed when the data is needed, by email to the rig
A phone call leaves no lineThe shut-in is phoned in; the report can say reaming

The Solution

Checked as it is writtenEach line against bit depth, pumps, pits and the mud checks for those hours
One question to the writerAsked before crew change, while the person still remembers the night
The writer corrects itAgents draft wording; the change goes in under the writer's own name
Signed on the morning callThe superintendent opens and signs; an event needs a second signature

Built-in controls

Agents never edit a report
Well control events need two signatures
Nobody signs their own work

What You Get

Superintendents start the call with each hour checked and each change made by the person who wrote it.

A morning call that starts trueEach rig's night, hour by hour, with who said what
Last year's reports re-readMarks grouped in lots and signed on a random sample
Sands that flow reach geologyPressures from the writer's own numbers, the same day

One night tour, by the clock

05:14 to 07:35: one daily drilling report, from the shut-in to the record

A small land rig takes a kick at a drilling break, shuts in and phones the superintendent. The draft report still says reaming. Here is how the line gets fixed before anyone goes home.

demoRigs, wells, crews and numbers here are all sample data.

0105:14
Rig 6 has been shut in on a gain for 2 h 38 min, its report half written
Drilling superintendent
Eight strips of 24 hours sit under a red line: Rig 6 shut in at 02:36, and the company representative phoned at 02:40. Each hour is colored by the code typed so far, with the bit depth traced beneath. The superintendent sees the whole night before the 07:30 call, including the rigs that did not phone.
0205:14
The pits were rising at 02:26, five minutes before the flow the call described
Drilling superintendent
The superintendent runs the check on Rig 6 and watches each step land with its source. The bit is flat at 6,412 ft with pumps off from 02:31. Active pits climb from 02:26, right after a drilling break at 6,398 ft. The call put the start at the connection. That puts the zone at the top of the sand, for the geologist and the incident record.
0305:14
The draft says reaming, carried in from the driller's tour sheet at 05:08
Drilling superintendent
The report as written sits beside the rig's own trace. The line from 02:30 to 05:00 reads code 3, ream and work pipe, tight at 6,412 ft, yet reaming needs pumps on and the bit never moved. Each mark cites a rig data window, a mud check or the call log, so the reason the hour does not fit is one click away.
0405:14
One plain question, asked before he goes off tour at 06:00
Night company representative
On his own screen the company representative sees the draft, eight lines, and a single question under the marked hour: did the flow start while drilling, and should 02:30 on read well control? He can answer yes, no or not yet. At noon he would be asleep and the driller would be home.
0505:14
He answers in his own words, then gets a drafted line he can change
Night company representative
He writes that the pits came up at the drilling break at 6,398 ft, before the connection, and that the flow check was positive. The agents draft one line from his answer, the 02:40 call and the rig data, covering 02:30 to 06:00. Nothing changes until he applies it. What he typed stays marked as his words.
0605:17
From 02:30 on, the report now reads code 35, well control, under his name
Night company representative
He applies the line and sends the report at 05:17. The reaming hours are gone; in their place sits the drilling break at 6,398 ft, the gain, the shut-in at 02:36, SIDPP 190 and the 10.8 ppg kill mud. The line carries his name as the person who rewrote it.
0707:31
The morning report call opens on Rig 6, with who said what beside it
Drilling superintendent
The agenda puts events first. Rig 6 shows the 12 bbl gain, that the writer says the flow began at the 6,398 ft break, and who said so: the call at 02:40 and his answer. Rig 7 arrived at 06:52 with 2.33 h it could not check, and Rig 8 is held.
0807:33
He rules it a well control event only after opening the report and rig data
Drilling superintendent
The event panel holds the line as first written, what the agents saw, what was said on the call and in the answer, and what the call missed. A shoe limit comparison is shown with sample figures and marked as no safety call. The superintendent records the event. It now waits for the drilling manager; he cannot countersign his own ruling.
0907:35
A second person signs, and the event never joins a lot of clean reports
Drilling manager
The drilling manager opens Rig 6's report and gives the second signature. The queue reads recorded as an event, while eight older possible events from last year's reports wait their own rulings. Two people read each such event on its own, so a busy morning cannot sweep one into a batch of clean reports.

Four other rigs whose hours did not fit the numbers beside them

Each was asked of the person who wrote it, and each answer came back under that name.

Rig 4: drilling with the bit off bottom

22:00 to 01:30 was coded drilling, yet the bit was off bottom from 22:15 to 01:00. The measurement tool had lost its signal, so the writer recoded 2.75 h to service company repair.

Rig 5: a mud weight that was a typing slip

The 03:00 line said 9.1 ppg while the mud check read 9.4. The writer answered at 03:22 and fixed it.

Rig 1: half an hour nobody wrote

03:30 to 04:00 was missing. Asked at 04:06, the writer added the line at 04:19: replacing drill line.

Rig 8: mud checks falling with no flow check result

11.6, then 11.4 in and 11.3 out, and the 05:00 flow check has no result. The question passed to the day writer and the report stays held.

demoSample data, from the working solution.

7.25 hours changed tonight, each by the person who wrote them

Four writers changed their own lines after one question each. No agent moved an hour.

Rig 1, the missing half hour added	0.5 h
Rig 2, the overlap corrected by the day writer	0.5 h
Rig 4, drilling recoded to service company repair	2.75 h
Rig 6, reaming rewritten as well control	3.5 h
Hours changed by their writers	7.25 h

demoSample data, from the working solution. Of 168 rig hours, 165.67 were checked against rig data; Rig 7's 2.33 h after its link went down were checked without it.

Around the morning call

What the geologist, the analyst and assurance take from these reports

The questions, the geology, last year's lots and the trail behind tonight's signatures.

List of questions sent to company representatives, each with the time asked, the question, its due time and its state — **Questions to the rigs**Six questions tonight, five answered by the writer before going off tour. Rig 8's went to the day writer, due 08:00; only a writer's answer closes it.

Geology view of tonight's reports: what each rig saw at the bit, mud weights, shows, and a pressure line for one sand — **Geology from tonight's reports**Tops, mud weights and shows from each report, and a pressure line for the S-4 sand from the writers' own numbers.

Back file of last year's daily drilling reports grouped into lots by kind of error, with marks, hours, sample size and state — **Last year's reports, re-read**2,555 reports and 61,320 rig hours read again: 546 marks, 538 of them in 13 lots by kind of error, and 8 possible events kept out of every lot.

Drilling report quality control rules with locked and adjustable checks, tonight's hits and last year's hits for each — **What is checked**Each rule, whether it is a setting or locked on, and what it caught tonight. A pit gain with another code cannot be loosened from settings.

Audit trail filtered to signatures: the superintendent's ruling and the drilling manager's second signature on a well control event — **Signatures on the trail**Rig 6's ruling and its countersignature, each with the person and the time, in a trail nobody can edit. The evidence downloads as a CSV.

Rig strips after the morning call with Rig 6 recoded to well control and Rig 8 held on falling mud checks — **Rig 8 stays held**All seven reports are in. Rig 8's mud checks fell from 11.6 to 11.4 in, 11.3 out, with no flow check result, so it stays held.

demoSample data, from the working solution.

Who answers, who rules, and who gives the second signature

The writer owns the report. The people who sign read the words the writer typed before they sign.

Company representative

Sees: The one question under the marked hour, with its evidence
Signs: Answers and corrects their own report; nobody else edits it

Drilling superintendent

Sees: Each rig's night, the marks, and who said what
Signs: Each report, a sampled lot of clean ones, and the first ruling on an event

Drilling manager

Sees: The event's evidence and the writer's last answer
Signs: The second signature on each well control event, and settles a disagreement

Drilling data analyst

Sees: Late reports, open questions and last year's marks
Signs: Proposes lots; the superintendent signs them on a sample

Operations geologist

Sees: Tops, shows and pressures from the writers' numbers
Signs: Writes the pressure note for the next wells

Who does the reading

Agents that read the rig's night may not edit one line of it

Each hands its work on, in the end to a named person.

Report reader

Reads each line as it is typed: times, code, depths, words, mud and bit.

Never edits a report or fills a line

Rig data matcher

Lines up bit depth, hole depth, pumps, rotary, pits and mud checks with each line.

Never treats sensor data as the record
Never fills an hour from it

Time checker

Finds hours that do not add up to the day, gaps, overlaps and footage that does not match the depths.

Never moves a time

Code checker

Holds each code against the numbers and words beside it; a shut-in on a gain goes to the superintendent at once.

Never decides what happened
Never calls an event a kick

Question writer

Writes one plain question to the person who wrote the line, before crew change.

Never answers its own question
Never writes into the report

Morning call builder

Builds the call agenda from answered and open items, events first.

Never hides an open question
Never signs

Back file reader

Re-reads past reports for time and number errors in lots and lifts possible well control lines out.

Never recodes anything
Never puts a possible event in a lot

What stays with the rig and the office, however busy the morning

The agents mark, ask and line up evidence. These calls belong to people.

No agent decides a kick happenedThe code checker says what does not fit. The superintendent rules, and the drilling manager gives the second signature.

The writer's report is the writer'sA drafted line goes in only when the company representative applies it, under their own name.

Safety questions go to a personAsk about a gain, a pressure or whether a well is safe, and the answer names the superintendent and gives no figures.

A held report is not releasedA rig with falling mud checks stays out of the well database until its writer answers.

What drilling superintendents ask about daily drilling report review

What is daily drilling report review?

Daily drilling report review checks each line of a rig's daily drilling report against that rig's own sensor data, mud checks and call log while the report is being written. When an hour does not fit, one plain question goes to the person who wrote it before crew change. The writer corrects the report, and the superintendent signs it on the morning call.

Does the software ever change a company representative's report?

No. Agents ask and, when asked, draft a line. The writer edits it or applies it, and the report shows the change under the writer's name.

How is a possible well control event handled?

It is lifted out at once. A shut-in on a gain becomes the superintendent's next step with a clock. The superintendent rules after opening the report and rig data, and the drilling manager gives the second signature. A possible event is read one by one by two people, never signed as part of a lot.

What happens when the writer has already gone off tour?

The question passes to the next tour's company representative, then to the superintendent. Until someone answers, the report stays held.

Can it check last year's daily drilling reports too?

Yes. Agents re-read the back file for hours not written, hours written twice, mud weights, footage, hole size and casing depth. The analyst proposes lots, and the superintendent signs each after opening a random sample.

Which activity code list does it use for drilling report quality control?

Yours. The customer loads its own activity code list, and the rules are set and signed by named people. Some checks, such as a pit gain coded as other work, are locked on and cannot be loosened from settings.

Drilling, Wells & Decommissioning

Bring one rig's night
with its rig data.

We will hold one of your daily drilling reports against the sensor data and mud checks from the same hours.

Book a demo Browse solutions

Daily Drilling Report Review

A shut-in phoned in at night can still reach the well database as reaming

The Problem Today

The Solution

What You Get

05:14 to 07:35: one daily drilling report, from the shut-in to the record

Rig 6 has been shut in on a gain for 2 h 38 min, its report half written

The pits were rising at 02:26, five minutes before the flow the call described

The draft says reaming, carried in from the driller's tour sheet at 05:08

One plain question, asked before he goes off tour at 06:00

He answers in his own words, then gets a drafted line he can change

From 02:30 on, the report now reads code 35, well control, under his name

The morning report call opens on Rig 6, with who said what beside it

He rules it a well control event only after opening the report and rig data

A second person signs, and the event never joins a lot of clean reports