Guides
How to find work worth replying to, and how to reply so it gets read.
- Replying to a freelance briefConnect your experience to the brief and ask useful scope questions.
- Replying to a developer briefCheck code dependencies, testing and what delivery includes.
- Replying to a design briefExplain your design contribution and clarify production and feedback.
- Replying to a video editing briefClarify the footage, versions and review stages.
- Replying to a marketing briefSeparate campaign diagnosis from implementation and spending.
- Replying to a data project briefCheck source files, reporting definitions and repeat use.
- Replying to a writing briefClarify the reader, source material and approval process before proposing a writing assignment.
- Replying to a customer support briefCheck support channels, coverage and escalation responsibilities before agreeing to handle a queue.
- Replying to a sales briefDefine prospect selection, qualification and handover before offering sales support.
- Replying to a consulting briefIdentify the decision, evidence and sponsor before proposing a consulting investigation.
- Replying to a finance briefClarify records, exceptions and review responsibilities before preparing a finance handover.
- Replying to a product briefIdentify the product decision, research access and ownership before proposing discovery or backlog work.
- Replying to an IT support briefSeparate investigation from repair and clarify access, approval and recovery arrangements.
- Replying to a virtual assistant briefDefine inbox permissions, calendar decisions and working hours before offering virtual assistance.
- Replying to a management or operations briefClarify the sponsor's authority, process boundaries and trial handover before proposing operations work.
- Replying to an engineering project briefSeparate model delivery from prototype testing and agree which references and reviews the work depends on.
- Replying to a recruiting project briefDefine the hiring criteria and who may contact candidates before promising a shortlist.
- Replying to an architecture or 3D briefClarify the intended use of the images, the reference drawings and the editable files the client needs.
- Replying to a QA testing briefDescribe test coverage, safe checkout checks and a report the developer can reproduce.
- Replying to a teaching or tutoring briefConnect your teaching approach to the learner's task, materials and session arrangements.
- Replying to a translation briefClarify the language audience, source version and terminology decisions before proposing translation work.
- Replying to an audio production briefSeparate recording limitations, editorial decisions and final exports in an audio proposal.
- Replying to a photography briefDefine capture or editing responsibilities, image selection and sample approval before proposing the work.