Booking
Bike Fitting Client Intake Form: What to Ask Before the Session
Build a practical bike fitting intake form that helps riders choose the right session, arrive prepared and give your studio useful context without turning a business form into a clinical record.
Overview
A good bike fitting intake form has one job: reduce avoidable uncertainty before the appointment. It should help the studio understand what the rider has booked, what bicycle they are bringing and what they want to accomplish, while helping the rider arrive prepared.
It should not become a miniature medical chart, a substitute for the fitter’s professional assessment or an excuse to collect every detail that might possibly be useful.
For many studios, the best intake form is short enough to complete on a phone and specific enough that the fitter does not start every appointment by reconstructing basic facts from email threads.
Start with the decision the form needs to support
Before adding fields, decide what happens after the form is submitted.
A pre-session intake form may support one of three workflows:
Those are different jobs. Combining them into one enormous form usually creates friction.
If your services are already clear and bookable, keep the pre-session form focused on preparation. If riders regularly choose the wrong service, improve the service descriptions first and use the form only for the remaining ambiguity.
- A rider has already booked. The form adds practical context before a confirmed appointment.
- A rider is deciding which service fits. The form helps the studio route an enquiry to the appropriate service.
- The request is unusual. The form captures enough information for a human to decide whether a standard booking is appropriate.
Ask for contact details once
For a standard business intake, the basics are enough:
Do not ask the rider to repeat the same details across several forms unless there is a clear reason.
A connected client record is most useful when the studio can recognize a returning customer and see the ordinary business history around their bookings. OneStudio’s public product information describes client contact details, interaction history and related bookings as part of its CRM layer. See OneStudio features.
That is a business relationship record. It should not be described as a medical record, treatment chart or bike-fit measurement database.
- rider name;
- email address;
- phone number if the business genuinely uses it for appointment communication;
- preferred contact method if that matters operationally.
Ask which service the rider is using
A pre-session form should make the selected service explicit.
Useful choices might include the studio’s real offers, such as:
Use the exact service names from the website. If the booking says “Full Fit” while the intake form says “Performance Optimization Session,” the customer is forced to guess whether those are the same thing.
If a service has a fixed duration and price, keep those details visible on the service page before the rider reaches the form. The form should add context, not hide information that belongs in the offer.
- full bike fit;
- cleat fitting;
- follow-up session;
- pre-purchase consultation;
- fit transfer;
- another service the studio genuinely sells.
Capture the bicycle context without building an equipment database
A fitter may need a few practical details before the rider arrives. Examples include:
Keep the questions tied to the studio’s real preparation process.
OneStudio should not be presented as providing a bike geometry database, component inventory, bike garage, fit calculation engine or measurement history. Those are specialist capabilities outside the currently verified OneStudio product scope.
- bicycle type;
- cycling discipline;
- number of bicycles involved in the appointment;
- whether the rider is bringing the bicycle currently being used;
- whether the appointment concerns a new or prospective bicycle;
- pedals, shoes or other items the studio specifically asks riders to bring.
Let the rider describe the goal in their own words
A short free-text field can be useful when it asks a practical question such as:
“What would you most like to improve or understand during this session?”
That may surface goals such as:
Keep the wording neutral. A general business form should not diagnose pain, classify injuries or imply clinical assessment.
If a fitter has a qualified professional process that requires health or injury information, that belongs to the fitter’s own compliant workflow. Do not assume that OneStudio’s generic website forms or CRM are a clinical intake system.
- feeling more comfortable on longer rides;
- setting up a new bicycle;
- checking cleat position;
- reviewing a position after equipment changes;
- preparing for a different cycling discipline.
Ask what the rider needs to bring
A strong intake flow does not only collect information. It also gives information back.
After the rider submits the form, repeat the studio’s actual preparation requirements. Depending on the service, that might include:
Do not copy another studio’s preparation checklist. Publish only what is true for the business.
The same preparation details can also appear on the service page and in booking reminders so the customer does not have to search for them later.
- bicycle;
- cycling shoes;
- pedals or cleats;
- normal riding clothing;
- spare components the fitter has specifically requested;
- arrival timing;
- parking or access instructions.
Keep the form short enough for mobile
A pre-session form often arrives in the rider’s inbox or is opened from a phone. Test it on a small screen.
A useful mobile check is:
A ten-question form that takes two minutes can be more useful than a forty-question form that customers abandon or fill with placeholder answers.
- labels are readable;
- required fields are obvious;
- long text boxes are limited to questions that genuinely need them;
- the submit action is easy to tap;
- there is no horizontal scrolling;
- confirmation text is readable;
- the rider knows what happens next.
Decide which questions are required
Required fields should protect the workflow, not satisfy curiosity.
Usually reasonable required fields include:
Optional fields can capture extra context without blocking the rider.
Avoid requiring sensitive information that is not necessary to deliver the service.
- identity/contact;
- booked or requested service;
- a minimal bicycle/context question when the session depends on it;
- acknowledgment of genuinely important preparation or policy information when the business chooses to require it.
Separate intake from policy acknowledgment
Cancellation, deposits and rescheduling rules deserve their own clear presentation. Do not bury them inside an unrelated free-text intake form.
If the business uses a deposit, OneStudio’s public pricing information says the Business plan includes online payments/deposits when enabled. The studio still needs to define its own cancellation, rescheduling and refund policy. See OneStudio pricing.
The intake form can link the rider back to the policy, but the policy should not depend on the customer discovering it inside a form.
Use a human review step for ambiguous requests
Not every enquiry should become an automatic booking.
A human review is useful when:
This is where a simple enquiry path can be better than forcing every visitor directly into a calendar.
OneStudio’s Site plan publicly includes contact forms/enquiries, while Business adds online booking and the broader scheduling/client workflow. See OneStudio pricing.
- the rider is unsure which service to choose;
- the request involves multiple bicycles or an unusual scope;
- the requested service is not actually offered;
- the rider asks for something outside the fitter’s professional scope;
- the studio needs clarification before offering a time.
Build a simple pre-session intake template
A practical template can look like this:
Contact
- Name
- Phone, if used for appointment communication
Appointment
- Service booked or requested
- Appointment date, if already booked
Bicycle
- Bicycle type
- Cycling discipline
- How many bicycles are included in the session?
Goal
- What would you most like to accomplish or understand during the session?
Preparation
- Have you reviewed what to bring?
- Is there anything logistical the studio should know before you arrive?
Final note
This template is intentionally modest. Add fields only when they change what the studio does before or during the appointment.
- Anything else you want the fitter to know before the session?
What not to promise through the intake form
Do not imply that a website form automatically provides:
Those claims belong to specialist fitter expertise or specialist software, not to a generic service-business intake flow.
- biomechanical assessment;
- injury screening;
- motion analysis;
- fit recommendations;
- bicycle geometry calculations;
- automated service selection;
- clinical consent;
- fit reports;
- outcome tracking.
CTA: Make the appointment easier before it starts
A useful intake form makes the rider’s next step clearer, not heavier. Ask only what changes the preparation or routing of the appointment, keep the service offer transparent, and carry ordinary client and booking history forward without turning your business system into specialist clinical software.
Explore OneStudio features and OneStudio pricing.
Questions businesses ask
Should the intake form appear before or after booking?
Either can work. If service selection is straightforward, booking first and collecting preparation details afterward keeps the purchase path short. If customers often need help choosing a service, a short enquiry before booking can be more appropriate.
Should a bike fitting form ask about pain or injuries?
A generic business form should avoid unnecessary sensitive health information. If a qualified fitter has a professional reason to collect health information, that should be handled through the fitter’s own appropriate process rather than assumed to be part of OneStudio’s general CRM.
Can the form replace a consultation?
No. The form provides context. It should not pretend to perform the fitter’s professional evaluation.
How long should the form be?
Long enough to remove predictable uncertainty, short enough to complete comfortably on a phone. Every required field should have a clear operational reason.