What’s new in Aldra

Open Projects within a Case to organise its work, conversations and reference documents. Set the outcome you are working towards and an optional due date. Existing project links still take you to the right place.

Link an accessible Behaviour Support Plan from the same Case. Open its preparation steps directly from the project and see progress from the versions you have saved in the plan builder.

See linked plan documents and their current status, then open them in the existing document editor. Saved preparation does not sign a document or replace practitioner review.

Correcting an organisation name as validation finishes now clears the old error message. You do not need another keystroke or a second press of Continue to refresh it.

Fixed a problem that could discard a completed summary when the AI service reported more usage than expected. Affected files can be summarised again as you use the Case.

A file with no readable text no longer triggers the same background attempt on every chat. Temporary service failures get limited retries, and a failed summary is no longer described to Aldra as still pending.

Both organisations work in the same participant record. Until now someone who accepted a share landed in it with no goals, no quality of life, no skills and no incidents. The record they were given now opens: goals and their progress, quality of life, skills, incidents and life circumstances.

→ Ending or revoking their access still takes effect at once, and it stays personal — a colleague of theirs is given nothing.

An invitation now opens on the invitation itself: sign in or create an account, set up a workspace if this is your first Case, accept, and land in the participant record. Before, the link could leave you on a sign-in page with nothing to say why.

The Case overview was drawn from the last three months, so a Case with years behind it looked like it started in winter. Goals, outcomes and funding now open on everything the record holds.

When a Case has a current plan, the Budgets tab offers Update this plan and New plan (reassessment). A Case with no current plan still shows Add plan and budgets and Upload NDIS plan.

Choose why the plan is changing: correcting a mistake, a new quote or report, a crisis or urgent change, a change to plan management, a plan extension, or something else. You can add a note, and a plan can no longer be marked as replaced by hand.

Open Changes on a plan to see each update with its date, reason, note, who made it and what moved, such as the end date or an amount.

Enter the new plan by hand or upload it. Before you save, Aldra says the current plan will end the day before the new one starts, that its unspent funds do not carry over, and that sessions after that date move to the new plan.

→ Plans on a Case no longer overlap, and a start date that clashes with an existing plan or with approved claims is explained in plain words.

A replaced plan moves to Previous plans, marked with the date it was replaced and a link to the plan that took over. Its budgets and the claims made against it are kept.

When you import a renewed plan, goals already on the Case are kept and only new ones are added. The confirmation says how many were kept and how many were added.

A session opens on a page that holds its goals, its scores and its cost together, and carries its own score link. One link can cover a series of repeats and files each score against the session it was given for.

→ No participant name appears on the page someone opens from a score link.

Behaviours of concern are scored from the session page and from the score link, separately from goal scores, and each behaviour can be linked to the goals it affects on the care map.

A session carries a single cost, divided evenly across the goals it worked on, with the case note and the behaviour scores shown beside it as the evidence. Work not attributed to a goal is collected on its own card so the totals still add up.

Restrictive practices have their own register on the Behaviours tab, beside behaviours and strategies.

Upload a behaviour support plan written outside Aldra and it becomes the plan in the builder, ready to edit, instead of being retyped.

While Aldra works on a Case chat reply, and under it afterwards, a line counts the records it read and gives their dates, for example Read 14 observations (11 September to 9 October).

A claim that rests on a Case record carries a small number. Choose it, or the matching entry in the list under the reply, to open that goal, session, incident, observation or file.

→ Each one is shown only to people who can open the record, and one that has since been deleted reads Record no longer available.

Share a Case and Aldra waits for the email to go, then says sent, failed, or not configured. A mistyped domain is caught before the Case is shared, and a bad address turns the field red as you type.

The account’s usage figures and the top-up card are now visible to owners and admins only, and only an owner or an admin can buy one.

Before a request is sent, every participant, worker, stakeholder and contact name in it is replaced with a stand-in. The reply comes back and the real names are restored before you read it.

→ The people in your records stay inside your organisation, including when Aldra is doing the reading.

A refused request now explains what it refused and why, in ordinary words, instead of failing quietly or returning an error.

Ask Aldra to fill an open Case Note and it writes into that note. In conversation it also files strategies, support needs, contacts and profile facts onto the participant they belong to.

→ The work of copying an answer out of a chat and into the right place is gone.

Create a tax invoice directly from a billable session, with the session as its evidence. Sessions now show their titles in the lists, and an unbilled session can be deleted.

Approving an invoice no longer discards a line you were part way through writing.

Link, re-point and unlink cards by dragging a line between them. Select several cards at once, and the layout stays where you put it when you fit it to the screen. One supporting goal can now feed several NDIS goals.

A goal score that needs your attention can be reviewed in place from the Inbox, rather than opening the Case to do it.

Documents in a Case are presented as documents, with the information you would use to pick one out.

Page content can be reached and scrolled with the keyboard alone, not only with a pointer.

A participant’s own rating is shown only after it has been recorded, instead of displaying an empty state as though a score existed.

Antecedents and consequences are recorded against set categories, so the Behaviours tab can show a patterns card of what most often comes before and after each behaviour.

A collection link keeps an observation on the device when there is no connection and sends it once the connection returns. A resend is recorded once, never twice.

Once a behaviour has at least 10 reviewed observations with a before or after category, Aldra sets out the evidence for and against each of the four functions, with counts and dates, and drafts a hypothesis. Nothing is saved until you save it.

