Board reporting for IT

What a board should actually expect from IT each quarter.

Most boards get IT updates that are either too technical to read or too vague to act on. This is a plain framework for the seven standing items every quarterly paper should cover, written for directors who are accountable for technology but aren't engineers.

Vendor-neutral. Free template. Movement, not metrics.

  • Seven standing items
  • Quarter-on-quarter direction
  • For non-technical boards

Reviewed by Blake Bath, General Manager, on 31 October 2026.

Board reporting for IT

  1. Top risks
  2. Security posture
  3. Spend
  4. Roadmap
  5. Incidents
  6. People
Free templateDrop it into your next paper.

Read this page as

The seven standing items

Same seven items, every quarter.

Consistency is the point. Directors should be able to lay one paper next to the last.

Top risks

Named, owned, rated and trending.

Want the whole picture?See how it worksTalk to us

Board paper check

How much of the seven does your paper cover?

Tick what you report today. Download the template and copy the gaps for your next paper.

Tick what your current IT paper covers. You get what's missing and how to add it, plus the template.

What does your board paper cover today? (pick all)
Which framework do you report against?

Your board paper

2 of 7

  • Top technology risks. Five to seven named risks, each with one owner, a rating, a target and a trend.
  • Security posture. Movement against a named framework, with deferred controls stated openly.
  • Twelve-month roadmap. Confirmed, planned and proposed work kept apart.
  • People. Named internal capability, key-person risk and training results.
  • AI governance. Approved tools, shadow AI and readiness for the December 2026 privacy rule.

Pick a framework first. Posture means little without one to measure against.

Start with the risk register. The other items hang off it.

Get help writing it

Want a person to look at your answer?Talk to usBook a free 30 minute chat (opens in a new tab)

Essentials series transition

The Essential Eight is evolving into the ASD Essentials series, published 15 October 2026. It remains current through the transition, and your existing Essential Eight work counts as evidence towards the Essentials.

Read the Essentials series guide

Item 01: Risk register

The board should know the top five technology risks.

Most Australian boards already maintain a risk register for finance, people and operations. Technology risk should sit alongside them, in the same format, reviewed at the same cadence.

Purpose: To give directors a single page that names the most significant technology risks, who owns each one, the current rating, and whether the rating has moved this quarter.

Useful to a directorLooks finished, says little
Five to seven named risks, no more, no fewer.Forty risks copied from a generic register.
Each risk has a single accountable owner inside the business.Risks owned by 'IT' as a function, with no named person.
Each risk has a rating, a target rating, and a quarter-on-quarter trend arrow.Ratings that never move quarter to quarter.
Risks tie back to specific operational scenarios, not abstract categories.Risk language so abstract that directors cannot picture what would actually happen.

Example: Risk 03 : Ransomware affecting financial systems. Owner: CFO. Current rating: Medium (down from High). Movement reflects independent backup testing completed in Q2 and Conditional Access tightened in Q3.

"Real Bytes run the entire IT department for my business. The service is nearly instant, and proactive with advice. Outstanding."

Timothy Mark, Google review

Item 02: Security posture

Security posture is a direction, not a score.

A single security score on its own tells the board very little. What matters is whether the business is improving, holding, or sliding, against a framework that is published and externally recognised.

Purpose: To show the board the direction of the security posture against a recognised framework, the specific controls that moved this quarter, and any controls deliberately deferred.

Useful to a directorLooks finished, says little
Posture tracked against a named framework (Essential Eight, SMB1001, ISO 27001 or NIST CSF).A single percentage with no context.
Quarter-on-quarter movement shown, not just the current state.Marketing slides from a security vendor presented as posture evidence.
Controls that moved are named, with the work that drove the movement.Posture only ever moving up, never sideways or down.
Controls that are deferred are stated openly, with reasoning.No reference to which framework is being measured against.

Example: Essential Eight maturity Q3 2026. Patching ML1 (held). MFA ML2 (up from ML1, driven by phishing-resistant rollout). Application control ML0 (deliberately deferred, scoped for Q1 2027 to coincide with the laptop refresh).

Not sure where you stand?Get a free checkTalk to us

Item 03: Spend

Spend should be predictable, not surprising.

Technology spend that surprises the board is usually a sign of poor categorisation rather than poor management. Once spend is separated into run, change, and incident-driven, the conversation becomes calmer almost immediately.

Purpose: To give directors visibility of total technology spend split into the three categories that actually drive decisions: running the business, changing the business, and responding to incidents.

Useful to a directorLooks finished, says little
Spend split into run, change, and incident-driven categories.A single 'IT cost' line in the management accounts.
Run spend tracked per user or per device, not as a lump sum.Cloud and SaaS spend buried in operating expenses with no per-user view.
Change spend tied back to roadmap items the board has previously approved.Project spend mixed in with run-rate so growth is invisible.
Incident-driven spend always shown separately, even if small.No comparison to comparable Australian businesses by sector or headcount.

