v1
A fictional 45-second tutorial clip calls a static example a live review. The reviewer records Changes requested and explains the missing label.
FOR CREATORS AND PARTNERS / MANUAL RESOURCE
Make the campaign
handoff clear.
Agree on the deliverable, reviewer, version and next action before work gets lost in feedback.
A public planning worksheet. Fill it in using your own agreed process. CodLab does not store submissions, invite participants, send feedback, execute contracts or handle payouts through this resource.
Download the campaign brief · English Markdown ↓
A useful brief has six parts
- Shared objective, intended audience and useful outcome.
- Named deliverables, responsible people, inputs, deadlines and time zone.
- Observable acceptance criteria and how they will be checked.
- Exact submission version, reviewer, feedback and next owner.
- Supporting references with independent access and expiry.
- One next action and a separate publication decision owner.
The download contains blank tables and a fictional example. Keep private customer information out of shared copies; a link does not grant access to its destination. A business acceptance does not validate code or establish legal rights.
FICTIONAL MANUAL EXAMPLE / NO REAL SUBMISSION
A changed version needs a fresh decision
v2
The creator corrects the narration and sample label. The reviewer checks the agreed criteria and records Accepted for the stated criteria for v2 only.
Publication
The named publication owner makes a separate decision. v3 would need another review; v2 acceptance does not carry forward. No results, contract or payout are claimed.
A proposed collaboration journey
Brief → authorized version submission → feedback → revised version → acceptance of that exact version is a proposed future CodLab area. Multi-user roles, storage, permissions and lifecycle still need implementation and qualification. The worksheet works manually today; the application journey is not enabled.
For developers: follow a reproducible source finding →