Scheduling & Online Booking

Scheduling is the operational backbone of any private GP practice. It determines how efficiently clinicians use their time, how smoothly patients book and attend appointments, and how reliably revenue flows from consultation to invoice. When evaluating practice management software, the scheduling module deserves closer scrutiny than any feature checklist can provide.

This comparison examines Jump EHR and Semble side by side across every dimension of scheduling and online booking. Both platforms serve UK private healthcare practices, but they take fundamentally different architectural approaches - and those differences compound into meaningfully different day-to-day experiences for clinicians, practice managers, and patients.

We have aimed to be fair and specific throughout. Where Semble has capabilities that Jump does not, we say so plainly. Where documentation is ambiguous, we flag it. The goal is to give you enough detail to make a confident decision for your practice.

At a Glance: The Headline Differences

The table below summarises the key capability differences. Items where one platform has the clear edge are noted.

• Calendar views - Jump: Day and week. Semble: Day column view only.
• Saved custom views - Jump: Named filter presets per user. Semble: Not available.
• Recurring schedule engine - Jump: RRule-based with per-instance overrides. Semble: Manual product-based scheduling.
• Group appointments / classes - Jump: Full capacity management with roster. Semble: Not available.
• Delivery mode (in-person + remote) - Jump: Per-type toggle; patient chooses at booking. Semble: Not explicitly documented.
• Booking policy controls - Jump: 10+ granular constraints per appointment type. Semble: Basic duration and pricing.
• Slot hold timer - Jump: Reserves slot during checkout with countdown. Semble: Not documented.
• Patient verification (OTP) - Jump: Phone/email one-time passcode. Semble: Not documented.
• Proxy/dependent booking - Jump: Built-in guest booking on behalf of others. Semble: Not documented.
• Post-booking questionnaires - Jump: Inline after confirmation. Semble: Not available.
• Attendance tracking - Jump: 4 stages (arrived, sent in, left, DNA). Semble: Basic arrival + DNA.
• Audit timeline - Jump: Full visual log of who/what/when. Semble: Not documented.
• Quick book from calendar - Jump: Floating popover without navigation. Semble: Not documented.
• Schedule blocks - Jump: 8 structured types + all-day + practice-wide. Semble: Not documented as structured types.
• Xero accounting integration - Jump: Native invoice/item linking from appointments. Semble: One-way Xero sync for invoicing only.
• Multi-site scheduling - Jump: Full multi-location with aggregated availability. Semble: Multi-location with filtering.
• Pre-booking questionnaires - Jump: Per-type, mandatory before confirmation. Semble: Available with conditional logic.
• Payment at booking - Jump: Stripe (card, Apple Pay, Google Pay). Semble: Stripe/Semble Pay (card, Apple Pay, Google Pay, Klarna).
• Automated reminders - Jump: Email + SMS, multi-rule stacking per type. Semble: Email + SMS, per-product templates.
• Drag-and-drop rescheduling - Jump: Not available (dialog-based reschedule). Semble: Available on calendar.
• External calendar sync - Jump: Not available. Semble: One-way iCal feed to Google/Outlook.
• White-label booking forms - Jump: Basic branding (logo, colour, custom text, embed mode). Semble: Full white-label (OnBrand premium add-on).
• Appointment pathways - Jump: Not available as a named feature. Semble: Sequential appointment sequences.
• Waitlist - Neither platform offers this.

Calendar and Day-to-Day Scheduling

Calendar Views: Seeing Your Day, Week, and Month

The most immediately visible difference between Jump and Semble is what you see when you open the calendar.

Jump offers four calendar layouts: day and week. Clinicians and practice managers switch between day and week layouts depending on context - a receptionist checking today's list uses day view, while a practice manager reviewing the week's cover uses week view.

Semble provides a column-based day view showing clinicians and rooms as vertical columns with time slots running vertically. Semble's documentation and marketing materials do not confirm the availability of week or month views. For practices that need to see the bigger picture - planning rotas or spotting gaps in next week's cover - the single-day column view may require more manual navigation.

Saved Custom Calendar Views

Jump lets every user create and save named calendar views - specific combinations of clinicians, locations, and filters that can be recalled in one click. A practice manager might save "Monday AM - Dr Patel, Harley Street" as a view, while a receptionist saves "All Clinicians - Oxford". These persist between sessions and are personal to each user, meaning different team members can have different saved views without affecting each other.

Semble does not document an equivalent feature. Filters can be applied to the calendar, but saving named filter combinations for instant recall does not appear to be available.

Quick Booking from the Calendar

