1. Skill Development Platform
  2. Features
  3. Assessment evidence
Feature · Assessment evidence

Assessment evidence

Keep learner references, scores and verification states attached to the request they support.

OverviewVerified Assessments
Skill Development Platform · Assessment evidence

Verified Assessments

Learning evidence

New
ParentLine numberLearner referenceOccurred atScoreRevision
LR-36923920LR-95325 Oct75280
LR-62232270LR-99413 Oct40400
LR-13481860LR-50405 Oct30120
LR-91649180LR-41613 Oct90640
LR-12559490LR-94314 Oct75250
6 of 6 records
LR-953Learning evidence · LE-68790
Assessment
ParentLR-36923
Line number920
Occurred at25 Oct
Score75
Revision280
Example screen with sample data

What you can do

Make the learning result inspectable

Assessor records individual evidence lines under the learning request. Each line has a number and revision, with a learner reference, occurrence date and evidence type where applicable. Assessment entries can carry a score and a Pending, Verified or Rejected verification state. These details let the completion decision examine a saved assessment result rather than infer achievement from attendance.

Supporting files add the material needed to understand the result. A clearly titled assessment document can be attached to the same request with its uploader and visibility. Credential Reviewer then has the context needed to examine a skill case, while Auditor can follow the evidence used for the request’s recorded completion.

How the work is organized

  • Evidence identity. Line numbers and revisions distinguish entries under the request. A consistent learner-reference convention helps staff identify which person’s work the line describes without relying on a free-form document title alone.
  • Assessment result. The score and verification state explain the recorded result. The team agrees who checks the assessment material and how a Pending entry becomes Verified or Rejected.
  • Evidence purpose. Attendance, Assessment, Credential and Payment identify different kinds of evidence. The completion check requires a verified Assessment entry; other evidence types serve their own operating purpose.

What to agree during setup

Agree the score scale and the evidence expected for the pilot skill. Define who checks the result before it is marked Verified and how a rejected assessment is corrected. Keep those decisions consistent with the actual learning objective rather than treating any numeric score as sufficient proof.

Choose a learner-reference convention that the assessor and coordinator both understand. Decide how the evidence line and its supporting file identify the same work. Set attachment visibility deliberately, especially where assessment material includes personal information. Establish what evidence must be reviewed across the cohort before the Program Administrator asks for learning completion.

Check the handoff on an actual case

For a rehearsal, use a practical spreadsheet task completed during a skills cohort. Record an Assessment line with the learner reference, score and occurrence date, then attach the relevant work sample or assessment record. Have the responsible person follow the agreed verification procedure and inspect the saved result.

Attempt the completion command while the assessment remains Pending and confirm that it cannot satisfy the verified-evidence requirement. Repeat the check with an attendance-only record to establish the same boundary. Once the assessment is Verified, inspect whether its request and revision agree with the completion command. Ask Credential Reviewer to identify the precise evidence line and file that support a later skill credential case.

What your team sees

  • Verified Assessments — Assessment entries with verified status, learner reference and score for completion review.
  • Assessment Evidence Review — Pending assessments that still need the agreed evidence check.
  • Internal Request Files — Working files retained with the request and their uploader details.

What it keeps track of

Data model
Learning evidence
Individual pieces of attendance, assessment, credential or payment evidence recorded against a learning request.
Learning requests
Enrollment and delivery requests for a program cohort, tracked from request through completion.
Record attachments
Files attached to a learning request as supporting evidence.
Credential reviews
Credential review cases that carry a skill, assessor score and evidence reference to an independent reviewer.

Who uses it

Permissions
Assessor
Records and checks assessment evidence under the agreed procedure.
Credential Reviewer
Examines evidence supporting a skill case.
Program Administrator
Requests learning completion.
Auditor
Reads the result and its supporting material.

Set up Skill Development Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started