Find a procedure
- Without WorkPane
- Search shared drives, old emails and intranet folders or ask several colleagues for the current version.
- With WorkPane
- Search one governed guidance index and see the owner and review status beside the result.
Critical Developments · Product 01
One dependable starting point for the school day.
The staff dashboard, intranet and single point of guidance.

The operational problem
Schools do not usually suffer from a shortage of information. They suffer from information without a dependable shape: guidance without an obvious owner, notices without an end date, and systems that make sense only if somebody remembers which one to open. WorkPane begins with a modest proposition: the route to the working answer should not depend on institutional folklore.
Current guidance is scattered across drives, inboxes and intranet folders.
Staff spend time searching and may act from an obsolete copy.
A permission-aware index presents the source, owner, audience and review state beside the route to the authoritative item.
The start of the day is split across several systems and channels.
Urgent changes, timetable context and useful links compete for attention.
A configurable Home view brings together the school day, current notices, trusted launchers, calendar context and optional widgets.
Whole-staff channels are used for information relevant to a smaller group.
Important material is buried beneath somebody else's important material.
Bulletin publishing uses defined audiences, expiry, acknowledgement and, where policy requires it, a second publisher's review.
Team resources depend on informal membership and private bookmarks.
Handover becomes fragile when roles or relationships change.
Personal, group and professional-relationship shelves follow explicit membership while preserving the source system's access rules.
A dashboard copies specialist information to appear complete.
The copy becomes stale, widens disclosure or competes with the real record.
Purpose-limited summaries show source and freshness, then deep-link to the owning product for action.
Capability map
WorkPane is a governed staff starting point, not another place to lose a document.
Date, school-day progress, current or next timetable item, important notices, quick launch and permitted suite work in one bounded view.
A navigable calendar, versioned school-day presentation and visible handling of one-off or recurring changes.
School-location weather with source health, plus a deliberately configured support route with honest disabled, test and live states.
Drafts, scheduling, expiry, acknowledgements, scoped audiences and optional second-publisher review.
Owned policies, staff links, licensed products and school systems with support routes, sources and review health.
Current permitted notices, catalogue items and shelves, with human labels and no general search across specialist pupil records.
Useful link metadata arranged around genuine access, with lifecycle rules that do not delete the source document.
Owned membership, review dates, archive or closure, restoration and delegated management within a named scope.
A preferred route into licensed products and school services while every licensed app remains independently usable.
School layouts, personal preferences, safe rollback, source health and a readiness view that keeps local setup distinct from live approval.
These are the product's designed capabilities. Live connections, deployment and school approval remain separate decisions.
Working sequence
The front door stays useful because it identifies the working answer and preserves the route back to its owner.
What do I need now?
The relevant notice, policy or service.
Owner, audience, source and freshness.
Open the record that can actually be acted upon.
Product roadmap
The school day, urgent notices, trusted links and personal widgets in one calm starting point.
Audience-aware notices, owned documents, review dates and search shaped around the job staff are doing.
Personal, team and relationship shelves that follow real membership without quietly broadening access.
A preferred route into licensed products and source-linked summaries, while each application remains independently useful.
Setup wizards, audit, publisher controls, connection health and approved Microsoft, Google or timetable adapters.
How it differs
Official published descriptions checked 27 August 2026. Feature sets change; procurement requires direct verification with each vendor.
Microsoft foregrounds a branded employee destination built around a curated dashboard, news, conversations, resources, announcements and Microsoft 365. WorkPane shares the front-door idea but narrows it to the school day: governed bulletins, policy ownership, staff relationships, source freshness and a strict distinction between a summary and the specialist record.
SharePoint foregrounds home sites, hubs, communication sites, pages, lists, libraries and collaboration. WorkPane is not a general content platform. It is a school-specific operational layer that points into authoritative document systems while owning the staff-day presentation and publishing workflow around them.
The practical difference
The point is less time searching, fewer decisions made from stale guidance and a dependable route into the school day for new and established staff.
Measure it properly. Any published time-saving figure will come from the same task measured before and during a school pilot.
Editorial perspective
Schools do not usually suffer from a shortage of information. They suffer from information without a dependable shape: guidance without an obvious owner, notices without an end date, and systems that make sense only if somebody remembers which one to open. WorkPane begins with a modest proposition: the route to the working answer should not depend on institutional folklore.
Every school accumulates documents. Some are statutory, some useful, some obsolete and some apparently immortal. They sit in shared drives, email attachments and, most reliably of all, inside the memory of the colleague who has worked there since fax machines were considered rather flash.
A search engine can retrieve a file while leaving the real problem untouched: is it current, who owns it, does it apply to me and which document has authority? More results do not necessarily produce more knowledge. WorkPane treats finding as a governed act rather than a lucky encounter.
A search result is not yet an answer. Someone still has to stand behind it.
There is an obvious temptation when building a staff hub: copy everything into it. The result feels complete for approximately a fortnight, after which the original changes, the copy does not, and the school acquires another place in which yesterday's certainty can linger.
WorkPane is intended as a front door, not a rival empire. Policies, services and specialist records retain their proper owners; WorkPane organises the route to them. A good front door helps people enter. It does not brick up the side entrances.
Schools contain several kinds of truth, held for different purposes and visible to different people. A notice can reach the staff who need it without occupying everybody's attention. Administrators can govern structures without inheriting the contents of every private shelf.
Information overload also favours those who already know how the institution works. A calm, role-relevant starting point is not cosmetic tidiness; it is a small correction to an otherwise invisible inequality.
Dashboards often confuse seriousness with density. WorkPane's promise is different: today, the next useful action, current notices, trusted routes and the work a person is actually permitted to see.
That calm depends on honest states. A stale source must look stale. An unavailable service must not present yesterday's answer as today's. These distinctions are less glamorous than a glossy home screen, but they are the difference between orientation and theatre.
WorkPane is an argument for a school day with fewer scavenger hunts and fewer unofficial gatekeepers. It cannot make poor information good by displaying it beautifully. It can give ownership, relevance and authority a visible form.
Security · UK GDPR
Security and data protection are part of the product boundary. Certification, school approval and live use remain separate decisions.
Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.
Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.
Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.
Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.
School-facing boundary: the school will still need an appropriate lawful basis, privacy information, access policy, retention decisions and—where the risk requires it—a DPIA. The supplier’s job is to make those decisions informed, documented and technically enforceable.