BTEC and OTHM Assignment Evidence Log Checklist:
Keep Coursework Traceable and Submission-Ready
BTEC／OTHM 作業怎麼穩：用一張「證據紀錄表」清單把基本功做到位（避免白白失分）
Many BTEC and OTHM coursework problems are not caused by weak ability, but by poor alignment with the assignment brief, weak evidence traceability, rushed referencing, or unclear authenticity records. This briefing gives students a simple evidence-log method for keeping coursework organised from Day 1.
Many BTEC and OTHM coursework problems are not caused by weak ability, but by poor alignment with the assignment brief, weak evidence traceability, rushed referencing, or unclear authenticity records. This briefing gives students a simple evidence-log method for keeping coursework organised from Day 1.
Start with the brief: turn requirements into a 1-page map
Before writing, break the assignment brief into a simple map: tasks, learning outcomes or assessment criteria, word guidance, required format and submission rules.
A useful working table is: criterion, where it appears in your draft, and which evidence file or appendix supports it.
Build an evidence log from Day 1
An evidence log records what you did, when you did it, what output exists, and which criterion it supports. It reduces deadline anxiety because you can see what is already submission-ready.
Keep it simple: date, activity, output filename, and a one-line explanation of the evidence value.
| Evidence-log field | What to record | Why it matters |
|---|---|---|
| Criterion / LO | The exact learning outcome, assessment criterion or task line from the brief. | Prevents writing a polished paragraph that does not answer the required point. |
| Draft location | Section, page, slide number or appendix reference where the evidence appears. | Makes it easy to audit coverage before submission. |
| Evidence file | Interview note, spreadsheet, screenshot, calculation, source extract or production output. | Keeps claims traceable instead of floating as unsupported statements. |
| Source / permission | Reference, data source, consent note, AI-use note or centre instruction. | Supports academic integrity and authenticity checks. |
Make traceability obvious: claims, evidence and sources
Assessors should not have to guess how your argument works. Important claims should be linked to evidence such as tables, screenshots, calculations, production outputs or source material.
If you use AI tools, follow your centre's policy, record the purpose of use, and preserve drafts and notes so your own thinking remains visible.
A practical test is to ask whether a tutor can move from one paragraph to the relevant brief line, evidence file and source without asking you to explain it verbally.
Use the log during drafting, not only at the end
The evidence log should be open while you write. When a paragraph is mainly description, mark it as weak and add analysis, evaluation or a direct link to the criterion.
For group work, the log also helps separate shared outputs from your own contribution. Record meeting notes, task ownership and version history so the final submission does not blur who did what.
Submit a clean pack: naming, versions and authenticity
Small administrative mistakes can create disproportionate delays. Use consistent filenames, keep a final-submission folder, and check that the name and student number match the submission system.
Before submitting, review references, figure labels, appendix links and any required declaration or authenticity statement.
A 10-minute final check before upload
Before upload, open the brief and the evidence log side by side. Tick only what is visible in the final document or named appendix, not what you remember doing.
If a criterion has no evidence, either add the missing support or flag the gap for tutor advice before the deadline. Guessing is riskier than asking early.