Tools & templates
Subcontractor Brief + QA Checklist
A checklist for briefing subcontractors, defining done, and reviewing quality before client delivery.
When to use this
- You are handing work to a subcontractor or specialist.
- You want cleaner delegation and less rework.
- You are trialing a collaborator on a bounded slice of work.
Preview
Progress
0 / 14 complete
Brief for quality, not only motion.
Context
Definition of done
Dependencies and ownership
QA
How to use this checklist
Run it before work starts and again before anything goes client-facing. The point is not bureaucracy. The point is to stop ambiguity from turning into rework.
- State the client context, business goal, deliverable, and deadline.
- Define what done means and what is explicitly out of scope.
- Name dependencies, owners, and the review path.
- Complete self-check, internal review, and approval before client delivery.
Use with
- Subcontractor incentives and quality control
- Client Onboarding & Kickoff Checklist
- Statement of Work (SOW) Template
FAQ
Should I share the full client context with the subcontractor?
Share enough context for good judgment and clean execution. Hiding the relevant stakes usually increases rework.
How to customize
- Add your specific quality rubric or style notes.
- Store the final version as the default brief for repeatable work.
Common pitfalls
- Sending tasks without enough context for judgment.
- Letting the client be the first meaningful QA step.
Related Codex pages
Read the explanation
Use the tool with the context, not in isolation.
Read Codex: Subcontractor Incentives Quality ControlRead the explanation
Use the tool with the context, not in isolation.
Read Codex: Onboarding Delivery RetentionRead the explanation
Use the tool with the context, not in isolation.
Read Codex: Freelancing Is Game TheoryLoading comments…
Comments
Sign in to comment.