Jump provides a QuickBookPopover - a floating, draggable booking window that appears when staff click a time slot on the calendar. The appointment can be created without leaving the calendar view, keeping the schedule visible throughout. This matters in busy practices where receptionists are simultaneously answering phones, greeting patients, and managing the day's list.

Semble's help centre does not document an equivalent in-calendar quick booking mechanism. Appointments are created through the standard booking workflow.

The Scheduling Engine: How Availability Is Defined

Recurring Schedules with Per-Instance Flexibility

Jump's scheduling architecture makes a clean separation between Schedules (recurring availability patterns) and Sessions (concrete date/time instances generated from those patterns). Schedules use the RRule standard (the same recurrence specification used by iCalendar) - for example, FREQ=WEEKLY;BYDAY=MO,WE,FR defines a Monday/Wednesday/Friday pattern. The system automatically expands these into bookable sessions.

Crucially, individual sessions can be modified, cancelled (with a captured reason), or reinstated without breaking the underlying pattern. If Dr Ahmed is normally available every Monday but is at a conference on the 15th, that single session is cancelled while all other Mondays continue as normal. This is significantly more robust than manually creating or deleting individual appointment slots.

Semble configures availability through appointment "products" - each with a name, duration, and pricing. The scheduling approach appears to be more product-based than pattern-based, with individual time slots configured rather than generated from recurrence rules. This works well for straightforward schedules but may require more manual maintenance for practices with complex or frequently changing availability.

Schedule Blocks and Protected Time

Jump provides eight structured block types for non-clinical time: admin, lunch, break, meeting, training, holiday, personal, and other. Each block carries a title, reason, and optional all-day flag, and can apply to a specific clinician or practice-wide. Blocks integrate directly with the slot generation engine - blocked time is automatically excluded from availability calculations, so patients never see those slots as bookable.

Semble's documentation does not describe structured block types. Clinician unavailability can be managed, but the granularity of categorised, reason-tracked blocks does not appear to be a documented feature.

Session Overlap Detection

Jump includes a dedicated SessionOverlapIndicator and SessionOverlapPicker that actively detect when sessions conflict and present resolution options to staff. Semble takes a different approach: double-booking triggers a warning but does not hard-block - staff can override. Both approaches have merit (flexibility vs safety), but Jump's structured overlap resolution is more proactive.

Appointment Configuration and Booking Policies

Booking Policy Granularity

This is one of the widest gaps between the two platforms. Jump offers over ten configurable booking policy controls per appointment type. These include buffer time before and after appointments (in minutes), slot interval subdivision, minimum notice periods, maximum advance booking windows, per-patient booking limits (daily, weekly, and total active), cancellation windows, and a requires-approval mode where bookings enter a pending state for staff review.

These policies are independently configurable per appointment type. A "New Patient Consultation" might have a 48-hour minimum notice period and require approval, while a "Follow-up" is bookable same-day with no approval required. A "Blood Test" might have a 5-minute buffer after each slot, while a "Health Screen" has 15 minutes.

Semble's appointment configuration focuses on name, duration, pricing, and colour coding. Buffer times, per-patient booking limits, minimum notice periods, and slot interval subdivision are not documented as configurable options.

Delivery Mode Flexibility

Every Jump appointment type can be independently configured for in-person availability, remote availability (video or phone), or both. When both are enabled, patients choose their preferred mode during the booking flow. Sessions carry an allow_remote flag, and meeting URLs are stored on appointments for video consultations.

Semble supports video consultations via integrations (including a Curoflow partnership), but per-appointment-type delivery mode configuration - where patients choose between in-person and remote during self-service booking - is not explicitly documented in the same way.

Group Appointments and Classes

Jump natively supports group appointments and classes with full capacity management. Appointment types define minimum and maximum participants. The calendar displays classes with a dedicated ClassSlotCard showing capacity at a glance. A ClassDetailsSidebar shows the attendee roster with individual statuses (confirmed, pending, cancelled), real-time tracking of remaining capacity, and whether minimum attendance has been met.

Each attendee retains an individual appointment record with independent status tracking, and group bookings work through the same online booking flow - patients book into classes just as they would individual appointments.

Semble does not offer group appointment or class booking functionality. Practices running group sessions (health education, group therapy, exercise classes, antenatal groups) would need to manage capacity manually outside the system.

Online Booking and the Patient Experience

The Patient Booking Flow

Both platforms offer patient-facing online booking with shareable URLs and website embedding. The flows are broadly similar in structure - select appointment type, choose a time, enter details, confirm - but differ in important details.

