01 /Delivery lead
Agree on the requirements
Define the task format, output, acceptance checks and schedule. Resolve unclear requirements before authoring starts.
Record: Task brief, acceptance criteria and delivery plan.
02 /Task author
Build the task
Write the instructions, reference solution and required environment. Keep the task focused on the skill it is meant to test.
Record: Task package, setup notes and reference solution.
03 /Technical reviewer
Review independently
Check instructions, assumptions and implementation. Look for valid approaches the tests might reject, shortcuts they might miss and results that cannot be repeated.
Record: Review notes and an issue list.
04 /Author and reviewer
Correct and verify
Resolve the findings and run the agreed checks again. If a test fails, investigate the task, environment and verifier as well as the solution.
Record: Correction history and verification results.
05 /Delivery lead
Accept and deliver
Confirm the agreed checks are complete. Package the files and review notes, and keep a clear route for follow-up questions.
Record: Accepted files, delivery notes and open limitations.
Capacity is agreed
for the project.
Team size depends on the work, review effort and current availability. We confirm engineers, reviewers and a delivery contact before agreeing on the schedule.
We can discuss a defined project or ongoing delivery support. Both start with clear responsibilities and acceptance criteria.
Access follows
the work.
We agree on access permissions, handling requirements and retention before receiving project data. The team works within the access and tools approved for the engagement.
Confidentiality, ownership, reporting and delivery terms are covered in the project agreement.