→ The hypothesis you sign rests on observations you can trace.

Upload a previous report and Aldra proposes the background it contains for the person’s profile. You accept or dismiss each proposal, and a restrictive practice mentioned in a report goes to the register for you to review, never straight onto the profile.

Mark a phase change and it shows as a dated line on the behaviour charts, alongside hypothesis versions and support plans. Export the raw ABC data as CSV or PDF for a period and behaviour, or send it to a colleague on the Case with clinical access.

A plan builder steps through escalation stages, proactive strategies and a skills plan with SMART goals. The interim and comprehensive behaviour support plans render from those records and show when the plan has moved on. Documents also export to Word.

→ A change to the plan updates every document drawn from it instead of being retyped.

An interim or comprehensive plan written from its template or imported now shows under Plans. Open it in the plan builder to start a structured plan with its title and type. The original document is kept as it is and linked from the plan.

Incidents can be edited, assigned and taken through investigation to an outcome, with every change kept. A deadlines list counts down the 24-hour and 5-business-day NDIS Commission notifications in your organisation’s time zone, which you can now set.

The Behaviours tab lists behaviours of concern and restrictive practices in registers laid out like the goals register, with columns you choose and resize. Each sub-tab has its own add button, and a restrictive practice is added, edited and archived from its own register.

Record each use of a restrictive practice against an incident or observation. It is checked against the register at the time, can be voided but not edited, and is reported monthly as CSV or PDF.

As you talk in a Case, Aldra files behaviours of concern, strategies, support needs, contacts and profile facts, each marked Added by Aldra with Undo until someone edits it. A restrictive practice you say is already in use is filed only as a draft for you to confirm, and Aldra never suggests one.

The Case Overview now asks whether the plan is working and answers live from the Case, with the plan review report’s quality-of-life and value-for-money findings and the evidence behind each. Under What would lift it, each action opens the Outcomes or Goals tab. People without access to clinical records see a plain line instead.

→ You can see where the plan stands at any point, not only when the review is due.

Risks and barriers now draft from the behaviour support register, informal supports from stakeholder contact notes, and barriers, the participant’s view and priorities from signed case notes, progress notes and the Individual Care Plan. Only signed documents are read, never drafts, and every value is quoted with its date.

→ Each drafted line can be traced to the signed record and the day it came from.

A goal names its NDIS outcome domain, asked for when you create or edit it and suggested from the support needs it addresses. Older goals linked to support needs have it filled in; the rest show Domain not set. The report places each goal under its domain and counts hours delivered per domain.

Quality of life now also rates home, relationships, lifelong learning and work, each optional. Overall change compares only domains rated in both checks. The trend line plots the overall of the domains rated at each check and marks checks rating a different set. Participants under 15 are read against the NDIS children’s outcome sets.

Record dated life circumstances on the Case Overview, such as home, work, study and community, and the diagnosis and mainstream services in Edit details. The report compares the first and latest circumstances in the plan period, and the funder draft quotes the diagnosis and services with their dates, leaving the judgement to you.

Record how the participant rates their own progress, overall and for each goal they speak to, with who answered, the date and their words. Ratings are kept as given. The report shows them in the participant’s view and drafts the progress rating from the latest one, for you to change.

→ The participant’s view rests on what they said, in their own words.

A supporting goal records its practitioner type, such as speech pathology or positive behaviour support, and a responsible person: a team member or external contact on the Case. The owner shows in the goal backlog, quick-score picker and session goal lists. The picker can select one discipline’s goals; anyone can still pick any goal.

Editing a session now reads in order: the goals it worked towards come first, with the activities delivered for each nested underneath, and unticking a goal clears its activities. Save stays at the bottom of the drawer as you scroll, and settings that apply straight away sit under their own heading and say so.

A plan review report can now be created from a Case in one click. It is built from a snapshot of the Case’s evidence at that moment, so the report records what the Case held when you built it rather than reading the information again later.

→ A report you wrote last month still reads as it did when you wrote it, even after the Case has moved on.

Fields the Case can answer arrive drafted from the snapshot: goals, methods, budget use, achievements, barriers, risks and value for money. The participant’s view is quoted only in their own words, and recommendations start at the supports delivered now, for you to change. Their rating and why the NDIS is the right funder stay yours.

→ You check and edit a draft instead of starting from an empty page.

With the report open, ask Aldra in the Case chat to revise a written field or suggest recommendation rows. Each change arrives as a proposal for you to apply or reject. Aldra never changes the evidence snapshot, and writes recommendations only when you ask.

The executive summary opens with what the report evidences under the Act, then answers whether supports improved the participant’s outcomes and quality of life, and whether the plan represents value for money, each with its evidence and the law it rests on.

→ A counter view has to argue with the evidence table rather than with an opinion.

A table shows what the report evidences in each of the eight outcome domains, and marks any domain it holds no measure for, so a gap in the record is visible rather than silent.

View PDF and Print now produce the same paginated document: pages break between rows and figures rather than through them, and each evidence section carries figures drawn from the same snapshot as its tables.

Every template, from case notes to care plans and behaviour support plan forms, now uses the plan review report’s layout: a cover with the title and contents, numbered sections, and a labelled box for each answer, on screen and in the PDF. Documents look different when you open them; what they hold has not changed.