Example: Q3 technology spend. Run: $42 per user per month, in line with Q2. Change: $84,000 (Microsoft 365 E3 to E5 migration, board-approved May). Incident-driven: $3,200 (one phishing incident, contained inside four hours).

Item 04: Roadmap

The roadmap should be visible twelve months out.

A technology roadmap presented to a board should show what is confirmed, what is planned, and what is proposed. Conflating the three is one of the most common patterns we see in environment reviews.

Purpose: To give directors a twelve-month forward view of technology work, separated into confirmed (approved and resourced), planned (scoped, awaiting approval), and proposed (under investigation).

Useful to a directorLooks finished, says little
Twelve-month rolling view, refreshed each quarter.A list of vendor product names with no business context.
Work items separated into confirmed, planned, and proposed.Roadmap that only shows the current quarter.
Each item linked back to a risk, a strategic objective, or a regulatory requirement.Confirmed and proposed work shown identically, leading to false expectations.
Dependencies between items shown plainly.Items that have been on the roadmap for two or more quarters with no movement.

Example: Q4 2026: confirm laptop refresh (capex approved June). Q1 2027: plan Microsoft 365 backup migration (vendor selection underway). Q2 2027: proposed identity governance review (subject to vCISO engagement).

Item 05: Incidents

Incidents are an input to governance, not a failure to hide.

Mature organisations report incidents to their board calmly. The board wants to see that incidents are being detected, classified, contained, and learned from. Hiding incidents is almost always more damaging to a board's confidence than reporting them.

Purpose: To give directors a true picture of operational technology incidents this quarter: how many, how severe, how quickly they were contained, and what changed as a result.

Useful to a directorLooks finished, says little
All incidents counted, including minor ones, with severity classification.Only severity-one incidents counted, everything else hidden.
Mean time to detect and mean time to recover, tracked quarter-on-quarter.Phrases like 'no significant incidents' with no underlying numbers.
Each major incident has a one-paragraph post-incident summary in the paper.Post-incident reviews never reaching the board.
Lessons learned are tied to specific roadmap items or policy changes.Lessons that never change anything in subsequent quarters.

Example: Q3 2026: 14 incidents recorded. One severity-two (phishing-led mailbox compromise, contained inside four hours, no data exfiltration, OAIC threshold not reached). Mean time to recover 2.1 hours, down from 3.4 hours in Q2. Lesson: legacy auth blocked tenant-wide, completed Q3.

Item 06: People

Technology depends on people, and people are a board matter.

Boards routinely review the people risk in finance, sales and operations. Technology people risk is reviewed less often, and when it is, the conversation tends to focus narrowly on whether the helpdesk is staffed. The framing below is broader.

Purpose: To make visible the people side of technology: who owns what internally, where key-person risk sits, and whether the workforce as a whole is being trained to operate safely.

Useful to a directorLooks finished, says little
Named internal IT capability, even where most work is outsourced.'IT' presented as a single entity with no named individuals.
Key-person risk identified for both internal staff and provider personnel.Key-person risk acknowledged only after that person leaves.
Security awareness training cadence stated, including completion rates.Security awareness reduced to a single annual video.
Privileged-user training treated as a separate, more rigorous item.Training completion rates not measured or reported.

Example: Internal capability: one IT lead (3 days/week), MSP for run and security, vCISO for governance. Key-person risk: IT lead is single point of knowledge for the legacy ERP; cross-training scheduled Q1 2027. Awareness training: 94 percent completion this quarter, simulated phishing click rate 4.2 percent (down from 7.1 percent).

Item 07: AI governance

AI use is now a board item, not an IT item.

AI tooling crossed the threshold from "interesting" to "material" inside the last twelve months. Boards are now expected to know what AI the business is using, what data it touches, and whether the business is on track for the Privacy Act ADM transparency rule that lands 10 December 2026.

Purpose: To give directors a single page that names the AI tools in use, the data categories they touch, the alignment to the Voluntary AI Safety Standard, and the readiness for the December 2026 ADM transparency rule.

Useful to a directorLooks finished, says little
Approved AI tools listed by name, licence model and data categories they may process.AI use described in vendor terms rather than data terms ("we use Copilot" with no detail on what it reads).
Shadow AI assessed honestly, including free-tier use on personal accounts.Shadow AI not measured or assumed to be zero.
Voluntary AI Safety Standard guardrails mapped to the controls actually in place.AI governance reduced to a single line stating that there is an acceptable use policy.
ADM transparency rule readiness tracked as a dated work item, not a vague intent.No reference to the Voluntary AI Safety Standard, the OAIC AI privacy guidance or the December 2026 ADM rule.
Where AI assists decisions about individuals, that fact is named and the human review path is documented.AI-assisted decisions about people running without documented human review.

