---
title: "Free scheduling for user research interviews"
url: https://meet.barq.dev/for/ux-researchers
updated: 2026-11-17
author: "Hammad Ali"
---

# Free scheduling for user research interviews

> **Short answer:** Scheduling for user research interviews works best after you've decided who should participate. Barq Meet lets a Google Calendar host offer 30- or 60-minute sessions, collect booking answers and send single-use invitations. We don't pay participant incentives or automatically qualify a respondent from their screener answers; your research team handles those decisions.


## Should participants book before or after the screener?

Send a booking invitation after you've reviewed the screener and accepted the participant. Booking questions can collect session preparation details, but an answer on the booking form doesn't automatically establish eligibility or reserve a place within a research quota.


Recruit first. If you need five participants in one segment and three in another, keep that recruitment count in your research process instead of expecting the booking page to balance it.


We provide custom questions attached to an event. We haven't built a research-panel manager that checks answers against eligibility rules and pays respondents when the interview ends.


For a UX researchers booking page, ask only what changes the session setup: a device category, an accessibility request or the agreed study reference. Don't request passwords, customer records or screenshots containing private account information.


The [booking form question sets](https://meet.barq.dev/templates/booking-form-questions-examples) show how to separate a preparation prompt from a qualification decision. Consent and research participation documentation deserve their own reviewed process. Use the [research conversation prompts](https://meet.barq.dev/templates/user-interview-script) after completing recruitment and consent, instead of treating the appointment form as permission to record. The [academic-researcher setup](https://meet.barq.dev/for/academic-researchers) keeps participant scheduling separate from study consent and recruitment records.


## Which interview settings leave enough time for notes?

Use different events when moderated interviews and short follow-ups need different durations or preparation. Allow at least ten minutes after a session for notes, then increase the gap when synthesis or a prototype reset takes longer. The following numbers are suggested starting points.


| Research session | Duration | Gap before / after | Notice | Question to collect | Invitation |
| --- | --- | --- | --- | --- | --- |
| Moderated usability session | 60 minutes | 10 / 20 minutes | 48 hours | Which device will you use? | Single-use link |
| Participant interview | 30 minutes | 5 / 15 minutes | 24 hours | Which study invitation did you receive? | Single-use link |
| Clarification call | 15 minutes | 0 / 10 minutes | 24 hours | Which earlier session is this about? | One-off link |

Protect the notes gap. Three 30-minute interviews plus fifteen minutes of notes after each require 135 minutes, before adding any preparation buffers or unrelated calendar conflicts.


Suppose your research block is 09:00 to 12:00. For 30-minute sessions with no before buffer and fifteen minutes after, starts at 09:00, 10:00 and 11:00 leave the required gap after every call. That leaves fifteen minutes between the first two occupied blocks, fifteen between the next pair and fifteen at the end.


Those starts are a proposed research schedule, not a claim about automatic participant distribution. If you need a precise set of choices, prepare those slots explicitly and inspect the invitation before sending it.


## How can I stop one participant booking several sessions?

Use a single-use invitation for a participant who should reserve one session. Once that invitation has been used, it stops accepting further bookings through the same link; another general booking URL can still offer appointments if you've shared it elsewhere.


Keep invitations individual. Forwarding a single-use link to the wrong person can consume it, and the link itself doesn't verify membership of your research sample.


We distinguish a secret event from a single-use link: the former hides the event from the public listing, while the latter limits reuse of the invitation. You can make a research event private to direct-link recipients without claiming that it's an authenticated participant portal.


Use the [full scheduling feature list](https://meet.barq.dev/features) to decide which controls your study needs. For a UX researchers scheduling app, predictable invitations matter more than a public list of every study you're running.


## How do I configure the research event before recruitment starts?

Create and test one host's event before distributing invitations, with a booking window limited to your study dates. If a coordinator must approve each booking, switch on "Requires approval" under "Booking page" and explain that selecting a slot submits a request.


1. Connect the moderator's Google calendars and choose the calendars that should count as busy.
2. Create an interview event with its actual duration and the moderator's meeting location.
3. Under "When people can book", set "Booking window" to "Date range" for the study period and add your notes buffer.
4. Add a short participant preparation form and review the confirmation under "Notifications".
5. Generate the participant invitation, then test the selected date, location and message before sharing it.


Review the guest view. The [booking page description examples](https://meet.barq.dev/templates/booking-page-description-examples) include research wording that separates session logistics from eligibility and payment information.


## Can an observer join without affecting participant availability?

An observer can receive an invitation as an extra guest, but their calendar isn't automatically checked for shared availability. Confirm the observer's availability before offering research slots, and describe who will attend in your participant information instead of surprising someone during the call.


Name the moderator too. The host needs Google Calendar; an Outlook-only moderator needs another calendar connection than we currently provide.


Incentives require a separate payment process because Barq Meet doesn't collect or send money. Tell participants the real payment owner and terms you have approved without promising that a booking triggers a transfer. The [product-manager setup](https://meet.barq.dev/for/product-managers) separates customer interview invitations from participant eligibility and incentive handling.


Check [what the research setup costs](https://meet.barq.dev/pricing), then [create your moderator's interview page](https://meet.barq.dev/app/sign-in) once your recruitment and consent process is ready.

## Frequently asked questions

### Does a single-use link prove participant identity?

No. A single-use invitation limits reuse of that URL, but a recipient can forward it. Review the participant details through your recruitment process before treating the resulting booking as a confirmed member of your sample. Complete recruitment checks before distributing the address and don't treat the person who follows it as authenticated by the link itself.

### Can I collect interview consent in a booking question?

You can add a question, but a scheduling response alone shouldn't replace your study's consent process. Provide the participant information and consent procedure required by your organization, with a way to ask questions before the interview. Record consent through the study's agreed process, keeping the scheduling prompt limited to information needed to prepare the interview.

### Will interview reminders go out as text messages?

No. Research appointment reminders use email. If your recruitment process calls for a text reminder, arrange that through an approved separate channel and tell participants how their contact details will be used. Tell participants the reminder arrives by email and agree another contact method yourself if attendance depends on a different communication channel.

## 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)
- [Booking form question examples by profession](https://meet.barq.dev/templates/booking-form-questions-examples)
- [Booking page description examples](https://meet.barq.dev/templates/booking-page-description-examples)
- [User interview script and agenda template](https://meet.barq.dev/templates/user-interview-script)

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