Clicking a support need’s row opens its edit panel. Before, only the actions menu at the end of the row would do it.

Sharing a Case can ask you to confirm who you are. When that could not be completed the message asked you to sign in again, which did not always help. It now tells you whether to set up a one-time code or to sign in again.

The eight getting-started emails for new workspaces and new team members were written in July and described a product that has moved on since. They now describe each feature as it works today.

Home, pricing, changelog, privacy and security now lead with what Aldra does, and share one column width across every page so they read the same way on a phone and on a wide screen.

Help has a guide for every screen, and each one explains why that part of Aldra works the way it does. The help link in your account menu opens the guide for the screen you are on, and any chat can answer how and why questions from the same guides.

Forms for adding and editing now open in a panel on the right instead of the middle of the screen: sessions, progress, participants, stakeholders, support needs, NDIS plans, observation and scoring links, Tax Invoices, projects and instructions. Confirmations still appear in the centre.

A support need could only be created and listed. You can now edit one, move it through monitoring, met and closed and back to active, delete it after confirming, and link it to the goals that address it. Current needs come first in priority order, with a filter for met or closed.

A goal you have just ticked on a session cannot be scored until the goal links are saved. The session’s scoring panel now says so, instead of leaving the new goal without a score box and no reason given.

Where an uploaded file is stored is decided by Aldra rather than taken from the request, chats and documents can only read files that scanned clean, and a sensitive change now asks for a passkey or a fresh one-time code.

Moving a chat to another Case dropped the AI consent check on content from the Cases it came from, so the assistant could read notes from a Case with AI turned off. Consent is now checked for each Case against the content itself, and every refusal is recorded.

A file you upload is scanned as soon as it arrives. Until it is cleared it cannot be downloaded, previewed, or read by anything in Aldra, including the assistant. Cleared files behave exactly as before.

→ A file that does not pass is not quietly kept: it is withheld, and trying to use it says so.

Anyone who can manage a Case can turn Aldra AI off for the person it belongs to. The Chats tab, Ask aldra, drafting, document pre-fill and plan import disappear for that Case, and the server refuses AI requests about them even if something asks anyway.

→ A Case is shared, so the switch binds every organisation holding a record for that person, not only the one that set it.

Only the organisation that recorded the most recent withdrawal can turn Aldra AI back on, and it must give a reason. Every change, and every AI request refused while the switch was off, is kept as a record you can read.

Intake now asks whether Aldra AI may be used. Answering no records the withdrawal straight away and skips the AI step that would otherwise read the plan.

Observations from a collection link and goal scores from a quick-score link now arrive on the same card: what was recorded and when, who sent it and how, whether their name was verified, and Accept or Exclude. Goal scores awaiting review sit above the goal’s history.

The Tasks page, its place on the side rail and the Task option in the Create menu have been removed. It listed Aldra’s background AI work and held an Ask aldra box, which Chat now covers. Drafting, extraction, chat and document pre-fill work as before.

→ Answers to earlier Ask aldra requests were only shown on that page, and are no longer shown.

Choosing a colleague on an inbox item only showed their name there. It did not notify them, change what they saw or filter anyone’s inbox, so the picker and the name are gone. Dismiss and Restore work as before.

Chats, writing, goals, schedule, money, people and files each have a colour, carried by an icon tile that always keeps its icon and label, including on the side rail. Captures open in a dock that can be minimised. Filter rows are one segmented control, and secondary buttons are quieter.

The system admin panel no longer scrolls past its own edges.

Pricing, privacy, security and this changelog each now serve their own title and link preview to search engines and shared links.

The new Free plan costs $0 and does not run out: 1 active participant, 1 GB of document storage, and all the core case, document and billing tools. Start free skips the trial and starts you there.

When a trial ends without a plan, or a plan is cancelled, the workspace moves to Free instead of becoming read-only. Nothing is deleted, and every participant you already have stays open and usable — the one-participant limit applies only when you add a new one.

Once each calendar month, a Free workspace has its AI token balance topped back up to 25,000 rather than added to, so unused tokens do not accumulate. A token pack you have bought is never capped or reduced: while your balance is already above 25,000 there is nothing to top up.

Month, week and day were rebuilt to look and behave like a calendar you already know: the weekday above the date, today marked, and each session showing its name, time, status and any funding warning.

Share Case has moved into the three-dot menu in the Case header, beside Edit details and Case instructions, and is offered only to people who can manage sharing on that Case. You can share by email, and the person finds it under Waiting for you to accept.

It used to list every kind of access a Case has, each with a Revoke button, including the access that comes with owning the Case. It now lists the shares that were made, and only those can be revoked.

The access you can offer when sharing a Case is now capped at what you hold on that Case yourself, and the form only offers those choices.

Goal progress now feeds the Case overview chart. A score that arrives through a public quick-score link waits, marked Awaiting review, until a practitioner accepts or excludes it, the way observations from a link always have.

Goal quick-score links now have what behaviour observation links had: the same edit dialog and Expires field, the live links row, and a confirmation before revoking takes a link away from a phone. An unnamed goal link reads Goal scores.

Editing a behaviour observation link now has an Expires choice: leave it as it is, or start a new window of 1, 7, 14, 30 or 90 days from now. The link and its QR code do not change, so anyone already using them carries on.

