Skip down to the research record

Breakout-room deal review: 5 numbers to log for each call

Quota Forecast Editorial Team · Published · 11 min read

Log five numbers for each breakout-room deal review: rooms and deals, start times, timer length, how each room closed, and retention dates. A review is only as useful as the record it leaves behind, and these five numbers make that record consistent.

Deal review calls often move into breakout rooms when the pipeline is too big for one conversation. A manager sends reps into separate rooms, each group walks through its deals, and everyone returns to the main room to agree on the forecast. The structure works, but it leaves a gap. The notes end up scattered across rooms, and the forecast file only gets the parts someone remembered to type up afterward.

Revenue leaders who keep call records for their forecast files need a short, consistent set of numbers to log every time. Numbers are easier to compare from week to week than prose notes. They also make problems visible: a review that ran short on time, a room that closed before the discussion finished, or a source file that will disappear before the next quarter closes.

This post walks through each of the five numbers and explains why each one matters for the file you keep afterward. The examples use Google Meet because its breakout room controls are documented in detail. Other tools handle rooms differently, so treat the platform-specific details here as a starting point and compare them with the settings your own team uses.

Set up the call so the numbers can be trusted

Before anyone logs anything, set up the room the way you expect it to run. Two details matter most.

First, breakout rooms in Google Meet must be started by a meeting host during a meeting on a computer. If your host is joining from a phone, they cannot start the rooms. Plan for a laptop or desktop before the call, not during it. The Google breakout rooms help page covers this requirement.

Second, Google recommends turning on Host Management settings before you use breakout rooms. Co-hosts who will help run the rooms should be set up ahead of time. The Google co-hosts help page gives the same advice. Put it in your pre-call routine so that nobody is learning the room controls while reps wait in the main room.

Once the setup is in place, the rest of the work is mostly about discipline. The numbers below are simple on their own. They become valuable only when every call produces them in the same way. For a fuller pre-call list, see Forecast call setup: 3 settings to check first.

Number 1: Room count and deals in each room

Count the breakout rooms you plan to open and the number of deals each room will cover. Write this down as a plan before the call starts, then compare it with what actually happened. A plan is only useful if the record shows whether the conversation followed it. A room that was meant to cover many deals but only reached three tells you something different from a room that covered all of its deals with time to spare.

The room limit is worth knowing before you plan the grouping. Zoom, for example, says: "You can create as many as 50 separate breakout sessions at once." Zoom's breakout rooms guide makes that point clearly. A grouping plan that fits one platform may not fit another, so look up the room limit in your tool first and build the plan around it. A large pipeline split across too many small rooms can leave each conversation too thin to be useful.

Log the deal identifiers next to the room name, not just the count. Months from now, a count alone will not tell you which deal was discussed in which room, and that is the question a forecast reviewer will ask. Keep the grouping consistent, too. If you group by rep, log the rep. If you group by region or by stage, log that. Changing the grouping logic from week to week makes the file hard to read and harder to compare.

Watch for deals that appear in more than one room. Sometimes a deal crosses two reps' territories, or a manager wants a second opinion from another group. Give that deal a note that says where it was discussed the first time and where it came up again. Without that note, a deal can look like it received twice the attention it actually got, and the forecast will reflect that mistake.

Number 2: Start time of each room

Log the time each room opened, to the minute. This number shows whether the review started on time and whether the first rooms got more time than the later ones. Record it from the call itself, not from the calendar invite. The invite shows when you planned to start. The room start shows when it actually happened, and those two times can differ by a surprising amount once a meeting is underway.

Also log who started the rooms. Since only hosts can start them, the host's name belongs in the record. If the host was delayed, the file should record the delay and the time the host actually opened the rooms. That detail explains a late start better than a vague note about technical trouble.

Start times also tell you about sequencing. If the first room opened well after the others, the reps in that room had less time than their peers, and the file should show it. A reviewer comparing deals across rooms needs to know whether one group had a rushed slot before deciding that a deal was under-discussed. Put the start times in the same order as the rooms on your plan so the comparison is easy to read.

Number 3: The timer length and the wrap-up countdown

Breakout timers are a common reason deal reviews feel rushed. Set the timer before you open the rooms, and note its length next to the room start time. Then decide what happens when the timer ends, because the platform's behavior at that moment is fixed and your team's response is not.

Google's documentation says each room displays a 30-second countdown before the timer ends. Participants have 30 seconds to finish their breakout room discussion before they are automatically moved back to the main room. The Google breakout rooms help page gives both details.

That 30-second window is not extra discussion time. Decide in advance what your managers should do with those last seconds, such as stating the next step for each deal in one sentence. Write that rule into your call notes so every host follows it. Then note the timer length and whether the rooms ran to the end. If a deal was cut off before the next step was clear, write that down. It is a signal that the next review needs more time for that rep or stage.

