How to audit your remote hands provider: 10 signs of unapproved work

Cómo auditar a tu proveedor de manos remotas: 10 señales de trabajo no aprobado

The ticket says “power supply replacement in rack B14, two hours of labor”. The technician entered at 23:40 and left at 01:10, on a Tuesday. Nobody on your team saw it.

Three months later, that same two-hour line shows up in six different invoices, with three work order numbers and no photo of the work done.

This text is not about accusing anyone. It is about reconciling records, which is exactly what you would do with your electrical provider, your landlord or your insurer. The difference is that in facility you rarely have the base evidence to do it.

What a forensic service audit is

It is the orderly review of primary evidence, not the reading of summaries: the electronic work order with its statuses, the entry log of your room, the raw log of the account that was used and the dated photograph.

Provider reports serve to orient, but they never replace the original data, because a PDF can be rewritten and a system log cannot.

The framework is not new: ITIL 4 separates incident from change and requires each to leave a record, and ISO/IEC 20000 asks to measure service quality with data, not with perceptions. If you cannot measure, you cannot audit.

The 10 signs and the evidence that confirms them

  • Inflated time on site. Ask for the check-in log by technician identifier, not the printed sheet, and cross every interval against the authorized window of the work order. If the clock says 4 hours and the documented work takes 50 minutes, the difference was billed with no counter-evidence.
  • Tickets closed without evidence. The complete file includes the closing note, a photo of the equipment worked on with the serial number visible and the record of the change applied. Without those three elements, someone closed a ticket because someone closed it, not because it was resolved.
  • Duplicated or reopened work orders with no cause. Ask for the full history with all statuses and comments, not just the final status. A reopen with copy-pasted text, the same description and less than 24 hours between them is the classic double-billing pattern.
  • Rotating staff without continuity. Ask for the monthly assignment matrix with full name, identifier and contract type. A provider that never repeats a technician on two consecutive visits has an operational explanation, and deserves to give it to you in writing.
  • Missing before and after photos. The “before” photo is the one that sets the baseline; without it, “after” may be from a different intervention. Require images with date and time metadata, captured on site.
  • Hours outside real coverage. Your room has an access log and, almost always, video surveillance. Cross every billed hour against the authorized shift. Working at three in the morning on a Sunday is not an error: it is a different cost that someone has to explain.
  • Costs that do not add up against volume. Divide the total billed by the number of closed work orders. If the cost per intervention rises quarter over quarter while the number of tickets falls, the cause is not in the operation. Ask for a breakdown by resource: hourly rate, travel and materials.
  • Gaps in the physical entry log. That document is yours, not the provider’s. It must reflect every entry and exit with a timestamp. Twenty- or thirty-minute gaps inside a billed window are minutes that are being charged and that nobody can place.
  • Shared or generic credentials. Require a badge with name, company, photograph and registry, and that data must match the name on the work order and on the check-in record. A credential that only says “provider” leaves no traceability for whoever entered.
  • Refusal to hand over logs or activity reports. This is where the auditable provider is separated from the one that does not want to be audited. Ask for the raw log of the service accounts used in your room, with unalterable timestamps. A rewritten PDF is already an answer.
  • How to request the evidence without breaking the relationship

    Write a five-point document and send it to billing before asking for anything. Request native formats, not PDF. Give a reasonable deadline, ten business days, and remind the provider that if the evidence exists, the review is quick.

    Tone matters more than it seems. Ask for reconciliation, not explanations. “I need these records to compare against the room log” opens a work table; “I think you are charging us extra” closes it.

    Build the baseline before the next cycle

    Capture three numbers every month: average cost per closed work order, percentage of tickets with before and after photos, and share of hours within the authorized window. A three-month series reveals more than any one-off audit, and it is the basis for any conversation.

    All three come from data you already have: the first from your invoice and your ticket manager; the second from the file of each closed work order; the third from the cross between the entry log and the authorized window.

    None of them requires asking the provider for anything, and that is exactly why they are the hardest to dispute.

    Without a baseline, any negotiation with the provider is a matter of opinion. With a baseline, it is a matter of data.

    What to do when a sign repeats

    An isolated sign is noise. The same sign in three consecutive months is a pattern. Store each piece of evidence with date, time, source and the name of who delivered it, and document the provider’s response too: a written refusal is evidence, not an administrative detail.

    Escalate through the contract, with folio and date, not by phone. ITIL 4 already provides for provider performance review, and NIST separates the incident record from its resolution. Applying them is not a conflict: it is the commercial relationship you signed.

    Sources

  • PeopleCert / AXELOS. «ITIL 4: IT Service Management and Vendor Management» — https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1
  • ISO. «ISO/IEC 20000-1: Information technology — Service management» — https://www.iso.org/standard/70636.html
  • NIST. «SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management» (April 2025) — https://csrc.nist.gov/pubs/sp/800/61/r3/final
  • Uptime Institute. «Uptime Intelligence: Data Center Operations & Staffing Research» — https://intelligence.uptimeinstitute.com/
  • Want to master this?

    Noxtel Academy →

    Also in Remote Hands

    ← Back to categories