Independent work means accountable decisions
Research uses sources, supervision, software and sometimes collaboration. Independence therefore does not mean isolation. A student demonstrates it by understanding the task, explaining decisions, attributing other contributions and taking responsibility for the submitted argument and evidence.
Standards must be available before work begins. A rubric should not be rewritten after suspicion arises so that previously optional drafts become compulsory evidence. Formal misconduct concerns follow their own authorised process; a mark scheme should not become an improvised disciplinary procedure.
Translate learning outcomes into observable performance
Start with what students should be able to do: frame a question, evaluate literature, apply a method, interpret data or build an argument. Write a criterion for each outcome. “Sounds independent” is not observable; “justifies inclusion and exclusion of central sources in relation to the question” is.
Separate product from process. Product criteria cover reasoning, method, evidence and communication. Process records may explain decisions through a search log, data dictionary, analysis journal, annotated draft or reflective note. A larger archive is not automatically better. Each requested object needs an educational purpose.
Request a proportionate process record
Collect only material tied to a learning outcome or declared integrity requirement. A search log can reveal selection decisions; a complete browsing history is disproportionate and exposes private activity. Named version milestones are more intelligible than thousands of automatic cloud saves.
Specify format, timing and retention. Process evidence should arise during the assignment, not be demanded retrospectively following an allegation. Offer equivalent routes where a particular cloud platform, device or writing workflow is inaccessible. Handwritten and offline work should not be penalised without a subject-based reason.
A reflective discussion can fill contextual gaps if it is part of the announced design or proper procedure. Use questions about the research problem, sources, method and revision. Nervousness, disability or language difference is not evidence of non-authorship. Apply required adjustments.
Never convert a technical signal into rubric points
An AI score is not a performance level. It should not directly reduce a grade or be described as proof that independent work is absent. Metadata, prose style and number of versions are also limited indicators. Where a specific concern arises, refer it through the authorised route rather than embedding a penalty in routine marking.
Calibrate assessors on several sample assignments. Compare reasons and revise ambiguous descriptors before live use. Keep examples disciplinary: what counts as a justified method choice in history will differ from laboratory science. Record calibration decisions without building personal suspicion profiles.
Group assignments require separate collective and individual criteria. A strong shared output can coexist with unequal contribution. An announced contribution log, reflection or individual subject discussion may support attribution, provided it remains accessible and proportionate.
Give evidence-based feedback and a reviewable mark
For each criterion, cite the observable feature that supports the selected level. A total without reasons provides little learning value and is difficult to moderate. Mark missing evidence as uncertainty rather than inventing a negative explanation. Use the designated second-marking or review path where judgement remains contested.
The AI-use declaration template records permitted assistance. The guide to communicating an AI score keeps tool outputs outside the mark. The higher-education practice hub joins related materials. The single foundation route is the evidence-review guide.
- Identify learning outcomes and applicable rules.
- Draft observable product and process criteria.
- Announce records and accessible alternatives.
- Calibrate the rubric with sample work.
- Keep technical signals out of point conversion.
- Justify every level with evidence.
- Document feedback and moderation.
A sound rubric recognises accountable judgement rather than prescribing one ideal writing process. It rewards reasoned choices and transparent boundaries around assistance, not the ability to generate a cosmetically perfect digital trail.
Review the rubric after a complete assessment cycle
Aggregate which descriptors produced disagreement and which records students found unclear. Do not infer prevalence of misconduct from low rubric levels. Review accessibility, workload and whether requested evidence actually supported learning outcomes. Amend the next published version prospectively.
Keep the old rubric with the assessments governed by it. Changing examples for future clarity is legitimate; applying new expectations to completed work is not. Version, date and scope allow students and moderators to identify the standard that actually applied.