Creating a link offers those windows instead of a number of days to type, and names the date it stops working, so you can see when observers lose access before you send it out.

The sign-up page no longer asks for a username as well as an email address. You give your email address once and sign in with it afterwards. If you already sign in with a username, it keeps working.

The page is now headed Create your Aldra account, with a Create account button and a Sign in instead link for people who already have one.

Pricing now says so at the top: every plan starts with a 14-day free trial of Team, and no card is needed to begin. Each plan button reads Start free trial and keeps the plan you picked.

Solo is $29 a month and now covers 5 active participants instead of 3. Growth is $249 a month. Team is unchanged at $99. Paying for a year up front costs $288 for Solo, $1,008 for Team and $2,532 for Growth.

→ All prices are in Australian dollars and include GST.

Contact in the site footer, Talk to us on an Enterprise plan, and the message you see if a billing change cannot be completed all now write to support@aldra.au. The older hello and sales addresses are no longer used.

If someone edited the lines on a draft Tax Invoice while it was being approved or voided, the participant’s Reserved and Claimed budget figures could end up wrong. An invoice is now held while it changes, so the budget always matches what the invoice says.

The calendar now runs from midnight to midnight and opens at 6am, so an early visit or an evening session sits on the grid with the rest of the day instead of being left off it.

When sessions fall outside the days you are looking at, a bar above the calendar says how many, with buttons that jump to the nearest earlier and later ones. Sessions with no start time wait in their own tray, ready to drag onto a day and time.

→ The calendar no longer counts a session it does not show you.

Month joins Day, 3 days, Work week, Week and Agenda. Pick a date to go straight to it, and Previous and Next move by the view you are in.

The date and view you are looking at are kept in the page address, so refreshing, a bookmark or a copied link opens the same place instead of returning to this week.

Sessions that overlap now sit side by side. When a day holds more than fits, +N more opens it in the day view, and a crowded day view leads on to the agenda.

Aldra now works out which day it is in Melbourne time. Early in the morning, a session logged for today is no longer filed as planned, and a planned session for today can be marked delivered.

Dialogs, drawers, menus and notifications now close with a short exit instead of vanishing, and menus grow from the button that opened them. A notification you swipe away keeps going in the direction you swiped it.

Movement across Aldra is shorter. A page now arrives in one quick fade rather than section by section, loading placeholders hold still instead of pulsing, and switching between light and dark changes the page at once.

→ If your device is set to reduce motion, Aldra still keeps movement to a minimum.

Buttons give slightly when pressed, and the close button on dialogs and drawers is a bigger target, larger again on touch screens.

Menus, tiles, photos and icons share one set of shapes and line weights, and onboarding, participant intake, billing and Case setup now match the rest of Aldra.

When someone submits your website referral form, every active owner and admin of your organisation gets an email saying a new referral is waiting in Inbox, with a link to review it.

→ The email names your organisation but includes nothing about the person referred or who referred them.

In Settings, Website referrals, choose whether owners and admins are emailed about new referrals, which is on unless you turn it off. You can also send the person who made a referral an acknowledgement at the email address they entered, which is off until you turn it on.

→ The acknowledgement names only your organisation, with nothing from the referral itself.

If a website referral arrives while you are using Aldra, owners and admins see a notice with a link to review it, or to open Inbox when several arrive together. It stays until you dismiss it, and referrals already waiting when Aldra opens are left to the Inbox badge.

In Settings, Website referrals, turn on browser notifications for this device to hear about a new referral while Aldra is open in another tab. Clicking a notification takes you to the referral, or to Inbox when there are several. Turn them off on the same page.

Sessions on the calendar now take a colour for each participant, and a participant keeps the same colour every time. Each session also names its status, such as Draft, Submitted or Invoiced, with an icon and a word, and planned sessions keep a dashed edge.

Today's date is highlighted and a line marks the current time across it. The Calendar and List switch and New session sit in the top bar, date, status, search and range share one row, and editing a session opens in a side panel.

Opening a document beside a chat now changes the page address. Back closes the document and Forward opens it again, refreshing keeps it open, and a copied link opens the chat with the same document beside it.

→ A copied link only opens the document for people who already have access to it.

Leave a chat with a document open and come back later, and the document opens beside it again on the same browser. Close the document first and the chat stays as you left it.

In a Case chat, ask Aldra to create a document, for example a behaviour support plan. An unsigned draft of that template opens beside the conversation with the template’s own headings and layout, and Aldra fills in what it knows. Anything it does not know is left blank.

Keep chatting to add information or change the wording. Aldra proposes field changes that you can edit, apply or reject, and one proposal can now cover a whole behaviour support plan.

The draft shows how many required fields are filled and lists the ones still needed. Switch between Preview template and Edit fields to change a field yourself, and save those edits before applying a proposal.

→ Filling every field does not sign the document: practitioner review and signing work as before.

When an answer in a Case chat names a document, invoice or file, a button beneath it opens or downloads it. Aldra can also offer to start a draft of a template, open the Case tab it talked about, or suggest follow-up questions you send with a tap.

→ A button opens something or starts a draft; it never signs, bills or changes a record.

A project linked to a Case now opens in that Case’s Chat tab, under the Case header, and chats started there belong to the Case. The Projects page and the organisation’s chat list show only organisation work.

