How to Set Up a Real-Time Business Dashboard

Which numbers need to be live, how Xero, MYOB and job systems feed a real-time dashboard, alerts, wallboards, and what to check before you trust it.

Best for: Business owners, operations managers Practical guide for business decision-makers

Who this is for

Business owners and operations managers who want a live view of the business without checking five systems.

Question this answers

How do I set up a real-time business dashboard, and which numbers genuinely need to be live?

What you'll leave with

  • How to sort your numbers into live, hourly and daily
  • Why job and booking systems can update in seconds while accounting figures usually lag
  • Why every tile needs a last updated time
  • How to set alerts, and how to put the dashboard on a wall screen or a phone
  • The checks to run before anyone makes a decision from it

A real-time business dashboard sounds simple. One screen, every number current, no more ringing the office to ask how the day is going. In practice, the hard part is not the screen. It is deciding which numbers truly need to be live, and getting each of your systems to hand its numbers over at the right speed.

This guide walks through the setup in the order it should happen. It assumes you already know what decisions the dashboard is for. If you do not, start with our guide on how to plan a useful business dashboard, then come back here.

What real time actually means

On a dashboard, real time rarely means instant. It means fresh enough that nobody acts on an old number. For a hospitality venue watching bookings for tonight, that might be within a minute. For a wholesaler watching cash in the bank, an hour is usually fine.

So the useful question is not "can it be real time?" It is "how old can this number be before it causes a wrong decision?" Ask that for every number, and the design of the whole dashboard follows from the answers.

Which numbers need to be live

Sort every number you want on the screen into three groups.

Live, within a minute or two. These are numbers someone will act on during the same shift. A trades business dispatching six vans needs to see which jobs are unassigned and which technician just finished. A restaurant needs covers booked against covers seated tonight. A professional services firm on a deadline day might want lodgements outstanding.

Hourly or every few minutes. These are numbers that guide the day but do not change minute to minute in a way that matters. Sales so far today, invoices raised, quotes sent and accepted, and labour hours against the roster usually sit here.

Daily or weekly. These are trend and health numbers: gross margin by job type, debtors over 60 days, stock turnover, work in progress for a firm. Refreshing them every minute adds cost and noise, and nobody reads them that way anyway.

Most businesses end up with only a handful of genuinely live numbers. That is a good result. It keeps the live part of the system small and reliable, and it stops a wall of flickering numbers from hiding the ones that matter.

How each system can feed the dashboard

A dashboard does not create numbers. It collects them from the systems you already use. Each system hands data over in one of two ways, and the way it works decides how fresh that tile can be.

Systems that push changes as they happen

Many job management, booking, point of sale and online store systems can send a short message the moment something changes: a job is completed, a table is booked, an order is paid. This is often called a webhook. The dashboard receives the message and updates the tile within seconds. These systems are the natural source for your live numbers.

The catch is that a pushed message can occasionally go missing, for example during an outage on either side. A well-built dashboard also checks back with the system on a regular schedule, so a missed message gets picked up instead of leaving a tile quietly wrong.

Systems that are read on a schedule

Accounting systems such as Xero and MYOB are built to keep the books correct, not to stream every change. They limit how often other software can read from them, and some figures, such as a bank balance, only change when the bank feed arrives. In practice, finance figures on a dashboard typically refresh every few minutes to hourly.

That is fine for almost every business decision. Nobody needs their debtor total to the second. What matters is that the dashboard reads Xero or MYOB politely, within the limits, and that the tile says clearly when it was last refreshed. If you are connecting these systems for other reasons too, our pages on Xero integration and MYOB integration explain what can be read and written.

Spreadsheets and older systems

Some numbers live in a spreadsheet or an older system with no way in from outside. These can still feed a dashboard through a scheduled export or a shared file, but they will never be live. Mark them as daily, and treat moving them into a proper system as a separate project.

When the numbers you need sit across three or four systems with different speeds, the work is mostly in the plumbing behind the screen. That plumbing is the main part of any business dashboard development project, and it is worth planning before anyone draws a chart.

Show last updated on every tile

This is the single most useful habit in dashboard design, and the one most often skipped. Every tile should show when its number was last refreshed, in plain words: "Updated 2 minutes ago" or "Updated 9:00 am today".

Picture a hospitality group where the Xero connection stops working on a Friday afternoon. Without a time on the tile, the weekly sales figure keeps showing the Thursday number all weekend, and the owner makes rostering decisions from it on Sunday night. With a time on the tile, the owner sees "Updated 2 days ago" and knows to ask.

Two simple rules make this work:

  • Grey out stale tiles. If a live tile has not refreshed in, say, ten minutes, fade it or add a warning colour so it cannot be mistaken for a current number.
  • Say where the number came from. A small note such as "from Xero" or "from the job system" saves arguments when two people see different figures.

Alerts for thresholds

