The Question Log That Makes a Software Trial Actually Useful
A simple method for support workers trialling new software: log what you tried, what happened, and the exact question to ask the supplier.
Published 27 October 2026. Published by Sparks Support Pty Ltd, the makers of Sparks Provider.
The short answer
Keep a running log with three columns: the task you tried, what actually happened, and your exact question for the supplier. That turns a vague week of clicking around into real evidence for a decision.
When you trial new support-work software, the easiest week to waste is the first one. You open the app between clients, poke around for a bit, and by day five you cannot remember whether the invoice step was genuinely slow or whether you just forgot to save. A written question log fixes that. It turns a vague impression into a list you can act on, whether that means keeping the software, going back to your old one, or sending support a specific question instead of a general complaint.
If you are trialling as a sole operator, the log is about your own clients and your own invoices. If you also roster staff, add a second column for what your team would need to be able to do themselves, because what works for you at your desk does not always work for someone checking a phone between shifts.
1. Your weekly roster and shifts
This is where most of your week actually lives, so test it with real patterns, not just one tidy example shift.
- Task: set up a recurring weekly shift. Result: worked for week one, but editing week three changed every future week too. Question to ask: how do I edit a single date without changing the whole pattern.
- Task: add an unassigned shift you plan to fill later. Result: it sat on the roster but was not obvious at a glance. Question to ask: how do unassigned shifts show up against filled ones.
- Task: record a cancellation. Result: unclear whether it stayed linked to the original shift. Question to ask: where does a cancelled shift go once it is marked.
2. Participant details and agreements
This section is about whether information stays attached to the right record, and whether it is where you expect it when you need it mid-shift.
- Task: add a new client with their service agreement. Result: document uploaded fine, but hard to find again later. Question to ask: where do uploaded documents sit once saved.
- Task: send an agreement for electronic signing. Result: no notification when it was signed. Question to ask: how do I know a signature has come back.
- Task: update a detail partway through the week. Result: unclear if it updated everywhere the detail appears. Question to ask: does one edit update every place that detail shows.
3. Invoicing and getting paid
Test this with a messy week, not a clean one, because messy weeks are the normal ones.
- Task: turn an approved shift into an invoice. Result: fine for one client, slower for several at once. Question to ask: can invoices be generated in a batch.
- Task: check pricing on the invoice. Result: unsure where the price actually came from. Question to ask: how is the price book set up and can I control which items appear.
- Task: work out what the subscription will cost for your size of business. If the software publishes a calculator, use it before deciding, rather than guessing from a sales page.
4. If you also manage a team
This is a separate set of questions from your own client work, and it matters even with only one or two staff.
- Task: invite a staff member. Result: unclear what they can see once logged in. Question to ask: do staff see only their own shifts and client details, or everything.
- Task: have a staff member submit hours. Result: no clear approval step before it became payable. Question to ask: who approves hours before anything goes further.
- Task: check what happens after approval. Result: unsure if hours need manual re-entry elsewhere. Question to ask: does an approved timesheet go anywhere automatically, and does it still need checking.
5. Moving your history across
If you are switching from an existing system, this is the section worth the most patience. If you are comparing systems before deciding, a transparent comparison page, such as sparksprovider.app/compare/shiftcare, is worth reading alongside your own trial notes rather than instead of them.
- Task: import past clients, staff and shift history. Result: some history came across, some did not. Question to ask: exactly how far back does an import go, and what happens if I run it twice.
- Task: check progress notes after import. Result: unclear if they attached to the right client. Question to ask: where do imported notes land.
6. How support actually responds
This tells you what the relationship will be like once the free trial ends and something actually goes wrong.
- Task: send a genuine support question during the trial. Result: note how long the reply takes and whether it answers the actual question. Question to ask: is there a how-to video library for the parts I keep forgetting.
Picture a fictional, anonymous example: a solo support worker trialling two different apps over the same week logs eleven entries across these six areas. By Friday, the log shows one app is faster for invoicing but weaker on importing old client history, and the other way around. That is a decision made on evidence, not a guess based on which app felt nicer to tap through.
If the software you are trialling is Sparks Provider, the same log works well across its seven day free trial, which does not need a card. Provider is built for a business that employs and coordinates its own support workers, keeping roster, participants, approved hours and invoicing together. If you are working for yourself with your own clients rather than running a team, Sparks Scribe, from the same Sparks team, is built for that instead, handling shift notes and invoicing for independent workers, typed or spoken. Either way, the question log above is the useful part, not the app you run it against.
Common questions
How many questions should actually be on this list by the end of a trial?
There is no set number. A short trial that goes smoothly might only produce three or four real questions. A busier week with staff, cancellations and an import usually produces more. The point is that every entry is specific enough to act on, not a tally to hit.
Should I keep separate logs for my own client work and for staff I manage?
Yes, if you employ anyone. Your own workflow and a staff member's workflow are tested differently, and mixing them makes it harder to tell which questions are about your admin and which are about what your team can do.
What if support cannot answer one of my questions straight away?
Note that too. A supplier that takes a few days to answer a genuine question during a trial is giving you useful information about what ongoing support will be like once you are a paying customer.
Is this log still worth keeping after the trial ends?
Yes. Many of these same questions come back up when you add a new staff member, take on a new type of shift, or hit a busier month. A log you already wrote once is faster to check than starting from scratch.
This article is general information about provider operations and Sparks Provider. It is not legal, financial, employment, NDIS or compliance advice. Check current requirements with the relevant authority 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