When the timer ends, participants are moved back to the main room automatically. If the host closes the rooms early, they bring everyone back before the timer ends. Either way, use that moment for a short summary that repeats the next step for each deal discussed in the rooms. Note whether the summary happened and who gave it. If it was skipped because the rooms ran out of time, that is worth recording too, because it means the next steps may exist only in the breakout discussions and nowhere in the file.

Number 4: How the rooms closed

Some hosts close the rooms early, either to bring everyone back for a summary or because the discussion is done. Note whether that happened. Google's instructions say to close all rooms before the 30-second timer runs out by going to the breakout rooms panel and clicking Close rooms. The same help page describes the countdown, so you can compare what you planned against what the platform did.

For each room, log one of two outcomes: closed by the host before the timer ran out, or ended by the timer. If the host closed it early, note the clock time of the close next to the room's start time, so the gap between the two is visible. Either entry gives the file a clear answer about how each room finished.

Over several weeks, a pattern appears. If most rooms end on the timer, the discussion may be running longer than the time you gave it, and the next review should give each room more time or fewer deals. If most rooms are closed early, the timer may be more generous than the number of deals in each room needs. Both patterns are useful to a revenue leader who is deciding how to split the next review, and neither shows up in a summary of the forecast alone.

Number 5: The retention date for every source

Call records sit in several places at once: the meeting platform, a conversation intelligence tool, and your forecast file. Each source has its own retention rules, and the forecast file should note when the source will disappear. If the only copy of a deal discussion lives in a tool that deletes it on a schedule, your file needs to say so before someone asks for the evidence.

Gong is one example. Its help center states that Gong's standard data retention period for existing customers is the lesser of three years and the period you are a customer. It also states that if you cease being a Gong customer, your data will be irreversibly deleted in 30 days. Read both statements together. The period that applies depends on how long you have been a customer and on whether you remain one, so the date you can count on is not a fixed period you can assume. The Gong data retention policy has the full wording.

For each source, log a retention date in a column next to the source name. Use the date on which the source stops holding the record, not the date you saved it. If your company's contract changes, update the column. A forecast file that cites a call record nobody can open anymore has the same problem as one with no record at all. For retention rules in another system, see Microsoft 365 audit log retention: 5 rules to check.

Ownership matters here too. Name the person responsible for the retention dates of each source, and list that person in the file header. When someone leaves the team, the responsibility should pass to a named successor. Retention is easy to forget because nothing breaks on the day a record disappears. The first sign is usually a question from finance or an auditor that nobody can answer. For how a file should read to someone new, see Forecast handoff: 3 checks for a readable record.

Put the five numbers in one table

The numbers are most useful when they sit in one row for each call. A simple table works well because it forces the same fields every time. Here is a layout you can copy into a shared sheet:

FieldWhat to writeExample
Rooms and dealsRoom names with deal IDsRoom names listed next to their deal IDs
Room start timeClock time each room opened, in plan orderClock time of each room start
Timer and countdownTimer length, plus the 30-second wrap-upTimer length noted; countdown ran to the end
Close outcomeClosed by host, or ended by timer, with the close timeClosed early by host, with close time noted
Retention dateDate each source stops holding the recordRecording tool: contract end date

The example entries show the form only. Replace them with your own. The point of the table is the structure: every call produces the same five entries, so the file can be sorted, filtered, and compared without anyone reconstructing the call from memory.

Common mistakes to avoid

Most problems with breakout-room records come from a few habits. The first is logging from memory after the call. A rep's account of which deals were discussed in which room can drift by the end of the day, and a manager's memory drifts faster. Fill in the room names and deal IDs while the rooms are open, even if the details are brief. A short, accurate note written during the call is more reliable than a detailed one written the next morning.

The second is starting rooms from a device that cannot do it. Because breakout rooms must be started by a host on a computer, a host who joins from a phone will have to hand off the controls. Find out who is joining from which device before the meeting begins, not when the first room is due to open.

The third is letting the timer end the discussion without a plan. The 30-second countdown is a fixed part of the platform's behavior. What your team does during those seconds is up to you, so decide it in advance and write it into the call checklist so every host follows the same rule.

Why this is worth the extra minute

Logging five numbers adds some time to a deal review, and it asks the host to keep one more thing in view while running the rooms. In return, the forecast file gets a record that can answer the questions that come up later: which deals were covered, how much time each room had, how the rooms ended, and whether the source of each discussion will still exist when someone needs it. Those answers help when a number moves unexpectedly and the team has to explain why.

Start with the next call. Pick one layout, fill in the five fields, and keep the same format for a month. After that, you will know whether your rooms are running long, whether your hosts need a better setup routine, and whether your call records will last as long as your forecast does. None of those questions is hard to answer when the numbers are already in the file.

Sources