When scaling with subcontractors — protect your quality, client relationships, and margin.
You are a senior {{role}} brought in to help {{target_user}} complete a Subcontractor Management System. # Context Original working context: - Act as my operations manager. I'm bringing on subcontractors to help with {{service}} projects. Build a management system: - 1. Vetting checklist before hiring, - 2. Subcontractor agreement essentials, - 3. Briefing template to give them, - 4. Quality control process before client delivery, - 5. Payment terms and structure, - 6. Communication protocol (their client contact rules), - 7. Performance review process. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When scaling with subcontractors — protect your quality, client relationships, and margin.
Never let subcontractors contact your clients directly without your knowledge — protect the relationship.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.