Skip to content
Avilo
Development status
Practice planning · Desktop · In development

One appointment, several
patients and devices

Avilo plans treatments by resource rather than by calendar column: a single appointment can hold several patients, several staff members and one or more devices at once. The app is in development.

Day overviewSample practice
Appointments today
38
Patients today
31
Free places
9
No-shows
2
Occupancy over the day
Utilisation per resource
  • Device 192 %
  • Device 274 %
  • Treatment room A61 %
Sample view with fictional data
01 — Overview

The bottleneck is the resource, not the calendar.

In many practices it is not a free calendar entry that decides an appointment, but the device, the room and how many staff are present. Avilo models that directly: an appointment points at any number of patients, staff members and resources – never at a single field per role. Whether it all fits is checked through schedulr, the same scheduling library that sits behind Timbra.

  1. 01Shared use — one device with a capacity, several patients in the same time window
  2. 02Checked — exceeding capacity blocks, a double booking warns
  3. 03Traceable — every relevant action lands in the audit log and the patient history
  4. 04Local — a desktop app with an SQLite database, no cloud service required
02 — Features

What is in the app today.

Appointments and the day plan

Day and week views along the resources. Create, reschedule and cancel appointments, set participation status, check in and check out.

Patient record

Master data with contact fields, the appointment history per patient, and a history that writes itself from every relevant action – extendable with manual entries such as phone calls.

Treatment series

A series across several appointments with a progress view. If one falls through, it can be rescheduled, replaced by a substitute appointment, or the rest of the series can be shifted.

Resources and configuration

Locations, rooms, resource types, resources with capacity and status, appointment types and staff – all created in the app, without a code change.

Availability

Working hours per staff member and exceptions to them. Treatment duration, setup time and the minimum staffing required are configurable per resource type.

Dashboard and hints

Today’s appointments and patients, “now and next”, patients without a follow-up, series still missing a replacement, plus the no-show rate and resource utilisation.

03 — Workflow

From the request to the follow-up.

  1. 1Create

    Assemble the appointment

    Patients, staff and resources go into the same appointment. For the chosen appointment type, Avilo suggests a free resource.

  2. 2Check

    Capacity and conflicts

    Exceeding a resource’s capacity blocks saving. Double bookings of patients or staff appear as a warning.

  3. 3Run

    Check-in and status

    Arrival, completion and no-shows are recorded per participant – not as one flag for the whole appointment.

  4. 4Follow up

    Series, history, hints

    Missed appointments enter the replacement workflow, and the dashboard lists patients without a follow-up.

04 — Data model

Four decisions at the core.

n:m instead of 1:1

Patients, staff and resources hang off the appointment as relations. There is no “the patient” field and no “the device” field that stops being enough later.

Capacity instead of a slot

A resource carries a capacity. Whether one more patient fits is a calculation, not the occupation of a rigid time slot.

Blocking or advisory

Conflicts come in two levels: capacity is hard and prevents saving, a double booking is a hint the practice decides on.

Transactional

If a change would overbook, the whole operation is rolled back. There are no half-saved appointments.

05 — Use cases

What Avilo is being built for.

Device-bound

Treatment at a device

When one device serves several people at once and the minimum staffing decides whether it is feasible.

Serial

Therapy across many appointments

Treatments planned as a series, where one missed session shifts the rest of it.

Several locations

Rooms in different places

Locations, rooms and resources are modelled separately instead of disappearing into a flat appointment list.

Development status — as of September 2026

Built

MVP scope

Patients, appointments with shared use, capacity and conflict checks, treatment series with a replacement workflow, day and week views, audit log, patient history, internal notes and tasks, the dashboard and the configuration from locations to appointment types. Tagged internally as version 0.1.0 – with no public output.

In progress

Sharpening the planning

Recently added: working hours and exceptions per staff member, the warning for double-booked staff, configurable treatment and setup times per resource type, and the suggestion of a free resource in the appointment form.

Planned

Later phases

Roles and permissions, a waitlist, automatic slot search for multi-step treatment plans, and billing. There is no signed, distributable version yet, and no date is promised for one.

Target platforms
  • macOS
  • Windows
  • Linux
Rust · Tauri 2 · Svelte 5 · SQLite · schedulr
06 — Limits

What Avilo is not today.

Avilo is being built for a concrete practice need. What does not follow from that yet is listed here.

Not publicly available

There is no download, no trial version and no public source code. No release date is promised.

Nothing is actually sent

Patient messages are generated from templates and logged as sent. A real connection to email or SMS services is missing.

No billing, no permissions

Avilo plans and documents. Billing as well as roles and permissions are planned for later phases.

No claims about approval

Avilo is planning software. Nothing is claimed here about certification, approval or use in regulated procedures.

07 — FAQ

Frequently asked questions.

Can I use Avilo yet?

No. Avilo is in development, the repository is not public and there is no version to download. As of September 2026.

What exactly does “resource-based” mean?

An appointment is not an entry in one practitioner’s column but a combination of patients, staff and resources. Whether it can take place is decided by the capacity of those resources and the availability of the people involved.

What happens on an overbooking?

If an appointment exceeds a resource’s capacity, Avilo refuses to save and rolls the whole operation back. Double bookings of patients or staff, by contrast, are shown as a warning and not prevented.

Where is the data stored?

In a local SQLite database on the machine running the app. A cloud service is not part of how it is meant to run.

How is Avilo related to Timbra?

Both are desktop applications on the same platform layer and use the same scheduling library, schedulr. Timbra plans lessons at educational institutions, Avilo plans treatments in practices.

Can a practice be set up without programming?

Locations, rooms, resource types, resources, appointment types and staff are created in the app. Treatment duration, setup time and minimum staffing are configurable per resource type.

What will Avilo cost?

There is no answer to that yet. Price and licence model will be set only with a release.

Planning along the scarce resource.

Avilo is in development. There is nothing to download yet – we are happy to answer questions about the project.