Before a recorded forecast call, check minimum scheduling notice, recording permissions, and the filters used to pull deals.
Key takeaways
- Set booking notice to cover your preparation time.
- Test recording with the host's account before the call.
- Save the deal filter and compare its count with the CRM view.
Why the setup matters more than the agenda
A forecast call usually goes wrong for reasons that have nothing to do with the pipeline itself. The invite goes out too late for people to prepare. Recording is switched off, or it is on for the host but blocked for the whole organization. The deal list pulled from the CRM quietly leaves out a few opportunities, and nobody notices until a manager asks why the total does not match last week's. Each of these problems shows up during the call, when there is no time to fix it.
The fix is to set things up before anyone joins. This post covers three settings that the person who runs the forecast call should lock in advance: the booking rules that control when the call can be scheduled, the recording settings that decide whether the call is captured, and the filters in the deal pull that decide which opportunities appear on screen.
Platform menus change, and the exact names depend on your plan and on how your administrator configured the tools. Treat what follows as a list of things to verify, not as a copy of anyone's current settings page. Where a vendor's help page states a specific rule, this post links to it so you can check the current wording yourself.
Who owns each setting
Three settings usually involve three different people, and that is where many setups fail. The revenue leader decides when the call happens and what it must cover. An operations or sales-systems person usually owns the booking page and the CRM query. An administrator controls the account-level recording permissions. None of these roles has to be a big job, but each setting needs one named owner, so a question about it has an obvious place to go.
Write the owners down in one place, next to the call details. When a setting changes, you will know who to ask, and you will know who made the change. That record matters most when the forecast is questioned weeks later.
Setting 1: Minimum scheduling notice
If the forecast call is booked through a scheduling tool, start with the notice rules on the booking page. Calendly's help documentation describes minimum scheduling notice as a way to require a set amount of time between when someone books and when the meeting starts. That gap is your prep window, and a booking page can enforce it for you.
Here is why it matters. A recurring call is easy to book in a hurry. A rep or a manager who wants a slot can schedule it for the same morning, and then the forecast starts without a refreshed deal list, without a reviewed agenda, and sometimes without the people who own the largest deals. A notice rule will not make the forecast accurate, but it gives the rest of the setup time to happen before the call.
What to lock down:
- Pick the notice period from your own prep time. Count how long it takes to refresh the deal pull, check the recording, and send the agenda. Set the minimum notice to at least that length. Do not copy the tool's default without thinking about it.
- Put the call on an event type you own. The revenue leader or operations should own the event, not a personal link that any rep can share. If the link belongs to one person, it can change without anyone else knowing.
- Check whether rescheduling follows the same rule. Test moving an existing booking. If a late move skips the notice window, the rule protects only new bookings, and you need a process for changes.
- Plan the exception. Sometimes a forecast needs an urgent call, such as after a large deal slips. Create a separate event type for that case, with its own rules, so the exception is visible and does not weaken the regular call.
A booking page also tells attendees what to expect. Put the agenda and the recording notice in the invite description, so people who open the calendar entry know the call is recorded before they join. That single habit saves a lot of awkward moments at the start of the meeting. For the meeting itself, use the forecast call agenda checks.
Illustrative example: Calculate the preparation window
The preparation window is 40 minutes. Use that illustrative total when choosing the minimum notice, then test a booking to check that it leaves enough preparation time. These times are examples, not recommended defaults.
Time zones deserve their own check. Pick one reference zone for the forecast, write it into the invite, and test the link from a second region before the week of the call.
Setting 2: Recording permissions and the recording limit
Recording is the setting most often forgotten, because the record button looks the same whether the feature is ready or not. Check the account level first. Google's help page for recording a video meeting says the setting is off by default, and your administrator can choose to turn it on. It also says that if you are a Google Workspace administrator who manages Google Meet for your organization, you must first allow meeting recording.
So the first step is a question to the administrator, asked well before the call week. Ask whether recording is allowed for the people who host the forecast call, and ask them to confirm it in writing. Do not wait for the morning of the call to discover that recording does not start.
Then run a test. Record a short meeting with the same account the host will use, with a second person on the call if possible, and confirm that the file appears where you expect it. A test takes very little time. A missing recording of a forecast call is hard to recreate.
Next is the recording limit. Google's help page says that meetings can only be recorded for a total of 8 hours, then the recording stops automatically. A regular forecast call will almost never reach that limit. A longer session can, such as a quarter-end review that runs all day or a planning meeting that reuses the same call. When you know the session may run long, decide ahead of time how you will handle it. You can end the call at a clean break and start a new one, or you can agree that someone will start a second recording at a fixed point. The key is to decide before the call, not during it.
Recordings also need a known location. Google's help page includes a note about folder changes: starting in July 2026, the existing "Meet Recordings" folder will be automatically renamed "Legacy Meet Recordings" and moved inside the new "Google Meet" folder. Confirm the current folder location, and update saved links only after checking whether the rename has happened.
Finally, decide who controls the recording during the call. Name one person to start it, one person to watch that it is running, and one person to confirm it has stopped at the end. Tell attendees before the call starts that the meeting will be recorded, and follow your company's policy and the rules that apply where people are located.
Decide what the recording is for before the call. A recording can serve as a record of the commitments made on the call, a reference for people who could not attend, or a source for the summary sent afterward. Each purpose points to a slightly different setup. If the recording is only a reference, the screen share of the deal list matters most, so make sure the list is visible and readable. If it is a record of commitments, the important moments are the questions and answers about close dates and amounts, so the host should slow down at those points.
This post uses Google Meet for its recording examples because Google publishes the rules in its help pages. If your team records with another tool, the same three questions apply: who must allow recording, how long a single recording can run, and where the files are stored. Find the answers in that tool's own help pages before you rely on them.
Setting 3: Filters in the deal pull
The third setting has the most effect on the numbers. Whatever tool produces the deal list, the call depends on a query. That query defines the pipeline, the stages, the close-date window, the owner group, and whatever else makes a deal count as part of this forecast. If the query is wrong, the call still looks organized, and it still shows a total that is wrong.
Some teams pull deals through an API. If your CRM exposes opportunities through an OData-style Web API, read the filter rules before you write one. Microsoft's documentation for the Dataverse Web API in Power Apps shows two cases that catch people out. In the first, a filter that uses a plus sign, such as contains(name,'+123'), does not work, because + is a character that can't be included in a URL. In the second, a name with an apostrophe, such as O'Bryan, produces an error about an unterminated literal when the value is not handled correctly.
Those are small details, but they matter for a forecast.
Choose the criteria on purpose. Every filter term should match a rule your team already uses in its forecast meeting. If the stage names in the query differ from the stage names your reps see, the list will look right to the CRM admin and wrong to the people reading it. Keep the list of stages, owners, and date windows in one document, and check it at the start of each quarter, since stage definitions and fiscal calendars often change then. Use the weekly deal review filters guide when reviewing those criteria.
Decide where the pull runs, too. A pull that a person starts by hand depends on that person's login and their permissions in the CRM. A pull that runs on a schedule needs an account with access to every record in scope, and someone must watch its output. Either way, record which account the pull uses, because a permission change on that account can quietly shrink the list.
What to lock:
- Write down the exact filter for each forecast view. Save it with the call notes, not in someone's head. Include the pipeline, the stages, the date window, and the owner group.
- Test the filter with known records. Pick a few deals you know should appear, including one with a special character in its name or account. Check that each one shows up.
- Compare counts. Run the same criteria in the CRM's own list view, and compare the number of records to the number your pull returns. A mismatch is a signal to investigate before the call, not during it.
- Assign one owner for changes. One person should edit the filter, and the change should be recorded with the date and the reason. Otherwise two people can fix the same problem in different ways.
- Handle errors on purpose. If the pull fails, the error message should go to the person who runs the call, not to a log nobody reads.
A useful habit is to pull the deals at a fixed point before the call, such as after the notice window has closed. That way the list you review is the list everyone sees.
Common mistakes
Most of the problems in this post come from a short list of habits. Teams tend to repeat them because each one seems harmless on its own.
- Testing the recording on the call itself. A first test should happen before the call, in a separate meeting, so a failure does not disturb the real one.
- Trusting the default filter. A saved view in the CRM can change when someone edits a field or a stage name. Check the saved query, not just the view's name.
- Letting the booking page drift. Event types get copied, and copies can keep old rules. Review the booking page each quarter and remove the copies you no longer use.
- Assuming the admin setting is permanent. Recording permissions and folder structures can change, and vendors announce changes in advance. Read the help notes when they arrive, and check the setup again after any change.
A checklist for the day before
Run these four checks before the call:
- Booking. The invite exists, the notice rule was met, and the event belongs to the revenue leader or operations.
- Recording. The administrator has confirmed that recording is allowed, a test recording has played back, the stop plan is agreed, and the team knows where recordings are saved.
- Deal pull. The filter is saved, the test deals appear, and the counts match the CRM view.
- Attendees. The agenda and the recording notice have gone out, and the people who must bring updates know what to bring.
If any item is not done, decide whether to delay the call or to run it with a known gap and say so at the start. A forecast with a stated gap is more useful than one that quietly hides it.
Print the checklist or paste it into the call's invite as a private note for the organizer. If the person who runs the call did not set things up, walk through it with them. The point is not ceremony. It is to make sure that the three settings were checked by someone other than the person who set them.
After the call
The setup is not finished when the call ends. Check that the recording exists, that it plays, and that it is in the folder you expect. Save the deal pull you used beside the notes, so anyone who reviews the forecast later can see the same list. If something failed, write down what failed and which setting caused it. Then the next call starts with that fix already in place rather than with the same surprise.
Write a short note while the details are fresh. Include the time the recording started and stopped, where the file was saved, which filter was used, and any count mismatch that remained unexplained. A note like that turns a one-time fix into a procedure the next person can follow. For a readable record, use the forecast handoff checks.
Over time, these three settings become routine. The booking rule gives you a fixed prep window. The recording check gives you a file you can trust. The filter review gives you a list that matches the CRM. None of this replaces the conversation about the deals, but it makes sure that conversation is about the right deals, and that the record of it survives the meeting.
Start with the recording check today
Today, run the short recording test described above and play back the saved file. It is easy to overlook, and it is the one that is hardest to repair after the call. Booking and filter problems can often be fixed with a quick reschedule or a corrected query.
Common questions
Does a notice rule make the forecast accurate?
No, a notice rule creates preparation time. Use that time to refresh the deal list and review the agenda.
Can the host check recording without a test meeting?
A test meeting checks whether the host can record and save a usable file. Written confirmation alone does not check playback.
What should happen if the deal counts disagree?
Investigate the mismatch before the call. Compare the saved filter with the CRM view's criteria and check known deals.