November 1, 2026 • Centoffer Editorial • 19 min read
Proof of Delivery (POD) in Field IT Services: What Evidence Every Ticket Should Carry
Proof of delivery (POD) in field IT service is the evidence showing a specific engineer did specific work at a specific site and time, and that the result was accepted. A usable POD combines timestamped before-and-after photos, a location record, the asset identifier, a named sign-off, and a short work note — defined per job type in the contract.
Proof of Delivery (POD) in Field IT Services: What Evidence Every Ticket Should Carry
Proof of delivery in field service is the part of an IT support contract that most buyers assume exists and few actually define. A ticket moves to “Resolved”, an invoice line appears at the end of the month, and the only record that an engineer visited a branch, swapped a switch and left it working is a status change in someone else’s system. When everything goes well, nobody looks. When a site reports that the same fault is back, that the engineer never showed up, or that a laptop with customer data went missing during a swap, the buyer discovers that “resolved” was never evidence of anything.
This guide is written for enterprise IT and procurement teams that buy on-site IT work: break-fix, IMAC (install, move, add, change), smart hands in data centres, structured cabling, and device swaps across many sites or countries. It sets out what proof of delivery (POD) is, which evidence elements each ticket should carry, how requirements should change by job type, where each type of evidence is weak, and how to write POD rules into a contract so that they are enforced rather than hoped for.
What is proof of delivery in field IT service?
Proof of delivery (POD) in field IT service is the evidence package attached to a ticket that proves a specific engineer performed specific work, at a specific site, at a specific time, with a specific result that someone accepted. It is the field-service equivalent of a signed delivery note in logistics, but richer, because IT work changes the state of an asset rather than just moving a box from one place to another.
The term is borrowed from shipping, where POD traditionally meant a signature on a consignment note. In field IT, a signature alone is far too thin. Centoffer’s own glossary definition of POD describes it as photos, an e-signature, a GPS geotag and a timestamp captured on site, which together close the job and feed billing. That is a useful starting point, but buyers should think of POD as a set of claims that need to be supported:
- Who — the named, verified engineer, not just “a technician from Vendor X”.
- Where — the actual site, and ideally the actual room, rack or desk.
- When — arrival, work start, work end and departure times.
- What — the asset touched (serial, asset tag), the work performed and any parts used.
- Result — a test showing the issue is fixed or the change works.
- Acceptance — a named site contact, or the buyer’s system, agreeing the result.
If a ticket cannot answer all six, it has a status, not proof of delivery.
Why does proof of delivery matter more than the ticket status?
Proof of delivery matters because a ticket status is a claim made by the party being measured, while POD is evidence the buyer can check. Every SLA metric that involves an on-site visit — arrival time, resolution time, first-time fix — depends on timestamps and outcomes that only the field engineer and the site witnessed. Without evidence, SLA reports are self-certified.
That has four practical consequences for buyers.
SLA credits become unenforceable. If the contract pays a service credit for a missed four-hour on-site response, the buyer has to show the response was missed. If the only timestamps are those the provider’s dispatcher typed in, a dispute turns into one party’s word against the other’s.
Invoices cannot be reconciled. Multi-site programmes generate hundreds of visit lines a month. Finance teams asked to approve them need a way to match each billable visit to a completed job. A POD record per visit makes that reconciliation mechanical; without it, approval becomes an act of trust.
Repeat faults cannot be diagnosed. When a printer, access point or POS terminal fails again two weeks after a “fix”, the first question is what was actually done last time. A work note with the replaced part’s serial number answers that in seconds. A closed ticket with the note “resolved on site” does not.
Security and audit exposure grows. Engineers handle laptops, disks, network gear and badges. When an auditor or a regulator asks who had access to a device and where it went, the answer has to come from records, not memory.
The point is not that providers are dishonest. Most are not. The point is that a programme running across many sites, subcontractors and time zones cannot be managed on memory and goodwill, and that a provider confident in its delivery should welcome evidence that proves it.
What evidence should every field IT ticket carry?
Every on-site IT ticket should carry a core evidence set of seven elements: verified engineer identity, arrival and departure timestamps, a location record, before-and-after photos, the asset identifier, a test result and a named sign-off. Each element answers a different question, and each has a known way of failing. The table below sets out what each one proves, what it cannot prove, and the most common weakness buyers see.
| Evidence element | What it proves | What it cannot prove on its own | Common weakness |
|---|---|---|---|
| Engineer identity (app login, ID badge photo or check-in code) | Which vetted person performed the job | That the person was competent for this task | Shared logins; subcontractor sends a substitute |
| Arrival and departure timestamps | When the visit started and ended | That work happened in between | Times typed in later by a dispatcher |
| Location record (geotag) | Approximate position of the device used to check in | Which room, floor or rack the engineer was in | Indoor GPS drift; check-in from the car park |
| Before-and-after photos | The visible state of the asset or site before and after | That the fault is fixed, or that the photo is from this visit | Blurry, cropped or reused photos; no identifying label in frame |
| Asset identifier (serial, asset tag, port ID) | Which specific device was touched | What was done to it | Serial not captured; generic “laptop replaced” note |
| Test result (screen, LED, ping, print test, user confirmation) | That the outcome works at the time of departure | That it will keep working | ”Tested OK” typed without evidence |
| Named sign-off (e-signature, confirmation code, or buyer-system acceptance) | That a responsible person at the site accepted the result | That the signer checked the work | Illegible scribble; signed by whoever was at reception |
Notice how the elements cover each other’s gaps. A geotag cannot tell you which comms room the engineer stood in, but a photo of the rack with its label in frame can. A photo cannot prove the fault is fixed, but a test result can. A test result typed by the engineer is a claim, but a sign-off from the named site contact confirms it. POD becomes evidence when the elements are captured together and cross-checked against the ticket, not when any one of them is present.
Two further elements are worth adding for most enterprise programmes:
- A structured work note. Not free text alone, but fields: fault found, action taken, parts used (with part numbers), and whether a follow-up is needed. Structured notes make repeat-fault analysis and parts reconciliation possible across thousands of tickets.
- Parts and materials record. For any job that consumes stock — a replacement drive, a patch lead, a power supply — the part number and serial of what went in, and the disposition of what came out (returned, scrapped, held for RMA).
How should POD requirements change by job type?
POD requirements should scale with the risk and value of the job: a password-reset desk visit needs far less evidence than a data-bearing drive replacement in a regulated data centre. Setting one heavy standard for everything wastes engineer time on low-risk work, and setting one light standard leaves high-risk work unprotected. Define a POD profile per job type in the statement of work (SOW).
| Job type | Minimum POD profile | Extra evidence worth requiring |
|---|---|---|
| Break-fix (desktop, printer, POS, access point) | Timestamps, geotag, before/after photo with label in frame, faulty and replacement serials, functional test, site sign-off | Photo of the error code or fault indicator before work |
| IMAC (install, move, add, change) | As above, plus the new location (desk, room) and the asset register update | Photo of cable labelling; user confirmation of login and peripherals |
| Smart hands in a data centre | Timestamps from the facility’s access log where available, photo of rack and U position, port or cable IDs, remote engineer confirmation | Facility escort name; photos of front and rear of rack after work |
| Structured cabling | Photos of terminations and labelling, test certification output per link, as-built drawing update | Sample of link test results reviewed by the buyer before acceptance |
| Site survey or audit | Timestamped photos per area surveyed, completed checklist, measurement outputs | Floor plan annotated with photo positions |
| Data-bearing device swap (laptop, disk, phone) | Serials of device out and device in, chain-of-custody record for the removed device, recipient sign-off | Sanitisation or destruction record when the contract requires it |
| Scheduled preventive maintenance | Checklist with each item marked and photographed where visible, readings recorded | Comparison to the previous visit’s readings |
The data-bearing row deserves particular care. If an engineer removes a drive or a laptop that held company data, the POD should show where that device went next. Where the contract requires sanitisation, the reference standard many organisations use is the U.S. National Institute of Standards and Technology’s Guidelines for Media Sanitization, NIST SP 800-88, which NIST published as Revision 2 in September 2025. The POD for the field visit does not need to contain the sanitisation itself, but it should link to the record that does, so the chain from “removed at site” to “sanitised or destroyed” is unbroken.
Is a photo, geotag or e-signature enough on its own?
No single POD element is enough on its own, because each has a well-understood failure mode. Buyers who know the limits of each element can write requirements that compensate for them instead of over-trusting one signal.
What does a geotag actually prove?
A geotag proves roughly where the engineer’s phone was when it recorded a check-in or took a photo. It does not prove which floor, room or rack the engineer was in. According to GPS.gov, the U.S. government’s official GPS information site, GPS-enabled smartphones are typically accurate to within a 4.9 m (16 ft) radius under open sky, and their accuracy worsens near buildings, bridges and trees. Most IT work happens inside buildings, often in basements and interior comms rooms where satellite signal is weakest.
The practical implication: treat a geotag as a coarse check — was the engineer at the right building, or 20 km away? — and rely on photos with identifying labels, facility access logs and site-contact confirmation for anything finer.
What can photos prove, and how can they be gamed?
Photos are the richest single element, but only if they contain something that ties them to this asset and this visit. A close-up of a generic switch proves nothing; a photo that shows the switch’s asset label, the rack position and the patch-panel labels proves a great deal. The common failure modes are photos taken from too far away, photos that crop out identifying labels, and — rarely, but it happens — photos reused from an earlier job.
Requirements that close these gaps:
- Capture in-app, not from the gallery. Photos taken through the field-service app at the time of the job carry the app’s own timestamp and location, which is harder to manipulate than an uploaded image whose metadata can be edited or stripped.
- Require an identifier in frame. A serial number, asset tag, rack label or room sign in at least one photo per job.
- Before and after, from the same angle. This makes the change visible and makes reused photos easy to spot.
- Minimum quality check. Automated checks for blur and minimum resolution, with rejection before the engineer leaves the site, not two days later.
Does an e-signature carry legal weight?
In many jurisdictions it can. In Singapore, for example, the Electronic Transactions Act provides that an electronic record or signature satisfies a rule of law requiring writing or a signature, subject to listed exclusions such as wills and contracts for the sale of immovable property, according to the CMS expert guide on e-signatures in Singapore (2020). That legal standing is about whether an electronic signature is valid, though — not about whether the signer checked anything.
For POD, the more important questions are operational: who signed, and what they were shown. A sign-off is strongest when the signer is a named person on an approved site-contact list, when the signature screen shows the work summary and test result, and when the signer receives a copy. A scribble on a phone from whoever was at reception is legally an e-signature and practically almost worthless as evidence.
Where no site contact is available — an unmanned branch, an overnight data-centre job — a confirmation code sent to the buyer’s on-call contact, or acceptance through the buyer’s own ITSM system, can replace the in-person signature.
How do you write POD requirements into a contract or SOW?
Write POD requirements into the SOW as a per-job-type evidence profile, a rejection rule, an SLA linkage, and a data-access clause. Without all four, POD stays a nice-to-have that erodes as soon as volumes rise.
Here is sample wording buyers can adapt. It is illustrative, not legal advice; have your own counsel review it for the governing law of your contract.
Proof of Delivery. For every on-site visit, the Provider shall capture, at the time of the visit and through its field-service application, the evidence listed for the relevant job type in Schedule X (“POD Profile”). A ticket shall not be treated as resolved for the purposes of the Service Levels until a POD meeting the POD Profile has been submitted.
Rejection. The Customer may reject a POD within [two] business days of submission if a required element is missing, illegible, or inconsistent with the ticket. A rejected POD returns the ticket to an open state, and the resolution time continues to run until a compliant POD is submitted or the work is re-performed.
Access and retention. The Customer may view and export all POD records relating to its tickets at any time during the Term and for [24] months after expiry. The Provider shall store POD records securely and shall not use them for any purpose other than delivering and evidencing the Services.
Three design choices in that wording matter more than the exact text:
- The SLA clock depends on POD. If resolution time stops when the engineer taps “done”, there is no incentive to capture good evidence. If it stops when a compliant POD is submitted, there is.
- Rejection has a short, fixed window. Buyers need time to check, but providers need certainty. Two business days is a common compromise; automated acceptance after the window keeps tickets moving.
- Data access survives the contract. Disputes and audits often arise after a contract ends or changes hands. Evidence that disappears with the old provider is no evidence at all.
What makes a proof of delivery rejectable?
A POD should be rejectable when it fails to support one of the six claims — who, where, when, what, result, acceptance — or when its elements contradict each other or the ticket. Publishing the rejection criteria to engineers removes arguments later and raises first-submission quality.
A practical rejection checklist:
- A required photo is missing, out of focus, or lacks the identifier the POD profile calls for.
- The serial or asset tag recorded does not match the asset on the ticket or in the asset register.
- The geotag places the check-in outside an agreed radius of the site address, with no explanation recorded.
- Arrival or departure timestamps were entered manually rather than captured by the app, without a recorded reason.
- The test result is a typed “OK” with no supporting photo, screen capture or user confirmation.
- The sign-off is from a person not on the approved site-contact list, or is unreadable with no name recorded.
- Parts used are listed without part numbers, or a removed data-bearing device has no recorded next destination.
- The work note describes different work from the ticket’s request with no change approval recorded.
Some of these checks can run automatically before the engineer leaves the site — missing fields, blurry photos, a geotag far from the address. Catching problems on site is far cheaper than sending someone back.
Proof of delivery and privacy: what should stay out of the photo?
POD photos should show assets, labels, racks and screens — not people, customer records or credentials — because images can capture personal and confidential data. Singapore’s Personal Data Protection Commission (PDPC) states in its Advisory Guidelines on the PDPA for Selected Topics (revised October 2021) that an image of an identifiable individual captured in a photograph or video recording is personal data about that individual. Similar principles apply under other data-protection regimes across Asia-Pacific and beyond.
Practical rules for engineers, worth including in the POD profile and in engineer training:
- Frame the asset, not the room. Shoot close enough that bystanders, whiteboards and desks are out of frame.
- No screens showing customer or employee data. For a test result, show a login screen, a status page or a diagnostic output, not an open mailbox or a patient record.
- Never photograph passwords, recovery keys or badge numbers. If a configuration step involves credentials, record that it was done, not the credential.
- Respect site rules. Some hospitals, bank branches and secure facilities ban photography in certain areas. The POD profile for those sites should specify the alternative — a facility log reference or an escort’s confirmation — before the engineer arrives.
Buyers should also ask where POD photos are stored, who at the provider can see them, and how long they are kept. POD is evidence for the buyer, not a photo library for anyone with a login.
How should buyers audit proof of delivery at scale?
Audit proof of delivery in three layers: automated checks on every ticket, a monthly human sample, and a quarterly review of trends. Checking every POD by hand does not scale past a handful of sites; checking none means the standard decays quietly.
Layer 1 — automated checks on every ticket. Required fields present, photos above a quality threshold, geotag within radius, serials matching the asset register, timestamps captured by the app. These should block closure, not just flag it.
Layer 2 — a monthly human sample. Pull a sample of completed tickets each month and review them against the POD profile. Weight the sample toward P1 incidents, high-value sites and any engineer or subcontractor with a recent rejection. Track the rejection rate by provider, region and job type.
Layer 3 — the quarterly business review. Bring POD metrics to the QBR alongside SLA attainment: POD first-submission acceptance rate, rejection reasons, average time to correct, and any tickets where the evidence contradicted the SLA report. A provider whose SLA numbers look excellent but whose POD rejection rate is climbing deserves a closer look.
A short worked example shows why the layers matter. Imagine a retailer with 120 stores receiving roughly 400 on-site visits a month across three providers. Automated checks block 6% of submissions for missing photos and get them corrected on site. The monthly sample of 40 tickets finds that one provider’s “tested OK” notes rarely have supporting evidence, and that this provider also has the most repeat visits to the same stores. Neither signal alone would justify action; together, they give the buyer a specific, evidence-backed conversation for the QBR. (The figures in this example are illustrative, not drawn from a real programme.)
What are the most common proof of delivery mistakes?
The most common POD mistakes are defining evidence too loosely, collecting it in too many places, and never connecting it to money. In practice, they look like this:
- “Photos required” with no further detail. Engineers satisfy the letter of the rule with one distant shot of a building. Define what must be in frame.
- Evidence scattered across email, chat and spreadsheets. A photo sent on a messaging app to a coordinator is not a POD record; it cannot be searched, audited or reconciled against an invoice.
- Different standards per subcontractor. Multi-country programmes often inherit each local provider’s own habits. The buyer ends up with strong evidence in one country and none in another. One POD profile should apply across every provider.
- POD captured after leaving the site. Evidence uploaded hours later, from home, is much weaker than evidence captured during the job — and any missing piece now needs a second visit.
- No link between POD and payment. If an invoice line is payable whether or not the POD is compliant, POD quality will drift. Linking acceptance of the POD to billing is the single strongest enforcement mechanism.
- Treating POD as a provider tool, not a buyer asset. If the buyer cannot export its own evidence, the buyer does not control it.
How does Centoffer handle proof of delivery?
Centoffer is a global IT field services platform — a Services OS™ connecting enterprises, IT service providers and vetted field engineers, operated by Brocent Asia Cloud Service Pte. Ltd. in Singapore. Proof of delivery is built into how every job closes rather than added as a reporting step at month end.
On a Centoffer job, the engineer captures POD on site through the engineer app: photos of the completed work, a client sign-off by on-screen signature or confirmation code, a geotag and a timestamp, together with a completion note. The POD is sent to Centoffer’s Global Service Desk and to the client portal at the same time, SLA compliance is calculated from it, and it feeds straight into billing. POD photos are checked against quality standards, and a rejected POD resets the completion clock rather than letting a weak record close the ticket. Our article on how Centoffer’s geo-dispatch and POD capture flow works walks through that sequence step by step.
For buyers running field IT across many sites or countries, the result is one evidence standard across every provider in the programme, rather than a different habit in each market. If you are setting up or re-tendering a multi-site field service programme, see how Centoffer’s global IT field services combine dispatch, SLA governance and proof of delivery under one contract — or talk to our team about defining POD profiles for your own job types.
Summary: proof of delivery is how a buyer turns a ticket into evidence
Proof of delivery in field service is not paperwork for its own sake. It is the only way a buyer can verify SLA performance, reconcile invoices, diagnose repeat faults and answer an auditor without relying on the word of the party being measured. The strongest programmes define a POD profile per job type, capture evidence in-app at the time of the visit, make the SLA clock depend on a compliant POD, keep personal data out of frame, and audit in layers. Each element — geotag, photo, signature — is weak on its own; captured together and cross-checked, they are what makes “resolved” mean something.
Frequently Asked Questions
What is proof of delivery in field IT service?
Proof of delivery (POD) is the verifiable record a field engineer captures to close an on-site IT job. It typically includes timestamped photos of the work, a location record, the serial or asset tag of the device touched, a sign-off from a named site contact, and a brief note of what was done. It turns a ticket status into evidence a buyer can audit.
Is a customer signature enough proof of delivery?
No. A signature shows that someone at the site agreed the visit happened, but not what was done, to which asset, or whether it worked. Site contacts often sign quickly without checking. A signature is strongest when it sits alongside photos, an asset identifier and a test result, and when the signer is a named person rather than a scribble.
Does a GPS geotag prove an engineer was on site?
A geotag is supporting evidence, not proof on its own. GPS.gov notes that smartphone GPS is typically accurate to about 4.9 metres under open sky and gets worse near buildings, which is where most IT work happens. Treat the geotag as one signal to cross-check against arrival times, photos of the site and the site contact's confirmation.
What should a POD photo show for a hardware replacement?
At minimum: the faulty unit's label or serial before removal, the replacement unit's serial after installation, the installed position (rack unit, desk, port), and a screen or indicator showing the device working. If the removed part is data-bearing, add evidence of its chain of custody or sanitisation, as agreed in the contract.
How often should buyers audit proof of delivery?
Automated checks should run on every ticket, for example that required photos and fields are present before closure. On top of that, a monthly human sample of completed tickets, weighted toward high-value sites and P1 incidents, catches weak evidence that passes automated checks. Results belong in the quarterly business review alongside SLA attainment.
Who owns POD data — the buyer or the service provider?
The contract should decide this explicitly. A common approach is that the buyer can access and export all POD records for its tickets for the life of the contract plus an agreed retention period, while the provider remains responsible for storing them securely. Without such a clause, evidence can become hard to obtain exactly when a dispute arises.