A Case’s projects, their documents, and the chats and messages filed in them are now visible only to people who can open that Case. A project that holds chats stays in its Case, and older links to a Case chat open it inside the Case.

The title of an open chat is now a menu with Rename and Add to project, or Move to project once it is filed. A Case chat can go in any project linked to its Case, and stays in the Case.

Aldra now moves to show you where things went, instead of things appearing and disappearing. Each page’s sections rise in one after another, table rows fade in down the page, and the navigation highlight and tab underline slide to your choice.

→ If your device is set to reduce motion, Aldra keeps movement to a minimum.

Dismissing or restoring an Inbox item moves it straight away, the items below close the gap, and focus moves to the next one. If the change cannot be saved, the item comes back. While the Inbox loads, it shows the shape of its lanes.

Applying proposed changes to a document scrolls to the first changed field and briefly highlights each changed field in turn. In a goal backlog, a goal, activity or strategy you drag slides into its new place.

Creating a scoring link now shows Goals on the link, with every active goal ticked; untick what this person is not there for. The preview follows your ticks, and each link lists the goals it carries.

Editing a live link shows the same checklist, and saving a change leaves its address, QR code and usage alone. Links issued before this release keep every active goal until you change their ticks.

In Add delivered services, Bill selected is now Add to Tax Invoice. A session that cannot be billed says why, such as a line item not in the NDIS price guide or no service time, and the dialog closes once everything selected is added.

→ If a session is left out, the dialog stays open and names it with the reason.

Creating a workspace now goes one step at a time: name your organisation, choose a starting point, then review and accept. A progress rail shows where you are across the whole sign-up, and these screens now match the sign-in page.

The sign-up page is now headed Start your free Aldra trial, says no credit card is needed, and lists the steps ahead. The link in the confirmation email now lasts 24 hours instead of 5 minutes.

Open Form templates in Settings and start from Aldra’s Case Note. Add your own sections and questions, put them in the order you work, and add a little guidance so your team knows what to write. Aldra’s standard Case Note stays as it is, and its essential questions stay in every version.

A question can take a short answer, a longer note, a number, a date, a time, a yes or no, or one choice from a list you write. Mark the questions that must be answered.

Fill in your form with fictional answers to see exactly what your team will see; nothing entered in the preview is saved. Drafts are saved for your organisation, so you can come back to one later.

Choose Make available to my team and your team can pick the form when starting a Case Note. Later edits show as unpublished changes until you make them available again.

Updates to a form apply to Case Notes started afterwards. Existing drafts and signed records keep the form and answers they began with.

→ A question already used in a published form keeps its answer type, so earlier answers are never read a different way.

Owners and admins can build forms and can give a team member Manage form templates in Team & access. That permission does not open completed records or Tax Invoices.

Creating a public link or emailing a signed document now keeps a PDF of that version first. Recipients can download or print it, each page shows the reference, version and page number, and later edits never change a copy already shared.

Delivery history lists each email with the version it carried and whether it was sent, failed or unconfirmed. View retained copy opens what the recipient received, even after the link is revoked.

→ Emails sent before this release show that their version was not recorded.

Discard draft is now in the document toolbar and the Case library row menu. The draft is removed from the Case and cannot be restored; signed documents, and drafts still listed on a Tax Invoice line, cannot be discarded.

Log a call, message or meeting from a stakeholder’s row in the Stakeholders tab, or from the Create or upload menu. Each entry keeps its notes, next action and follow-up date, with that contact’s earlier conversations alongside.

The Stakeholders tab is now a searchable table showing when each contact was last contacted and their next follow-up, with a filter for open follow-ups. A contact can also hold a job title, preferred contact method and notes, which the Case team can see.

Owners and admins can set up a referral form under Settings, Website referrals, then copy its embed code or link. Submissions arrive in Inbox, where you can accept one into a new or existing participant, or decline it with a reason.

Add participant now opens in a dialog, including manual entry. Gender is a list of options with room for the participant’s own words, and gender already recorded is kept.

The navigation column now opens with Today, Chat, Inbox and Calendar, and Create new participant sits under your Cases.

When a plan in the Budgets tab cannot be saved, each problem now appears beside the field it belongs to, and the form scrolls to the first one.

The participant’s name, status and details, now including date of birth, sit in the top header and fold away smoothly as you scroll. The section tabs stay in place, with that section’s own actions in a row beneath them.

Going back to a Case tab reopens the view you last used in that Case, until you close the browser.

A Case’s Chat tab now lists every project linked to that Case above its chats. Starting a project there with the plus links it to the Case.

The shared observation page is back to a single form with a Behaviour dropdown and one Submit observation button. The collector’s name, role and organisation stay filled in for the next entry.

→ This replaces the separate card for each behaviour introduced on 8 September.

Unsaved changes to a document now survive a page refresh. If the document changed in the meantime, you can export your edits or load the latest version before deciding.

If you belong to more than one organisation, each browser tab now stays in the organisation chosen there, and a new tab opens in the one you chose last.

If cancelling a subscription cannot complete straight away, Billing now shows it as pending, retries it automatically and offers Retry cancellation. Your records stay available to read.

Organisations on an annual plan now receive their monthly AI token allowance in each month of the plan.

The mobile app’s Unsent work screen lets you export, retry or discard work saved on the device. Captures the server turns away are kept there instead of being lost, and only the practitioner who saved one can send it.

