WorkflowCapital Projects & Commissioning

Turnover Package Management

Turnover package software that reads each binder showing complete and puts its records on one calendar, so the QA/QC lead rules on evidence before mechanical completion.

See the demo Book a demo

Follow one binder from the night read to the hold ↓

The problem

A turnover package reads complete over a test that no longer proves the weld

The completions system counts signed check sheets. When a subsystem reaches its last signature the contractor submits the binder, and it lands with hundreds of others in the weeks before first gas. Reviewers sample, because nobody can read them all.

Each record is checked alone. A weld repair closes on its own radiograph; its form never asks whether that weld sat inside a pressure test someone already signed. The test pack and the repair live in different parts of the binder, with different owners, and each one reads correct. The mismatch shows up in commissioning, or not at all.

Built forCompletions engineersQA/QC leadsCommissioning managersAcceptance leadsInternal auditors

The Problem Today

Completions systems track that each sheet is signed, and nobody reads whether the records agree with each other.

Design: construction must match it before hazardous chemicals go in published
3,782: hours to read 453,803 pages by hand, at 30 seconds a page our estimate

Checked by hand today

Sheets
Weld logs
Test packs
Gauges

Each record checked aloneA repair closes on its own film, never on its test
Binders get sampledHundreds arrive together, close to first gas

The Solution

Each page readCheck sheets, weld logs, test packs and certificates, in each binder
One calendar per subsystemEach dated record laid in order, whoever filed it
Records that disagreeA test before a repair, a gauge out of date, no gate record for a signer
The QA/QC lead rulesOpens both pages and holds the binder; a retest item goes out

Built-in controls

Agents read and flag, and never sign
Whoever proposes cannot sign it
A hold stops commissioning

What You Get

Faults come out while a retest costs days, and commissioning sees exactly what it cannot take.

Each ruling on one recordName, reason and both pages, with an evidence download
A register that follows rulingsA hold changes the file commissioning loads, at once
Contractor answers in one placeRetests and records owed, dated and tracked

One binder, one morning

Weld 1147 was cut out three days after its turnover package test was signed

Train 3 of the gas plant has 41 days to first gas, and hundreds of binders read complete in the same fortnight. On this morning the seal gas binder for one compressor stops being taken on trust.

demoPlant, contractor, crew and counts in this walk-through are sample data.

01Overnight
364 subsystems show 100%, and in 23 the records don't add up
Binder reader and calendar builder
The completion tree draws the train as 14 systems and 638 subsystems. Overnight the agents read the 364 unsigned binders that show 100%, none sampled: 109,553 records on 453,803 pages. They left 27 flags in 23 subsystems: 22 wait for the completions engineer, 3 for a ruling, and 2 are already held.
0208:00
158 of 158 check sheets signed, and in filing order nothing looks wrong
Completions engineer
Subsystem 31-04 feeds seal gas to Compressor A. Its binder is 1,412 pages and 344 records, all sheets signed, so the completions system calls it complete. Laid out as filed, each record sits at its page and the dots read like any clean binder. The engineer sees the flag only because the agents read every page, not a sample.
0308:05
On one calendar the test sits three days before the weld it covers was redone
Completions engineer
One click lays every dated record on one line. Pressure test HTP-31-0412 was signed, a film audit then rejected weld 1147, and the weld was cut out and rewelded three days after the test. The repair page says it plainly: no later pressure test is named on this record. Both records are signed and correct alone. Together they leave a gap.
0408:11
The agent is 97% sure, and says the ruling is not its call
Completions engineer
The two pages open side by side: the test boundary covers welds 1139 to 1152 at 2,160 psig, and the repair record puts weld 1147 inside it. The date tester states what it found and hands the question to the QA/QC lead. Below sit what stands on this test: the reinstatement check, the nitrogen blow, and the compressor taking gas on recycle.
0508:17
He proposes a hold with a reason, and cannot sign it himself
Completions engineer
The engineer has opened both records, so the proposal is open to him. He picks the reason that fits what the pages show: the repair is inside the test boundary, so a retest is owed. A note is optional and he leaves it. The proposal goes to the QA/QC lead, because the person who proposes a hold may not be the one who signs it.
0608:29
The QA/QC lead opens both pages herself, then signs the hold
QA/QC lead
She does not rule from the proposal. She opens the test record and the repair record, and only then can she rule. Her ruling is that this test no longer proves the weld. Mechanical completion for 31-04 cannot be signed, and commissioning cannot take it, until it is released after a retest or lifted by two people who open the records.
0708:30
The retest goes to the contractor as an item, after her signature
Item writer
Item RX-0412 asks the contractor to pressure test the boundary again after the repair of weld 1147, then redo the steps that followed the old test. It was drafted after the ruling and sent on her signature. The contractor's coordinator sees only their own items and answers there, so the request is dated and tracked instead of living in an email thread.
0809:00
Three subsystems are stopped by a hold, and he can see which
Commissioning manager
Systems are listed by the date they take gas, each with its sign-by date and where its binders stand. A band across the top names the three subsystems a hold stops, what each one feeds, and whether the contractor has booked a retest. For 31-04 that is Compressor 210-C-3101 on recycle, with no retest date yet. He knows what he cannot touch.
0909:10
Seven entries show who opened which record, minute by minute
Internal auditor
Filtered to people, the audit trail reads the morning in order: the engineer opened the repair, the test and the repair again, then proposed; the QA/QC lead opened the test at 08:20 and the repair at 08:23, and signed at 08:29. The hold also wrote a category A punch item. Nothing here can be edited, and the evidence downloads with it.

