Skip to content

Procurement checklist for scheduling software

Six areas Swiss IT and procurement teams review before approving online booking tools—use this as a structured conversation, not a pass/fail scorecard.

1. Data residency & subprocessors

Ask where appointment data, client contact fields, and calendar sync metadata are stored and processed. Request a current subprocessor list with locations—not marketing copy about 'global infrastructure'.

For Swiss regulated professions, document whether data stays in the EU/EEA or Switzerland, how backups are handled, and whether support staff in third countries can access production data.

2. Data processing agreement (DPA)

Confirm the vendor offers a DPA aligned with GDPR Art. 28 and Swiss nFADP expectations: purpose limitation, security measures, breach notification timelines, and audit assistance.

Check whether the DPA covers both the marketing site and the scheduling application, and whether your organisation can attach its own annex for client health or legal data classifications.

3. Languages (DE · FR · IT · EN)

Client-facing booking pages should work in the language your clients book—not only the admin UI. Verify confirmations, reminders, and reschedule flows in German, French, Italian, and English.

Swiss teams operating across cantons often need Romandie clients in French while Zurich operations run in German. A single-language booking link creates manual work at the front desk.

4. Pricing currency & total cost

Request list prices in CHF. If the vendor bills in USD or EUR, model FX spreads and accounting overhead—finance teams care about the franc amount, not the sticker price on a US website.

Compare total cost of ownership: seats, SMS reminders, payments, SSO, and support tiers. A cheaper per-seat USD plan can cost more in CHF once cards convert and invoices need manual reconciliation.

5. SSO & access control

For teams above a handful of users, ask about SAML/OIDC SSO, role-based permissions, and offboarding: when someone leaves, how fast is calendar access revoked?

Review whether managed event types let administrators standardise booking flows without giving every user full admin rights—important for law firms, clinics, and franchises.

6. Exit strategy & portability

Before signing, understand export options: booking history, client fields, webhook integrations, and calendar disconnect procedures. Open scheduling engines typically offer cleaner API exit paths than closed SaaS.

Plan a short overlap when switching: keep the old tool live while you test a new booking link, update email signatures, and point procurement to documented hosting and pricing. Most Swiss SMEs complete cutover in two weeks, not two quarters.

Further reading: Security & privacy, Privacy policy · About Zitli