Before Their Work Wears Your Name: Five Checks for Subcontractors
Photo: Deutsche Welle from Bonn, Berlin, Deutschland, CC BY 2.0, via Wikimedia Commons
A handshake is a lovely thing. It is also not an insurance policy.
When you run a small consultancy, your reputation is the product. If a subcontractor misses a deadline, sends sloppy work, or goes quiet for a week, the client will not remember their name. They will remember yours. That is the deal you are making when you put someone else's work under your brand.
I have learned to run five checks before that happens. None of them are dramatic. All of them have saved me at least one awkward conversation.
1. Insurance and the boring paperwork
Start with the unglamorous stuff. Ask for a professional indemnity insurance certificate. If the work involves visiting client sites or handling physical equipment, ask about public liability too. Check the limit and the expiry date. Do not accept a verbal yes. A certificate takes two minutes to send and tells you whether they take their own business seriously.
Then there is the paperwork around data. If they will touch client data, you need a data processing agreement. If they will see confidential information, you need a confidentiality clause. If they are a limited company, get the company number. If they are a sole trader, make sure you have their trading name and address. I keep a one-page subcontractor agreement that covers the basics: scope, rate, payment terms, confidentiality, IP assignment, and notice. It is not a legal masterpiece, but it is a clear record of what we agreed.
2. Availability that is real, not optimistic
Freelancers are often optimistic about time. I am one, so I know. The problem is that optimism can turn into a missed deadline with your name on it.
I ask specific questions now. Can you commit to three days in the week of the 14th? What else is on your plate that week? Who is your backup if something goes wrong? Can you hold those days in your calendar before we sign? I also pay attention to how quickly they reply during the enquiry. If it takes four days to answer a paid question, it will take four days when a client is waiting.
I set core hours and a response expectation before work starts. Nothing elaborate. Something like: I need to hear from you within one working day, and immediately if a deadline is at risk. That single sentence prevents most surprises.
3. A paid test task
I do not ask for free samples. Free work attracts a certain kind of person and tells you very little about how someone operates when they are paid.
Instead, I scope a small paid task. A one-page analysis. A short research note. A code review. A draft section of a report. I pay their normal rate, keep it time-boxed, and treat it as a real piece of work. It shows me three things: the quality of their output, how they handle a brief, and how they respond to feedback. It also tests my own brief. If they misunderstand it, maybe I wrote it badly.
A good subcontractor will welcome this. Someone who refuses a paid, scoped test is telling you something. Listen to it.
4. A clear escalation path
Most problems do not start as disasters. They start as small delays that nobody mentions until they become urgent. The fix is an escalation path.
I agree a simple rule: if a deadline is at risk, tell me the moment you know, not the day before. If you are stuck on a decision, ask. If a client changes the scope, flag it before you do the extra work. We use one shared channel for the project and one named point of contact on each side. That sounds corporate for a two-person arrangement, but it stops the dreaded message that begins with sorry for the late reply.
5. Exit, handover and ownership
Finally, decide what happens at the end. Who owns the work product? I ask for an IP assignment so the client owns what they paid for, and so I can hand it over cleanly. What happens if the subcontractor disappears or gets ill? Can I access the files? Do they work in their own tools or mine?
I keep a short handover checklist: source files, drafts, notes, client contacts, passwords where relevant, and a summary of what is finished and what is not. Payment terms and notice period go in the same agreement. None of this is about expecting failure. It is about making success easier to repeat.
The handshake is the start, not the contract. The best subcontractors I have worked with welcome the checks because it means everyone knows where they stand. The ones who bristle are usually telling you something useful. Your name goes on the work. Make sure the handshake has a paper trail.