This release adds more flexibility to profiles, makes notes and forms easier to use, and gives schedulers more control over shifts before they are published.

What’s new: you can now add custom tabs to profile sidebars.

​What it does: this gives you more control over how profile information is grouped, so important details are easier to find.

​Use case: create separate tabs for service information, funding details, compliance notes, or internal team fields.

What’s new: custom attributes now support Checklist, Time, Phone, and Email. You can also set a default value for an attribute.

​What it does: this makes custom fields more useful for structured data, and default values can prefill new records on the web app without staff entering the same information each time.

​Use case: set a default onboarding status, add a standard contact method field, or prefill a common time value for new profiles.

What’s new: the notes editor now supports creating an Appointment Note linked directly to a shift.

​What it does: this makes it easier to write shift notes from the client record and keep them attached to the correct appointment.

​Use case: add post-shift notes straight to the shift while reviewing a client’s record.

What’s new: the client Notes tab now shows general notes, task notes, and appointment notes together in one place. Filters can be applied and are remembered when you come back.
​

What it does: you can search and filter notes by things like author, note type, source, and date without resetting your view each time.
​

Use case: keep a saved filtered view for handovers, audits, or reviewing only appointment notes.

What’s new: client documents now support Use Form, submit, and edit for form-based documents in supported document folders, where this was previously limited to care plans.
​

What it does: teams can complete forms inside client documents and come back later to update them.
​

Use case: create an assessment or client document from a form, save it into the client record, and edit it later if details change.

What’s new: adding a client, staff member, site, or incident now has fewer default required fields.
​

What it does: this reduces the amount of information needed before you can save a record.
​​

Use case: create a record quickly during intake or while on the phone, then fill in the remaining details later.

What’s new: admin staff (web-app only) can add shift notes after a shift has been clocked out of, add shift notes without marking the shift as clocked in, or use Complete Shift to finish the shift and notes in one step.
​

What it does: this gives admin staff a cleaner way to record what happened during a shift, even when the clock-in flow was missed by the support staff, or by allied health teams that don't require a clock in & out flow.
​

Use case: a support worker forgets to clock in but still needs to leave accurate shift notes before ending the appointment, or a physiotherapist adds notes throughout the appointment, through the web app.

What’s new: new shifts are now created as unpublished by default. The Publish Shifts flow lets you publish by date range or choose specific shifts.
​

What it does: this gives schedulers a draft stage before shifts go live. The mobile app will take the published shifts visibility, instead of the old 7 days in the future method.
​

Use case: build next week’s roster, review changes, and publish only the shifts that are ready, or create for a month & view a month in advance in the mobile app.

What’s new: you can now add clients and shift types directly from the compact roster sidebar while creating a shift.
​

What it does: this reduces the need to leave the roster just to create missing setup items.
​

Use case: create a new client while scheduling and continue building the shift without breaking your workflow.

What’s new: shift creation now shows staff cost, shift charge, and NDIS funding details, with shift charge also visible in shift sidebars and modal views.
​

What it does: this gives better visibility of the financial impact before a shift is saved or published.
​

Use case: confirm that a shift fits the client’s funding and expected charge before locking in the roster.

What’s new: incidents can now be reported directly from the roster, with the appointment linked to the incident, just like how you can convert a shift caution into an incident from the clients profile. Involved parties will also be auto attached from the appointment.
​

What it does: this keeps incident reporting closer to the shift where it happened and reduces re-entry.
​

Use case: report an incident from the affected appointment while the details are still fresh.

What’s new: incident evidence now supports Use Form, submit, and edit, and forms are also available in company documents.
​

What it does: this makes it easier to create structured records in more places, instead of relying only on uploads.
​

Use case: complete an evidence form for an incident, or create an internal company document from a form and update it later.

If you already work across profiles, client notes, documents, rostering, and incidents every day, these changes are aimed at cutting down repeat data entry and keeping more work inside the page you are already using.