---
title: "Free scheduling for HR 1:1s and benefits office hours"
url: https://meet.barq.dev/for/hr-teams
updated: 2026-11-17
author: "Hammad Ali"
---

# Free scheduling for HR 1:1s and benefits office hours

> **Short answer:** HR staff can offer employee 1:1s and benefits office hours through individual Google Calendar booking links. Barq Meet provides email reminders, custom questions and approval when needed. Start with 20-minute benefits conversations; it doesn't route employees between HR advisers or check shared availability, and sensitive case details belong in your established HR channel.


## Who should own a booking link for HR office hours?

Assign each office-hours link to the HR adviser responsible for those appointments and name that person in the invitation. Barq Meet checks that host's chosen Google calendars; it doesn't select an adviser from an HR team or distribute appointments according to workload or employee department.


Start with clear ownership. An employee should know whose diary they're opening, what the adviser can discuss and where to go if that person isn't the right contact.


We support several events for one host, so benefits questions and onboarding check-ins can have different descriptions and durations. The [individual host feature overview](https://meet.barq.dev/features) explains those settings without suggesting a shared HR queue.


Your HR appointment page also needs an alternative contact route. If the named adviser is away, update the invitation or point employees to another named adviser; a collection of individual links won't automatically cover an absence.


## How much time should I reserve for benefits and employee 1:1s?

Reserve twenty minutes for a narrow benefits question and thirty for a broader employee check-in, then leave time to write notes. The proposed settings below are a starting point for scheduling for HR 1:1s and benefits office hours, not a standard for handling cases. For project office hours, the [open-source maintainer recipe](https://meet.barq.dev/for/open-source-maintainers) separates an issue reference from private debugging credentials. For developer office hours, the [technical appointment recipe](https://meet.barq.dev/for/developer-relations) asks for public issue context without collecting private credentials.


| Conversation offered | Booked length | Time before / after | Advance notice | Minimal booking question | Invitation type |
| --- | --- | --- | --- | --- | --- |
| Benefits office hour | 20 minutes | 0 / 10 minutes | 24 hours | Which benefits topic? | Internally shared secret event |
| New starter check-in | 30 minutes | 5 / 10 minutes | 24 hours | Which onboarding step? | Direct event |
| Manager process question | 25 minutes | 0 / 5 minutes | 48 hours | Which process needs clarification? | One-off invitation |

For example, a 13:00 to 15:00 benefits block with thirty-minute start steps and no calendar conflicts can offer 13:00, 13:30, 14:00 and 14:30. Four twenty-minute calls occupy eighty minutes; their ten-minute notes gaps use the remaining forty.


That's a full two hours. If you need one half-hour for follow-up work, set "Maximum bookings per day" to three for that benefits event and keep other appointment commitments in view.


We apply that limit to its event. An onboarding event can still add work to the same day, so check the combined diary before promising an adviser a fixed total.


## What should stay out of the HR booking form?

Keep the form to information needed to arrange and prepare the conversation, such as a broad topic. Direct medical details, grievance accounts and documents to your established HR process; don't describe an appointment form as a private case record or a way to restrict who can read calendar details.


A topic is enough. "Benefits eligibility" gives the adviser a starting point without asking the employee to enter a family history before choosing a time.


For existing calendar events, we read timing, busy/free, status, event type and your own accept/decline response to calculate conflicts. We don't read their titles, descriptions, locations or other attendees, although Google's consent screen requests broad access because creating bookings needs it.


That limited reading concerns existing events. Choose neutral wording for new appointment descriptions and questions, and review where bookings will be written; it doesn't establish confidentiality for anything an employee types into the booking flow.


## How do I prepare an adviser's HR office-hours calendar?

Connect the adviser's Google account, choose the calendars that should block appointments and attach a schedule to the employee event. Test the guest-facing wording before distributing the link, including the location and the difference between a confirmed appointment and a request awaiting approval.


Keep the test routine. Use a non-sensitive topic so the check doesn't put a real employee matter into a sample booking.


1. Select the conflict calendars and the calendar that will receive employee appointments.
2. Create the benefits event with a neutral description and a broad topic question.
3. In "When people can book", choose the schedule and open "Advanced" for notice, buffers and start steps.
4. Under "Booking page", enable "Secret event" for an internally distributed link; add "Requires approval" only if someone will review requests.
5. Make a test appointment and inspect its invite and reminder wording before publishing the URL.


We send appointment messages with Reply-To pointing to the host, so the adviser needs to monitor those replies. Reminders are email messages, which means employees shouldn't expect an SMS from this booking setup.


## How should employees find the right HR appointment?

Put a named adviser's link beside the description of the help they provide, using your internal communications channel. Explain how to contact HR for urgent matters or when the offered appointments are full, instead of letting a booking page become the only way to reach someone. For career discussions, the [counselling appointment recipe](https://meet.barq.dev/for/career-counselors) starts with the decision the guest needs help making. For a mentee's first session, the [mentoring booking recipe](https://meet.barq.dev/for/mentors) starts with a defined question and manageable preparation.


Keep the invitation contextual. The [link-sharing guide](https://meet.barq.dev/guides/where-to-share-your-booking-link) explains placement, while your organization decides who receives each invitation and how eligibility is checked. The [one-on-one invitation](https://meet.barq.dev/templates/one-on-one-meeting-invite) makes attendance and preparation clear without concealing a formal concern inside a routine catch-up label.


A Google-connected adviser can use these controls without a paid tier; generous fair-use limits address misuse. Check [the included scheduling controls and cost](https://meet.barq.dev/pricing), then [set up a named adviser's office hours](https://meet.barq.dev/app/sign-in) if individual appointment booking meets the need.

## Frequently asked questions

### Can an employee describe a complaint in the booking question?

Ask for a broad category and use your established HR channel for detailed or sensitive information. A calendar appointment can arrange the conversation, but its form shouldn't be presented as a confidential case-management or reporting system. Ask for a neutral topic and explain the approved private channel for employee concerns, instead of collecting the complaint in scheduling copy.

### Can one appointment include the employee and their manager?

Yes, you can include extra guests, but that doesn't find a shared opening in all their calendars. Agree the manager's attendance before offering the appointment, and make the expected participants clear to the employee in advance. Confirm both people can attend before sharing the final date, and keep the invitation title suitable for their work calendars.

### Does the booking page restrict access to our employees?

A secret event hides its public listing, but the URL can be forwarded beyond your company. Distribute it through your internal channel and check eligibility yourself when needed; link visibility alone doesn't establish employment or employee identity. Share the address through internal channels and review requests where needed, because a secret listing alone doesn't enforce employee authentication.

## Related pages

- [Scheduling features](https://meet.barq.dev/features)
- [Free scheduling, with every feature included](https://meet.barq.dev/pricing)
- [Where to share your booking link: 25 places that work](https://meet.barq.dev/guides/where-to-share-your-booking-link)
- [One-on-one meeting invitation templates for managers](https://meet.barq.dev/templates/one-on-one-meeting-invite)
- [Free scheduling for career counselors](https://meet.barq.dev/for/career-counselors)
- [Free scheduling for mentors and mentorship programs](https://meet.barq.dev/for/mentors)

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