Last updated
When a technician leaves a site, the closeout package is the only record of what happened there. It is how you prove to your client that the work was done, how you bill for it, and how the next technician understands what they are walking into. A weak closeout package turns every future question about that site into another visit.
Closeout requirements belong in the contract and in every work order. If they are not written down, every vendor and every technician will interpret them differently.
The core closeout package
Check-in and check-out times
Time stamps from the platform, help desk, or call log show when the technician arrived and left. They resolve disputes about late arrivals and billable hours, and they show whether the work was done inside the approved window.
Signed work order
A signature from the site contact confirms that someone at the site saw the work completed. Require the signer's printed name and role, not just a signature. When no one is available to sign, the work order should say so and name who was contacted.
Photos
Photos are the most useful part of a closeout package when they are specified, and the least useful when they are not. Ask for:
- Before and after photos of the work area, taken from the same position
- A wide shot that shows where the work is, and a close shot that shows how it was done
- Each installed device with its label visible
- Serial number and model plates, readable
- Cable routing, termination, and labeling where cabling was part of the job
- Anything unusual: damage found on arrival, blocked pathways, or missing equipment
Photos should never show customer data, documents, payment card information, or anything the site has restricted. Say so in the work order.
Technician notes
Short, specific notes on what was done, what was found, and what was left. "Replaced switch, moved 24 cables per port map, all links up, old switch boxed for return" is useful. "Job complete" is not.
Test results
Test results prove that the work performs, not just that it was installed. Depending on the job, that means cable certification reports, help desk confirmation of a device coming online, test calls, test transactions, or camera view approval. For cabling, request reports in the tester's native file format as well as PDF, so they can be archived and re-read later.
Asset data
Serial numbers and asset tags for every device installed and removed, in a format you can import, such as a spreadsheet. This keeps inventories accurate and is essential for payment devices, which merchants must track under PCI DSS.
As-built notes
Anything that differs from the plan: a drop that moved, a port map that changed, an access point mounted in a different spot. As-built notes keep the documentation true to the site, which saves the next technician from tracing everything again.
Exceptions and open items
If anything was not completed, the package should say what, why, and what is needed to finish. An exception list with a clear next step is far more useful than a job marked complete when it is not.
Return shipping
Tracking numbers for old equipment returned, and what was left on site if anything.
How to specify closeout requirements
- Write a standard closeout list for each type of work, and attach it to every work order
- Give photo requirements as a numbered shot list, so missing photos are easy to spot
- Set a file naming convention, for example site number, date, and photo number
- Set a delivery deadline: we deliver closeout documentation within 24 hours of the completed visit
- Say where the package is delivered: platform, email, or shared folder
- Say who reviews the package and how quickly problems are raised
How to review a closeout package
Review packages as they arrive, not at the end of the project. A missing photo raised the next day can often be fixed by the site. The same gap found three weeks later usually needs a return visit.
- Are check-in and check-out inside the approved window?
- Is the work order signed by a named person at the site?
- Does every required photo exist, and are labels and serial numbers readable?
- Do test results cover every device or link in scope, and do they pass?
- Do serial numbers match the inventory?
- Are exceptions listed with a next step?
Why it matters beyond one visit
Good closeout documentation builds a record of each site that gets more valuable over time. When the next refresh is planned, the photos and as-built notes from the last one answer most of the survey questions. When a client asks whether a job was done, the answer takes minutes instead of a site visit.
Every Relion work order closes out with check-in and check-out times, photos, technician notes, a signed work order, and test results where applicable, delivered within 24 hours. See how we work with partners, or read how to write a work order that makes these deliverables easy to collect.