---
title: "How to approve meeting requests before booking"
url: https://meet.barq.dev/guides/approve-meeting-requests-before-booking
updated: 2026-11-17
author: "Hammad Ali"
---

# How to approve meeting requests before booking

> **Short answer:** Open an event in Barq Meet, choose Booking page and turn on Requires approval. Requests hold a slot while you decide; Google invitations follow approval. Approval timeout (minutes) defaults to 1,440, or 24 hours, but a request expires at the earlier of that deadline and its proposed meeting start.


## When should I approve meeting requests before booking?

Require approval when you need to assess the request before committing to the appointment. A consultant may need to check a project brief, while a recruiter may need to verify which role a candidate is discussing. Keep ordinary catch-ups immediate.


Use two events if only one meeting needs screening. An introductory call can confirm at submission while a detailed project review waits for your decision, even when both use the same availability schedule.


We put Requires approval under Booking page because it changes what happens after the guest submits. It doesn't replace your hours or conflict calendars. The [approval feature details](https://meet.barq.dev/features/approvals-and-limits) explain that separation from daily limits and other availability controls.


## What does an approval-required booking page need to say?

Say that the guest is requesting a time and should wait for confirmation before treating the appointment as booked. Put that statement in the event description, beside the appointment's purpose. Don't make the request email deliver the first warning.


You can adapt this wording:


> Request a 30-minute project review. Tell me what you need help with and share a short brief. I'll review the request before confirming; please wait for the confirmation email and [calendar invitation](https://meet.barq.dev/glossary/calendar-invite).


Ask one required question if one answer will decide whether the meeting can go ahead, such as whether the project needs the kind of review you offer. For a project review, "What decision do you need help making?" gives you something to assess without demanding a long biography.


We include guest answers with the request information so you can make the decision before a calendar event is created. Choose questions you intend to read. A form full of ignored answers adds work for both people.


## What minimum notice and approval timeout should I set?

Start with 24 hours of minimum notice if you review requests once a day, and keep the default 1,440-minute approval timeout until you know you need less. These are two different clocks. Minimum notice controls which meeting starts a guest can request.


The timeout measures how long a submitted request may wait, capped by the proposed meeting start. It isn't a promise that every request receives a full day of review.


| Example request | Proposed start | Timeout | Expiry |
| --- | --- | --- | --- |
| Monday 09:00 | Monday 15:00 | 24 hours | Monday 15:00 |
| Monday 09:00 | Wednesday 15:00 | 24 hours | Tuesday 09:00 |
| Monday 09:00 | Wednesday 15:00 | 120 minutes | Monday 11:00 |

These examples assume all clock times use the same zone and the selected notice setting permits the request. We schedule expiry at the earlier of submission plus timeout and meeting start. The first row expires at 15:00, not at an unspecified time before it.


## What happens after I approve or decline meeting requests?

Approval moves the request into confirmation and triggers creation of its Google event. Declining or allowing expiry releases the internal hold and notifies the guest. Until approval, there's no Google busy event protecting that request in other scheduling channels.



**A meeting request waits for one of two outcomes**

| Step | Title | Details |
| --- | --- | --- |
| 1 | Guest submits | The requested time is held inside the app; request emails explain that approval is pending. |
| 2 | Host reviews | Approve or decline before the earlier of the timeout and meeting start. |
| 3 | If approved | Create the Google appointment and send confirmation; Google Meet follows the selected location. |
| 4 | If declined or expired | Release the hold and notify the guest; no confirmed Google invitation is created. |


Source: booking request, approval and expiry behavior, checked 17 Nov 2026. The final two stages are alternative outcomes, not consecutive actions.


The hold stays inside this app. A pending hold protects bookings inside Barq Meet only. If you also schedule by phone, put commitments into a selected Google calendar and remember that your manual invitation can overlap a held request. Approval requires a current decision about that time.


