Summary
This guide walks assessors and SDP staff through recording assessment outcomes in skillSYMS: capturing a Competent or Not Yet Competent decision, scoring against the criteria, attaching feedback, and moving the result through the moderation pipeline. Accurate, well-evidenced decisions are the foundation of every QCTO submission.
Who This Guide Is For
- Assessors recording formative and summative outcomes
- SDP staff capturing results on an assessorβs behalf
- Quality officers checking that decisions are complete and defensible
Prerequisites
- An assessment plan and event already set up (see Assessment Instruments, Plans & Events)
- The learner enrolled in the relevant programme and unit standard
- Evidence reviewed and ready to reference
Step 1: Open the Results Workspace
Navigate to Assessments β Results.
The Results tab shows every recorded outcome with the learner, programme, unit standard, assessor, date, result, and pipeline status. The stat cards summarise Total Results plus the Competent, Not Yet Competent, and RPL counts.
Tip: Filter and sort the table before you start. Working through one programme or one event at a time keeps your decisions consistent.
Step 2: Record an Assessment
Click Record Assessment and complete the form:
- Learner and Enrolment β select the candidate and the enrolment being assessed
- Unit Standard ID, Unit Title, and Credits
- Assessment Type β Formative, Summative, Practical, Written, Oral, or Project
- Assessment Date
- Assessor Name and Assessor Registration #
Step 3: Capture the Outcome and Scores
In the same form, set the result:
- Competent (C) β the learner meets all criteria
- Not Yet Competent (NYC) β further development is needed
- RPL β competence recognised through prior learning
- Absent (A) β did not attend or submit
Then record:
- Marks Achieved and Total Marks for scored instruments
- Comments (Internal) β notes for moderators and the audit trail
- Feedback to Learner β specific, actionable guidance
Tip: For every NYC, name the exact criteria not yet met in the learner feedback. This makes re-assessment targeted and gives moderators a clear rationale.
Step 4: Move the Result Through the Pipeline
Each result follows the pipeline: Draft β Submitted β Moderated β Final. Use the bulk actions on the Results table to Mark as Moderated or Request Revision, and Export CSV when you need a snapshot for reporting.
Expand any row to see the full breakdown β criteria scores, evidence referenced, and moderation notes β before it advances.
Step 5: Handle Re-Assessment for NYC
For a Not Yet Competent outcome, agree the gaps with the learner, schedule a re-assessment event (see Assessment Instruments, Plans & Events), and record the new attempt as a fresh result so both attempts remain on file.
Common Mistakes to Avoid
- Leaving feedback blank β unevidenced decisions fail moderation
- Recording marks without an outcome β always set Competent / NYC / RPL / Absent
- Overwriting a failed attempt β record re-assessments as new results to preserve history
- Forgetting the assessor registration number β it is required for QCTO traceability
Verification Checklist
- Every result has an outcome and an assessment date
- Marks are entered where the instrument is scored
- Learner feedback is specific, especially for NYC
- Results have advanced from Draft to at least Submitted
- Re-assessments are recorded as separate results
Next Steps
- Moderation Sampling β quality-assure these decisions
- Assessment Instruments, Plans & Events β the instruments behind each decision
- Statement of Results β turn final results into an SoR
- Assessor & Moderator Workflow β the full workflow