What is a Practical Observation?

Practical observations are assessment tools designed to evaluate student performance in real-world or simulated scenarios. Unlike assessments that test theoretical knowledge, observations focus on demonstrating practical skills, workplace behaviours, and competency in authentic contexts.

Nimbu’s observation tool allows Trainers to record evidence in real-time using digital checklists. This ensures that practical skills, such as operating machinery, providing first aid, or conducting a client consultation which are assessed consistently and captured as robust evidence.

What's Covered in This Article

This guide explains how practical observations function in Nimbu:

What Are Practical Observations?

Practical observations are activity content that captures evidence of student performance in practical, real-world, or simulated workplace scenarios. They enable trainers to assess skills, behaviours, and competency that cannot be measured through written assessments alone.

Key characteristics:

  • Focus on demonstrating practical skills and workplace behaviours
  • Conducted in real-world or simulated environments
  • Can involve trainer observation, student submission, or both
  • Support multiple question types for evidence collection
  • Can be applied to entire classes simultaneously
  • Support multiple attempts to achieve competency

Observation Types

Nimbu supports two distinct types of observations based on who completes them.

  1. Trainer Observation

Trainer-only observations contain questions that only the trainer completes. Students do not interact with or submit responses.

Characteristics:

  • All questions are "trainer questions"
  • Automatically available in marking upon class activation
  • No student action required before marking
  • Ideal for direct observation scenarios

Use cases:

  • Observing students performing tasks in a workplace
  • Assessing professional conduct during work placement
  • Evaluating safety procedures in a simulated environment
  • Checklist-based skill verification

Example: A trainer observes a student performing a customer service interaction and completes a checklist of behaviours and communication skills demonstrated.

  1. Student Observation

Student observations contain questions that require student input before the trainer can mark. These may include:

  • Student-required questions (must be completed by students)
  • Trainer-only questions (completed by trainer)
  • Or a combination of both

Characteristics:

  • Requires student submission before trainer marking
  • Students complete their portion first
  • Trainer then completes observation and marking

Use cases:

  • Practical tasks requiring documentation (e.g., work samples, photos, completed forms)
  • Skills demonstration with written reflection
  • Portfolio-based evidence collection
  • Self-assessment combined with trainer observation

Example: A student submits photos and a written report of a completed carpentry project, then the trainer conducts an in-person observation and completes their checklist.

Observation Question Types

Observations support three question types for collecting evidence:

  • Checklist (document with checkmark icon) : Verify specific criteria or competency indicators
  • Short Answer (pen icon): Capture written responses or reflections
  • Online Submission (upload arrow icon): Collect files, photos, or documentation

This variety allows you to design observations that capture exactly the evidence needed for competency determination.

Observation Workflow

Observations move through distinct stages from assignment to completion. The exact workflow depends on your RTO's configuration and the observation type.

1. Awaiting Activate

If Trainer Activation Required is enabled for the observation, it begins in Awaiting Activate status.

At this stage:

  • The observation is assigned but not yet accessible to students
  • Trainers must manually activate it in Class Management
  • Upon activation, trainers can set read-only time, open time, and due date
  • Students receive notification when activated

Trainer observations can be activated immediately upon class activation or manually activated later.

2. Awaiting Completion

After activation (or if activation is not required), the observation shows Awaiting Completion status.

Trainer observations:

  • Available immediately in the trainer's marking queue
  • No student action required

Student observations:

  • Student can view requirements and terms/conditions (if configured)
  • Must accept terms/conditions before starting (if required)
  • Must click "Start" to begin completing their portion

3. In Progress

For student observations only:

The status changes to In Progress once a student begins working on their submission.

At this stage:

  • Students complete required questions
  • Work is automatically saved
  • Students can exit and return to continue later
  • Must submit before trainer can mark

Trainer observations skip this stage entirely, as trainers access them directly for marking.

4. Be Marked

After submission (for student observations) or upon activation (for trainer observations), the observation appears in the trainer's marking queue as Be Marked.

At this stage:

  • Trainer reviews student submissions (if applicable)
  • Trainer completes observation checklists or questions
  • Trainer assigns results to individual criteria or questions
  • Trainer may request resubmission if evidence is insufficient

5. Completed

Once the trainer finalises marking and assigns a result, the observation shows Completed status with either Satisfactory (S) or Not Satisfactory (NS) outcome.

At this stage:

  • Result is locked and recorded
  • Feedback is permanently accessible to students
  • Evidence is preserved for compliance and audit
  • The observation can be repeated if needed

Note: Observations do not have an "Awaiting Accept" status at the task level. Result acceptance occurs at the unit enrolment level when students acknowledge their overall unit outcome.

Key Features of Observations

Apply to Class

A distinctive feature of observations is the ability to apply questions to the entire class rather than individual students.

How it works:

  • When creating observation questions, you can enable "Apply to class"
  • The trainer's answer to that question applies to all students simultaneously
  • Ideal for whole-class observations or shared criteria

Use case: A trainer observes an entire class during a fire safety drill and uses one checklist to mark all students' performance, rather than completing separate checklists for each student.

Terms and Conditions Acceptance

Observations can require students to accept terms and conditions before starting. Students must read and accept these terms before they can begin the observation.

Repeatability

Observations can be conducted multiple times for the same student:

  • Allow additional opportunities to demonstrate competency
  • Conduct progressive skill checks throughout a course
  • Re-observe after corrective training or practice

Resubmission Capability

Trainers have flexible options when marking observations:

Resubmission scope:

  • Full resubmission: Student redoes all student-required questions
  • Selected questions: Student resubmits only specific questions

Resubmission timing:

  • Immediately: Student can start resubmission right away
  • Lock until date: Observation locked until specified date/time, then automatically opens
  • Manual activation: Trainer must manually reactivate in Class Management

Important: Trainer-only questions are not affected by resubmission requests. Any answers trainers have already input remain unchanged.

  • Creating a Practical Observation (Happy Path)
  • Observation Question Types
  • Marking Observations
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us