Resources / Case Studies
Scoping a Secondary-Side Header Retrofit Without Inventing Details
The checklist we use when an existing loop has to be extended or re-headed - described as method, with no client or site information.
%s
Retrofit work starts with what cannot be changed: existing connection types, available access, and the isolation arrangement of the running loop. We capture those constraints in a scoping checklist before discussing any new fabrication.
This note describes the sequence only - survey inputs, interface confirmation, prefabrication limits and the verification gate before handover. It intentionally contains no client name, capacity, location or performance figure.
Key Points
- Record existing interfaces and access constraints before proposing a new header.
- Prefabricate what can be built off site to shorten the intervention window.
- Agree the pressure / leak verification and documentation scope at quotation.
De-identified at the owner's request. No client name, location, capacity figure, operating result or identifiable site photography is published.
CASE STUDIES
More from Case Studies
What a De-identified Project Note Records – and What It Never Does
A clear boundary: engineering sequence and documentation are publishable; customer identity, operating data and photographs are not.
Editorial policyRead MoreFrom Sample Manifold to Repeat Order: The Qualification Gates We Document
What changes between a first engineering sample and a repeat batch - and the records that make the second one reproducible.
De-identified project noteRead MoreNext step
Ask an engineer
Send the question behind this note and we will reply with project-specific feedback.