
BLITZMETRICS · META / HOW WE DO IT
Give your team the board your clients never see
A partner’s team asked for two things in one Basecamp note: fix a handful of members whose audits weren’t showing, and give the staff their own scoreboard that clients can’t reach. Both are patterns we now repeat for every cohort. Here’s the whole build.
The message had two topics, and they looked unrelated. They weren’t.
We run a personal-brand program for Sigrun’s members — every member gets a score, a private dashboard, a downloadable audit, and a team of agents. Her operations lead, Jagoda, wrote in: (1) nine people on the scoreboard show no audit, even though they submitted everything — what’s wrong? And (2) could the team and their mentors get their own scoreboard and dashboards to practice on, without clients being able to see it?
One is a bug. One is a feature request. But both come down to the same question every program eventually asks: who is allowed to see what, and how do you keep each board honest without babysitting it? We shipped both the same afternoon. This is how — written so you can do it for any group you run.
The one idea: every cohort needs two boards, walled apart — the one members see (the shared ranking plus their own dashboard) and the one only the team sees (a private practice board, on their own brands, that clients can’t reach). And “your audit isn’t showing” should be a state the system fixes itself, not a ticket someone chases.
We fixed nine stuck audits, made that failure self-healing so it can’t recur, and stood up a separate password-gated team board — all on the live site, all verified.
Topic one: nine audits that wouldn’t show
The nine were the newest joiners. They’d been scored and placed on the scoreboard — so from the outside everything looked fine — but their audit PDFs had never actually been generated and uploaded. The scoreboard has a quiet safety rule: if a member’s audit file doesn’t exist yet, their button points at their dashboard (“View”) instead of a dead link. Useful. But it meant nine people sat there with a button that went nowhere near an audit, and nobody could tell why from the front end.
So we generated all nine full audits — seventeen pages each, the same engine as everyone else — uploaded the PDFs, and republished. All nine now show a real “Audit →” on the scoreboard and a working “Open your audit” on their own dashboard.
The fix that matters isn’t the nine PDFs. It’s that we made the failure impossible to repeat. The scoreboard used to carry a hand-kept list of “new joiners without an audit yet.” Hand-kept lists rot. We rewrote it so the list derives itself: a member counts as “no audit” only while their audit file is genuinely missing, and the moment it’s rendered, their button flips from “View” to “Audit” on its own. Nobody maintains a list. The board tells the truth about itself.
The gotcha that cost us an hour, so it won’t cost you one: these boards are built in a page builder that renders from its own cached copy of the content, not the raw page. Update the page the normal way and the database changes while the live page keeps showing the old thing — silently. The real fix is to edit the builder’s widget and save through its pipeline, then clear the edge cache. If a “saved” change isn’t showing up, you’re almost always writing to the wrong layer.
Topic two: the board only the team sees
The second ask is the more interesting one, because it’s a pattern, not a one-off. The team wanted to run the program on themselves — score their own brands, run the agents on their own sites, feel what a member feels — so they can coach from experience instead of theory. Good instinct. But a team’s practice scores don’t belong on the members’ board, and clients definitely shouldn’t stumble onto them.
The answer is a second board that looks and works exactly like the member one, lives at its own address, and sits behind its own password — a different password from the member area. Members have the member key. The team has the team key. Anyone without a key gets a password prompt and nothing else. We seeded it with Sigrun’s own score as the model to aim at, and the team and mentors get added exactly like members: send a name and a personal-brand URL, and they’re audited onto the board the same day.
Who sees what, exactly:
| Board | Gate | Who gets in | What it’s for |
|---|---|---|---|
| Member scoreboard | Member password | Members | The shared ranking — see where you stand, open your own dashboard |
| Member dashboard | Per-member link | That one member | Their score, gap, audit, weekly focus, agent team |
| Team board | Separate team password | Staff + mentors | Practice the whole program on your own brands, out of client view |
| Client / public | — | Nobody | Sees a password prompt; no content leaks |
We proved the wall before we called it done. A gate you didn’t test is a gate you’re guessing about. We loaded the team board as an anonymous visitor — no login, no cookie — and confirmed it returns the password form with none of the team’s content in the page source. Then we entered the key and confirmed the board renders in full. Verify the lock from the outside, not just the inside.
The one honest gap — and the fix on the shelf
Here’s the part most programs get wrong and never notice. The shared scoreboard is meant to be shared — that’s the motivation. But the individual dashboards, in a lot of setups, are only protected by a hard-to-guess web address. Which means a curious member could open a colleague’s dashboard by editing the link. That’s not “members see only their own” — that’s “members see only their own unless they’re nosy.”
The clean fix is a private, one-time link per member — a key baked into each person’s own address that unlocks only their view. We didn’t flip it on automatically, because it changes links that may already be in members’ hands, and that’s a decision the program owner should make, not a surprise we spring. So it’s built, explained, and waiting on a yes. That’s the standard: surface the gap, put the fix on the shelf, let the owner choose the moment.
The pattern, so you can repeat it for any group
Strip out the names and this is a recipe. Any cohort, any partner, same five steps.
- One board per audience, each with its own key. Members get the shared ranking. The team gets a private clone. Different passwords, so holding one key never opens the other.
- Seed the team board with the model. Don’t ship an empty room — put the founder’s own score on it as the target, so the team sees what “good” looks like the moment they walk in.
- Add people the same way you add members. Name plus a personal-brand URL in, a scored audit and a dashboard out. One intake, no special path for staff.
- Make “no audit yet” self-healing. Derive the missing-audit state from whether the file actually exists, so a placeholder button becomes a real audit on its own the instant the work lands.
- Test the wall from the outside. Visit every gated board with no key and confirm it leaks nothing before you hand out the address.
Do that and a partner’s team stops watching from the sidelines and starts running the program on themselves — which is the fastest way we know to turn a coach into a believer.
The deliverable
Two boards, walled apart and verified live: a self-healing member scoreboard where every audit now resolves, and a separate password-gated team board seeded with the model and ready for staff and mentors. The reply back to the team went out with the address and the key.
Part of the BlitzMetrics Content Factory — the same personal-brand engine behind the SOMBA members’ scoreboard and our Personal Brand Score. Built, gated, and verified by a Claude agent working in a logged-in browser on the live site — then written up here so the next group gets the same thing faster.