Jump's booking flow is a multi-step wizard: select appointment type, choose delivery mode, pick an available slot (grouped by date and practitioner), patient identification via OTP verification, optional proxy/dependent booking, pre-booking questionnaires, payment, review and confirm, post-booking questionnaires. A slot hold timer reserves the selected slot during checkout with a visible countdown, preventing the frustrating scenario where two patients attempt to book the same slot simultaneously.

Semble's patient-facing flow proceeds: select appointment type, optionally select a clinician, choose date/time, enter personal details, optionally pay, complete custom tickboxes, receive confirmation. The system supports a manual confirmation mode where staff must approve bookings. Semble's OnBrand add-on enables full white-labelling across booking forms, emails, and the patient portal. Jump offers basic booking customisation (logo, brand colour, custom title, welcome message, and instructions, plus an embed mode with accent colour and light/dark theme) but does not extend branding to emails or the patient portal.

Patient Identification and Verification

Jump uses OTP (one-time passcode) verification via phone or email for returning patients. When a patient enters their phone number or email, the system checks for an existing record and sends a verification code. This ensures returning patients are matched to their existing clinical records without requiring passwords or separate login credentials. New patients complete a registration flow.

Semble's patient identification during online booking is not documented as using OTP verification. Patients enter their personal details, and the system matches or creates records accordingly.

Proxy and Dependent Booking

Jump includes built-in proxy booking - the ability to book on behalf of another person. A parent booking for a child, a carer booking for an elderly relative, or an assistant booking for a patient all follow a dedicated guest booking flow. The proxy relationship is recorded on the appointment, visible to clinicians and staff.

Semble's documentation does not describe an equivalent proxy booking mechanism for online self-service booking.

Slot Hold Timer

Jump reserves the selected time slot during the booking process with a visible countdown timer. This prevents race conditions where two patients select the same slot simultaneously - a real operational problem for popular clinicians with limited availability. If the timer expires before checkout completes, the slot is released.

Semble's documentation does not describe a slot hold or reservation mechanism during the booking flow.

Pre-Booking and Post-Booking Questionnaires

Both platforms support pre-booking questionnaires that patients complete before their appointment is confirmed. Semble's questionnaire builder is notably feature-rich, supporting conditional logic (where questions appear based on previous answers), file uploads, digital signature capture, and relationship fields. Jump's pre-booking questionnaires are configured per appointment type and are mandatory before confirmation, with completion tracked as tasks on each appointment.

Where Jump adds a capability Semble lacks is post-booking questionnaires - additional forms shown inline after booking confirmation. This is useful for collecting information that doesn't gate the booking decision but is still needed before the appointment (dietary requirements for a group session, specific concerns the clinician should prepare for, or consent forms that benefit from a calmer moment after the booking rush).

Semble's questionnaires cannot be reordered after creation - a documented limitation - and patient contact details from questionnaire responses do not automatically update existing records.

Appointment Lifecycle and Attendance Tracking

Status Workflow

Jump appointments follow a structured lifecycle: pending, pending_approval (if required), confirmed, attendance tracking, completed or cancelled. The attendance workflow provides four granular stages: arrived (patient checked in), sent in (directed to consulting room), left (departed), and DNA (did not attend). Each status change is timestamped and logged.

The "sent in" and "left" stages are particularly valuable for busy multi-room practices. Reception knows not only that a patient has arrived, but whether they've been collected from the waiting room and when they've left - enabling better room turnover management and real-time visibility into where every patient is in the practice.

Semble tracks patient arrival/sign-in, consultation in progress, consultation complete, and DNA. This covers the core workflow but without the "sent in" granularity that helps reception manage the physical flow of patients through the building.

Audit Timeline

Every Jump appointment carries a full visual audit timeline recording who made each change and when - creation, modifications, cancellations, reschedules, attendance events, and status transitions. This provides complete traceability for CQC compliance, clinical governance, and resolving disputes about what was booked, changed, or communicated.

Semble's documentation does not describe a per-appointment audit timeline feature.

Reminders and Notifications

Both platforms support automated appointment reminders via email and SMS. Jump's notification system operates at three configurable levels: system-wide defaults, practice-level rules, and per-appointment-type overrides. Multiple reminder rules can be stacked per appointment type - for example, sending an email 48 hours before and an SMS 2 hours before the same appointment. The system also supports automatic notifications for booking confirmations, cancellations, reschedules, and post-visit follow-ups.

Semble's reminders are configured as templates assigned to specific products (appointment types), with configurable timing, content, and channel selection. Reminders can include cancellation links. SMS incurs additional usage fees. Both approaches are functional; Jump's three-tier inheritance model may be more efficient for practices with many appointment types sharing common notification patterns.

Payment Collection at Booking

