What we're currently working on

Upcoming OpenFIT updates

Below is a preview of items that are either in final testing, actively in development for the next three months, or on our longer-term roadmap. Timelines may change based on testing feedback and customer priorities.

In final testing

Reporting – Capture Methods in User Statistics

Capture methods (for example, in-person, SMS, email, QR code) are being added into the User Statistics Report. This will allow managers and supervisors to see how feedback is being collected and compare adoption across methods.

API – More Robust Client Lookup by Account and External Key

The AccountApi client lookup is being enhanced to better handle the combination of account and client external keys. This will reduce lookup errors and simplify integrations where multiple systems use their own identifiers.

Usability – Remove “Add Case” Button for Clinicians

We plan to remove the “Add Case” button from the clinician view in scenarios where it leads to confusion or unintended case creation. Case creation will be restricted to the appropriate roles, reflecting how many organisations actually work.

Surveys – Smarter Default Share Survey Template

The Share Survey feature will use a proper reusable template as its default, including better defaults for languages other than English. This will reduce clicks for clinicians and support more consistent messaging to clients.

Client UI – Make Preferred Name More Prominent

We are updating the client header so that Preferred Name is more visible during sessions. This supports more person-centred communication, especially when legal and preferred names differ.

Language addition for ORS/SRS surveys (Chuukese)

In development (next three months)

Messaging – Delivery Reports in OpenFIT

We are adding support to receive and process SMS delivery reports from Twilio directly into OpenFIT. This will give clearer visibility into whether survey invitations and codes are successfully delivered.

Configuration – Default Location for Users or Cases

A default location will be added so that users or cases can automatically inherit the correct site or clinic. This will reduce manual selection and help standardise reporting by location.

Localisation – Translate Report Labels and Column Names

We are extending localisation to cover report labels and column headings. This will make reports easier to use for non-English speakers and align them with translated survey content.

Add filter in reports for Client Language

Allow users to view reports data specific to clients preferred language set in the Client Add/Edit screen.

Infrastructure – Azure SignalR for Real-Time Updates

The current same-site hub mechanism will be replaced with Azure SignalR Service. This modernises how OpenFIT handles real-time notifications and prepares the platform for more responsive in-app updates.

Localisation – Updated Finnish Translations

Finnish translations for the web app and related content are being refreshed from the latest translation spreadsheets. This includes terminology updates requested by Finnish customer teams.

Future roadmap (no fixed timeline yet)

Messaging UI – More Detail on Mail/SMS Symbols

We plan to enhance the mail/SMS icons so users can see more detailed status information (for example, sent, delivered, failed) directly from the icon or tooltip, without navigating away from the main screen.

Administration – New Screen for Managing Tags

A dedicated Tags management screen is planned to allow administrators to create, edit and organise tags used across OpenFIT (for example, for clients, cases and outcomes). This will make it easier to maintain a clean taxonomy over time.

Reporting – DNA (Did Not Attend) Counts

We intend to add DNA counts to the Statistics and User Statistics reports. This will allow services to track non-attendance patterns alongside outcomes, helping identify where engagement support may be required.

Reporting – Language Filter for Reports

We are considering a language filter for key reports so that organisations can review outcomes and usage by client or survey language where this is needed for service planning and governance.

Localisation – Further Finnish Translation Work

Additional Finnish translation updates are planned via the central translation spreadsheets, allowing us to refine terminology and expand coverage as feedback comes in from Finnish-speaking users.

Architecture – Static Hosting for the Web App

We have a multi-step project on our roadmap to host the AngularJS-based OpenFIT web app as a static site, externalise configuration, and use Azure Functions for server-side logic. This will simplify deployment and improve performance and reliability.

Platform – Next-Generation Identity and App Support

Future work includes support for a newer generation of Identity Server, an updated Angular-based web app and an Ionic-based mobile app. These investments are aimed at modernising the OpenFIT front-end experience across devices.