Guide: How to run a weekly business review with a scheduled AI brief

A weekly business review (WBR) is a short operating meeting that uses the same core metrics every week to decide where leaders need to act. A useful WBR does more than report numbers: it shows what changed, why it changed, which goals are at risk, and which decisions cannot wait.

Tability can prepare the brief before the meeting from the goals, KPIs, initiatives, and check-ins already in your workspace. Save the request as a Scheduled prompt, choose a weekly time and recipients, then verify the generated brief against its linked evidence before the review.

Requirements

You'll need a Tability account – start a free Tability trial here.

Note: Scheduled prompts can make mistakes. Treat the generated WBR as decision support. Keep your workspace data current and verify important claims against the linked Tability items.

What should a weekly business review include?

Use a stable scorecard so that the team can compare this week with last week. The brief should answer six questions:

1. Which business metrics changed materially?
2. Which goals moved on or off track?
3. Which check-ins are missing or too old to trust?
4. What caused the most important changes?
5. Which risks or blockers need intervention?
6. Which decisions need an owner and a deadline?

A compact WBR works better than a large dashboard tour. Include only the metrics and goals that can change a decision in the meeting.

Weekly review scorecard fields

• Scorecard: Current value, target, trend, and previous value — Material movement or a widening target gap
• Goals at risk: Progress, confidence, latest check-in, and remaining time — Recovery action or target review needed
• Initiatives: Work completed, active work, and blocked work — Continue, change, stop, or escalate
• Data quality: Missing metrics and overdue check-ins — Evidence must be refreshed before deciding
• Decisions: Decision, owner, due date, and supporting evidence — Clear commitment before the meeting ends

Prepare your Tability workspace

The scheduled brief can only use evidence available in your workspace. Before automating the WBR:

• add the goals and KPIs that belong in the weekly scorecard
• make sure each metric has a current value and target
• ask owners to publish their latest check-ins before the review
• keep initiative states and blockers current
• use clear plan and team names so the prompt can identify the right scope

If a critical signal lives only in another system, connect it to Tability or update it before the brief runs. Do not ask the prompt to invent missing data.

Copy this weekly business review prompt

Replace the bracketed text with your plan, team, and reporting window.

Use only current Tability workspace data. Link the relevant goals, KPIs, initiatives, and check-ins. If evidence is missing or stale, say so explicitly.

Include:
- A scorecard of the core metrics with current value, target, prior value, trend, and status.
- The three most important changes since the previous review and the evidence behind each change.
- Goals at risk, overdue check-ins, and blocked initiatives.
- Likely causes, clearly separated from confirmed facts.
- Decisions needed this week, with a proposed owner and due date.
- A short action list for the next seven days.

Keep the brief concise, optimised for human readability, use paragraphs and don't abuse bullet points. Do not hide missing evidence and do not treat an inference as a confirmed fact.

Start with one plan or leadership team. A precise scope produces a more useful first brief and makes it easier to spot missing evidence.

Schedule the weekly brief

1. Open AI Mode from the Tability sidebar.
2. Select Scheduled prompts.
3. Click New prompt. You can also start from the Weekly Summary template.
4. Give the prompt a recognisable title, such as Monday weekly business review.
5. Paste the prompt above and replace the bracketed scope.
6. Set Schedule to Weekly.
7. Choose the weekday and hour. Schedule it early enough for owners to correct missing information before the meeting.
8. Add the workspace members who should receive the brief.
9. Check the displayed next-run date, time, and workspace timezone.
10. Click Save prompt.

Tability requires at least one recipient for a recurring prompt. The scheduled result is generated from the workspace and emailed to the selected recipients. Your on-screen AI Mode allowance and workspace eligibility determine whether a run can be delivered.

Verify the first generated WBR

Do not rely on the schedule until you have reviewed one complete resul.

Once your scheduled prompt is saved, you'll find an new button to send a test email.

Check that:

• every metric belongs to the intended plan or team
• current values and targets match the linked Tability items
• changes are compared with the correct prior period
• at-risk goals include the latest available confidence and check-in
• confirmed facts are clearly separated from possible causes
• missing or stale evidence is called out instead of filled with assumptions
• each proposed decision has enough evidence for a human owner to act

If the brief is too broad, narrow the plan, team, timeframe, or number of metrics in the prompt. If it misses important context, update the underlying Tability data before adding more prompt instructions.

Run the meeting from decisions, not status updates

Send the brief before the OKR meeting and ask participants to read it in advance. During the WBR:

1. Correct any material data issue.
2. Discuss metrics or goals that changed enough to require action.
3. Resolve the highest-impact blockers.
4. Record decisions, owners, and due dates.
5. Update the relevant Tability item so next week's brief includes the decision.

This turns the WBR into a closed loop: current work produces evidence, the brief identifies exceptions, the meeting makes decisions, and those decisions improve the next review.

When not to automate the WBR

Keep the process manual until:

• the scorecard has stable metric definitions
• owners publish updates consistently
• the team agrees on the decisions the meeting should support
• important business data is available in Tability

Automation cannot repair an unclear operating model. Start with a small, trustworthy scorecard and expand it only when the brief repeatedly supports better decisions.

Start your first scheduled review

Create one plan, add the metrics your leadership team reviews every week, and schedule the prompt only after the data is ready.

Start a free Tability trial