Example: AI tooling Q3 2026. Approved: Microsoft 365 Copilot (tenant-wide, Australian data residency), ChatGPT Team (12 named licences, finance and marketing). Shadow AI: free-tier ChatGPT use on personal devices reduced from 38 percent to 6 percent of staff (Q3 acceptable use rollout). Voluntary AI Safety Standard alignment: 7 of 10 guardrails mapped to existing controls, 3 in flight. ADM transparency: privacy policy update scoped for Q4 2026, no AI-assisted decisions currently affect individuals outside HR shortlist support, which has documented human review.

Security theatre

Report the number that matters.

Activity numbers make a slide look finished. Risk numbers let a director ask a useful question.

Looks good on a slideTells you about risk
Training completion %Phishing click rate, trending
Backups scheduledLast tested restore, and how long it took
Patch policy approvedUpdates missing right now
MFA switched onWhich MFA, and what skips it
Audit passedWhat's changed since

Real Bytes, after Y. Samadi, AISA CyberCon Review 2026-2027.

Essential Eight

Which maturity level do you actually need?

Maturity targets are a board decision, not an IT preference. Set the level deliberately, then report movement against it.

  • Level 1: the floor

    For everyone. Dozens of requirements. Do it properly, with evidence.

  • Level 2: when asked

    Insurer, tender or regulator. Admin rights, MFA and backups first.

  • Level 3: with a reason

    Rarely practical across the board. Targeted, not blanket.

Real Bytes guidance, informed by J. Stevenson, AISA CyberCon Review 2026-2027.

The new board question

Are we allocating wisely?

Writing in the AISA CyberCon Review 2026-2027, Jay Hira recounts a director asking what two or ten million dollars would buy instead of five, and where the curve flattens. His point: boards have moved on from "are we secure?" to "are we allocating wisely?". Alongside the standing items, include one page on what was funded, what was deferred, and why.

  • Show what you deferred

    Work you considered and didn't fund, with the reasoning. Some risks should be accepted or insured, on a register the board can see.

  • Depth before breadth

    Score each capability on process, technical effectiveness and coverage. Coverage without depth builds confidence that won't survive an incident.

  • Response compounds

    Once the basics are in place, detection, response and recovery often return more than another lock on the door.

Getting it going

First paper in one quarter.

  1. Step 1Pick a framework

    Essential Eight, SMB1001, ISO 27001 or NIST CSF.

  2. Step 2Build the risk register

    Five to seven named risks.

  3. Step 3Fill the template

    All seven items, honestly.

  4. Step 4Repeat

    Same structure next quarter.

Ready when you are.Book a free 30 minute chat (opens in a new tab)Talk to us

Questions

What directors ask about IT reporting.

What should a quarterly IT board paper cover?

Seven standing items: the top technology risks, security posture against a named framework, spend split into run, change and incident-driven, a twelve-month roadmap, incidents, people, and AI governance. Keep the structure the same each quarter so directors can compare.

Which Essential Eight level should a board target?

Level 1 is the floor for everyone, done properly with evidence. Level 2 when an insurer, tender or regulator asks. Level 3 rarely makes sense across the board, so target it where there's a reason. Setting the target is a board decision, not an IT preference.

How much can a breach cost a small business?

Verizon's 2026 Breach Impact Study found that in the worst 2.5% of cases, breach costs for small businesses ran to over 7% of revenue. For mid-market and large organisations it never went above 2%.

Should we report what we chose not to fund?

Yes. Boards are asking whether money is allocated wisely, not just whether the business is secure. A page on what was deferred, accepted or insured, and why, gives directors something they can defend.

Can you write the paper for us?

Yes. Our vCISO service prepares the quarterly paper with you and presents it to the board if you want. The template on this page is free to use either way.

Next step

Want help with the next paper?

Our vCISO service prepares it with you, and presents it if you want.

What happens next

  1. You pick a time that suits you.
  2. One of our engineers calls you. It takes 30 minutes and it's free. There's no slide deck.
  3. If we can help, we send a written plan. If we can't, we'll tell you who can.
  4. Nothing happens until you say yes.
  • Mason Wise, MSP Practice Lead at Real Bytes
  • Bill Nobbs-O'Brien, Service Desk & Field Engineer at Real Bytes
  • Travis Jacob, Operations Manager at Real Bytes

You talk to the people who do the work, not a sales team. Rather talk now? Call 07 3114 2808.

Already a client? Log a job in the client portal (opens in a new tab)

Cookie Preferences

We use cookies to improve your experience, analyse site traffic, and personalise content. By clicking "Accept All", you consent to our use of cookies. Privacy Policy

Privacy Act 1988 compliant. Your data is never sold.