Selected Work / 01
NECA ICT Academy
Engineering the operating system
behind a modern training academy.
NECA ICT Academy coordinates learners, courses, centres, schedules, instructors, attendance and stipend-related operations. Mannova's work focuses on bringing those moving parts into one structured digital environment.
OPERATIONSNECA ICT ACADEMY
The operating context / 02
Training delivery creates more
operational complexity than the classroom reveals.
Running the academy means coordinating multiple layers of activity at once.
Who is enrolled, and in what programme
Which centre and course each learner belongs to
Which class group and schedule applies
Which instructor is responsible for a session
Whether a scheduled training session actually took place
Who attended, and when
What that attendance means for stipend eligibility
Which partners or programmes are involved
Who should have access to which information
As operations grow, manual coordination becomes increasingly difficult to manage consistently.
Before the platform / 03
The operating context
the platform is designed to improve.
Attendance capture relied on paper sign-in sheets with pre-printed learner names. Manual processes can make it difficult to connect attendance with schedules, learners, cohorts and stipend calculations in one consistent operational record.
The system question / 04
How do you turn an academy
into one connected operating system?
The challenge is not simply digitising paper. The platform must understand the relationships between an organisation, its centres, programmes, courses, cohorts, class groups, schedules, sessions, learners, instructors, attendance, stipends, partners and access — and keep them consistent as the academy runs.
Academy domain map / 05
One academy.
Many connected parts.
Key workflows / 06
Four workflows.
One operating rhythm.
QR attendance / 07
A QR code is not
the attendance system.
The QR interaction must connect to the correct session, the right class and group context, eligible learners, attendance records, operational review and downstream stipend logic. The attendance foundation and QR-supported workflow direction are established as part of the platform's engineering direction.
Attendance → stipend logic / 08
From a verified session
to a stipend calculation.
The platform must support the academy's current stipend rule — ₦3,000 per eligible attendance day — and connect that rule to verified attendance records, computed on a weekly basis. This describes the operating rule the system is designed to apply, not a record of payments made.
Access & responsibility / 09
Access should
follow responsibility.
Academy data should not be universally visible or editable. Access-control foundations are being designed so that users can operate within the organisational context appropriate to their role — across centres, programmes, cohorts, class groups and training sessions.
Engineering the foundation / 10
Engineering the foundation
underneath the interface.
A responsive operational interface built with Next.js and React.
Academy workflows and domain logic — programmes, cohorts, sessions, attendance.
A structured relational data model, built on a Supabase-backed foundation.
An authentication and role/permission foundation for organisational context.
Attendance, scheduling, learner and instructor coordination, and stipend logic.
Designed to grow / 11
Designed around entities,
not one location.
The architecture is structured around entities such as centres, programmes, courses and cohorts, rather than a single hardcoded location or course. This is designed to accommodate additional centres, new programmes, new courses, new cohorts and groups, evolving schedules, and further operational workflows.
Current state / 12
A platform being
engineered in stages.
NECA ICT Academy Platform is currently in development.
- Academy domain model
- Core relational schema
- Authentication / role-based access foundation
- Operational interface foundation
- Attendance / QR workflow foundation
- Data-access architecture
- Broader operational workflows
- Attendance operations
- Stipend workflows
- Scheduling experience
- Reporting
- Programme / centre administration
- Further product refinement
What this project demonstrates / 13
The work is not the dashboard.
The work is understanding the operation behind it.
Systems thinking before screen design
Modelling complex operations
Connecting physical-world activity to digital records
Role-aware platform architecture
Turning policy and rules into system logic
Designing for multiple operational entities
Building foundations that can evolve
Next step / 15