Back to Blog

Power BI Goal Check-Ins - Building a Weekly Rhythm That Sticks

November 21, 2026•8 min read•Michael Ridland

Most scorecards die quietly. Someone builds a nice set of goals in Power BI, the leadership team looks at it for a fortnight, and by week six the statuses say "On track" for things that went sideways a month ago. Nobody deleted it. Nobody used it either.

The part of Power BI goals that decides whether a scorecard lives or dies is not the build. It's the check-in. Microsoft's documentation on staying on top of your goals covers the mechanics: how to record a check-in, add notes, change status and follow goals so you get told when something moves. The mechanics take ten minutes to learn. The habit takes a quarter to build, and that's where most organisations we work with get stuck.

So this post is less about which button to click and more about how to make check-ins part of how a team actually runs.

What a check-in actually is

A check-in is a dated entry against a goal. When you open a goal in a scorecard and add a check-in, you pick a date and can record three things:

  • A value - the current number for that goal, if the goal is manual rather than connected to a report
  • A status - On track, At risk, Behind, Overdue, Not started, Completed, or a custom status if your scorecard has them
  • A note - free text explaining what's going on

Each check-in lands in the goal's history, which you can see in the details pane. Over time that history becomes a running log: the number went from 42 to 38 on 3 March, the owner marked it At risk, and the note says a major customer delayed their order to April.

That log is the useful bit. A chart tells you the number dropped. The check-in note tells you why, written by the person who knows.

For connected goals, where the current value comes from a Power BI report, you don't type the value in, but you can still add notes and set status manually. This is worth knowing because a lot of people assume connected goals are fully hands-off. The value is automatic. The context isn't.

Following goals

You can follow a goal so that you're notified when its status changes or someone adds a note. For a manager with twenty goals across a scorecard, this is the difference between "I'll check the scorecard on Friday" (which never happens) and "I'll hear about it when something changes".

My honest view: following is underused and slightly noisy at the same time. Underused because most people never click it. Noisy because if someone follows every goal on a busy scorecard, they'll get a stream of notifications and start ignoring them. The sweet spot we've found is that each executive follows the five or six goals they personally care about, and the scorecard owner follows everything.

Why check-ins go stale

We've rolled out goals for a few clients now, and the failure pattern is predictable enough that I can describe it before it happens.

Nobody owns the check-in. The goal has an owner listed, but that person doesn't know they're expected to update it, or assumes the BI team does it. Three weeks later the most recent check-in is the one the BI analyst entered on setup day.

Status is treated as decoration. Connected goals update their value on refresh, so people think the scorecard is "live". But the status doesn't change on its own unless you've set up status rules. So the number is red and the status still says On track. That's worse than no status at all, because it tells leadership something false.

Notes are empty. A check-in with a value and no note is barely better than the report it came from. The note is what makes the scorecard worth opening.

The meeting doesn't use it. This is the big one. If the monthly operations meeting still runs off a PowerPoint deck someone builds on Thursday night, the scorecard is a side project. People update what gets looked at.

What works

Here's the rhythm we recommend, and it's not complicated.

Pick a check-in day. Every goal owner checks in on the same day each week or fortnight. Tuesday morning works well for a lot of teams because Monday is chaos and by Wednesday the week's already gone. Put it in calendars as a 15 minute recurring block.

Write the note for someone who wasn't in the room. Our rule of thumb: one or two sentences, covering what changed and what's being done about it. "Revenue down 8% on forecast. Two deals slipped to December, both still verbally committed. No action needed yet." That's enough. Nobody needs an essay.

Set status rules where you can. For connected goals, status rules let Power BI set the status based on the value against target. If revenue is under 90% of target, mark it At risk. Under 80%, Behind. This takes the subjectivity out and stops the "everything is green" problem. Keep manual status for goals where judgement matters, like a project milestone that's technically on schedule but you know is shaky.

Run the meeting from the scorecard. Open the scorecard on the screen. Go goal by goal, or better, filter to only the At risk and Behind ones. The owner talks to their note. If the note is missing, everyone notices, and it rarely happens twice.

Review the history quarterly. Once a quarter, pick two or three goals and read their full check-in history. You'll learn things. One client discovered that a customer satisfaction goal had been marked At risk for eleven straight weeks with notes that all said roughly "working on it". The scorecard had been telling them the truth the whole time. Nobody had read it in sequence.

Editing and deleting check-ins

You can edit or delete a check-in after the fact. This is handy for fixing typos or a wrong value. It's also a governance question worth thinking about. If the scorecard is used for anything like performance reviews or board reporting, decide early who's allowed to change historical check-ins. Scorecard permissions let you control who can update which goals, so a goal owner can check in on their own goals without being able to touch anyone else's.

I'd be cautious about letting people quietly rewrite last month's notes. The value of the log is that it's an honest record of what people thought at the time.

Where it's still rough

I like goals, but it's fair to be clear about where they fall short.

Notifications are basic. You get told something changed. You don't get much control over frequency or digest options, and the notifications land alongside every other Power BI and Teams alert people already ignore.

There's no built-in reminder to check in. Power BI won't nag a goal owner who hasn't updated in three weeks. You can build this yourself with Power Automate, and we've done that for clients: a weekly flow that looks for goals without a recent check-in and posts a Teams message to the owner. It works well, but it's something you have to build. If you want a hand with that kind of automation, our Power Automate consultants do this sort of thing regularly.

Notes are plain. You can write text, but it's not a rich discussion thread. For goals that need a longer conversation, teams end up taking it to Teams or email, and the scorecard loses that context.

Mobile is fine, not great. Checking in from a phone works, but goal owners who live in the field (construction site managers, sales reps between meetings) tend to put it off until they're back at a desk, and then forget.

None of these are deal breakers. They're just the things you plan around.

A quick example

One of our clients is a mid-sized logistics business with depots in Brisbane, Sydney and Melbourne. They had a weekly ops meeting that ran off a spreadsheet each depot manager emailed in by Monday night. Half the spreadsheets arrived late, the formats drifted, and the regional manager spent Monday evenings stitching them together.

We moved them to a Power BI scorecard with about fifteen goals: on-time delivery, damage rate, fleet utilisation, overtime hours and a few others. Most were connected to their existing reports, so the numbers updated themselves. Each depot manager owned the goals for their site and checked in every Tuesday before 10am with a status and a short note.

The first month was patchy. Two of the three managers checked in reliably and the third didn't. What fixed it wasn't a reminder flow (though we added one). It was the regional manager opening the scorecard in the meeting and asking, in front of everyone, "Melbourne, no note this week, what's happening?" That only had to happen twice.

Six months on, the Monday spreadsheet is gone, the meeting is 20 minutes shorter, and the check-in history has become the thing they look back on when explaining a bad month to the board.

Should you bother?

If you already pay for Power BI Pro or Premium Per User, and you have recurring numbers people are accountable for, then yes. Goals with consistent check-ins are one of the cheapest ways to get a team talking about the same numbers with the same context.

If your problem is that nobody trusts the underlying data, fix that first. A scorecard built on numbers people argue about just moves the argument to a new screen. That's often where our Power BI consultants start: getting the model and measures right before anyone builds a goal on top of them.

And if you're thinking about the bigger picture, like how reporting, scorecards and AI-generated summaries fit together, our work on AI for business intelligence is worth a look. We've started using AI to draft check-in notes from the underlying data so the owner only has to edit and approve, which takes the friction out of the weekly habit.

The tool is the easy part. The ritual is the work.