A Quarterly Business Review Template for Remote Staffing Programs

A quarterly business review is the moment to step back from day-to-day support and ask whether a remote assistant program is delivering what it should. Done well, a QBR aligns the client and provider on results, surfaces risks early and sets priorities for the next quarter. Done poorly, it becomes a slide show of activity counts that nobody acts on.

This guide offers a practical QBR template for organizations running remote assistant programs with a provider. It covers who should attend, what the pack should contain, how to run the meeting and how to follow through. It builds on our reporting and QBRs overview.

Who attends

Keep the group small enough to make decisions:

• Executive sponsor: owns the program's goals and budget.
• Program coordinator: runs the program day to day.
• Department leaders: one from each department with assistants, or representatives.
• Provider account lead: and, where useful, the provider's operations or recruiting lead.
• Optional: IT or security, procurement, HR, when agenda items require them.

Assistants themselves usually don't attend the QBR, but their feedback should be represented, for example through a short survey summarized by the provider.

The pack

Send the pack several days ahead so the meeting can focus on discussion. A good pack is short, with an appendix for detail.

1. Summary

One page: overall status, highlights, concerns and the decisions needed in this meeting.

2. Program overview

• Number of assistants by department and role.
• Changes this quarter: new placements, departures, replacements, role changes.
• Schedule and coverage overview.

3. Results against goals

Report against the goals agreed at the program's start or last QBR, such as:

• Output measures: queue volumes, turnaround, backlog.
• Quality measures: sampled error rates, rework.
• Leader experience: survey results on time saved and quality.
• Business outcomes where measurable, such as faster close, quicker candidate scheduling or improved response times.

Show trends over several quarters where possible, and be candid about measures that moved the wrong way.

4. Quality and coaching

• Summary of quality sampling results.
• Coaching themes and actions.
• Recognition of strong performance.

5. Coverage and continuity

• Absences and how they were covered.
• Upcoming holidays and leave, including local holidays in assistants' countries.
• Single points of failure and mitigation.

6. Security and access

• Access reviews completed and findings.
• Incidents or near misses and lessons.
• Changes to devices, tools or controls.

7. Risks and issues

A short register: each risk, its owner, status and next action.

8. Roadmap

• Planned new roles or departments.
• Process improvements and automation opportunities.
• Training priorities.

9. Commercial and contract

• Upcoming renewals or changes.
• Any open contractual items.

Keep commercial details in the meeting, not in widely shared documents, if your organization prefers.

10. Decisions and actions

The list of decisions requested and, after the meeting, the actions agreed with owners and dates.

Running the meeting

A sixty- to ninety-minute agenda:

The sponsor or coordinator chairs. Ask each department leader to come with one success and one improvement request.

Making it about outcomes, not activity

The most common QBR failure is focusing on activity: tickets closed, emails processed, meetings scheduled. Activity matters, but leaders care about outcomes. Translate where possible:

• Not "processed many invoices," but "invoices now processed within the agreed time, and the month-end close started on schedule."
• Not "scheduled many interviews," but "time from application to first interview shortened, according to the ATS report."
• Not "managed the CEO's calendar," but "the CEO reports gaining focus time each week, and board prep is no longer last minute."

Use real data from your systems and be careful not to overstate. If an outcome can't be measured, say so and use qualitative feedback.

Gathering inputs efficiently

Preparation shouldn't be a burden. Build the QBR from material produced throughout the quarter:

• Weekly scorecards from managers.
• Monthly department reviews.
• The provider's account reports.
• Access review records from IT.
• The risk register.

The provider's account lead can assemble the first draft; the program coordinator reviews and adds the client perspective.

After the meeting

Within a few days, circulate:

• The decisions made.
• The action list with owners and dates.
• Any changes to goals or measures for the next quarter.

Review the action list at the start of the next QBR. Actions that roll over quarter after quarter signal a problem worth discussing.

Choosing the right measures

Measures should reflect why the program exists. A few principles help:

• Start from the goal. If the purpose is giving executives focus time, measure leaders' assessment of time regained and meeting load, not just tasks completed.
• Use data you already have. Ticket systems, AP platforms, applicant tracking systems and calendars already record most of what you need. Avoid creating new tracking just for the QBR.
• Balance speed and quality. Turnaround improvements are hollow if error rates rise. Report both.
• Keep the set stable. Changing measures every quarter makes trends impossible to see. Adjust only when goals change.
• Include a qualitative voice. A short quote or two from leaders and assistants, with permission, adds context that numbers can't.

Agree the measures at the first QBR and record definitions in the program documentation, so everyone calculates them the same way.

Including assistant feedback

Assistants often see process problems first: unclear requests, duplicate work, access gaps, tools that slow them down. A short quarterly survey, run by the provider and summarized anonymously in the pack, gives them a voice. Useful questions include what slows them down most, which procedures are unclear, what training would help and what they would change if they could. Acting on even one or two suggestions each quarter improves retention and performance, and it shows assistants that they are part of the team rather than an external service.

Department deep dives

For larger programs, rotate a short deep dive into one department each quarter. The department leader and their pod lead present what the assistants do, what's improved, what's still hard and what they plan next. Deep dives spread good practices across departments and give the sponsor a closer view of the work than summary metrics allow.

A worked example

A company with assistants in finance, the executive office and recruiting holds its quarterly review. The pack's summary notes that finance turnaround improved and the month-end close started on schedule all quarter, while recruiting scheduling slowed during a hiring surge. The coverage section flags upcoming local holidays affecting two assistants, with backups assigned. The security section reports a completed access review with two unnecessary permissions removed and one phishing near miss reported promptly by an assistant. Department leaders discuss the recruiting surge; the group decides to add a second recruiting coordinator for the next quarter and asks the provider to begin recruiting. Actions are circulated two days later.

Keeping the QBR honest

A QBR is only useful if it reflects reality. Encourage both sides to raise problems early rather than saving them for the meeting, and to present setbacks plainly. If a placement didn't work out, say so and explain what changed. If a measure can't be calculated reliably, leave it out rather than estimate it. Trust built through candid reviews makes it much easier to agree on expansion, changes or difficult decisions later.

Common mistakes

Activity-only reporting. Tie measures to outcomes.

No decisions. Every QBR should end with decisions and actions.

Overlong packs. Put detail in the appendix.

Skipping risks. Surfacing risks early is the point.

Frequently asked questions

Does ExecWing prepare QBR packs?

Your account lead prepares a draft from program data and joins the review. See account management.

How often should we hold QBRs?

Quarterly is typical for multi-department programs. Smaller programs may prefer semi-annual reviews with monthly check-ins.

What if goals weren't set at the start?

Set them now. Use this quarter as a baseline.

Can assistants contribute?

Yes. A short assistant survey, summarized in the pack, often surfaces useful improvement ideas.