The foundations are in place. Execution is the next priority.
Technology (2.44) progressed faster than Process (1.70) and Organisation (1.76), revealing a gap between technological readiness and institutional transformation.
▥
6InstitutionsPublic higher education & TVET
▦
40Academic unitsFaculties, schools & equivalents
◎
19Readiness dimensions3 building blocks · 8 pillars
◈
2026Assessment baselineDevelopmental readiness · not ranking
SERI READINESS ARCHITECTURE
National readiness profile
Three building blocks · scale of 0–4
2026
The eight readiness pillars
Select a pillar to explore its diagnostic.
0–4
SYSTEM COMPARISON
Higher education vs TVET readiness profile
Group averages reported for HEIs (UBD, UNISSA, UTB, KUPU SB) and TVET institutions (PB, IBTE).
0–4
INSTITUTION × BLOCK
Readiness pattern across six institutions
Exact 2026 Process, Technology, Organisation and overall scores from the national report.
2026
National pillar anchorInfrastructure · 2.75
Relatively strong technological foundation with established connectivity, hardware and digital learning platforms.
Digital tools are mainly used to support traditional teaching rather than transform learning. General digital skills are common, but specialised digital and AI skills, digital assessment and stakeholder engagement remain limited.
Technology
Institutions have strong infrastructure and digital systems, but many systems are disconnected and data sharing is limited. AI adoption is also slow due to concerns about ethics, privacy, academic integrity and staff capability.
Organisation
Staff have basic digital skills, but professional development, governance and policies are not well coordinated. The greatest weakness is the lack of clear digital-transformation roadmaps with timelines, budgets and measurable targets.
01Uneven digital-transformation maturity
The national score of 1.97 indicates that digital transformation remains uneven and partly institutionalised.
02Technology–practice gap
Robust infrastructure is a crucial foundation, but it does not by itself guarantee improved educational outcomes; purposeful integration into pedagogy, governance and institutional decision-making remains the challenge.
03Governance & implementation gap
Staff digital literacy often reflects individual readiness rather than institution-wide transformation. The Roadmap score of 1.00 signals weak translation of strategic intentions into priorities, timelines, responsibilities and measurable outcomes.
04HEI–TVET gap
HEIs averaged 2.09 overall compared with 1.73 for TVET. The report notes that TVET institutions face larger hurdles adapting digital tools to hands-on, practical and competency-based curricula.
System-generated signals based on baseline priorities and current implementation records.
Rule-based
Transformation portfolio health
Current action distribution, execution risk and evidence assurance.
Diagnostic coverage
Are the weakest verified SERI areas actually receiving intervention?
Institution implementation signals
Implementation visibility without institutional ranking.
Institution
Actions
Active
At Risk
Verified Evidence
Signal
Roadmap-stage balance
Shows whether transformation remains concentrated in early governance activity.
Stage 1
GOVERN
0 actions
Stage 2
INTEGRATE
0 actions
Stage 3
SCALE
0 actions
Stage 4
SUSTAIN
0 actions
Executive decision questions
Questions senior leadership should be able to answer from the current evidence base.
What changed since baseline?
Longitudinal outcome intelligence only becomes available after a future reassessment cycle is verified and published.
No post-baseline reassessment data available
The portal can currently report actions, risks, evidence and learning after the 2026 baseline. It cannot yet claim that SERI readiness scores have improved or declined.
Intelligence logic
Transparent rules used to generate the executive signals above.
Signal
Rule
Unaddressed priority
Verified priority area has no linked transformation action.
Execution risk
Action status is At Risk or target date has passed while action is not Completed.
Evidence assurance gap
Action is Completed but has no evidence record with Verified status.
Inactive institution
Institution has no action with status In Progress, At Risk or On Hold.
Portfolio imbalance
Action distribution is disproportionately concentrated in one roadmap stage.
Outcome movement
Only calculated from verified published reassessment cycles — never from action percentages.
National Diagnostic
Readiness diagnostic
Explore building blocks, pillars and the 19 SERI dimensions using verified 2026 baseline scores.
STAGE 4 · NATIONAL PILLAR INTELLIGENCE
Eight-pillar readiness profile
Verified national pillar averages on the SERI 0–4 scale. Select a pillar to inspect its cross-institution profile.
01234
Higher national pillar2.75Infrastructure · report-highlighted relative strength
Lower national pillar1.33Stakeholder Engagement · report-highlighted priority
Profile spread1.42Descriptive difference between highest and lowest pillar averages
PILLAR LENS
Selected national pillar
A source-faithful view of the selected pillar across all six institutions.
2.75/ 4.00 national average
Building blockTechnology
Institution range2.00–3.25
HEIs have a relatively strong technological foundation, with established connectivity, hardware and digital learning platforms.
INSTITUTION × PILLAR
Readiness pattern across the eight SERI pillars
Exact institution-level pillar scores from the 2026 national report. Colour intensity indicates maturity on the report’s 0–4 scale.
Move from national system signals into institution, building block, pillar, dimension, academic unit and evidence layers.
Current evidence depth
Baseline → Institution → Pillar
Dimension-level national data and report-derived academic-unit Process scores are available; underlying evidence records are not yet loaded.
Diagnostic profile
Verified 2026 baseline view.
Baseline, not ranking
—
/ 4.00
Scope
National
Layer
Pillar
Data status
Verified 2026 baseline
Select a diagnostic layer to view its verified baseline signal.
Available next-level detail
Click a component to move deeper into the diagnostic.
Academic units
Participating faculties, schools and equivalent units for the selected institution.
Evidence layer
Future drill-down will connect validated evidence directly to the selected diagnostic record.
Detailed evidence not loaded into this prototype
Evidence references from future assessment cycles should be linked to institution, academic unit, dimension and validation status before being shown here.
Academic-unit Process scores
The report provides faculty/school-level Process data. Technology and Organisation were assessed at institutional level.
*Source consistency note: page 13 labels the third Process component “Assessment”, while the SERI framework and page 12 use the pillar “Teaching & Learning”. The portal preserves the page-13 label rather than silently relabelling the source. Institution-level pillar scores in the portal use page 12.
How this drill-down should work in production
The intelligence chain becomes progressively more specific without losing the national context.
Level 1
NATIONAL
System-wide readiness signal.
Level 2
INSTITUTION
Institution-specific baseline.
Level 3
BLOCK
Process, Technology or Organisation.
Level 4
PILLAR
Eight SERI capability pillars.
Level 5
DIMENSION
Nineteen diagnostic dimensions.
Level 6
ACADEMIC UNIT
Faculty / school-level detail where applicable.
Level 7
EVIDENCE
Validated source records and supporting evidence.
Data-integrity rule: if a lower level has not been loaded or validated, the portal should stop the drill-down and state “data not available” rather than calculate or infer values.
Institutional Intelligence
Institutional readiness landscape
Compare verified 2026 institutional profiles against the national baseline, then inspect each institution’s building-block pattern and report-stated strengths and improvement areas. This remains diagnostic, not a league table.
Overall readiness relative to the national baseline
Six verified institutional overall scores shown in the same order as the national report.
National baseline · 1.97
01234
Royal-blue dot: institution overall scoreGold diamond: national baseline 1.97
INSTITUTION LENS
Selected readiness profile
2.43/ 4.00
2026 VERIFIED OVERALL
UBD readiness profile
Technology is the strongest building block in the verified UBD profile; Process is the lower relative block.
Strongest blockTechnology · 3.26
Lower relative blockProcess · 1.89
Within-profile spread1.37 points
Strengths stated in report
Areas for improvement
The strongest/lower-relative labels and spread are calculated from the three verified block scores; they are descriptive portal summaries, not separate SERI indicators.
SOURCE SNAPSHOTS
Six verified institutional profiles
Exact scores plus strengths and areas for improvement stated in the national report.
Interpretation rule: use these profiles to identify different transformation needs, not to create an institutional league table.
Source: SERI 2026 National Report, pp.12 & 20Institution scores are verified 2026 baseline values · developmental diagnostic only
Report-Aligned Way Forward
National recommendations & implementation priorities
This page reproduces the action direction in the September 2026 SERI national report and separates national recommendations from implementation horizons.
Source-backed recommendations; wording is kept close to the report.
Report p.25
01Establish a National Digital Framework
Develop a coherent national framework through the Ministry of Education to align digital-transformation goals with Wawasan Brunei 2035.
02Draft Shared Policy Guidance
Formulate collective standards for ethical AI use, data governance, cybersecurity and system interoperability.
03Embed Specialised Digital Competencies
Systematically map discipline-specific digital skills across academic programmes and introduce authentic digital assessments.
04Mandate Institutional Roadmaps
Require each institution to develop a phased, resourced and measurable digital-transformation roadmap.
05Formalise Stakeholder Partnership
Strengthen structured and sustained partnerships and formalise stakeholder-engagement mechanisms across institutions.
06Sustain Evidence-Based Monitoring
Conduct SERI assessment every two to three years to measure progress against the national baseline.
Source note: the p.25 slide repeats the roadmap description under Recommendation 05. The portal retains the Recommendation 05 title and uses supporting partnership language from pp.12 and 26 rather than duplicating the roadmap text.
Immediate
Within 12 months
Establish or confirm institutional taskforces
Develop or update institutional roadmaps
Conduct policy and staff-capability gap analyses
Map digital competencies in priority programmes
Prepare common guidance on AI, data governance and cybersecurity
Convert SERI diagnostic priorities into governed institutional actions with ownership, milestones, risk and evidence.
Progress data rule
Entered actions only
No implementation progress is inferred from the 2026 assessment.
You are viewing this module in read-only mode for the selected role.
0
Total actions
0
In progress
0
At risk
0
Completed
0%
Average progress
Action
Institution
SERI area
Stage
Owner
Status
Progress
Target
0
No transformation actions recorded yet
Add the first real action when an institution begins responding to a SERI diagnostic priority.
Not Started0
In Progress0
At Risk0
Completed0
On Hold0
Roadmap stage portfolio
Counts are calculated from actions entered in this prototype.
0–12 months
GOVERN
0 actions
Years 1–2
INTEGRATE
0 actions
Years 2–3
SCALE
0 actions
Years 3–5
SUSTAIN
0 actions
Governance controls
Minimum information required for a credible transformation action.
Named accountability
Every action should have a responsible owner and, where needed, a supporting unit.
Diagnostic linkage
Actions should connect to a SERI block, pillar or dimension rather than exist as generic projects.
Evidence before completion
A “Completed” status should later require supporting implementation or outcome evidence.
Progress history
Production deployment should preserve every progress update rather than only the latest percentage.
Prototype storage: actions entered here are saved only in this browser using local storage. They are not uploaded to a server and do not modify the verified SERI baseline.
Evidence Assurance
Evidence & Learning
Connect transformation actions to documentary evidence, implementation artefacts, verification status and lessons learned.
Evidence principle
Completion requires proof
A completed action should eventually be supported by verified evidence.
Validated practices highlighted in the 2026 report
Three Process examples identified in the report. Scores are reproduced exactly.
You are viewing this module in read-only mode for the selected role.
0
Evidence records
0
Draft
0
Submitted
0
Verified
0
Completed actions without verified evidence
Evidence
Institution
Linked action
Type
Date
Status
Verified by
E
No evidence records yet
Register documentary, implementation or outcome evidence against a real transformation action.
Completion assurance
Completed actions should be supported by credible evidence, not only a progress percentage.
Learning notes
Capture what changed, what worked and what should be adapted.
Evidence verification workflow
Recommended production assurance sequence.
Stage 1
Draft
Evidence record prepared.
Stage 2
Submitted
Sent for verification.
Stage 3
Verified
Authorised reviewer confirms evidence.
Stage 4
Archived
Historical or superseded record retained.
Evidence quality controls
Minimum standards for credible transformation reporting.
Traceability
Evidence should link to a specific action and SERI diagnostic area.
Verification
Submitted evidence should remain distinct from evidence formally verified by JPT or an authorised reviewer.
Outcome distinction
Implementation artefacts show that activity occurred; outcome evidence shows whether the intended result was achieved.
Learning capture
The system should record not only what was delivered, but what changed in practice and what needs adjustment.
Prototype storage: evidence records are saved only in this browser using local storage. No documents are uploaded to a server in this version.
Historical Baseline
Assessment Cycle 2026
This section records the completed assessment and validation cycle. It is separate from post-SERI transformation progress.
6
Institutions
40
Academic units
3
Building blocks
19
Dimensions
Mixed-method assessment design
Self-assessment was triangulated using documentary evidence, validation interviews and institutional visits/observations where applicable. Process was assessed at faculty/school level; Technology and Organisation were assessed institution-wide.
Important: completion of the 2026 assessment does not mean an institution has completed transformation implementation.
Longitudinal Intelligence
Assessment Cycle Comparison
Compare future reassessment cycles against the verified 2026 baseline without turning SERI into an institutional ranking.
Current comparison status
2026 baseline only
No future reassessment dataset has been published.
2026
Verified baseline
Published national baseline. Locked and used as the reference point for future movement.
2027
No published reassessment
Future data will appear here only after upload, validation, officer review and verification.
Future
Longitudinal series
Each assessment cycle will remain separately stored rather than overwriting earlier results.
National movement summary
Future comparison values will be populated from published reassessment cycles.
↑ Improved→ Stable↓ Declined— No data
Measure
2026 Baseline
Comparison Cycle
Movement
Trend
Overall SERI
1.97
—
—
Awaiting reassessment
Process
1.70
—
—
Awaiting reassessment
Technology
2.44
—
—
Awaiting reassessment
Organisation
1.76
—
—
Awaiting reassessment
Interpretation control: a future score will not automatically be labelled “improved” or “declined” until JPT defines the minimum movement that is considered substantively meaningful. This avoids over-interpreting trivial score changes.
Institution movement matrix
Movement is assessed against each institution's own baseline, not against another institution.
Institution
Overall
Process
Technology
Organisation
UBD
—
—
—
—
UTB
—
—
—
—
UNISSA
—
—
—
—
PB
—
—
—
—
IBTE
—
—
—
—
KUPU SB
—
—
—
—
No published reassessment cycle exists yet. The matrix will populate automatically once a future cycle passes the publish gate.
What this comparison should answer
Executive questions enabled once longitudinal data exist.
Where has readiness measurably improved?
Identify movement by block, pillar and dimension against the 2026 baseline.
Which gaps persist?
See dimensions that remain weak across multiple assessment cycles.
Where has progress stalled?
Distinguish stable capability from areas requiring renewed intervention.
Are actions translating into readiness gains?
Later, connect reassessment movement with transformation actions and evidence.
Dimension movement view
The 19 dimensions will become the main longitudinal diagnostic layer.
Dimension
2026
Future Cycle
Change
Interpretation
Roadmap
1.00
—
—
Awaiting reassessment
Stakeholder-related dimensions
Low baseline
—
—
Awaiting reassessment
Assessment
1.56
—
—
Awaiting reassessment
AI Adoption in Education & Research
1.78
—
—
Awaiting reassessment
Digital Infrastructure Readiness
2.83
—
—
Awaiting reassessment
Comparison governance rules
Policy decisions required before longitudinal interpretation becomes official.
Meaningful movement threshold
JPT should define how much score movement is needed before classifying an area as improved, stable or declined.
Comparable methodology
Future cycles must preserve sufficient methodological consistency for valid trend interpretation.
Framework versioning
If dimensions or scoring rules change, the portal must record framework version and avoid invalid direct comparisons.
No rank conversion
Comparative views remain baseline-oriented and should never become institutional league tables.
Future comparison data contract
Minimum fields required to make longitudinal comparison reliable.
Assessment Cycle
Year / cycle identifier
Framework Version
Ensures like-for-like comparison
Institution
Stable institution identifier
Academic Unit
Where Process is assessed at unit level
Dimension
Stable SERI dimension identifier
Score
Validated 0–4 score
Validation Status
Only verified/published data used in executive comparison
Data Governance
Data Management & Upload Centre
Controlled ingestion of future SERI datasets. New data passes through mapping, validation and approval before it can affect executive dashboards.
Current published dataset
2026 Verified Baseline
Locked · protected from accidental overwrite
Published assessment cycle
2026
Verified national SERI baseline
Institutions covered
6 / 6
Baseline coverage complete
Academic units
40
Validated in the 2026 cycle
Validation issues
0
For the locked published baseline
Dataset registry
Published datasets are locked; operational datasets remain editable.
Dataset
Cycle
Status
Access
National SERI Baseline
2026
Verified
Locked
Institution Baseline Profiles
2026
Verified
Locked
Transformation Actions
Live
Operational
Editable
Evidence Registry
Live
Operational
Editable
Future SERI Reassessment
2027+
Not loaded
Staging only
Data publishing rule
The dashboard never reads directly from an unvalidated spreadsheet.
Governance control:
Raw Excel / CSV → Staging → Column Mapping → Validation → Review Changes → Approval → Published Dataset
Baseline protection
The verified 2026 baseline remains immutable unless a formally authorised correction is made.
Version history
Future cycles are stored separately rather than overwriting previous years.
Publish gate
Executive dashboards update only after validation and approval.
Upload a new SERI dataset
Prototype workflow for future Excel / CSV imports.
Staging environment
Step 1
UPLOAD
Select Excel or CSV and identify the assessment cycle.
Step 2
MAP
Map source columns to SERI standard fields.
Step 3
VALIDATE
Check completeness, duplicates, score ranges and required fields.
Step 4
REVIEW
Compare changes against the currently published cycle.
Step 5
PUBLISH
Authorised approval makes the new cycle visible to dashboards.
Drop Excel / CSV here
Prototype only — files are not uploaded in this version.
Expected standard fields
The importer can map differently named source columns into these fields.
Standard field
Example source headings
Institution
Institution · HEI · Institution Name
Academic Unit
Faculty · School · Unit · Faculty Name
Building Block
Block · SERI Block
Pillar
Pillar · SERI Pillar
Dimension
Dimension · Indicator Area
Score
Score · SERI Score · Final Score
Evidence / Reference
Evidence · Source · Document Ref.
Validation checks
Minimum controls before a dataset can move to review.
Required fields
Institution, dimension and score cannot be blank.
Score range
SERI readiness scores must remain within 0.00–4.00.
Duplicate detection
Duplicate institution / unit / dimension records are flagged.
Framework integrity
Unknown blocks, pillars or dimensions require mapping or correction.
Coverage checks
Missing institutions or expected units are highlighted before approval.
Future Data Quality Dashboard
Operational visibility for the SERI secretariat before publication.
Submission coverage
6 / 6
Institutions represented in current baseline.
Unit coverage
40
Academic units represented.
Completeness
—
Calculated for future imported datasets.
Warnings
—
Displayed after future dataset validation.
Data Governance
Data Quality & Validation
Operational assurance before any new assessment cycle can be published. This dashboard separates system checks, officer review and final verification.
Publish gate
No staged dataset
Upload a prototype CSV below to run local validation checks.
Validation workflow
A dataset cannot move directly from upload to publication.
Stage 1
Uploaded
File received into staging.
Stage 2
Mapped
Columns aligned to SERI fields.
Stage 3
System Validated
Automated quality checks.
Stage 4
Officer Reviewed
Warnings and anomalies resolved.
Stage 5
Verified
Authorised validation sign-off.
Stage 6
Published
Dashboard dataset updated.
—
Records received
Rows in staged dataset
—
Institutions
Unique institutions detected
—
Missing fields
Required values absent
—
Duplicates
Repeated key records
—
Invalid scores
Outside 0.00–4.00
—
Unknown framework
Unrecognised institutions/dimensions
Validation issue profile
Counts are populated only after a staged CSV is tested.
Missing required fields
—
Duplicate records
—
Invalid score values
—
Unknown institutions
—
Unknown dimensions
—
Publish readiness
The system blocks publication when critical validation rules fail.
No staged dataset
Run a validation check to determine whether the dataset is ready for officer review.
The prototype recognises common alternative headings such as HEI, Institution Name, Faculty, School, Block and SERI Score.
Validation rules currently modelled
These rules form the minimum viable assurance layer.
Institution
Required and must match one of the six participating institutions.
Dimension
Required and must match one of the 19 SERI dimensions.
Score
Required, numeric and between 0.00 and 4.00.
Duplicate key
Institution + Academic Unit + Dimension must be unique.
Coverage
Institution-level presence is summarised before officer review.
Issues requiring officer review
The production system should support issue assignment, resolution notes and verification sign-off.
No validation results yet
After a staged CSV is tested, representative issues will appear here with row number, issue type and recommended action.
Access Governance
Roles, Access & Governance
Define who can view, edit, validate, verify and publish SERI information before production deployment.
Core principle
Least privilege
Users see and change only what their role and institutional scope require.
JPT Superadmin
National scope · Full platform administration
Manage datasets, users and framework configuration
View and edit all institutions
Approve / publish validated datasets
Manage actions and evidence nationally
JPT Verifier
National scope · Assurance and verification
Review staged data and validation issues
Verify evidence records
View institution diagnostics and actions
No framework or user administration
HEI Focal
Institution-scoped · Operational contributor
View own institution diagnostic profile
Create and update own institution actions
Submit evidence and learning notes
Cannot publish national assessment data
Executive Viewer
National scope · Read-only leadership access
View Executive Overview and Intelligence
View national / institution diagnostics
View progress and evidence assurance
No create, edit, delete, verify or publish rights
Permission matrix
Recommended minimum access model for production.
Capability
Superadmin
Verifier
HEI Focal
Executive
View executive dashboards
✓
✓
Own HEI
✓
View national diagnostic
✓
✓
Read only
✓
Upload assessment dataset
✓
Review only
—
—
Validate staged data
✓
✓
—
—
Publish assessment cycle
✓
Recommend
—
—
Create / edit actions
✓
Review
Own HEI
—
Submit evidence
✓
Review
Own HEI
—
Verify evidence
✓
✓
—
—
Manage users / roles
✓
—
—
—
Change SERI framework structure
Controlled
—
—
—
Institutional scoping rule
HEI focal access should be restricted by institution identifier.
Own institution only
A UBD focal should not be able to edit UTB, UNISSA, PB, IBTE or KUPU SB operational records.
National data remains centrally governed
HEI focal users can contribute operational data, but cannot alter the locked national baseline or publish reassessment cycles.
Cross-institution visibility
Any cross-institution comparison visible to HEI users should be explicitly approved and remain non-ranking.
Segregation of duties
High-trust actions should not rely on a single user step.
1
Contributor
Uploads or submits data/evidence.
2
Validator
Checks data quality and anomalies.
3
Verifier
Confirms evidence / readiness for publication.
4
Publisher
Authorised national publication step.
Production governance requirements
Controls to implement when the prototype moves to a real database and authenticated users.
Authentication
Named user accounts
No shared operational login for contributors, validators or verifiers.
Authorisation
Role + institution scope
Every database write should be evaluated against role and institutional scope.
Audit
Immutable change history
Record who changed what, when, and the previous value.
Approval
Explicit publish gate
Validated data do not become executive data until authorised publication.
Versioning
Framework + assessment cycle
Historical cycles and framework versions remain traceable.
Data retention
Preserve evidence lineage
Archived evidence remains available for audit without appearing as current evidence.
Prototype limitation: this role simulator is front-end only. It demonstrates intended behaviour but is not a security control. Production access must be enforced in the database / backend, not merely by hiding buttons in the interface.
Production Foundation
Production Data Architecture
Define how raw SERI data moves safely from institutional files into validated, versioned and publishable intelligence.
Architecture principle
Raw data ≠ published score
Official scores are produced only through a versioned, approved calculation method.
Layer 1
Source data
Excel / CSV submissions, institutional evidence and approved reference datasets.
Layer 2
Staging & validation
Raw rows, column mappings, data-quality checks and unresolved issues.
Layer 3
Verified assessment records
Clean records linked to cycle, framework version, institution, unit and dimension.
Layer 4
Published intelligence
Versioned official scores, actions, evidence and executive dashboards.
End-to-end ingestion pipeline
The future portal should automate this chain without bypassing validation or approval.
01
SOURCE FILE
Excel / CSV received from approved source.
02
IMPORT BATCH
File fingerprint, uploader, cycle and timestamp registered.
03
RAW STAGING
Original values preserved before transformation.
04
MAP & VALIDATE
Columns mapped; missing, invalid and duplicate values checked.
05
VERIFY
Authorised review confirms records are fit for use.
06
CALCULATE
Approved scoring rules create official derived scores.
07
PUBLISH
Versioned cycle becomes visible to executive dashboards.
Assessment-cycle registry
Historical cycles remain separate and immutable after publication.
Cycle
Framework
Status
Records
Published
2026
SERI HEI 2026
Verified baseline
Verified source
2026
Locked
Scoring-method protection
Why a raw upload should not immediately change national SERI scores.
Required production rule: every calculated score must reference a framework version and a calculation version. The system should never silently average uploaded rows and call the result an official SERI score unless that aggregation rule is explicitly approved.
Reproducibility
The same verified input and calculation version must reproduce the same published score.
Method changes
If scoring methodology changes, old cycles retain the calculation version originally used.
Audit trace
Every published aggregate links back to verified source records and the calculation rule that produced it.
Local staging lab
Functional prototype: register and inspect a standardised CSV as a future assessment-cycle import batch.
Browser-local prototype
This prototype accepts CSV. Production ingestion should support controlled XLSX parsing as well.
0
Rows
0
Institutions
0
Critical issues
0
Warnings
0
Mapped required fields
Source preview
First 12 rows only. Original file remains outside the published score layer.
Publishing here records only cycle metadata and validation status in browser local storage. It does not create official SERI scores and does not modify the locked 2026 baseline.
Core production tables
Recommended relational model for a PostgreSQL/Supabase-class backend.
Domain
Table
Purpose
Reference
institutions
Stable institution registry.
Reference
academic_units
Faculty / school registry linked to institution.
Framework
framework_versions
Versioned SERI definition.
Framework
building_blocks / pillars / dimensions
Locked diagnostic hierarchy per framework version.
Cycles
assessment_cycles
2026 baseline and future reassessment cycles.
Ingestion
import_batches
File-level provenance and processing state.
Ingestion
staging_records
Raw source rows preserved before validation.
Quality
validation_issues
Structured errors, warnings and resolutions.
Assessment
assessment_records
Verified dimension-level source records.
Calculation
calculation_versions
Approved scoring / aggregation logic version.
Publication
published_scores
Official versioned dashboard scores.
Transformation
transformation_actions
Actions linked to SERI diagnostic areas.
Transformation
action_updates
Immutable progress history.
Evidence
evidence_records
Evidence and learning registry.
Governance
user_role_scopes
Role + institution access scope.
Audit
audit_log
Who changed what and when.
Minimum assessment data contract
Fields required to make a future raw-data pipeline reliable and auditable.
Field
Purpose
Rule
Assessment Cycle
Separates longitudinal datasets
Required
Framework Version
Controls comparability
Required
Institution
Stable institutional scope
Required
Academic Unit
Faculty / school-level source where applicable
Conditional
Building Block
Process / Technology / Organisation
Required
Pillar
Framework hierarchy
Required
Dimension
19-dimension diagnostic key
Required
Score
Validated source score
0.00–4.00
Evidence Reference
Traceability to supporting source
Recommended
Source Record ID
Stable row lineage
Generated if absent
What happens when a future dataset is published?
Target production behaviour.
Assessment
Cycle becomes selectable
The verified cycle appears in Assessment Comparison and institution diagnostic views.
Calculation
Official aggregates regenerate
Only the approved calculation version may create national, institutional, pillar and dimension aggregates.
Dashboard
Published views refresh
Executive pages read the new published-score layer while retaining historical cycles.
Comparison
Movement becomes available
2026 versus future-cycle movement can then be calculated against the locked baseline.
Audit
Publication is traceable
Batch, verifier, calculation version and publisher are preserved.
Rollback
Previous cycle remains intact
A bad future publication can be superseded without rewriting the 2026 historical baseline.
Reference & Methodology
SERI 2026 source, framework & assessment design
All baseline scores and report-derived findings in this portal are cross-checked against the September 2026 national report.
Department of Higher Education (HiED), Ministry of Education, Brunei Darussalam. (September 2026). Smart Education Readiness Index (SERI): National Report on Digital Transformation of Public Higher Education and TVET Institutions in Brunei Darussalam. SERI HEI project commissioned by HiED, MOE and implemented by SEAMEO VOCTECH.
Open source report28 pages · Prepared by Department of Higher Education · September 2026
Study objectives
Evaluate current digital readiness across six public HE and TVET institutions using the SERI Framework.
Identify institutional strengths, gaps and challenges related to digital transformation.
Validate findings through triangulation of quantitative and qualitative data.
Develop recommendations and action plans for each institution to strengthen DT strategies.
Provide evidence-based insights to support HiED in national policy and framework development.
Source: report p.4.
Mixed-method assessment design
01
Quantitative
SERI self-assessment scores via JotForm.
02
Qualitative
Validation interviews and supporting evidence.
03
Triangulation
Verify scores to reflect current practices.
Source: report p.5.
Validation evidence
Document evidence
Module guidelines, MoUs, student assignments, screenshots, reports, records and other supporting materials.
Interview evidence
Context and clarification beyond documents to verify scores and understand institutional practices.
Observation evidence
Optional visits to digital systems, infrastructure and facilities, plus review of student work such as projects or prototypes.
Source: report p.6.
Unit of analysis
Process was assessed at faculty/school or programme level. Technology and Organisation were assessed at institutional level because related systems and services were mostly centrally managed.
6
Institutions
40
Schools / faculties
3
Respondent groups
Source: report pp.3, 7–8.
Data collection process
Four-step sequence stated in the report.
Report p.8
1Standardised tool
SEAMEO VOCTECH developed the SERI HEI assessment tool and distributed it to six participating HEIs via JotForm.
2Three respondent groups
Each institution completed the assessment through one group for each building block.
3Three forms
HEIs received separate JotForm links and QR codes for Process, Technology and Organisation.
4Review & validation
The research team reviewed scores and evidence before scheduling validation visits.
Talent ReadinessDigital Literacy of Academic & Non-Academic StaffContinuous Professional Development (CPD)Taskforce
Framework provenance: the report states that SERI was tested at regional level, was originally designed for TVET and training institutions, and was adapted for higher education with greater emphasis on digital transformation, AI in education and research, and overall institutional readiness. Source: report p.10.
Higher scores indicate greater digital-readiness maturity. The report describes the national 1.97 baseline as the “learner stage”, with uneven implementation.
Source: report p.11.
Report conclusion
The assessment provides the first consolidated national baseline of digital-transformation readiness across six public higher education and TVET institutions, covering 40 participating faculties, schools and equivalent academic units. The report calls for a shift from technology provision and individual initiatives towards integrated transformation, with SERI used to guide improvement and monitor progress.
Source: report p.27.
Source consistency notes
Page 12 vs page 13: PB and IBTE institution-level Process component figures on p.13 do not fully match the institution-level pillar table on p.12. The portal uses p.12 for institution-level pillar scores and reproduces p.13 only for academic-unit Process detail.
Page 13 terminology: the third Process row is labelled “Assessment” although the framework identifies “Teaching & Learning” as the pillar and “Assessment” as a dimension. The academic-unit table preserves the source label.
Recommendation 05: the p.25 description duplicates the institutional-roadmap wording. The portal uses the report’s “Formalise Stakeholder Partnership” title and supporting stakeholder language from pp.12 and 26.
Transformation Action
Add action
Create a governed action linked to a SERI diagnostic area.
Evidence Record
Register evidence
Link evidence to a real transformation action and record its verification status.
File upload is intentionally not implemented in this prototype. In production, the record should store a controlled document reference or secure file location.