Operations
A closeout report is not a formality. It is the artefact that lets somebody else reopen, escalate or trust the work six months later.
Who the report is actually for
The report is not for the person who did the work. It is for the engineer who picks up the ticket next — possibly at a different company, possibly two years later, when the same symptom comes back on the same sector.
Write it for that person and the structure follows naturally.
1. The problem as it was reported
What the customer saw, on which sites and sectors, over what period, and what had already been ruled out before GCorp was engaged. This section exists so that a reader can tell whether their situation resembles this one.
2. The baseline
RTWP trends and spectrum captures from before any work was done. Without a baseline there is nothing to compare against, and every claim in the rest of the document becomes an assertion.
Baselines should cover a period long enough to show the pattern — not a single snapshot taken on the day of mobilisation.
3. Signal characterisation
Centre frequency, occupied bandwidth, duty cycle, timing behaviour and how the signal behaved over the observation period. Screenshots from the analyser with visible scale and settings.
A plot with no axis labels or no reference level proves nothing.
4. Field method and bearings
Where the team stood, what equipment was used, and what heading was recorded at each vantage point. Bearings plotted on a map — KML, or an equivalent format the customer can open.
Include the bearings that did not converge as well as the ones that did. The discarded readings are part of the evidence that the conclusion was tested rather than assumed.
5. The located source
Coordinates, a description of the device and its installation, and photographs where the location was accessible. If the source could not be positively identified, say so plainly and describe how close the investigation got.
6. Mitigation performed
What was actually done, by whom, on what date, and with whose agreement. If a third party switched off or replaced equipment, record who authorised it. This is the section that matters most if the problem recurs.
7. Validation
The same measurements as the baseline, taken the same way, after mitigation. RTWP compared over a comparable period, and post-mitigation sweeps from the same vantage points as the pre-work sweeps.
Like-for-like comparison is the whole point. A post-mitigation sweep taken from a different position at a different time of day does not demonstrate anything.
8. What remains open
Any source that could not be resolved, any site still showing elevated RTWP, any follow-up that depends on a third party, and any recommendation the customer has not yet acted on.
A report that closes every item is either unusually lucky or incomplete. Stating the open items honestly is what makes the closed ones credible.
The test to apply before sending it
Hand the report to an engineer who was not involved and ask them three questions: Do you know what the problem was? Do you believe the source was correctly identified, and can you see why? Could you reopen this investigation from what is written here?
If any answer is no, the report is not finished.
A note on confidentiality
Closeout packages routinely contain site identifiers, coordinates, customer names and performance data. None of it goes into published material — case studies, articles or marketing — without written approval and appropriate anonymisation. The report’s job is to serve the customer’s engineering team, not to become content.