A subcontractor brought on quickly to cover a capacity gap, without a real onboarding process, is exactly how confidentiality gets thin, client access gets broader than it should be, and quality ends up inconsistent with the standard the client actually expects. The urgency that usually accompanies bringing on a subcontractor is exactly what makes skipping the checklist tempting.
A real onboarding process doesn't need to be slow. It needs to cover the handful of things that actually create risk if skipped.
A subcontractor added quickly to cover a gap is how problems quietly slip in
The pressure that usually drives bringing on a subcontractor, a deadline, an unexpected gap, is exactly the pressure that makes it tempting to skip proper onboarding. That's precisely when the risk is highest, not a reason to lower the bar.
Confirm confidentiality terms before any client access is granted
Client information, files, and communication should never be accessible to a subcontractor before confidentiality terms are actually signed, not verbally agreed to and formalized later. Get this in place first, before any access, not as a follow-up step.
In Stelaah, access to a client's projects and files can be scoped precisely per team member, so a subcontractor gets exactly what the work requires without broader default visibility. See how team works.
Scope access to exactly what the work needs, not broad default visibility
Granting a subcontractor the same access level as a full team member, out of convenience, exposes far more client information than the specific work actually requires. Scope their access deliberately, to exactly what the assignment needs.
Set the same quality bar explicitly, not an assumed shared standard
A subcontractor doesn't automatically share your internal standard for what "done" looks like unless it's communicated explicitly. State the quality bar directly, with examples if useful, rather than assuming it's understood.
Decide in advance how they're introduced to the client, if at all
Whether a subcontractor is introduced to the client directly, presented as part of your team, or kept entirely behind the scenes should be a deliberate decision made in advance, not something improvised the first time the question comes up.
A simple checklist
If you do nothing else, do these five things:
- Confirm confidentiality terms before granting any client access.
- Scope access to exactly what the specific work requires.
- State the quality bar explicitly, not as an assumed shared standard.
- Decide in advance how they're presented to the client, if at all.
- Don't let urgency be the reason the checklist gets skipped.
Do that, and bringing on a subcontractor stays a controlled, low-risk decision, not a quiet gap in confidentiality, access, or quality.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