For video calls, read [when an approved request receives its Meet link](https://meet.barq.dev/guides/add-google-meet-link-automatically). Calendar writes can retry, so confirmation and the final appearance of joining details may not be simultaneous.


## How can I verify approval before sending the link?

Submit a test request far enough ahead that you can inspect it while pending, then approve it and check the resulting Google invitation. Use a 30-minute meeting tomorrow or later, according to your notice rule. Watch the state change.


Before approval, the guest should receive a request acknowledgement and the host should have a pending request to review. After approval, inspect the calendar destination and confirmation email. Cancel the test only after checking both stages.


Configure [reminders for confirmed appointments](https://meet.barq.dev/guides/send-meeting-reminders-free) after that test. A request acknowledgement, a confirmation and a reminder each tell the guest something different; their wording shouldn't suggest that pending means confirmed.


## Fixing approval timing problems

Check the event's approval setting and both timing rules when a request behaves unexpectedly. A long approval timeout can't keep a request alive beyond its meeting start, and it can't supply the advance notice missing from a last-minute request. Give yourself review time.


| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Request confirms immediately | Requires approval is off | Enable it under Booking page |
| Request expires sooner than 24 hours | Meeting starts before the timeout | Increase minimum notice or offer a later start |
| Pending request has no calendar event | Expected pre-approval state | Approve before expecting a Google invitation |
| Requests wait unseen | Notifications off or queue unchecked | Review Settings and check Meetings regularly |

See [the included account features](https://meet.barq.dev/pricing), then [create a meeting link that waits for your approval](https://meet.barq.dev/app/sign-in) with a review deadline you can keep.

## Steps

1. **Open Booking page for the event**: Enable Requires approval. The Approval timeout (minutes) field appears beneath it.
2. **Set Approval timeout (minutes)**: The default is 1,440 minutes, or 24 hours. Choose a shorter timeout if you routinely review requests sooner.
3. **Set notice in When people can book**: Allow enough minimum notice to review the request. For next-day reviews, start with 24 hours instead of accepting a request just before the call.
4. **Explain the request in Basics**: State that the time is provisional until you approve it. Use Questions to collect the information needed to make that decision.
5. **Review the request in Meetings**: Approve a request you can accept, or decline it with a reason. Confirmation triggers calendar creation; decline or expiry releases the hold.
6. **Test both request and approval**: Submit a test request and inspect its pending state before approval. Approve it, verify the Google invitation, then cancel the test.

## Frequently asked questions

### Will a request stop another guest taking that slot?

Yes. A pending request holds the slot against overlapping bookings inside Barq Meet. It doesn't create a Google Calendar busy event yet, so meetings arranged manually or through another booking app can still conflict with the held time. Review pending holds promptly and inspect the guest date during a trial request, instead of assuming an unconfirmed meeting leaves its interval freely available.

### Where should I look if I miss request emails?

Check Meetings for pending requests and review the host request-notification controls in Settings. An approval queue still needs attention even if email delivery is delayed; choose a timeout and minimum notice you can manage without relying on an instant alert.

### Does declining a request cancel another calendar meeting?

No. A declined request never reached the Google-event creation stage for that booking. Declining releases its internal hold and notifies the guest; it doesn't remove an unrelated appointment from a calendar you're checking for conflicts. Manage the specific request you are reviewing, and check any separate accepted appointment through its own controls before telling another guest that their meeting has changed.

## Related pages

- [Booking approvals: hold a time before you say yes](https://meet.barq.dev/features/approvals-and-limits)
- [How to add a Google Meet link automatically to bookings](https://meet.barq.dev/guides/add-google-meet-link-automatically)
- [How to send meeting reminders for free](https://meet.barq.dev/guides/send-meeting-reminders-free)
- [Booking pages that ask the questions you need answered](https://meet.barq.dev/features/booking-pages)
- [What is a calendar invite?](https://meet.barq.dev/glossary/calendar-invite)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
