PRODUCT REQUIREMENTS · V1 DRAFT · JUN 2026

STA CLUSTER M&E AND OVERSIGHT PLATFORM

Requirements for the platform behind the screens in this system. Written for the CEO, the M&E core team and the department heads who will report through it.

11 departments · 5 linked modulesAlexandria cluster · ATS 005Dual system · BIBB / GIZ / MoETE
01

Problem and purpose

Departments across the El Sewedy Technical Academy cluster plan and report in separate workbooks. Targets, actuals and deficits exist, but nobody can see the whole cluster at one moment in time, so shortfalls surface late — after a deadline has passed or after an accreditation milestone has slipped. The platform makes one shared record of departmental performance and renders it as a single verdict for the CEO and designated stakeholders.

02

Goals

  • One screen answers: is the cluster on track, and if not, which department and which deadline.
  • Every department reports through the same target / actual / deficit / deadline / note structure.
  • Deviation becomes an alert with an owner and a due date, not a note in a spreadsheet cell.
  • Quarterly monitoring cycle (monthly for Admission, Financial, Business Development, Training, Operation, PMO and Procurement) runs inside the system.
  • Accreditation readiness for BIBB, the German chambers and MoETE is measurable at any moment.
03

Out of scope for v1

  • Student-facing portals, timetabling and grade books.
  • Payroll and accounting ledgers — Financial reports summary lines, not transactions.
  • Replacing the existing admission module; v1 reads from it and reports on it.
  • Automated AI decisions. Recommendations are advisory and always attributed.
04

Users and permissions

RoleSeesCan do
CEOWhole cluster, all departments and modulesRead everything, close escalations, export the cycle report
Designated stakeholder (GIZ, BIBB, MoETE, board)Overview plus assigned modulesRead, comment, download the reports shared with them
Department headOwn department in full, cluster overview read-onlyEnter and confirm data, answer alerts, add notes
Data entry officerOwn department's input formsInsert and edit rows before the cycle is locked
M&E core teamEverythingDefine KPIs and thresholds, run audits, lock and reopen cycles
05

System hierarchy

Four layers, in order, matching the M&E framework: Data insertion (department forms) → Data management (validation, ownership, locking) → Data monitoring (targets against actuals, deficits, deadlines) → Dashboard overview (cluster verdict and escalations). Nothing appears on the overview that did not enter through insertion, so every number on the CEO screen is traceable to a row, an owner and a timestamp.

06

Departments and linked modules

Eleven departments report: Financial, Business Development, Admission, Academic, Training, Operation, Marketing, Alumni, HR, Project Management and Procurement. Five linked modules carry cross-cutting records: Accreditation bodies, Internal QA, Stakeholders' management, Archive and the Employment Portal.

07

Core data record

Every department row uses the same shape, so the roll-up needs no per-department logic.

FieldMeaning
EntityClass, cohort, facility, package or milestone the row measures
Year / occupationProgramme year and track (mechanical, electrical, automotive, logistics, IT)
TargetApproved plan figure for the period
ActualConfirmed figure at the reporting date
DeficitActual minus target, always signed and never hidden
DeadlineDate the gap must be closed by
NoteCause in the owner's own words, e.g. 'BD got only 20 places from Industry'
08

Severity rules

  • On-track: deficit is zero or positive, and no deadline within 14 days is unresolved.
  • At-risk: actual is between 85% and 100% of target, or a deadline falls inside 14 days.
  • Critical: actual is below 85% of target, or a deadline has passed, or an accreditation or HSE item is blocked.
  • The cluster verdict is the worst standing department, stated with the count of critical items and the net financial deficit.
09

Screens in v1

  • CEO Overview — cluster KPI band, verdict, department and module cards, alerts by deadline, strategic recommendations, drill-down table, monitoring cycle spine.
  • Department screen — headline indicator, four departmental KPIs, full monitoring table, department review cycle.
  • Data insertion form — one row per entity with validation against the approved plan, per department and period.
  • Reporting — cycle report export for the CEO and each stakeholder body.
  • This requirements document, kept inside the system so scope stays visible.
10

Alerts and escalations

An alert is created automatically when a row breaches a severity rule, and carries the department, the deficit, the deadline and the named owner. Alerts sort by deadline, not by severity, so the nearest commitment is always on top. An alert closes only when the underlying row clears the rule or the M&E team records a decision against it. Notifications go to the owner, the department head and — for critical items — the CEO.

11

Reporting cycle

Each cycle opens for data insertion, moves to department confirmation, then to M&E review, then locks. Locked figures form the baseline the next cycle is compared against. Quarterly for most departments, monthly for the seven fast-moving ones. Continuous improvement follows the PIER model: each closed cycle produces recorded actions carried into the next.

12

Business intelligence and recommendations

The platform reads across departments to surface causal links a single workbook cannot — an apprenticeship shortfall in Business Development explaining an Admission deficit, which in turn explains a fee-income gap in Financial. Recommendations are written as specific, dated actions with the affected departments named, and are always presented as advice for a human to accept or reject.

13

Success measures

  • Cluster status is current within one working day of any department's update.
  • No critical deficit is discovered after its deadline for two consecutive cycles.
  • Every department submits through the platform, with no parallel workbook in circulation.
  • Accreditation evidence completeness is reportable on demand, without a manual collection round.
14

Release plan

PhaseContents
Phase 1 — VisibilityOverview, department screens, severity rules, alerts, this document. Data loaded from the current workbooks.
Phase 2 — Data ownershipInsertion forms, validation, ownership, cycle locking, notifications, audit trail.
Phase 3 — ModulesAccreditation evidence register, Internal QA audits, stakeholder reporting, Archive index.
Phase 4 — IntelligenceCross-department analysis, recommendation engine, Employment Portal matching and alumni outcomes.
15

Open questions

  • Which system of record holds student registration — the existing admission module or MoETE — when the two disagree?
  • Who signs off a locked cycle: the M&E lead alone, or jointly with the CEO?
  • Do stakeholder bodies read live figures, or only the report published at cycle close?
  • Is the financial deficit reported per class, per campus, or both, for the board?