Skip down to the research record

Deal review call: 4 checks on roles, calendar, deck, chat

Quota Forecast Editorial Team · Published · 13 min read

Four checks before and after a deal review call cover roles, the calendar, the deck, and chat. A deal review call has two jobs. It moves a deal forward, and it leaves behind a record that someone will need later. In practice, that record is the set of notes, slides, calendar event, and chat that lets a stranger understand what was decided and why.

The sales manager who asks why a forecast changed will need that record. So will the finance partner checking a close date, and so will the rep who joins the account a few weeks later and has to pick up the thread. Most review calls go fine while they are happening. The trouble comes afterward. The notes sit in someone's personal document. The deck was shared in a form nobody could read on a laptop. The chat scrolled out of view. The meeting itself lives on a calendar owned by someone who has since changed roles.

This post walks through four checks you can run before and after a deal review call. They cover roles, the calendar that holds the meeting, the deck, and the chat. We follow one example case through all four so each check has something concrete to test. The platform rules we quote come from the vendors' own help pages, and we link each page where we use it. Where a point is our advice rather than a vendor rule, we say so. This is not a guide to running a sales process, and it does not replace your own policies for records. It is about the mechanics of the call: which role holds which control, which object holds the time and link, how a deck survives being read later, and how chat can disappear before anyone needs it.

The example case we will follow

Our example is a renewal for a single account that is up for review. The account executive owns the deal and wants a yes or no on a discount. The sales manager runs the review call. A deal desk analyst checks pricing and contract terms, and a solutions engineer answers questions about how the product would be set up for the customer. The deal has its own chat channel, which the group uses all week, and the plan is to present a short deck on screen during the call.

Nothing in this case is a real company or a real rule. It is a plain example, so each check has a concrete thing to look at. We come back to it within each check, and at the close we look at what the record holds after the call.

The reason to pick one example is practical. Checks like these are easy to agree with in the abstract and easy to skip on a busy afternoon. A concrete call makes it obvious which step failed. If you can point to the moment the host was unclear, or the slide nobody could read, you can fix that step and leave the others alone.

Check 1: Set the roles before anyone joins

Start with the call itself. Google's Meet help page describes the default plainly: a meeting has one host by default, and up to 25 co-hosts can be added once inside the meeting. Anything beyond the one host is a choice someone has to make on purpose.

For our example, the sales manager should be the host, because the sales manager is the person who will answer for the review afterward. The deal desk analyst and the account executive can be co-hosts. Even with co-hosts, the record needs one named owner. Write that owner into the invite or the first chat message so nobody has to guess who is accountable.

Presenting and hosting are different jobs. Separating them is a team choice: it lets the sales manager keep control of the room while the account executive walks through the slides.

Breakout rooms are where roles matter most. The breakout room guide says that "Meeting hosts can use breakout rooms to divide participants into smaller groups during meetings." In our case, the pricing question might go to a breakout with the deal desk analyst while the account executive walks the solutions engineer through the customer's rollout timeline. A split like that is useful, but it creates a second conversation the main record may not capture. Assign one person to write down what each room decided and to bring it back to the main call.

The same guide notes that "You can create up to 100 breakout rooms in a call." A deal review will almost never come near that ceiling. The number matters less than the habit behind it: keep breakouts few, and make each one report back before the call ends.

Before the call, run a short roles check:

  • Confirm who the host is, by name, not by assumption.
  • Keep the co-host list short, and note why each person is on it.
  • Decide who can start and close breakout rooms.
  • Name the owner of the decision summary.

Do this in the invite, not at the start of the call. Role confusion in the first few minutes eats the time the agenda needed, and nobody can fix a host gap while they are also trying to present.

Also decide what happens if the host has to leave early. Agree on who takes over the controls and who keeps the notes going, so the call does not stall while someone searches for the right button. This is a team agreement, not a platform setting, so write it down in the same place as the owner. For the settings to check before the call, see Forecast call setup: 3 settings to check first.

Check 2: Check whose calendar holds the meeting

The calendar event is part of the record too. It holds the time, the attendees, the invite text, and in many setups the link people use to join. The event also has an owner, and that owner can matter more than you expect. Google's help page warns: "If you transfer or schedule a meeting on someone else's calendar, the other person could become the meeting host." That sentence is the reason to check this before you send the invite.

In our example, the account executive first booked the review on the deal desk analyst's calendar because that calendar had open time that week. The call went well. A few weeks later the analyst moved to another project, and nobody was sure who could change the meeting or who the host was. The deal record still linked to a meeting that no one on the current team could easily edit.

The fix is small. Book the review on the calendar of the person who will own the deal record, which in our case is the sales manager, and invite everyone else. Before you send the invite, confirm who the host should be, and do not assume the person who booked the event is the host.

Run through this quick pass before you send the invite:

ItemWhere to lookWhat to confirm
Calendar ownerThe event's calendarStill owns the deal next month
HostInvite and meeting host controlsMatches the named owner
Join linkInvite textCopied into the deal record
Late readersEvent descriptionAgenda and deal link are present

Then write the calendar owner into the deal record. That way a future reader knows where to look, even if the person who booked the meeting has moved on. A meeting that depends on one person's calendar is harder to find once that person changes roles, so plan for that move in advance. For reminders on a review event, see Deal review: 3 call and reminder settings to check.

Think about who sees the invite afterward. Attendees who could not make it may find the event on their own calendars, and the description is the first thing they read. Put the decision agenda and the deal link in that description, so a late reader is not left guessing about the purpose of the call.

