Connected Campus · Classroom operations

The board is smart. The teacher should not work twice.

When the board, register and learning app each need the same information, new technology adds another handoff. Start with the assigned class, the learner and the action the teacher needs to take.

Your separately ordered BCO classroom integration connects the selected tools to attendance, learning, support and communication workflows—configured, tested and accepted before your agreed launch, with professional judgement kept with the teacher.

Realistic classroom concept showing teacher and learners connected to roster, attendance, resources, communication, support and notification workflows
Classroom workflow illustration. Selected tools support the teacher's judgement, context and next action.
Before connecting classroom tools
Bring
A repeated teacher task and the tools your institution uses.
Check
Class context, staff permissions and the next teaching action.
Agree
The selected connections, support roles and classroom acceptance tests.
Your commissioned workflow

Keep the class details together. Make the next action simpler.

Connect the selected device or learning tool to a useful teaching sequence, rather than asking the teacher to manage another isolated dashboard.

01

Open

Start from the teacher's assigned class, group and learner context.

02

Understand

Check the agreed device or tool update against the lesson, timetable and institution’s rules.

03

Decide

Keep the decision with the authorised teacher or support team.

04

Act

Open the agreed attendance, assignment or communication process.

05

Follow through

Record the result and pass the relevant details to the next responsible person.

The moments that matter

Make the investment serve the teaching day.

Problem

Attendance interrupts the lesson.

Uncertain device events leave the teacher checking the whole register instead of the few exceptions.

Your commissioned BCO response

Show updates from the selected attendance source against the correct class, and agree who checks and corrects uncertain records.

Problem

A learner needs help. The context is scattered.

A classroom observation, missed assignment and support action can sit with different people.

Your commissioned BCO response

Connect the permitted learner information to a private support action, visible only to staff with the relevant permission, and record the follow-up.

Problem

Every tool asks the teacher to start again.

Repeated class selection and entry can outweigh the benefit of a capable board or app.

Your commissioned BCO response

Design the selected connection around the class, staff permissions and next action. Agree in the implementation plan how each tool passes work to the next.

Acceptance before launch

Judge the workflow from the teacher's chair.

The checks agreed for acceptance follow the actual teaching day: open the class, understand the learner’s situation, act and handle something unexpected without losing the learner relationship.

Commissioned for your classrooms

The workflow leads. The technology fits.

Classroom-device and third-party learning-tool integrations are commissioned separately from the base ERP subscription. Your order names the selected tools, how they connect, delivery stages and the checks required for acceptance. The agreed integration is configured, tested and accepted before the agreed launch.

Operating design

Your teaching context

  • Assigned classes, teachers and learner groups.
  • Selected attendance, learning and communication actions.
  • What each staff role may see and do, who reviews decisions and how corrections are made.
  • Staff handover and the classroom checks agreed for acceptance.
Integration agreement

Your delivery scope

  • The selected boards, devices or learning tools, and the ways they can connect.
  • How users sign in to each connected tool, who supplies its licence and which provider supports it.
  • Accessibility, consent, permitted access and how long information is kept.
  • Testing, support ownership, usage costs and launch dates.

The agreed scope lists each connected tool and how it passes work to the next, so your institution can distinguish included ERP features from separately ordered integrations. Read the Connected Campus buyer questions.

Continue the Smart Campus story

Follow the connected operating context.

Make the next classroom investment earn its place.

Bring a teacher's repeated task and the tools your institution uses. Define the context and handoffs a connected workflow should preserve.