Case study

KR8 registration and attendance — making a learning programme measurable

An internal system giving KR8 DIGITALS student registration, unique identity numbers, attendance history, graduation management and certificate issuance.

Historically reportedClient approval: not requestedIn use internally. Public features limited to non-sensitive descriptions.

1. Background

The context before anything was built.

KR8 DIGITALS teaches in cohorts, with multiple programme streams and several attendance points. A programme that cannot say who attended cannot credibly issue a Certificate of Professionalism.

2. Problem

What was actually wrong or missing.

Registration lived in forms and chats, attendance in messages, and graduation decisions in memory. As cohorts grew, the programme could not prove its own outcomes.

3. Objective

What success was supposed to look like.

Build an internal system that records enrolment, identifies each student uniquely, captures attendance consistently, and supports graduation and certificate decisions.

4. Proposed solution

The approach, in plain terms.

A database-backed registration and attendance system with student records, unique KR8 identity numbers, attendance types, attendance history and a graduation workflow. The specific attendance types and administrative controls are internal and are not published.

5. Timfire's exact role

What he did, and what he did not do.

Designed and built the system for KR8 DIGITALS programme delivery.

6. Team and contributors

Who else was involved.

Timfire as designer and developer, working with KR8 programme leads.

7. Development process

How the work moved from idea to delivery.

  1. Define what must be recorded for a graduation decision to be defensible.
  2. Design registration with unique identity numbers.
  3. Capture attendance across defined attendance points.
  4. Provide attendance history per student.
  5. Support graduation lists and certificate issuance.

9. Deliverables

What was handed over.

  • Registration
  • Unique KR8 identity numbers
  • Attendance capture and history
  • Graduation and certificate workflows

10. Features

What the thing can do.

  • Identity-number based student records
  • VIP tagging
  • Attendance history
  • Graduation management

11. Results

Only what can be evidenced.

What is claimed, and what is not

The system is in operational use for programme delivery. No student records, attendance passwords or identifiable participant data are published here.

12. Lessons

What the work taught.

Education work becomes credible when its records are structured. The system was less about software than about making a promise auditable.

13–16. Status, demonstrations, references and approval

Project status
In use internally. Public features limited to non-sensitive descriptions.
Client approval
not requested
Public reference
Not published
KR8 registration and attendance — making a learning programme measurable | Timfire