Skip to content
Qentak — The Education Operating System

Campus & Student Services

Maintenance & Asset Management

Keep a campus issue connected to its resolution.

Bring asset records, reported faults, assigned work and maintenance history into campus operations.

Try the workflow
Facilities manager and technician inspecting classroom equipment
THE PEOPLEAn asset register

Connect identifiers, locations, ownership, and service information.

01 / 03

START WITH THE ACTUAL WORK

Why connect maintenance & asset management?

A reported fault needs a location, affected asset, priority, owner, and history. Without that context, recurring problems look like unrelated requests.

WHAT THIS CAPABILITY BRINGS TOGETHER

Maintenance & Asset Management: records, decisions, and handovers.

01

An asset register

Connect identifiers, locations, ownership, and service information.

02

Owned work orders

Turn a reported issue into a prioritized task with a responsible person.

03

Maintenance history

Retain the work completed, follow-up, and next planned service.

FOLLOW THE WORK FROM START TO FINISH

Explore the maintenance & asset management workflow.

This interactive illustration explains the operating model. It contains no live institutional records.

Campus coordination workspaceIllustrative preview

Prepare

An asset register

Connect identifiers, locations, ownership, and service information.

Current focus

Coordinate

Owned work orders

Turn a reported issue into a prioritized task with a responsible person.

Next handoff

Follow through

Maintenance history

Retain the work completed, follow-up, and next planned service.

Next handoff
STEP 1 OF 4

Register an asset

Register the asset and its location or responsible department.

A WORKED EXAMPLE · ILLUSTRATIVE SCENARIO

A failed projector affects a scheduled lesson

A projector fails shortly before teaching begins. Logging the fault is useful, but the class also needs a workable immediate alternative.

The decision and its context

Record the asset, location and operational impact. Assign the repair owner and coordinate the teaching workaround separately, keeping the issue open until the agreed completion check is satisfied.

What a complete outcome looks like

The requester should see progress and the facilities team should retain repair history. Closing a ticket should mean the required service is restored or an accepted resolution is recorded.

FOLLOW THE HANDOVERFacility & Room BookingsAffected room availability and replacement space need to reflect the maintenance situation.

A CAPABILITY, NOT AN ISLAND

Connect maintenance & asset management with the next workflow.

The same institutional context should support the next responsible team’s action. Explore the connected capabilities.

YOUR INSTITUTION’S RULES

Set the rules for maintenance & asset management.

  • Asset categories and campus locations
  • Priority levels and assignment rules
  • Preventive schedules and closure evidence
Explore configuration and flexibility

WHEN THE DAY DOESN’T FOLLOW THE DEFAULT

A fault affects a booked or teaching space

Flag the operational impact and coordinate room or timetable changes alongside repair work.

A clear exception keeps the reason, owner, and next decision visible.
Education proprietor and school leader reviewing a model of proposed learning spacesMaintenance & Asset ManagementAn asset register → Maintenance history

SEE HOW THE WORK CONNECTS

Maintenance & Asset Management

Facilities teams · Operations managers. Connect identifiers, locations, ownership, and service information.

  1. 01

    An asset register

    Connect identifiers, locations, ownership, and service information.

  2. 02

    Owned work orders

    Turn a reported issue into a prioritized task with a responsible person.

  3. 03

    Maintenance history

    Retain the work completed, follow-up, and next planned service.

Illustrative workflow · Shape the details around your institution.

AUTOMATION WITH A PURPOSE

When a planned service becomes due.

Use an agreed trigger and response while keeping the responsible person in the decision.

WHEN

A planned service becomes due

THEN

Prepare the maintenance task with the asset’s recent history.

How connected workflows work

APPROPRIATE CONTROL

Who can act on maintenance & asset management?

Closure should record who completed and verified the work; purchasing or disposal decisions need the appropriate separate authorization.

Explore security and institutional control

KNOW WHETHER THE CHANGE IS HELPING

Reliable assets and spaces

Review repeated faults, overdue critical work, and the interval between report and verified resolution.

Agree the baseline, reporting period, and owner before comparing results.Connect evidence to decisions

SEE IT IN YOUR CONTEXT

Different institutions. Specific responsibilities.

A practical introduction

Bring a representative workflow, one recurring exception, and the people who own the handoffs.

Plan your implementation

BEFORE THE CONVERSATION

Useful questions about maintenance & asset management.

Can recurring maintenance be planned?

Asset-specific schedules can create a repeatable service obligation while retaining each completed task as a separate historical record.

How does this fit the institution’s operating procedures?

Map the actual service handoffs, staff cover arrangements, and exception procedures first. Test a normal day and a disrupted day with the people responsible for running the service.

PUT YOUR PROCESS IN THE PICTURE

Explore maintenance & asset management in your institution.

Start with your current workflow, the decisions that take time, and the handoffs you want to improve.

This public page presents Qentak’s capability model and an illustrative workflow. Available modules, integrations, operating rules, and rollout scope are established in your implementation plan.

Explore all 69 capabilities