EthosGov
Oversee

EthosGov / The Portfolio Partnership

The Portfolio Partnership.

What a twelve-month partnership with EthosGov builds for a department, a Director, and twenty to forty school sites.

Apply to the Portfolios PilotRead the partnership brief

The portfolio view Education Directors have never had, built over a year, in partnership, from the live site-level data the schools are already running on.

Portfolio risk heatmap concept across twenty-five schools (concept).

Where departments sit today

Twenty-five schools live in the Director's head, until they don't.

There is no portfolio surface in Australian public education today. Directors carry it in their heads. Patterns that were always visible become a 2am phone call instead of a Monday morning insight. Storm mode is not the exception, it is the default.

Burden 1 of 3

No portfolio surface.

Twenty-five schools held in Excel, email, and one Director's memory.

Burden 2 of 3

The bi-weekly data refresh.

A re-ask the Principal resents and the Director cannot avoid, because the data lives nowhere else.

Burden 3 of 3

Patterns visible only after the harm.

The conversation is retrospective when it should be coaching.

The twelve-month cycle

Four quarters. One Director. A working portfolio surface by year-end.

The partnership runs in four quarters. Each quarter has its own deliverables, participants, and decision point.

  1. Quarter 1

    Scope.

    Discovery with the Director and the Department. Data audit at five to ten pilot sites. Signal inventory. Definition of what 'visible in time to act' will mean in this department.

    Deliverables
    • Director and Department interviews
    • Site data audit at five to ten pilot sites
    • Signal inventory
    • Working definition of 'visible in time to act'
    Participants
    Director, Department sponsor, EthosGov delivery team.
    Decision point
    Confirm the pilot cohort and the surfaces to stand up.

  2. Quarter 2

    Implement.

    EthosGov site-level modules stood up across the pilot sites. Portfolio Dashboard and Storm Mode surfaces built on top of the live data. First Director fortnightly review using the surface.

    Deliverables
    • Site-level modules live across the pilot sites
    • Portfolio Dashboard and Storm Mode surfaces (concept)
    • First fortnightly Director review run inside the surface
    Participants
    Director, Principals at pilot sites, Department observer, EthosGov.
    Decision point
    Confirm full-portfolio expansion path.

  3. Quarter 3

    Deploy.

    Expansion to the full portfolio of twenty to forty schools. Site Comparison, Strategy Roll-up, and Cross-Portfolio Library activated progressively. Department roles onboarded, including system leaders, policy, audit, and risk.

    Deliverables
    • Full-portfolio rollout across 20 to 40 schools
    • Site Comparison, Strategy Roll-up, and Cross-Portfolio Library activated
    • Department roles onboarded
    Participants
    Director, full-portfolio Principals, Department system leaders, EthosGov.
    Decision point
    Confirm the cadence and governance for year two.

  4. Quarter 4

    Analyse and improve.

    Evidence pack. What the patterns told you. What the Department decided to act on. Commitment to multi-year if the pattern holds.

    Deliverables
    • Evidence pack covering twelve months of portfolio activity
    • Department decision register
    • Multi-year commitment, if warranted
    Participants
    Director, Department executive, EthosGov.
    Decision point
    Continue into a multi-year arrangement, or close out the partnership.

Modules, as future scaffolding

Six modules built during the partnership, on top of the data the sites already run on.

Each module below describes a surface the partnership will build over twelve months. Visuals are concept. The modules are what the partnership delivers, not what is shipping today.

Oversee / module

Portfolio Dashboard

Will be built from Risk, Compliance, Board Reporting, and Meeting Health data the site is already running on. The Director's daily view across the portfolio, composed from live site data.

Concept. Surface built during the partnership.

The three promises, reframed

What twelve months of partnership delivers, in three roles.

These three promises are what the partnership has to make true to be worth a year of joint work. Each is what the surface delivers over twelve months, not a claim about a product today.

For the Education Director

The surface you have been building in your head.

Twenty to forty schools on one surface, colour-graded, by year-end. The patterns that matter become visible at the site long before they become a 2am call. Your portfolio finally has a place to live that is not your memory.

Read for Education Directors

For the Department

A roll-up composed from real data, not a PowerPoint.

By Quarter 4, system-level reporting on the data the sites are actually running on, refreshed live. The Department stops asking Principals to produce what Principals are already producing.

Read for Departments and Go2Gov

For the Principal

You stop being invisible upstream.

By the end of Quarter 2, the Director sees your site the way you see it. The coaching conversation starts on evidence, not on a data request. The time you would have spent rebuilding the report becomes time you spend with students.

Read for Principals

Answers

Frequently asked questions

How is the partnership different from a Power BI dashboard sitting on top of EDSAS?

Power BI is a reporting layer. The partnership builds a working layer. The Director will not log in to read a chart. The Director coaches twenty-five Principals, and the dashboard happens to be the surface they share. The work is the artefact, not the chart.

The Department already has a portfolio reporting tool. What does the partnership add?

The Department's tool is a return. The partnership builds what the Director and Principals will work from in the week between returns: the patterns, the early signals, the conversations that mean a return is never a surprise.

How will you keep schools from feeling surveilled?

Because the same data the school uses to run the week is the data that surfaces at portfolio level. There is no second instrument the Director sees that the Principal cannot. The transparency runs both ways.

Will a Director see things a Principal has not yet escalated?

Yes, and that is the point. Patterns will be visible before they become an escalation. The conversation can happen on Monday morning instead of as a 2am phone call after the harm.

What is the cadence; will the Director still meet every school every fortnight?

Yes. The cadence does not change. What changes is what the meeting is about. The data is already shared, so the conversation moves straight to coaching, not to a status update.

Who decides what is a portfolio-level decision and what stays at the site?

The same people who decide today, the Director and the Principal, in conversation. The partnership makes the underlying signals visible to both, so the line between site decision and portfolio decision is drawn from evidence, not memory.

Do you need a state innovation fund to run the pilot?

Not strictly, but the innovation funds are designed for this. Go2Gov in SA, CivVic Labs in VIC, MVP Ventures and Test and Buy in NSW, Innovation Pathways in WA, ICON in ACT, Advance Queensland, Industry Growth in Tasmania, and BRII federally. EthosGov co-applies with the department. Most pilots are funded, in whole or in part, by the innovation programme matched to your jurisdiction.

Ready to start with the pilot?

The pilot is the entry point to the partnership. Sixty days. Five schools. One Director. One clear decision at the end.

Apply to the Portfolios PilotBook a partnership conversation