How to Write a Task Brief with Clear Acceptance Criteria
Use a practical task brief template to agree on scope, review points and evidence of completion.
Reviewed by CallPayMin Team.
A brief should make review possible
Describe an observable result rather than “make it better.” A good brief lets the client and expert agree what is included, what evidence to review and when to discuss extra work. Keep estimates separate from commitments.
Copy this task brief template
Task: What needs to change? Context: Where does the problem occur? Current behavior: What happens now? Desired behavior: What should happen instead?
Inputs and access: Which files, examples and limited accounts are available? In scope: Which changes are included? Out of scope: Which adjacent changes require another agreement?
Acceptance criteria: Which observable checks must pass? Handover: Which files, notes or demonstration are required? Rate and checkpoint: What rate is agreed, and when should progress and spend be reviewed?
Example: a contact form repair
Task: repair the contact form on a staging site. Current behavior: submitting valid input shows no confirmation. Desired behavior: show a success message after a successful submission and a useful error after a failed request.
Acceptance criteria: required fields reject empty values; a valid submission reaches the intended test destination; success and failure messages display correctly; the form remains usable at agreed mobile and desktop widths.
Out of scope: redesigning the website or changing the CRM. Handover: changed files, test notes and deployment instructions. This is an illustrative brief, not a customer result or fixed-price offer.
Agree how to handle uncertainty
If investigation reveals another dependency, stop at the agreed checkpoint, explain the finding and revise the scope together. Avoid treating an initial estimate as permission for unlimited additional time.
Review against the brief
Walk through each acceptance criterion and record any remaining issue. Activity logs help reconcile time, while the acceptance checks establish whether the requested result was delivered. For a new requirement, create another task or explicitly agree on an extension.
CallPayMin billing, recording and payouts
Work charges use the agreed per-minute rate and elapsed billable time. Charges are normally processed at five-minute intervals, with remaining unbilled time settled at the end. This processing interval is not a five-minute price unit. Optional video use can add a separate charge.
Call recording is off by default. Recording requires a request and both participants’ consent. AI summaries and transcripts depend on an approved recording; they are not produced for every call automatically.
Earnings recorded in your account are separate from a bank payout. Experts request a payout from their available balance, subject to the minimum shown in the dashboard, verification and admin approval. Transfer availability and arrival time depend on the payout method, country and bank. A completed session does not mean funds have arrived in your bank account.
Review billing and support details and the refund policy before starting.
Plan your next task
Explore CallPayMin Work or browse technology experts. Availability and results depend on the expert and scope.