Back to Shift Notes App GuideComparison / SPARKS SUPPORT PTY LTD

Your Own Client Notes or a Shared Team Record: Which Setup Fits You?

Working out if you need a personal client file or a shared team record for shift notes. Four observable tests to check which setup actually fits your work.

Published 18 October 2026. Published by Sparks Support Pty Ltd, the makers of Sparks Provider.

The short answer

If you are the only person supporting your clients, you need a personal client file. If other workers support the same clients, you need a shared team record so the next worker can see what happened last visit. Test it by checking who actually reads your notes this week, not your job title.

Before you pick a note-taking tool, answer one question honestly: who else needs to read what you write. That single test decides whether you want a personal client file or a shared team record, and getting it backwards wastes months of setup.

The real question is who reads this note

A personal client file holds your own notes about your own clients. Nobody else logs in, nobody else adds a line, and the history travels with you. A shared team record holds notes written by everyone currently rostered on a client, so a worker on Thursday can see what happened on Tuesday even though they were not there. Both are legitimate. The mistake is choosing based on how big you think your business should become, instead of how your week actually runs right now.

Test one: does more than one person cover the same client

Open your calendar for the last fortnight. If every client was supported by exactly one person, you, then a shared record buys you nothing except extra screens to maintain. If two or more people rotated through the same client's shifts, a shared record stops each of them starting from zero.

Test two: one file per worker, or one file per client

In a shared setup, each worker still writes their own note against the shift they worked, usually one entry per person per shift. What changes is where those notes land afterwards: all of them sit together under that client, readable by anyone currently supporting them. A worker who has never supported that person sees nothing. In a personal file, there is no pooling step because there is nobody to pool with.

Personal file: notes stay with you, searchable by date or client, never shared automatically
Shared record: notes pool under the client, visible to everyone currently rostered on them
Both: a submitted note cannot be edited or deleted, only added to as a new entry

Test three: who approves the hours behind the note

If you invoice yourself, there is no approval step beyond your own say-so. If someone else reviews a week of shifts before invoicing or sending timesheets onward, that is a sign you are already running a small team, not a solo file. That approval layer is what a shared record is built to sit underneath.

Test four: what happens to an incident report

This is worth checking before you commit to either setup. Even inside a shared team record, an incident report is not shared with the rest of the team the way a regular note is. Typically only the person who wrote it and the owner or admins can see it. If a tool you are trialling pools incident reports the same way it pools regular notes, ask why, because that is a meaningful difference in who sees sensitive detail.

A fictional example

Picture two fictional support workers, Worker A and Worker B, both anonymous and invented for this example. They alternate shifts with the same client each week. Worker A writes a note after Tuesday's shift describing a change in routine. Worker B, starting Thursday's shift, reads that note before walking in. Neither has seen the other's roster, pay, or messages, only the notes for the client they both currently support. That is the practical test for whether a shared record is doing its job: the next worker should know what happened without a phone call.

Where this fits with Sparks tools

If you are an independent support worker managing your own client work solo, Sparks Scribe handles shift notes and invoicing for that one-person file, including typed or spoken note capture. If you employ or coordinate a team of workers across shared clients, Sparks Provider keeps the roster, shared notes, approved hours and invoicing together for the whole business. Both come from the same Sparks team, but they do not share records automatically and one does not replace the other, so pick based on the tests above rather than which name you have heard.

Common questions

Can a worker see notes for a client they have never supported

No. In a shared team record, a worker only sees notes for clients they are currently rostered to support. Someone who has never worked with that client sees nothing about them.

If I start solo and later hire staff, can my personal notes move into a shared record

That depends on the specific tools involved. Check with the provider of your personal-file tool and your future shared-record tool about what, if anything, can be carried across before you rely on it.

Does a shared record mean everyone can edit old notes

No. A submitted note typically cannot be edited or deleted by anyone, including admins. Corrections are usually added as a new, separate entry that references the earlier one.

Are incident reports visible to the whole team in a shared record

Usually not. Incident reports are commonly restricted to the person who wrote them and the business's owner or admins, unlike regular shift notes which the rostered team can read.

This article is general information only and is not legal, employment, payroll or award advice. Check current requirements with the Fair Work Ombudsman (fairwork.gov.au) or an adviser for your business.

Need a simpler way to run your provider business? Explore Sparks Provider. $499 a year including GST, with unlimited staff and clients.

Questions or corrections? Contact the publisher. Please do not send client or health information.

Explore more guides