Both platforms use Stripe for online payment collection and support credit/debit cards, Apple Pay, and Google Pay. Semble adds Klarna (buy now, pay later) through its Semble Pay product, and supports in-clinic terminal payments via Stripe hardware - capabilities Jump does not currently match.

Jump's distinction is deeper accounting integration. Appointment types can be linked to Xero item codes, enabling automatic invoice generation tied directly to appointments. This creates a cleaner audit trail from booking through to financial reporting. Semble does offer Xero integration, but for invoice syncing rather than per-appointment-type item code mapping.

For practices where Klarna or in-clinic terminal payments are important, Semble has the edge. For practices prioritising clean appointment-to-invoice accounting workflows, Jump's Xero integration is more tightly coupled.

Multi-Site and Multi-Practitioner Scheduling

Both platforms support multi-location scheduling as a core capability. Jump's NativeAggregatedSlots engine calculates available slots across multiple clinicians and locations simultaneously, respecting each practitioner's individual schedules, blocks, buffer times, and existing bookings. Staff can filter aggregated results by practitioner or view all availability together, with location-level availability summaries providing at-a-glance capacity data per site.

Semble shows all locations and clinicians in one unified calendar view with location-based filtering, and appointment products can be configured per location. Both approaches work for multi-site operations; Jump's aggregation engine may offer more sophisticated cross-site availability calculations, while Semble's unified calendar view provides a familiar, visual approach.

Where Semble Has the Edge

A fair comparison must acknowledge where the incumbent is stronger. Semble has several scheduling capabilities that Jump does not currently offer:

• Drag-and-drop rescheduling. Semble lets staff click and drag appointments to new times and dates directly on the calendar. Jump handles rescheduling through a dialog-based flow - functional, with both slot picker and manual override modes, but less tactile than drag-and-drop for quick adjustments.
• External calendar sync. Semble generates an iCal feed URL that can be subscribed to in Google Calendar, Outlook, or any calendar supporting URL feeds. This is one-way only (Semble to external, not back), but useful for clinicians who want their Semble schedule visible alongside personal commitments. Jump does not currently offer this.
• White-label booking forms. Semble's OnBrand premium add-on enables full white-labelling with clinic logo, colours, and branding across booking forms, emails, and the patient portal. Jump offers basic booking customisation - practice logo, brand colour, custom title, welcome message, and instructions, plus an embed mode with accent colour and light/dark theme - but does not extend branding to emails or the patient portal.
• Appointment Pathways. Semble supports sequential appointment sequences - a pathway product containing multiple appointment types (e.g., for chemotherapy courses or treatment programmes). When booked, all appointments appear on the calendar. Jump does not have an equivalent named feature.
• Klarna and in-clinic terminals. Semble Pay supports Klarna (buy now, pay later) and Stripe hardware terminals for in-person card payments. Jump's payment collection is currently limited to online card payments and Xero invoicing.
• Pre-booking questionnaire features. Semble's questionnaire builder includes conditional logic, file uploads, and digital signature capture - a richer form-building toolkit than Jump's current questionnaire capabilities.

The Bottom Line

Jump and Semble are both capable scheduling platforms, but they serve different operational priorities.

Jump is the stronger choice for practices that need: sophisticated availability management (recurring patterns with per-instance flexibility), granular booking policy controls, group appointment or class management, detailed attendance tracking for busy multi-room sites, robust audit trails for CQC compliance, and tight appointment-to-accounting workflows via Xero. Its day and week calendar views, saved custom views, quick booking, slot hold timer, and OTP patient verification add up to a more technically complete scheduling engine.

Semble is the stronger choice for practices that need: drag-and-drop calendar management, external calendar visibility for clinicians, full white-labelled patient-facing booking forms and emails, sequential appointment pathways, Klarna payment flexibility, or rich pre-booking form-building with conditional logic. Its scheduling may be simpler, but for practices with straightforward availability patterns, that simplicity is a feature, not a limitation.

For growing multi-site private GP practices - particularly those managing complex clinician schedules across multiple locations, running group services, or needing granular control over who books what, when, and how - Jump's scheduling architecture provides meaningfully more depth. The architectural decisions (RRule-based recurrence, aggregated slot calculation, structured blocks, per-patient booking limits) are the kind of foundations that become increasingly important as a practice scales.

Methodology

This comparison was compiled in February 2026 using Semble's public help centre documentation (help.semble.io), product pages (semble.io), verified user reviews from Capterra, GetApp, and Software Advice, and direct inspection of Jump EHR's codebase and product functionality. Where a feature is described as "not documented" for either platform, it means we could not find public evidence of the feature - it may exist but not be publicly visible. We encourage readers to verify specific capabilities during a product demonstration.