Nobody stares at a dashboard all day, and they should not have to. Alerts do the watching. When a number crosses a line you have set, the right person gets a message by email, text or a team chat app.

Useful alerts are specific. A wholesaler might alert the warehouse manager when a fast-moving product drops below two days of stock. A trades business might alert the operations manager when a job booked for today still has no technician by 10 am. An accounting firm might alert a partner when work in progress for a client passes the agreed fee.

Three rules keep alerts from becoming noise:

  1. One owner per alert. If an alert goes to everyone, nobody acts on it.
  2. A known response. The person receiving it should already know what to do. If they do not, the alert is not ready.
  3. Few of them. Start with three or four alerts. Add more only when the first ones are trusted. Too many alerts and people start ignoring all of them.

Wallboards and phones

The same data usually needs to appear in two very different places.

A wallboard is a large screen in a workshop, warehouse, kitchen or office. It is read from across the room, so it needs very few numbers, large text and strong colour: jobs open, jobs late, orders to pick. It should run without anyone logging in each morning, and it should recover by itself after a power cut or a dropped connection.

A phone view is read by an owner or manager between other things, often outside the office. It needs the same top numbers in a single column, with the ability to tap into detail. It also needs a proper login, because a phone gets lost in a way a wall screen does not.

Design these as two views of one set of numbers, not as two separate dashboards. That way the warehouse wall and the phone in your pocket always show the same figure.

What to check before you trust it

A dashboard that is wrong is worse than no dashboard, because people act on it with confidence. Before anyone makes a real decision from it, run it beside your existing systems for a few weeks and check the following.

Checks before the dashboard goes live

  • Totals match the source

    Sales, invoices and job counts agree with Xero, MYOB or the job system for the same period, including GST treatment.

  • The awkward days are right

    Month end, a public holiday, a refund, a cancelled job and a split payment all show correctly.

  • Every tile has a time and a source

    Each number says when it was refreshed and which system it came from.

  • Stale data is obvious

    Switch off one connection on purpose and confirm the affected tiles show a warning.

  • Definitions are written down

    Everyone agrees what counts as a sale, a completed job or an active client.

  • Alerts reach the right person

    Each alert has been triggered in a test and the owner received it.

  • Access is right

    Staff see what they need, and wage or margin figures are limited to the people who should see them.

The definitions point matters more than it looks. If the sales team counts a sale when the quote is accepted and finance counts it when the invoice is paid, the dashboard will be "wrong" to one of them every day. Settle it on paper first. Our key performance indicator (KPI) dashboard best practices article covers how to choose and define those numbers.

For an example of this in practice, the multi-venue restaurant group dashboard case study shows point of sale, rostering and accounting data brought into one view across several venues.

If you are still deciding whether to build something of your own or use a ready-made reporting app, read custom business dashboard or template: how to choose. And if your numbers sit across several systems and you want them live in one place, our custom business dashboard development service starts with exactly the sorting exercise in this guide.

Key takeaways

  • Very few numbers need to be live. Decide which ones would change what someone does in the next hour, and refresh the rest hourly or daily.
  • Job, booking and point of sale systems can often send changes as they happen. Accounting systems such as Xero and MYOB limit how often other software can read them, so finance figures usually refresh every few minutes to hourly.
  • Put a last updated time on every tile. A number without a time is a guess.
  • An alert is only useful if a named person owns it and knows what to do when it fires.
  • Before trusting the dashboard, check it against the source systems for a few weeks, including the awkward days.
DashboardsReal-Time DataReportingXeroMYOBAlerts

Meet the person

Written by the person who does the work

This guide comes from real projects. If it raises a question about your own system, you can ask the founder directly.

HELLO PEOPLE designs, builds and looks after AI, software, app and data solutions for Australian businesses, with senior expertise on every project and a scope agreed before work starts. For software, that means starting with how your business runs, not with the code.

Since 2007, HELLO PEOPLE has delivered more than 100 projects from Perth for small and medium businesses across Australia: custom software and apps, system integrations, data migrations, reporting and dashboards, and AI that works inside the systems a business already runs.

I lead every engagement myself. I trained in accounting before moving into IT, hold accounting and IT professional qualifications and an MBA, and bring more than 20 years of experience across sales, service delivery, inventory and compliance. I am also a PhD candidate in AI at Curtin University, researching retrieval-augmented generation (RAG), so the technology is always judged by what it does for the business.

  • An old-fashioned service

    Small and boutique. The person who scopes your software is the person who builds it, and the same person is there on launch day.

  • Quick responses

    No ticket queue and no account manager in between. You hear back within one business day, usually sooner.

  • A long-term partner

    The first release is the start, not the end. When you need the next system, integration or report, you call the same person, who already knows your business.

Ask the author

Question about setting up a real-time business dashboard?

Ask it here and it comes straight to Kasun, who wrote this. No sales call, no obligation, and a real answer even if the answer is that you do not need us.

Kasun Wijayamanna, Founder Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.