What the 31-04 binder said, page by page, and what it meant together

Each record below is signed and correct on its own. The problem sits in their order.

Record	What it says	Read together
HTP-31-0412, pressure test	2,160 psig, held 60 minutes, no leak; boundary welds 1139 to 1152	Covers weld 1147
Film audit	Rejects the first radiograph of weld 1147 for lack of fusion at the root	Opens a repair after the test
WR-31-2406, weld repair	Weld 1147 cut out and rewelded; new radiograph accepted	No later pressure test is named
Reinstatement check and nitrogen blow	Both signed after the repair	Both stand on the old test
Check sheets	158 of 158 signed	The completions system shows 100%

demoSample data, from the working solution.

Around the binder

Batches, gauges, signers and the mechanical completion register

The same train as the QA/QC lead, the commissioning team and the auditor see it.

Clear batches by system: binders read clean, sign-by dates, binders still blocked, and a propose button for each system — **Clear batches**Clean binders grouped by system with a sign-by date. One person proposes, the QA/QC lead opens a random sample, the acceptance lead signs second. Flagged binders stay out.

Gauges on test day: five gauges whose calibration was out of date on the test day, with range and ratio to test pressure — **Gauges on test day**1,846 test packs set against 641 gauge and recorder certificates. Five gauges were out of date on their test day; each stops its binder until a person rules.

Signers compared with the site gate log: four inspectors with flagged signatures and their role and signature counts — **Who signed, and could they have**412 stamps and signers compared with the site gate log and the authorization list. A missing gate record is not proof that someone was away, so a person decides.

Mechanical completion certificate register: 638 subsystems by state, signed, read clean, records owed, flagged, not submitted — **Mechanical completion register**One row per subsystem, the file commissioning loads. It says how each was signed and how many binders in a batch no person opened. Agents never sign a row.

Completions engineer's queue: flagged subsystems with the kind of flag, the agent's confidence and a propose-by clock — **What waits for the engineer**Each flag the agents raised for him, how sure they are, and the date he should propose by. He opens the records before anything moves.

Turnover package agents: binder reader, calendar builder, date tester, gauge checker, signature checker and punch reader with limits — **The agents at work**What each agent read last night, what it may never do and who it hands to, beside the night's figures in plain words.

demoSample data, from the working solution.

Four kinds of record that read fine alone and wrong together

The 27 flags from the night read fall into these kinds.

Repairs or additions after the test

Work inside a boundary dated after the test that covers it

Gauges and recorders

A certificate out of date on test day, or a range unsuited to the pressure

Signers

A stamp with no gate record or authorization for that day

Other work out of order

Closed before inspected, tightened before the gasket change, dried out before the patch

demoSample data, from the working solution.

Who proposes, who rules and who takes the system

Each person opens the records before acting.

Completions engineer

Sees: Flags with both pages, the calendar and his queue
Signs: Proposes holds and batches; never signs his own proposal

QA/QC lead

Sees: Both records behind a flag, and the random sample of a batch
Signs: Rules on holds and signs mechanical completion

