BL TECHNO Global School Management Platform • Local-currency pricing Explore the platform
← Feature LibraryADMINISTRATION FEATURE
SC
BL TECHNO FEATURESchool Command

Bring school-wide operational work into one command centre.

Give authorised management users a focused operational surface for school context, centre context, timetable records, transferred learner history, contracts/documents and connected action areas.

Built for Owners • Principals • Administrators • Operations
Command CentreSchool / Centre ContextTimetableLearner HistoryContractsDocuments
FeatureSchool Command
Operating areaAdministration
Product familyBL TECHNO School
Access modelRole + scope aware
ExperienceResponsive
WHY THIS FEATURE MATTERS

Give authorised school teams a clearer operating view without exposing every control to every user.

Give authorised management users a focused operational surface for school context, centre context, timetable records, transferred learner history, contracts/documents and connected action areas.

See BL TECHNO School →
01School identity
02Centre scope
03Permission model
04Audit-aware administration
HOW SCHOOL COMMAND WORKS

Follow the workflow from first action to review.

Tap a step to change the visual. Each stage comes directly from the feature workflow defined for BL TECHNO.

BL TECHNO School Command Centre illustrative mockupSTEP 01
ADMINISTRATION WORKFLOW

Enter

School / centre context

School Command Centre
BL TECHNO Attendance Control illustrative mockupSTEP 02
ADMINISTRATION WORKFLOW

Review

Operational records

Attendance Control
BL TECHNO Assessment Intelligence illustrative mockupSTEP 03
ADMINISTRATION WORKFLOW

Open

Timetable / learner history

Assessment Intelligence
BL TECHNO Global Billing Command illustrative mockupSTEP 04
ADMINISTRATION WORKFLOW

Manage

Contracts & documents

Global Billing Command
BL TECHNO School Command Dashboard illustrative mockupSTEP 05
ADMINISTRATION WORKFLOW

Act

Move to connected module

School Command Dashboard
OPERATIONAL OUTCOMES

What School Command is designed to improve.

These outcomes describe the operating purpose of the feature without inventing customer statistics.

01

Operational focus

Bring management-oriented records and shortcuts into a focused command environment.

02

Cross-module visibility

Move from school context into connected learner, timetable and document workflows.

03

Management continuity

Keep operational history and records available to authorised leaders.

CAPABILITY MAP

Go inside School Command.

Six capability areas show what the feature organises and how the workflow becomes operational.

CC

Command Centre

Surface management-oriented school context and operational entry points.

School nameCentre scopeRole contextActive status
TT

Timetable

Open and review timetable records from the command environment.

TimetableRecordsSchool contextOperational access
LH

Learner History

Review transferred-learner history where authorised.

Transfer historyLearner contextRecord continuityAdministrative review
CT

Contracts

Keep signed contract and document context available.

Signed contract PDFContract recordsDocument historyAuthorised access
DC

Documents

Add and review school command documents.

Contract documentsDocument uploadSaved recordsOperational archive
LN

Connected Navigation

Use the command area as a launch point into wider BL TECHNO operations.

StudentsCentresUsersSchool services
OPERATIONAL SIGNALS

Bring the information that matters closer to action.

The exact records shown depend on the signed-in user, school configuration and current school data. These labels show the kinds of context this feature organises.

SchoolCurrent context
CentreAssigned scope
TimetableOperational record
TransfersLearner history
ContractsDocument status
RoleAuthorised user
BL TECHNO School Command Centre mockupSchool Command Centre
WHO USES IT

One feature. Different responsibilities.

Switch roles to see how the same feature serves different authorised users without giving everyone the same view.

CONNECTED WORK

School Command does not have to become another isolated tool.

Move into the neighbouring workflows that share relevant school context.

CONNECTED PLATFORM STORY

See School Command as part of the wider BL TECHNO environment.

This public-safe motion teaser uses illustrative marketing visuals and demo interface language. It is designed to communicate the connected platform story without exposing production school data.

IMPLEMENTATION PATH

Introduce School Command as an operating process, not just another screen.

The exact implementation depends on school size, plan and scope. This path shows the practical sequence for introducing the feature responsibly.

01

Discover

Identify where School Command fits into the school’s current operating process and what should improve.

02

Configure

Confirm school, centre, role and permission boundaries before operational use.

03

Prepare

Check the records, settings and authorised users needed for School Command to work cleanly from day one.

04

Train

Walk the responsible teams through the School Command workflow using their real roles and school scope.

05

Launch

Introduce School Command into the agreed school process with controlled access and clear ownership.

06

Review

Review usage, exceptions and operating quality, then refine the school process where needed.

SECURITY & GOVERNANCE

Access follows responsibility.

School Command inherits BL TECHNO’s role, scope and permission principles. Public marketing shows the controls; authenticated product access remains authoritative.

Management-only operational scope
School/centre context
Document access controls
Server-side permission enforcement
Explore Security →
IDENTITYWho is signed in?
ROLEWhat is their responsibility?
SCOPEWhich school / centre / class?
FEATURESchool Command
RESPONSIVE EXPERIENCE

Fit the feature to where the role works.

Responsive management viewsTablet-friendly operational controlPhone-ready review surfacesTouch-friendly navigation
Explore Mobile Experience →
GLOBAL CONTEXT

Keep local school context configurable.

Country and centre contextSchool timezoneLocale/language settingsLTR/RTL-ready architecture
Explore Global Platform →
FEATURE FAQ

Questions about School Command.

It is positioned as a focused operational command area rather than a replacement for every dashboard or module.

The current interface includes transferred learner history, timetable records, signed contracts and contract documents.

Only authorised school-management and administrative roles should receive access appropriate to their responsibilities.

SEE SCHOOL COMMAND IN CONTEXT

Bring this workflow into your tailored BL TECHNO demo.

Inspect the feature in detail, then see how it connects to the product family and wider school operation.