Open
Start from the teacher's assigned class, group and learner context.
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.

Connect the selected device or learning tool to a useful teaching sequence, rather than asking the teacher to manage another isolated dashboard.
Start from the teacher's assigned class, group and learner context.
Check the agreed device or tool update against the lesson, timetable and institution’s rules.
Keep the decision with the authorised teacher or support team.
Open the agreed attendance, assignment or communication process.
Record the result and pass the relevant details to the next responsible person.
Problem
Uncertain device events leave the teacher checking the whole register instead of the few exceptions.
Show updates from the selected attendance source against the correct class, and agree who checks and corrects uncertain records.
Problem
A classroom observation, missed assignment and support action can sit with different people.
Connect the permitted learner information to a private support action, visible only to staff with the relevant permission, and record the follow-up.
Problem
Repeated class selection and entry can outweigh the benefit of a capable board or app.
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.
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.
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.
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.