Uploads accept documents, spreadsheets, presentations, archives, images, audio and video, and say when a file type is not supported. An image or PDF page too large to read is turned away with a message rather than failing quietly.

Captures are rough notes without a template to fill in. Open Captures above a Case’s sessions or from the Create menu; you can save, revise or discard what you wrote.

Choose “Turn into a Case Note” to open a draft and have the assistant fill its empty fields from your capture and the Case record. The draft keeps a reference to the capture for you to review alongside the note.

Only you can read an unstructured capture. Once it is attached as the source of a Case Note draft, the Case team can read it, even if the assistant’s fill fails or you leave the draft unfinished; only you can edit or discard it.

The mobile app offers Capture in Record and after logging a session. Notes queue on the phone when offline and keep their original time when sent; revising a capture and turning it into a Case Note happen on the web.

The Case header takes less space and shrinks as you scroll. The assistant rests on one line until you use it, while a draft or attachment keeps it open; Sessions and Budgets now follow Overview in the tabs.

The navigation column can show full labels, just icons, or stay hidden. Use the header control or the [ key to cycle through them; Aldra remembers your choice.

The Case name in the top navigation now opens a searchable Case picker. Switching from Goals opens the next Case’s Goals, and the same applies to the other Case tabs.

Press ⌘K on a Mac or Ctrl K elsewhere to search available actions and Cases by name or NDIS number. Press ? to see the shortcuts available where you are, including moving between daily pages and switching Cases.

Click a row in the organisation’s invoice register to see its payer, dates, line items and totals in a panel. Close it to return to the same place, or open the invoice in its Case to make changes.

Tax invoices now carry a Draft, Sent, Paid or Void stamp where applicable, on screen and in print. The payer’s shared copy shows Paid or Void when applicable, so an old link reflects those changes too.

The History tab shows what happened to an invoice, including who created or approved it and when its shared link was opened. Repeated opens within an hour are grouped together.

Register actions appear when you point at a row or reach it with the keyboard, and stay visible on touch screens. Archiving or deleting a goal, or reinstating a Case, now offers Undo after the action.

A shared observation page now shows a card for each behaviour, with separate inputs and a save button. Collector details are entered once, and the page keeps a running record of observations sent during the visit.

Goals and Behaviours now show a newly created collection link with the same copy, open and Done controls. Copying the link confirms that it worked.

“Repeat this session” is now available when editing a session. It saves your changes and creates separate follow-on sessions from those details, starting after the original date; repeated sessions also keep their title.

Public Aldra pages now have page-specific titles and descriptions, with a branded image for shared links.

On a draft, quantity, unit price and the line amount are editable in the row where they are printed, rather than in a separate editor beside it.

A tax invoice draws the records it reaches: the participant, the plan and funding it claims against, the sessions behind its lines, and the documents that evidence them. It is for your team only and is not part of the invoice anyone receives.

A built-in template for supervision: who was supervised, by whom, when and for how long, then what was discussed, what the supervisee took from it and what was agreed, with an optional next session date.

The template records the supervision of a practitioner, so it reads nothing from a Case. Composing one asks for a source document rather than pulling in a participant’s goals, sessions and plan detail.

A behaviour carries an operational definition and an explanation for the people collecting the data. Both now explain themselves under the field, and a shared collection link puts the plain-language wording above the scoring controls.

Where a definition was shown as plain text, its dot points ran together into a paragraph. Every surface that displays one now keeps its formatting.

Mandatory fields carry one shared marker across every form, and optional fields say so.

Three ways an observation could go missing are closed: a duration the field would not accept, a cleared count read as zero, and a failed save that showed nothing. The form keeps your values, says what happened, and clears only once the observation is recorded.

→ An observation you record is either saved, or clearly reported as not saved.

Goals sat on the organisation rail as the only clinical roll-up, among work and money that run across the whole account. That account-wide Goals surface has been removed, and an old link to it opens the list of Cases.

→ There is one way to read a person’s goals, in the Case they belong to.

The goal backlog and the activity and strategy registers were the same filter in two styles. They are now the same control, which also gains the accessible name the registers were missing.

A project is a folder of chats. Add instructions and reference documents once and every chat in the project uses them. Projects are at the top of the chat rail: the six most recent, then a link to the rest.

→ The background you keep repeating at the start of a chat is written down once.

A chat was assigned to a project when it was created and could not be moved. The chat row menu now offers Move to, with No project to lift one back out. Chats about a participant stay with the Case.

The rail appears beside a project chat with the open project marked, and the project header carries a back arrow.

Three buttons were reserving space in every row, cutting titles short. They are now one menu.

The create button reads Create or upload. Files upload sits under the document templates, and an Import submenu offers an NDIS plan and an interim behaviour support plan. The Case library’s Add button is the same menu.

The document list is ordered by how often your account has used each template. Long menus now scroll, so the last of twenty-three templates can be reached.

A plain upload takes as many files as you select and files them all. An import is still one file at a time.

Goals gains a Collect data sub-tab: the link form on the left, and on the right a preview of what the scoring page will ask, the links already out there, and the QR code the moment a link is made.

One New control makes whatever the open sub-tab lists, and activities and strategies are flat registers with a filter, a search and a count. An activity can now be edited after it is created.

Organisation and Admin appeared both on the side rail and in the profile menu. The rail now holds the day’s work, your pinned chats and your Cases, and organisation settings are reached from the profile menu.

Grant and revoke used to appear for everyone and then fail with a message about signing in. They now show only if you can manage access for that Case. Accepting access offered to you is unchanged.

Hide used to leave a one-line strip that never went away. Dismiss removes the card for that Case on that device, and every step on it is a link to the tab that owns that work.

The chat, its header, the chat rail and the document panel were four slightly different greys. They are now all white, like the rest of Aldra.

A Case keeps everything in one place. What you uploaded and what was written here sit in the same list, under folders that hold both. Old links to the Files tab still land somewhere sensible.

Every row carries an icon and a colour for what it is: a spreadsheet, an image, a recording or a word-processor file. A document written here from a template is drawn in Aldra’s own colour, and it is the only kind that is.

Drag a row onto a folder, right-click it, or open its actions menu. All three offer the same actions, so the library works with a keyboard, a screen reader or a switch.

Aldra can put the values from a completed assessment into the template they belong to. Ask in a chat, or use the two-source menu in the document editor. What comes back is an unsigned draft with every field editable, and it says which files it read.

Composing from a file fills empty fields only. Anything entered by hand is left alone, nothing is written until you save the draft, and nothing is signed.

A plan that has run its course can be archived. It stops being the plan a session reserves against, and drops out of the roll-up. Nothing is deleted, and restoring it puts it back. Aldra will not archive a plan whose funding is held by booked sessions or draft invoices.

→ The Budgets tab shows the plan you are working to, not every plan the Case has had.

Editing a goal offers the same fields as writing one, so the goal type, the measure and the goal it contributes to can all be corrected. A goal cannot end up beneath itself, and the measure locks once a score has been recorded.

Where there was nothing to contribute to, the picker now offers to create that goal on the spot and selects it straight away.

A Case returns you to the section you left, including the thread or sub-view you were in. It is remembered for the session on the device you are using.

The QR code and address for a behaviour collection link sat below a form taller than most screens. The preview now stays beside the form as you scroll, and each link says when it was made as well as when it expires.

A behaviour observation recorded before mid-morning in Australia was being shown as the previous day. It now reads on the clock in front of you.

On a Case with more than a handful of files, the assistant only ever saw the first few. Every file is now named, and the room left over is shared across summaries, newest first.

→ You can ask about a document filed months ago and expect Aldra to know it exists.

When Aldra reads a document it records what that document refers to and matches it against the Case’s goals, so a goal shows the documents that talk about it.

Ask Aldra about this, on the behaviour dashboard, was read as a request for help using Aldra, so it never looked at the behaviour data. It now answers the question that was asked.

A separate container for work a Case already holds split the record in two, so it is gone from the side rail. A conversation that was attached to a project keeps everything it held.

A link you issue for field scoring carries a name you choose, such as the Tuesday support worker or the school. The person holding the link never sees it. Each link shows how many scores have come through and when the last one arrived.

→ You can tell which link belongs to whom, so you can revoke the right one.

A new link is shown once as a QR code beside the address, so the phone that will use it can pick it up from the screen. Aldra keeps only a hash of the link: if it is lost, revoke it and make another.

The name and the expiry of a live link can both be changed from its row, and the address never changes. Expiry is written in plain words: expires today, expires tomorrow, expires in three days.

The field scoring page shows the wording behind each number, and what has just been recorded stays on screen underneath. Goal attainment anchors read as much less than expected through to much more than expected, and a count or duration carries its unit.

Anywhere Aldra offered today as a date it worked the day out from Greenwich, which before mid-morning in Australia produced yesterday. It now reads the local calendar day.

Every chat takes a file dropped anywhere on it, and a screenshot on the clipboard pastes straight into the message box. Several files can go at once, and Aldra reads photos as well as documents.

A video, or a photo in the format an iPhone saves by default, is refused as soon as it is dropped, with a message naming the file and saying what to do instead.

Replies render tables with their columns aligned, headings, quotes, nested lists, task lists and rules. A wide table scrolls inside the reply.

A behaviour definition can carry a second, plain-language explanation alongside the clinical one. That is what someone opening a shared collection link on a phone reads. Aldra can draft it from the clinical definition, which is never rewritten.

Adding or editing a behaviour opens a pane at the side, so the behaviours already defined stay in view. Creating offers save and add another. The list has search, filter chips and renaming on the row.

A document opens with what the Case already knows: a behaviour support plan starts with the participant’s NDIS number, date of birth and details, and a shift note opens on today’s date. Anything you have typed wins, and a signed document is never touched.

→ The same details stop being retyped into every plan.

A chat can be renamed from the recent list and from pinned chats in the side rail, not only from inside the chat itself.

Aldra was greeting people by the name on the account, which for an organisation that signed itself up is the organisation’s. It now works out the person’s own first name.

A new session slides in from the side rather than covering the calendar. Title, location, participant and NDIS support item are type-aheads, and title and location suggest from that participant’s earlier sessions.

Goals, activities, Case strategies, behaviour support records and sessions all open in a panel at the side rather than a box in the middle. A centred box is kept for a short decision that cannot be undone.

Actions on a goal in the backlog are named in a menu rather than crowded into icons beside the figures. Recording progress stays a button, and archiving and deleting ask before they act.

Issued, due and terms stack one to a line, opposite and level with who the invoice is billed to. The subject sits below across the full width.

A plan’s dates and funding can be edited from the plan card in a Case’s Budgets tab. Category amounts can be changed, added or removed, and the totals are recalculated. What is already reserved or claimed is left alone.

A category is funded once, under the support budget the NDIS funding model puts it in, and a dated release of funding has to sit inside the plan’s own dates and within what its category holds.

→ An amendment that would not add up is refused on save and says which amount to check.

Editing a plan is recorded with who made the change and what was changed.

A draft tax invoice is one document you work on directly. A line’s quantity and unit price open in place, still checked against the rate cap and the remaining budget. The invoice’s actions are held while an edit is unsaved.

Lines are added from the invoice itself, and the sessions already delivered can be pulled in without leaving it. Support codes sit with their descriptions, and quantities carry their unit.

Case note evidence for a line opens beside that line while you work. It is never part of the invoice that is printed or shared.

→ A participant’s case notes cannot leave with an invoice sent to whoever is paying it.

On a narrow screen each line becomes a readable description with its four amounts labelled, instead of a table pushed sideways.

How Aldra protects participant information is readable at aldra.au/security and downloadable as a PDF. It sets out the controls that are running, the obligations they exist to satisfy, how each is verified on every change, and what Aldra does not claim.

The privacy page names the obligations behind it and what Aldra does about each, links the instruments it quotes to their published wording, and gives one address for any privacy question.

A goal can be archived or removed from the Case. Archived and deleted goals have their own lists and can be restored, and a restored goal brings back the goals it hangs from.

Case history reads out each change in full: the old wording and the new, and who archived, deleted or restored it.

A title that runs too long is flagged in the field as you type instead of failing when you save.

Aldra answers questions about the product from a set of reviewed workflows that ship with each release: defining a measurable behaviour, collecting and reviewing observations, uploading files and writing a clinical document. Where there is no reviewed guide, it says so instead of guessing.

A new document opens already titled with the participant and the date it was started. You can change the title before you begin, or rename it later.

A stakeholder can be named as the Client, meaning the party the tax invoice is addressed to: a school, an insurer, an employer or a family paying privately. A Case without one bills as before.

→ A payer who is not a plan manager can be billed without being recorded as one.

A tax invoice shows the participant it bills, the plan it draws down, the sessions its lines consumed, the case notes evidencing them, and every send attempt. That used to take four screens.

Download works for every file in a Case, not only PDFs, and preview is offered for the formats that display safely in a browser. Each retrieval is written to the audit trail.

→ You can see who has opened a participant’s file.

File folders are drawn as paper folders, matching the project folders, and the Case sections all sit on the strip, wrapping onto a second row where they need to.

The Case actions menu carries discharge and reinstate, and each confirms before it acts.

The Case overview opens on three outcome measures with a switchable graph, and the three goals currently in play.

The header carries the participant and the actions you need. Case details and history open and close in place instead of taking you off the page.

The Case assistant sits beside every tab, so you can ask about what you are looking at without leaving it.

Every tab strip in a Case announces the panel it opens, so assistive technology can relate the two.

Whether a session can still be edited is decided in one place, so the calendar and the session form always agree.

Around 195 inputs, dropdowns and text areas were drawing their own heavy black outline. They now use the shared controls.

Organisation chat and the Case Chat tab share one layout and the same empty states, and a new chat starts on a single click instead of asking you to name it first.

A screening capture is written to the device before it goes near the network, so work recorded in a home with no reception is not lost.

Run a standardised screening instrument, score it, and keep the result with the participant record. Captures made on iOS are stored on the device and sync when a connection returns.

Projects are drawn as folders and open into their own home, with the project instructions, documents and chats inside.

My profile uses the full page and carries your notifications alongside your account settings.

Creating an NDIS plan was removed from the iOS app. The app still shows plan detail, and the plan itself is set up on the web.

→ A plan is entered on a screen big enough to check it before it is saved.

The sign-in screens and the sub-tabs inside a Case were brought into line with the rest of Aldra.

Behaviour definitions and their active collection forms are editable, so a measure that reads badly in the field can be corrected instead of replaced.

Ask Aldra in a Case to set up a behaviour and it creates the definition from your request, recorded against the message that asked for it.

An observation submitted through a collection link appears under Needs your attention, counts on the rail, and opens straight to the unreviewed entry. Accepting or excluding it clears the item for everyone.

→ An observation sent in from the field is seen the same day.

A case-note variation for Social Skills Connect, available wherever sessions and invoice lines carry their evidence.

Approving a tax invoice updates every view of it straight away, so no screen is left showing the old state.

The public site, the sign-in screens and every onboarding step use the same design system as the rest of the product.

The side rail went from thirteen entries to four, and a Case from ten tabs to four. Everything else is still reachable.

Aldra was rebuilt on one set of components and colour tokens, so spacing, controls and contrast behave the same way everywhere.

Import a plan document into a Case and its categories and amounts land in the budget without being typed in.

→ A new plan is in the budget in minutes, with no transcription to check.

Aldra proposes changes to a document as a set you accept or reject, so drafting happens over the real document.

A session can record several lines and carry them through to billing, on the mobile app as well as the web.

Stakeholder dates save correctly, organisations can upload a logo, and a participant without a photo gets an illustrated face instead of an empty circle.