Acceptance lead

Sees: Batches, releases and any flag ruled no conflict
Signs: Gives the second signature

Commissioning manager

Sees: Systems by gas date and what each hold stops
Signs: Takes a subsystem into commissioning once signed

Contractor coordinator

Sees: Only the contractor's own items
Signs: Books retests and sends records

Internal auditor

Sees: Everything, read only
Signs: Exports the evidence

The agents

Binder reader to item writer: what each agent may not do

They read, date, compare and draft. Rulings go to named people.

Binder reader

Reads each page and splits it into its records.

Never treats a scan it cannot read as read

Calendar builder

Lays date, tag, weld and signer on one calendar.

Never guesses a date

Date tester

Tests what must come before what, by equipment class.

Never says whether a test proves a weld

Gauge checker

Checks gauges and recorders on test day, and their range.

Never rules on an as-found reading

Signature checker

Compares stamps with the gate log and authorizations.

Says no record was found, never that a person was away

Punch reader

Reads each punch item against what is behind it.

Never recategorizes an item

Item writer

Drafts the retest item or return note after a ruling.

Sends nothing, and writes nothing before a signed hold

Calls that stay with the QA/QC lead and the acceptance lead

The agents flag. These decisions belong to people.

Whether a test still proves a weldThe date tester lists what it found; the QA/QC lead opens both records and rules.

Whether a repair is minor enough to waive a retestYour piping code lets the owner waive a retest for minor work. That is the owner's call, with two signatures and a written reason.

Lifting a holdA hold is released after a real retest, or lifted by two people who each open the records.

Taking gas into a held systemCommissioning is refused while a hold stands, and the screen says which hold.

What completions and QA/QC leads ask about turnover package review

What is a turnover package?

A turnover package is the binder a contractor submits for a subsystem when its check sheets are signed: check sheets, weld logs, radiographs, test packs, certificates and punch lists. This solution reads each turnover package in full, lays its records on one calendar and flags where they disagree, for the QA/QC lead to rule on before mechanical completion.

Does it replace our completions management system?

No. It reads the binders your completions system and document management system already hold, plus the calibration register, site access records and the project schedule. Status tracking stays where it is.

What happens when a weld is repaired after the hydrotest?

The date tester flags it with both pages. The completions engineer opens them and proposes, and the QA/QC lead opens them herself and rules. If she holds the binder, a retest item goes to the contractor and commissioning sees the hold.

Can a whole system be signed in one batch?

Yes, for binders that read clean. One person proposes the batch, the QA/QC lead opens the records of a random sample and the acceptance lead signs second. The mechanical completion certificate says how many binders no person opened.

Do the agents ever sign a mechanical completion certificate?

No. Agents read and flag. A person proposes, a different person rules, and the acceptance lead gives the second signature where one is needed.

What does the contractor see?

Only its own items: retests asked for, records owed, and their dates. It books retests, sends records or disputes with a reason, and the owner's rulings in progress stay hidden from it.

Capital Projects & Commissioning

Bring one binder
your team already passed.

Lay its records on one calendar with us, and see what a reviewer would have had to open.

Book a demo Browse solutions

Turnover Package Management

A turnover package reads complete over a test that no longer proves the weld

The Problem Today

The Solution

What You Get

Weld 1147 was cut out three days after its turnover package test was signed

364 subsystems show 100%, and in 23 the records don't add up

158 of 158 check sheets signed, and in filing order nothing looks wrong

On one calendar the test sits three days before the weld it covers was redone

The agent is 97% sure, and says the ruling is not its call

He proposes a hold with a reason, and cannot sign it himself

The QA/QC lead opens both pages herself, then signs the hold

The retest goes to the contractor as an item, after her signature

Three subsystems are stopped by a hold, and he can see which

Seven entries show who opened which record, minute by minute

What the 31-04 binder said, page by page, and what it meant together

Batches, gauges, signers and the mechanical completion register

Four kinds of record that read fine alone and wrong together

Who proposes, who rules and who takes the system

Binder reader to item writer: what each agent may not do

Calls that stay with the QA/QC lead and the acceptance lead

What completions and QA/QC leads ask about turnover package review

Related completions and handover solutions

Bring one binderyour team already passed.

Bring one binder
your team already passed.