Make your recording and notes policy visible before the next client call

The client call starts, someone asks whether the conversation is being recorded, and the answer is buried in a shared document. The room goes quiet. That pause is the cost of a policy nobody saw before joining. The waiting room is where the policy is read. In Google Meet, an administrator can show a custom short policy message in the Green Room before users join a call. For a small company, the recording rule is only real when it is read before the call starts.

The short line is the whole policy

A long memo will not be read. The Green Room policy notice carries the rule, the trigger, and the next step in one breath. If the call is recorded, transcribed, or captured as notes, say so plainly. The message can also point to a webpage with more detail about the company's policies. That link is for the person who wants the full rule, not the person trying to decide whether to join.

Keep the line short enough to read in the Green Room. It does not ask for permission in the room. It removes the question before the room starts. For a client or investor call, that visible notice is the first document they see. It sets the tone before the first agenda item.

The detail page can hold the longer rule and the context behind it. The notice line does not need to carry all of that. It only needs to make the expectation visible before the participant joins.

Turn the feature on before the first real call

The feature is disabled unless an administrator turns it on. Setup happens in the Google Admin console's Meet Safety Settings at the Organizational Unit level. If you have not seen the option, check the rollout. It began on November 2 and covered Rapid Release and Scheduled Release domains. Availability includes the Business Standard and Business Plus tiers, the Enterprise tier, and Google Workspace for Education accounts. An admin can confirm the setting for the right group of users, not just for the founder's account. That matters when calls run from different accounts.

Choose the display mode deliberately. Administrators can choose to show the policy at all times or only while a meeting is being recorded, transcribed, or captured as notes by Gemini. Always-on suits calls where the same expectation applies every time. The trigger-only mode suits calls where the rule changes with the call. Pick the mode that matches how the company actually runs calls, then write that choice into the policy page.

If the company uses multiple groups, the admin should check each group. A setting that works for the founder's account may not apply to other accounts. Setup belongs in the admin settings, not in a single user's preferences.

Keep the card visible and re-read it weekly

Post the short line in the waiting room, not in a handbook. The card names the rule, the trigger, and the detail page. Put a weekly review on the calendar. Re-read the line as if you are a client, not the founder. If the wording has drifted, fix it before the next call. A weekly review takes a minute, not a meeting. It checks that the visible rule still matches the current practice.

Run the one-minute check before the next client call

Keep this checklist in the ops folder. Each item is a quick check. It exists because a policy that is not seen is not enforced. Run the check before the next client call, then again after any change to recording, transcription, or note capture. Do the weekly re-read in the same minute.

• Confirm the short policy line appears in the Google Meet Green Room before a test call.
• Check that the line names the rule, the trigger, and the detail page.
• Set the display to always show or only during recording, transcription, or Gemini note capture.
• Verify the feature is turned on in the Google Admin console's Meet Safety Settings for the right organizational unit.
• Check whether your domain release track and Workspace tier are covered by the rollout.