Tools & templates

Subcontractor Brief + QA Checklist

Brief a subcontractor and review their work before it reaches your client: a checklist, a copy-ready brief template, a margin example, and QA gates.

checklistUpdated Nov 03, 2026

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

This subcontractor brief and QA checklist helps you hand part of a client project to another freelancer without losing quality. It covers the four things a brief must carry (context, definition of done, ownership, and review) and the checks to run before anything reaches the client.

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.

  1. State the client context, business goal, deliverable, and deadline.
  2. Define what done means and what is explicitly out of scope.
  3. Name dependencies, owners, and the review path.
  4. Complete self-check, internal review, and approval before client delivery.

Why subcontracting fails

Subcontracting usually fails because the brief hides judgment. The owner knows the client context, risk, quality bar, and political sensitivities. The subcontractor receives a task. Then everyone acts surprised when the output technically matches the task but misses the situation.

This checklist forces the missing context into the brief before work starts. It also creates a QA path so the client does not become the first reviewer.

Brief quality controls

  • Context: why the client needs this and what business outcome it supports.
  • Acceptance criteria: what must be true before work is considered done.
  • Examples: references, preferred style, previous work, or anti-examples.
  • Dependencies: assets, access, inputs, decisions, and owners.
  • Review path: self-check, internal QA, client-facing approval, and escalation rules.

QA gates

Before work starts

  • Brief has outcome, scope, deadline, and owner.
  • Subcontractor confirms unclear points in writing.
  • Dependencies are available or explicitly blocked.
  • Margin and revision budget still make sense.

Before client delivery

  • Deliverable matches acceptance criteria.
  • Known client preferences are respected.
  • No unresolved comments or placeholders remain.
  • Owner has reviewed and approved client-facing version.

Copy-ready subcontractor brief

The checklist tells you what the brief must contain. This template is the document you actually send. Fill every placeholder; a placeholder you cannot fill is usually the question you need to answer before anyone starts.

Subcontractor brief template

SUBCONTRACTOR BRIEF

Project: <client or code name> / <project name>
Owner (your name): <name + how to reach you>
Brief date: <YYYY-MM-DD>

1) Context
- Why the client needs this: <one or two sentences>
- Who will use it: <audience or end user>
- What a good result changes for them: <outcome>

2) Deliverable
- What you will hand over: <files, format, length, environment>
- Deadline for first version: <date + time zone>
- Deadline for final version: <date + time zone>

3) Definition of done
- Must be true: <acceptance criterion>
- Must be true: <acceptance criterion>
- Quality reference: <example to match> / anti-example: <example to avoid>

4) Out of scope
- <excluded item>
- <excluded item>
- Ask before doing anything outside sections 2 and 3.

5) Inputs and dependencies
- Provided by me: <assets, access, data> by <date>
- Blocked until: <decision or input still pending>
- Tools and data rules: <where to work, what not to upload, AI tool limits>

6) Questions and review
- Send questions to: <name>, answers within <timebox>
- Self-check before handover: <list or link>
- Internal review by: <name>, within <timebox>
- Revisions included: <number of rounds>; more rounds are agreed in writing

7) Terms
- Fee: <amount + currency>, paid <when>
- Confidentiality and ownership: per our subcontract agreement dated <date>

Confirm by reply: "Brief understood. Open questions: <list or none>."

Section 5 matters more now that many specialists use AI tools. If the client contract limits where their data can go, the brief has to pass that limit on. The Radar briefing on AI-use clauses in client work explains what clients typically ask for and how to word it.

Worked example: check the margin before you brief

A hypothetical example in round numbers. You sell a client a content-migration package for $6,000. A specialist quotes $3,000 for the build. You expect to spend 10 hours writing the brief, answering questions, reviewing, and handling the client.

  • Planned margin: $6,000 − $3,000 = $3,000, or $300 for each of your 10 hours.
  • If a vague brief causes two extra review rounds of 4 hours each, your time rises to 18 hours: $3,000 ÷ 18 = about $167 an hour.
  • If the rework also needs 8 more paid specialist hours at $100, the margin falls to $2,200 over 18 hours: about $122 an hour.

The work did not get harder; the brief got weaker. That is why the “margin and revision budget still make sense” check sits in the first QA gate. If your effective rate after realistic review time is below your own floor from the freelance rate calculator, fix the price, the scope, or the brief before you commit.

Incentives matter

If you pay only for speed, you will often get speed. If the brief does not define quality, the subcontractor has to guess. If revisions are unpaid and unlimited, resentment shows up somewhere. Good subcontracting requires a simple incentive design: clear scope, clear quality bar, fair payment, finite revisions, and fast feedback.

Common mistakes

  • Forwarding the client email as the brief. The client wrote it for you, with context you already have. Rewrite it for someone who has none.
  • No written confirmation. Ask the subcontractor to reply with open questions before they start. Silence is not understanding.
  • Reviewing only at the end. A short check on the first 20 percent of the work catches direction problems while they are cheap.
  • Promising the client dates you have not confirmed. Confirm the subcontractor's timeline and your review window before you commit to a delivery date.

Contracts and related tools

Before you brief anyone, check what your client agreement says about subcontracting, confidentiality, and who owns the work. The freelance contracts guide covers the IP and confidentiality clauses to look for. The incentive side of delegation, including how payment terms shape quality, is covered in subcontractor incentives and quality control.

The brief should match what the client already approved, so build it from your statement of work and the decisions from the client onboarding and kickoff checklist. If you are subcontracting because you are over capacity, the client concentration and capacity scorecard helps you check whether delegation or a smaller pipeline is the better fix.

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. You can protect confidential details while still explaining the goal, buyer, quality bar, and risks.

How much QA is enough?

Enough that the client never becomes the first person to find obvious misses. The higher the client risk, the more explicit the acceptance criteria and internal review should be.

Do I need the client's permission to subcontract?

Check your client contract before you brief anyone. Some agreements restrict subcontracting or require the client's consent. Your agreement with the subcontractor should also carry the client terms that bind you, such as confidentiality, ownership of the work, and deadlines, so you can deliver what you promised.

Who pays for revisions when the subcontractor misses the brief?

Agree on it before work starts. A common split is that rework to meet the written acceptance criteria is included in the subcontractor's fee, while changes caused by new client requests are paid as extra work. That only holds if the brief was clear enough to judge the miss against.

Should the subcontractor talk to the client directly?

Only if you decide it in advance and the client knows who they are working with. Direct contact is faster for technical questions, but it can blur scope and approvals. If you allow it, name what they can answer alone and what must come back to you.

How to customize

  1. Add your specific quality rubric or style notes.
  2. 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

Comments

Sign in to comment.

Loading comments…