Brief a subcontractor or white-label partner on client work
A brief that sets a subcontractor up to deliver to my standard, with scope, quality bar, client contact rules, and confidentiality.
The prompt
Write a brief for a subcontractor or partner who will deliver part of a client project for me.
The client project and what they're doing: [SUMMARY and their portion]
Deliverables and deadlines: [LIST]
Quality standard: [examples of good work, style guides, tools, file formats]
Budget and how they'll be paid: [fixed / hourly, invoicing terms]
Client visibility: [will the client know they exist, or is this white-label?]
Confidentiality concerns: [what's sensitive]
Create a brief with:
1. Background: the client's goals and why this piece matters (only what they need to know).
2. Scope and deliverables with acceptance criteria, plus explicit exclusions.
3. Timeline with internal review points that leave me time to fix issues before the client sees anything.
4. Rules of engagement: who talks to the client (and who doesn't), how to raise questions, response times, and which brand or email to use if they're client-facing.
5. Quality checklist I'll review their work against.
6. Confidentiality and ownership reminders: client data handling, no portfolio use without permission, and IP assignment as set out in our agreement.
7. Payment terms and what happens if deadlines slip.
Also list the clauses my subcontractor agreement should cover (NDA, IP assignment, non-solicitation of the client), and recommend having that agreement reviewed by a lawyer.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- SUMMARY and their portion
- LIST
- examples of good work, style guides, tools, file formats
- fixed / hourly, invoicing terms
- will the client know they exist, or is this white-label?
- what's sensitive
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a procurement plan for a projectA project procurement plan with make-or-buy decisions, sourcing methods, contract types, a lead-time schedule, risks, and roles.
- Turn a client brief into a statement of work with clear exclusionsA statement of work with objectives, deliverables, acceptance criteria, assumptions, and exclusions that prevents scope arguments later.
- Write a closed-won handoff from sales to customer successA complete handoff document so the customer success or implementation team starts with everything the buyer was told and expects.
- Write a scope of work and SLAs for a 3PL warehouse partnerA clear 3PL scope covering services, volumes, KPIs, pricing basis, and responsibilities to avoid disputes after go-live.