Check 3: Make the deck readable later

The deck is the part of the call people look at most, and it is often read again later as a file. Microsoft's accessibility guidance for PowerPoint says: "Use a larger font size (18pt or larger), sans serif fonts, and sufficient white space." The same page adds: "Select templates and themes with sans serif fonts that are 18 points or larger."

Those are Microsoft's words on accessibility. They make a sensible floor for any deck that will be shown on a screen and read later. They are not a legal standard for your review. Use them as a default, and check the result on a small screen before the call.

Our example deck has a few slides that matter most: the pricing summary, the risk list, and the mutual close plan. The pricing summary carried small footnotes in a thin serif font. On the presenter's large monitor it looked fine. On a laptop in a hallway, with the screen shared at a smaller size, the footnotes were hard to read. The deal desk analyst asked a question the slide should have answered, and the answer had to be typed into chat.

The fix is to change the deck's theme, not to fiddle with each slide. Pick a theme with sans serif fonts sized at 18 points or larger, and leave enough white space that a reader can scan each slide in a few seconds. If a slide needs more detail than that, move the detail into the record. The deck is for the room; the record is for the reader who was not in it.

Second, keep the version you presented. A deck is shown once and read many times. Save the file as presented, name it with the deal and the review date, and link it from the decision summary. If anyone edited slides during the call, note which slides changed. Without that note, a future reader finds a file in a folder and assumes it is exactly what the room discussed.

Some reviewers will want a printed copy or a PDF. Test both. Print one slide at the size your reviewers will use and see whether the smallest text is still readable. A slide that works on a projector can fail on paper, and the reader who has only the printout is the one the record most needs to serve.

Speaker notes deserve a line too. If the presenter keeps notes in the file, decide whether those notes are part of the record. Notes can hold remarks that never reached the slide, so check them before you share the file. For limits on sharing the screen during the call, see Screen sharing limits: 6 checks for forecast calls.

Check 4: Plan the chat before it scrolls away

Chat carries the call's running commentary: links, figures someone pastes in, and the question a participant wants to raise after a slide. It is also where a record can quietly go missing, because some workspaces delete old messages on a schedule. The Rocket.Chat retention guide shows how that works in one product: "For instance, entering 30 and selecting days will delete all messages older than 30 days."

The example is about one product's setting, so do not assume your workspace behaves the same way. Check it. The point is simple: a retention setting decides how long a message lasts, and the setting may have been chosen by someone who is no longer on the team. For how deleted records can be recovered, see Recover deleted sales records with 4 retention checks.

The same guide describes the trash: "The trash holds every deletion from the last 30 days across the whole workspace, not only the incident." Two things follow. The trash covers the whole workspace, so it holds deletions from every channel, not only the one you care about. The window is the last 30 days, so the trash is a short safety net, not an archive.

In our example, the deal channel had a retention setting of 30 days, set when the workspace was created and never reviewed. The review call happened in the first week. Some weeks later the sales manager went looking for a message in which the solutions engineer confirmed a support commitment for the customer. The message was gone.

Chat should never be the only copy of a commitment. Before the call, look up the retention setting for the deal channel, or ask the admin who manages the workspace. During the call, paste the decisions and links into the deal record, not only into chat. After the call, copy anything the record depends on out of chat: the decision, the owner of each follow-up, and the source of any figure someone quoted.

Threads and side messages need the same care. A reply thread can hold the detail behind a decision while the main channel shows only the headline. When the decision matters, copy the thread's conclusion into the summary and say where the rest of the discussion lives. Otherwise the next reader sees a decision with no reasoning behind it.

Chat is also where numbers get pasted without context. A figure with no source line is hard to check later. Paste the figure with the file or report it came from, and the date it was pulled.

Afterward: make the record usable for someone who was not there

Bring the four checks together into one summary, written soon after the call while memory is still fresh. Keep it short enough to read in a few minutes and specific enough that a reader does not have to ask what happened. It should cover these points:

  • Who was the host and who were the co-hosts.
  • Who owned the calendar event, and whether that owner still works on the deal.
  • Which breakout rooms ran, and who reported back from each.
  • The deck version that was presented, with a link to the saved file.
  • Each decision, with an owner and a date for the follow-up.
  • Where the chat lived, and whether its retention setting would have deleted anything.

Store the summary where the deal lives, not in a personal folder. If the record sits with one person's files, it leaves when that person does. Link the summary from the deal's main page, and link the calendar event and the saved deck from the summary so a reader can reach all three from one place.

Then test it. Give the summary to someone who was not on the call and ask them one question: what did we decide, and why? If they can answer without asking you, the record is usable. If they cannot, the gap is in the summary, not in their reading.

Keep the summary free of guesses. If a number came from a slide, say which slide. If a point was still open at the end of the call, write it as open, with an owner, rather than letting it read like a decision. A record that mixes settled points with open ones is harder to use than one that marks each clearly.

In our example, the sales manager wrote the summary that week, linked the saved deck, noted that the discount was approved on condition, and named the deal desk analyst as the owner of the pricing follow-up. Weeks later, when the account executive was out, the solutions engineer opened the record and found the answer on the first screen.

The four checks are small on their own. Roles tell people who runs the call. The calendar tells people where the meeting lives. The deck shows what was presented in a form people can read. The chat holds the side conversation, and its retention setting decides how long that conversation lasts. Together they turn a good call into a record that still works after everyone has moved on to the next deal.

Sources