Key takeaways

  • Hand over the physical work: racking, cabling, component swaps, on-site diagnostics and evidence gathering.
  • Keep the relationship, the commitments and the decisions: customer contact, service levels, design, change approval and acceptance.
  • Treat configuration and privileged access as a deliberate decision, not a default.
  • A written job brief does more for quality than any amount of goodwill on the day.

Subcontracting field engineering is easy to describe and easy to get wrong. The risk is rarely that the engineer cannot do the task. It is that nobody agreed who decides what when the situation on the floor does not match the ticket. A clear line between what you hand over and what you keep prevents most of those arguments.

This guide assumes you are a provider using a partner such as DACPROS as part of a white-label arrangement. If you are new to the idea, start with what white-label IT is.

What to hand off

The best candidates for subcontracting are tasks that are physical, well defined and checkable afterwards:

  • Racking and stacking. Mounting equipment, connecting power and network, labelling and testing. See our rack and stack checklist for what a complete job involves.
  • Cabling. Running, dressing, labelling and tracing cabling to a standard you specify.
  • Component swaps. Replacing a failed disk, PSU, optic or card where you or the vendor have supplied the part.
  • Physical diagnostics. Looking at the kit, reading what the LEDs and displays say, and reporting what is actually there.
  • Moves and migrations. Relocating equipment in the sequence you set.
  • Physical decommissioning. Powering down, de-racking and removing equipment on site.
  • Evidence gathering. Recording what was done, with serial numbers, port maps and, where the site allows it, photographs.

What to keep

Some things look like part of the job but belong with you:

  • The customer relationship. Updates, expectations and escalations go through your people. A partner who talks directly to your customer is a partner you have stopped controlling.
  • Service commitments. If you have promised your customer a response or fix time, that promise is yours. A subcontractor cannot absorb it unless they have agreed to the same commitment in writing. Check this before you rely on it, because many field partners work scheduled hours and do not guarantee response times.
  • Design and change approval. The engineer should carry out a change you have approved, not decide what the change should be.
  • Acceptance. Whether the job is done is your call, based on the report and your own checks.
  • Anything needing parts to be sourced. If a repair depends on buying or warranty-claiming a part, keep that with you or the vendor.
The grey zone: configuration and access

Operating system installs, switch configuration and remote management setup sit between physical and logical work. Decide each case deliberately. Where credentials are involved, keeping them with your own team and having the engineer work to your instructions, with a live session if needed, is usually safer than sharing them. Whatever you choose, record it in the job brief.

What a good job brief contains

A brief does not need to be long. It needs to answer the questions the engineer will otherwise ask you from the floor:

  1. Site and access. Facility, cage or cabinet, who raises the access request, what ID is needed, and any restrictions on photography or equipment.
  2. Equipment and parts. What is being installed, moved or replaced, and who is supplying each part. Include delivery receipts if kit is arriving at the site.
  3. Window. The date, the time and how firm it is. Note that attendance is scheduled around location, scope and engineer availability.
  4. Runbook. The steps, in order, with anything that must not be touched.
  5. Definition of done. What you will check before you accept the job.
  6. Escalation. Who the engineer calls if the situation does not match the brief, and what they should do while waiting.
  7. Report. The format and the evidence you need back, so you can pass it on under your name.

If you find yourself writing a long brief, that is a sign the job is better suited to a planned build and deployment project, with a design review beforehand.

Make the exclusions explicit

Every partner has things they do not do. For DACPROS, that includes warranty-backed break/fix and hardware maintenance that needs its own parts sourcing. Recycling, disposal and certified data destruction are handled by partners. Ask any provider for their list, and put it next to yours, so the first time you discover a gap is not in front of your customer.

Where this leaves you

Handing over the physical layer and keeping the relationship, the commitments and the decisions is a split that works for most providers. Overflow work, where you use a partner only when your own engineers are booked, adds one more thing to plan: timing. We cover that in overflow delivery: using a partner when your engineers are booked. To discuss a specific arrangement, get in touch.