Custom software for Teaching School Hubs

See the whole hub.
Know what needs you.

Bring your Hub’s data, workflows and reporting into one connected view — built around how your team actually works. Less time reconciling systems, more time acting on what matters.

Live solutions with Berkshire TSH, SFET Teaching School Hub and Swindon & Wiltshire TSH
Illustrative hub dashboard with school map, programme figures and recent activity
Hub dashboard / Illustrative interface, sample data
Explore the work

Fix the workflows
slowing your hub down.

Explore how custom views replace manual admin. Each view is illustrative—your platform is built around your specific processes.

01 / HUB OVERVIEW

Your whole hub, at a glance.

When updates sit across different spreadsheets and systems, getting a clear picture of what’s happening means checking them all.

IN ONE VIEW

An interactive school map, key figures, latest comments or outstanding actions. You decide what’s useful; we bring it together in one view.

Discuss this workflow
Illustrative hub overview showing schools engaged, participants, red schools, overdue QA visits and flagged ECTs
Hub overview Illustrative interface · sample data
Start with a focused workflow, or connect more of the operation over time — scoped to your hub.
Why hubs struggle

When the hub outgrows
spreadsheets and bolted-on tools.

Teaching School Hubs work across programmes, schools and teams that were never designed to fit neatly into one system. The team ends up spread between provider platforms, DfE services, spreadsheets, inboxes and internal tools.

01

Data lives everywhere

Participant, school and programme data sits across different systems, making it difficult to maintain one reliable operational picture.

02

Different workflows, shared data

Each part of the Hub runs differently, but the same schools and records often appear across them — creating repeated checks, reconciliation and manual updates.

03

You lose the bigger picture

When activity is split across systems, it becomes harder to see a school’s full engagement, a participant’s history, or what needs attention next.

The answer is software built around how your hub actually works — connecting the workflows and data that currently sit apart.

See how engagement works
Built with hubs

Built with the teams
doing the work.

Built alongside Teaching School Hub teams, around the workflows, data and reporting challenges they deal with every day.

“The application and ongoing support have helped us move away from managing our Hub across a multitude of spreadsheets and made what was once very complicated feel seamless.”

Susan Watson

Ops Manager, TSH Berkshire

How we work with hubs

Built on experience.
Shaped around your operation.

We start by understanding how your Hub actually works — your workflows, data, systems and reporting requirements.

Then we scope and build around the problems worth solving, whether that’s one specific workflow or a wider Hub CRM.

Clear scope. Practical build. No forcing your team into someone else’s process.

Book a discovery call

30 mins. A practical conversation about your current setup.

01

Friction Audit

A focused 30-minute conversation to identify where manual work, spreadsheets and disconnected systems are slowing your team down.

02

Map & Design

We map your workflows, data and reporting requirements, then shape the system around how your Hub actually operates.

03

Build Fast, Refine Quickly

Get working software into your team’s hands early, then improve it around how they actually use it.

04

Build To Adapt

If your programmes, reporting requirements or internal processes change, the software can change with them.

Practical questions

A sensible place
to start.

You don’t need to arrive with a specification. We can start with the problem, the systems you already use and where your team is losing time.

01. Do we need to replace the systems we already use?

No. Often the best solution sits around the systems you already have to use — bringing their data together, filling the gaps and improving the workflows between them.

02. Can you work with our existing data and provider systems?

Yes. We can work with existing databases, spreadsheets, CSV exports and external platforms, using them as sources of data rather than asking your team to maintain everything twice.

03. Does it have to be a full Hub CRM?

No. Some Hubs need a wider operational system; others need one specific workflow fixed. The scope is based on the problem you’re trying to solve.

04. How much work does implementation create for our team?

The main input is helping us understand your current processes and checking that what we build reflects how your team actually works. We keep this lightweight—requiring just a few short check-ins, with zero heavy lifting or technical work for your staff.

05. How long does a project take?

Once the scope is clear, we move quickly from requirements to working software, so your team starts seeing the benefit within weeks, not months.

06. How do you handle security, GDPR and ongoing support?

Security and UK GDPR requirements are considered from the start, including access controls, data handling and the services used to host the system. We’ll also agree what support and maintenance looks like before launch.

Ready to give your hub
a central brain?

Let's build a system scoped around how your team actually works.

Book a discovery call

A practical conversation about your current setup.