Few engineering offices cover every discipline in-house. An architectural practice subcontracts structural work at times; a small office brings in a specialist for mechanical, fire, or geotechnical scope when needed.
That is normal and healthy. What isn't healthy is running the arrangement on a phone call and a verbal understanding — because the client neither knows nor deals with your sub-consultant. You alone answer to them for work someone else performed.
Your Liability Cannot Be Subcontracted
This is the rule most often forgotten: you can subcontract the work; you cannot subcontract the liability.
When the sub-consultant is late, you are late in the client's eyes. When they err, the error is contractually yours. Managing that relationship isn't secondary administration — it is management of risk that lands on you.
What a Sub-Consultancy Agreement Should Contain
- Precise scope of work, matched to what you committed to the client — any gap between the two scopes comes out of your margin.
- Required deliverables, counted: number of drawings, calculations, reports, and file formats.
- The programme, tied to your own client programme with a buffer before your date, not on the same day.
- Number of revisions included, because the client's revisions will land on you and then on them.
- Payment terms and when each instalment falls due.
- Professional liability and its limits, plus insurance where required.
- Ownership of deliverables and the right to use them — a clause ignored until it is needed.
The first item matters most. An office that commits to the client on a wider scope than it subcontracted discovers the gap mid-project — and covers it out of pocket.
Linking What You Collect to What You Pay
The most dangerous aspect of managing sub-consultants is a timing mismatch: paying them before you have collected from your client.
The remedy is to build their instalments on the same logic as your own payment certificates: tied to completed and delivered stages, and timed to follow your collection rather than precede it.
| Mistake | Its effect on you |
|---|---|
| Paying before collecting from the client | You finance your client's project from your own cash |
| Instalments tied to dates, not stages | You pay for work not yet delivered |
| Subcontracted scope narrower than your commitment | You cover the difference from your margin |
| Not posting fees to the project | Project profitability shows higher than it really is |
| No cap on revisions | Every client revision costs you twice |
Sub-Consultant Fees Are Part of Project Cost
This item specifically distorts profitability calculations in many offices. Because the fees are paid from the office account, they get booked as a general expense and never reach the account of the project they were spent on.
The result is a project that looks profitable when it isn't — by exactly what you paid the sub-consultant. On multi-discipline projects that gap can be half the assumed margin.
Review Before Delivery: Never Issue What You Haven't Checked
A deliverable received from a sub-consultant becomes your deliverable the moment you pass it to the client. Issuing without internal review is gambling your name on work you never examined.
Review here isn't redesign — it is checking coordination with the other disciplines, adherence to scope and specification, and completeness of the agreed deliverables. Its time must be built into your programme, not squeezed into the final day.
What Changes When Sub-Consultancy Lives Inside a System
Inside an engineering consultancy management system, five things change:
- Every sub-consultant is linked to the project and the discipline assigned to them
- Their fees are posted to the project, so its real — not optimistic — profitability shows
- Payments are tied to completed stages and comparable against what you collected from the client
- Due, paid, and outstanding are clear per sub-consultant at any moment
- Their deliverables live within the project's drawings with their revisions, not in a separate inbox
Frequently Asked Questions
Am I still liable for the sub-consultant's work?
Yes. The client contracted with you, and usually has no contractual relationship with your sub-consultant. You can subcontract the work but not the liability — which is why internal review before delivery isn't optional.
When should I pay a sub-consultant?
Tie their payments to completed and delivered stages, timed after your collection from the client rather than before it. Paying ahead means financing your client's project from your own cash, and it is the biggest cash-flow strain on smaller offices.
How do I calculate my margin on subcontracted work?
Subtract the sub-consultant's fee from the corresponding portion of your own fee, then subtract your team's hours spent coordinating and reviewing. The second item is always forgotten, and it is what makes the calculated margin higher than the real one.
What if the sub-consultant is late?
The delay lands on you in front of the client. Their programme must therefore run ahead of yours by a genuine buffer, and you must track their progress before the delivery date rather than on it. Checking at the deadline means discovering the delay when you have no time left.
Should I tell the client that part of the work is subcontracted?
Check your contract — some require prior approval for subcontracting. Transparency serves you here: disclosing in advance is far better than the client discovering it from a stamp on a drawing.
Who owns the deliverables?
The sub-consultancy agreement should state this explicitly, allowing you to hand them to the client and reuse them later for maintenance or modification work. The absence of that clause surfaces late — when you need a file and don't hold the right to use it.
Conclusion
A sub-consultant isn't a supplier — they are an extension of your office in front of a client who doesn't know them. Anything left uncontrolled in that relationship shows up later in one of three places: your margin, your cash flow, or your reputation.
Review the last project where you subcontracted a discipline: are the sub-consultant's fees posted to that specific project? If not, that project's profitability in your books is a wrong number.
Read next: Running an Engineering Consultancy — The Complete Guide From Proposal to Handover.