No requester account required
Public requesters can suggest times without becoming users of your internal system.
Request-first scheduling
Request-first scheduling for organizations that want the final say.
SchedRequest starts with the requester, protects calendar privacy, and keeps confirmation in the hands of the organization. It is scheduling built around requests, review, and approval.
Request-first, not forced auto-booking
A new category between intake forms and booking links.
Forms collect information but do not solve calendar timing. Booking links solve timing but can remove judgment. Request-first scheduling combines the two: context, availability, routing, and approval.
Built for multi-person meetings
Organizations can move toward shared member availability instead of hard-wired one-person booking pages.
Human-controlled confirmation
The organization reviews requests and confirms only the meeting that should actually happen.
Common questions
What to know about request-first scheduling
What does request-first scheduling mean?
It means the requester proposes meeting times, but the organization reviews and confirms before a calendar event is created.
How is this different from a scheduling poll?
SchedRequest is designed around organization workflows, roles, calendar availability, and confirmation—not just collecting votes.
Who is SchedRequest for?
SchedRequest is for organizations, teams, advisors, educators, service providers, and other groups that need control over which meetings get confirmed.