LOOM - A Coherent Governance and Leadership Workspace

Governance in schools often goes on as a necessary but largely invisible task behind the scenes – until there’s a complaint, inspection, or legal challenge.

And when decisions are questioned, it’s not just what the board agreed that matters – but where it is documented and how leadership interpreted, implemented, or adjusted those commitments in practice.

That’s where inconsistencies between minutes, policies, and operational decisions are brought into question.

Loom is a governance and leadership platform purpose-built for schools and non-profit trusts. It unifies board meetings, leadership decisions, committee oversight and strategic initiatives into a single, coherent workspace – connecting governance actions instead of simply recording them.

Loom recognises that school governance operates across distinct layers: board decisions that bind the organisation, committee recommendations that inform board decisions, and leadership actions that implement strategy. The platform tracks each of these institutional acts separately yet links them transparently, so there is no ambiguity about who authorised what and when.

    Sandbox access is now open for a limited number of schools that want to test Loom with real workflows (and constructive feedback).

    The Problem LOOM Solves

    Most schools can produce meeting minutes.

    What they can’t reliably produce is a straight answer to questions like:

    • “When did the board approve this wording?”
    • “Which committee recommended this – and who was in the room?”
    • “Did leadership implement what the board actually committed to?”
    • “Why are we discussing this again?”

    The documentation exists. But it’s scattered across:

    • minutes archives
    • email threads
    • board packs and attachments
    • local drives and Google folders
    • individual memory

    Loom connects the record to the reality.

    What Makes LOOM Different
    Loom is built around a simple but often-missed distinction:

    There are three kinds of institutional act

    • Board decisions that bind the organisation
    • Committee recommendations that advise the board
    • Leadership actions that implement and adjust delivery

    These are not interchangeable – and importantly Loom doesn’t treat them as interchangeable.

    When you record outcomes in Loom, the registers build themselves:

    • Board minutes produce a Decision Register entry
    • Committee minutes produce Recommendations Awaiting Consideration
    • Leadership minutes produce an Operational Log of implementation activity

    No copying. No reconstructing. No “where did we put that?”

    What You Can Do in the Sandbox
    1) See how to run governance through meetings, not email

    • Create meetings by workspace (Board, Safeguarding, HR, Academic Planning, Working Parties)
    • Build agendas and attach board packs in one place
    • Capture reports, minutes, and outcomes directly under each agenda item

    2) Turn notes into tracked follow-ups (without losing context)
    Board members can add:

    • personal notes (private)
    • shared notes (visible to relevant members)
      When a note matters, it can be elevated into a follow-up action which is assigned, dated, and tracked.

    3) Approve policies with a clean audit trail
    Loom manages a formal document lifecycle:

    • draft → awaiting approval → approved → published → review due

    Board approvals can be recorded as:

    • Approved
    • Approved with amendments (conditional approval)

    Conditional approvals trigger a structured handoff:

    • the amendment is captured
    • an amended draft is created
    • a board-sponsored follow-up is generated for Head/Chair execution (due by the next board meeting)

    4) Keep implementation connected to governance intent
    Initiatives and actions aren’t separate from governance—they are the implementation layer.

    Loom allows:

    • board-level initiatives (oversight)
    • operational initiatives (delivery)
    • links between them (so oversight doesn’t become noise)

    How LOOM Helps Different Roles
    Chairs

    • See what needs board attention before the meeting
    • Detect contested items early (notes and concerns on agenda items)
    • Keep accountability with the board while delegating execution clearly

    Trustees / Board Members

    • Understand what is awaiting decision or approval
    • Add notes and concerns without waiting for the meeting table
    • Track what the board has committed the organisation to

    Heads and Senior Leaders

    • Turn governance direction into executable action
    • Keep follow-ups visible (with sponsor cues)
    • Maintain a clean line between board authority and leadership implementation

    Committee Leads

    • Make recommendations that don’t disappear into minutes
    • Build credible evidence trails for board decision-making
    • Keep oversight structured without inflating governance workload

    Deeper Features (for schools that care about the details)

    Time-stamped membership
    Governance is often questioned years later. Loom time-stamps membership changes so you can reconstruct:

    • who held delegated authority on a given date
    • who was present when a recommendation was made
    • quorum and composition at the time – not just “current members”

    Decision–document traceability
    When a board decision adopts a policy, Loom links:

    • the decision
    • the adopted document version
    • the published version

    So you can answer: “When did we approve this wording?” without searching through archived packs.

    Policy–procedure integrity
    When a published policy changes, Loom can accelerate review dates on linked procedures – prompting implementation teams to realign practice with governance intent.

    Role-based permissions (including guests)
    Loom supports guest access for working parties and external contributors – while controlling visibility to prevent leakage across unrelated workspaces.

    What the Sandbox Is For (and what it isn’t)
    The sandbox is designed to test:

    • your real governance workflow (meetings → decisions → policies → follow-ups → review cycles)
    • role separation (chair vs trustee vs leader vs guest)
    • whether LOOM reduces rework, ambiguity, and governance drift

    The sandbox is not:

    • a finished configuration for your school
    • a generic “board portal” clone
    • a meeting scheduler with a document folder attached

    Request Sandbox Access

    If you’re a school or trust that wants to test a more coherent governance record, request access.
    Call to action: Request sandbox access →
    Secondary: Book a 20-minute walkthrough →

    When you request access, include:

    • School / Trust name
    • Approximate board size and committee structure
    • Whether you want to test guest access (e.g., PTA reps, working party members)

    Frequently Asked Questions

    Is Loom a document repository?
    No, it’s much more. Documents live inside a governance workflow: approval authority, lifecycle, review schedule, and traceability.

    Can we import existing policies?
    Yes. Documents can be imported individually or in bulk, then classified into Loom’s governance taxonomy.

    Does Loom replace our existing board portal?
    Potentially. Most schools have to use multiple tools because none of them hold the full governance record together. Loom might well be able to manage all features you’re looking for.

    Is guest access safe?
    Guest visibility can be scoped to a single workspace. Loom is designed to prevent “metadata leakage” (e.g., seeing meeting titles or document names without permission).

    LOOM – Strategic Coherence for School Governance

    Board • Committees • Leadership • Policies • Decisions • Initiatives – connected and coherent.