Adult Day Care Software for a Small Centre: Billing and AI Notes Checklist

Look for software that records daily attendance by participant, produces transport and meal lists, bills each payer from the attendance record, keeps care notes and plans, and exports everything in plain formats. AI helps most with drafting notes from staff entries, but only if staff review every note before it is saved.

The hardest part of buying is that most vendor pages sound identical. What separates one product from another is how it handles the awkward cases: a participant who attends on three different funding rules in a month, a transport change at 8am, a billing rejection from a payer, a note that must be corrected without losing the original. The checklist below is built around those cases.

Follow me on Instagram@sagnikteaches

The centre this checklist is written around

Everything here is illustrative. Imagine a small adult day centre with 28 enrolled participants, about 19 attending on an average day, six care staff, a manager, an administrator and a driver who runs two vans. Participants arrive from home on the vans or are dropped off by family. Funding comes from three sources: a public funding programme that pays by the day, a long-term-care insurer that pays for specific services under authorisation, and private-pay families billed monthly. The administrator spends about 14 hours a week on attendance sheets, billing and chasing signatures, and staff spend about 50 minutes each on notes on a busy day.

Connect on LinkedInSagnik Bhattacharya

Use the checklist in three passes. First, mark each item as a must-have, nice-to-have or not needed for your centre. Second, put every shortlisted product through the demo script near the end. Third, score what you saw, not what you were told.

Subscribe on YouTube@sagnikteaches

Group 1: attendance, the record everything else depends on

Billing is only as good as the attendance behind it, so test this group hardest. A product that makes sign-in slow will be bypassed, and a bypassed system produces bad bills.

• Check-in and check-out per participant, with times. Verify by asking the vendor to record a half-day attendance and show how the unit of service is calculated.
• Works on the device you actually have. A tablet at the door, a phone for van staff. Ask what happens when the Wi-Fi drops; good products let you record offline and sync later.
• Planned schedule versus actual. The system should show who is expected on Tuesday, who actually arrived, and mark absences with a reason (hospital, holiday, illness). Absence reasons matter because some payers handle them differently.
• Corrections with an audit trail. If you change a check-out time, the system should keep who changed it and when, not silently overwrite.
• Daily census and emergency roll. One screen showing everyone currently in the building, printable if the power is out.

Transport lists

Transport is where small centres lose mornings. The software should produce a run sheet per van: pickup order, address, mobility needs, door-code or carer notes and the return order. It should flag a participant who is marked absent before the van leaves. A realistic failure: a participant marked absent at 7:40 still appears on the 8:00 run sheet because the two lists are separate, and the driver spends 12 minutes outside an empty house. Ask the vendor to change an attendance in the demo and show the run sheet updating.

Group 2: billing and exports

Billing is the reason most centres buy software, and the reason switching is risky. Ask for the billing demonstration to use your real rules, not a tidy example.

Be careful of the phrase "billing included". It sometimes means invoices to families and no help with payer submissions. Write down which payers you bill and ask the vendor, for each, whether the software submits, exports a file or leaves it to you.

A filled-in billing test

Give the vendor this scenario and watch them do it live. Participant A attends Monday, Wednesday and Friday, funded by the public programme at a daily rate for a full day, so a full week should produce three billable days. In week two she goes into hospital on Wednesday: Wednesday and Friday are absences with a reason, and Monday is billable. In week three she returns on Monday with a new authorisation from her insurer covering two days a week. The system should bill week one as three days, week two as one day, and then split week three between programmes, warn when the insurer's authorised units are used and produce a private-pay invoice for the third day she attends. If the vendor needs more than a few minutes, or says "we would set that up for you later", mark it down.

Group 3: care notes, plans and the record of what happened

• Daily notes by template. Quick tick-boxes for meals, activities, mood and toileting, plus a free-text line. Check that notes are saved against the participant and the date, and editable only with a record of the change.
• Care plans and goals. Review dates, goals and the staff who review them, with reminders when a review is due.
• Incidents and medication notes. Structured forms for incidents, with who was told and when. If you record medication, check what the product does and does not do, and keep your own procedures in place.
• Permissions. Role-based access so that a driver sees addresses and mobility needs but not notes, and a family portal, if offered, shows only what you choose.
• Signatures and consents. Electronic signature for consent forms and service agreements, stored with the participant.
• Printing. Anything a surveyor or auditor may ask for must print clearly: attendance by month, care plans, incident forms.

Group 4: where AI helps with notes, and where it must not

AI inside care software is either a drafting feature or a general chat box. Both can save time; both can create risk. At least one adult day care vendor, MyAdultDayCare, now advertises an AI tool that turns conversations into clinical notes for staff to review, edit and sign off. If a feature works from recorded conversations, it also needs the participant's or their representative's agreement and a written answer on where the audio goes. Treat any AI feature as a writing assistant that works only from what a staff member has entered, and ask five questions in the demo.

1. What does the AI see? Only the note being written, or the whole participant record?
2. Where is the text processed and is it kept by the AI provider? Ask for it in writing, and whether the vendor will sign a data agreement.
3. Can staff edit the draft, and is it clearly marked as a draft until a named person approves it?
4. Can the feature be switched off for the centre, or for specific participants?
5. Does it ever add content the staff member did not enter, such as a symptom or a mood?

The last question matters most. In care records, an invented detail is worse than a short note.

A sample: from staff entries to a draft note

Illustrative entries from a care assistant at 3:30pm: "Ate most of lunch. Joined chair exercise. Quiet in the afternoon, said her knee ached. Left on van 2 at 4:10." An AI draft might read: "She ate most of her lunch and joined the chair exercise session. She was quiet in the afternoon and mentioned that her knee ached. She left on van 2 at 4:10pm." That is fine. A weaker draft says: "She enjoyed the exercise session and seemed in good spirits, though her knee discomfort may need monitoring." The tool has added "enjoyed", "good spirits" and a recommendation that no one wrote. The reviewer deletes all three. The practical rule for the team: if the draft says something you did not enter, delete it, and tell the manager so you can decide whether to keep the feature.

What stays outside the AI feature

Keep participants' names and details out of general chatbots entirely. If staff want help with a family letter, use a template with placeholders, such as "[first name]", and fill in the details afterwards. If your software has no AI, you lose little: a good note template and a typing habit get most of the time back, and a centre can add a drafting feature in a year without changing platforms.

For a broader look at what drafting tools can and cannot do for residential care, ten back-office uses in care homes is a useful companion, and factual, name-free incident narratives shows how to keep wording objective, which applies equally to a centre's incident forms.

Group 5: contract, data and the cost of leaving

• Pricing basis. Per participant, per user or flat per month? A centre with 28 enrolled participants but only 19 a day should check whether enrolled or active participants are counted.
• Set-up and training fees. Ask for them in writing. Some vendors charge for onboarding and data import while others advertise none, so a quote that adds one deserves a question.
• Contract length and renewal. Some vendors sell annual terms that renew automatically, while others advertise month-to-month billing; note the cancellation notice period either way.
• Data export. A full export in CSV or a similar standard format, at no charge, within a stated time of cancelling.
• Security basics. Two-factor sign-in, role-based access, a statement on encryption and backups, and the vendor's incident process. Ask for their security summary and keep it with your records.
• Support hours. Does support answer when your day runs (7am to 5pm), and is a person reachable by phone when billing is due?

Pricing practice varies. When checked in November 2026, ElderSuite published a flat $299 a month for one facility, with no set-up fees, no per-user charges and no long-term contract, while CareTap and MyAdultDayCare asked centres to request pricing or book a demo. Compare every option on total cost per active participant per month, including every fee, rather than the headline.

Group 6: family messages, staff rotas and everything around the edges

Two more areas decide whether staff like the system a year on. Family communication: can you send a message to one family or all of them, with a record of what was sent, and can a family see only their own relative's information? A realistic need is the 7am "no van today, snow on the lanes" message to 19 households. Rota features are a second check. Some centres buy software for attendance and keep rotas in a spreadsheet; that is fine, but if the system offers staffing ratios against the day's census, test it. With 19 participants and a required ratio of, say, one staff member to six, the rota needs four on the floor, and a system that warns you when two call in sick is worth having.

Reports your manager will actually open

Ask for four reports in the demo: attendance by funder for the month, authorisations nearing their limit, overdue care plan reviews and open incidents. If each takes three clicks or fewer, managers will use them. If they need a vendor-built custom report at an hourly fee, they will not, and billing problems will surface only when a payer complains.

Realistic mistakes that show up in the first quarter

Three failures recur in small centres, each with a clear early sign.

• Attendance written up from memory after the participants leave. The sign is billing rows with identical check-out times. Fix by making check-in the van driver's or door staff's job at the time, on a device in their hand.
• Rates set up once and never updated. The sign is invoices that no longer match the funder's letter. Fix by putting rate reviews in the calendar with the contract's renewal date.
• Staff copying notes into a free chatbot because the software has no AI. The sign is notes that suddenly read very smoothly. Fix by saying out loud that no participant information goes into outside tools and offering the template or built-in route instead.

One illustrative case: a centre has a participant whose daily rate changes when a new authorisation starts on the first of the month. The administrator updates the rate on the fifth, so five days are billed at the old rate. Nothing is rejected, and the underpayment is noticed only at the quarterly reconciliation. A rule that rate changes are entered before the start date, and a monthly check of authorisation start dates, would have caught it; so would a system that warns on an authorisation change, which is why that item is on the checklist.

How to tell after 90 days that the software is working

Measure four things against your baseline. Administrator hours a week on attendance and billing (aim for a drop of a third or more by the end of month three). Billing rejections per month (counted before and after). Minutes per day each staff member spends on notes, taken as a simple sample over a week. And the number of times a transport run sheet was wrong on the day. If the first two fall and the second two do not rise, the system is earning its place. If staff say the care note screen is slower than paper, listen: a faster template or a drafting feature may help, but a system that is slower at the point of care will end up with notes written late.

Finally, put a review date in the diary for the contract's notice period, six weeks before renewal. That date is when you can still ask for a lower price, a better export or a clause you wanted. Missing it means another year on whatever terms the vendor chose.

An eight-step demo script for day centre vendors

Send this to each vendor ahead of the call and ask them to run it live on a test account, not slides.

1. Record an arrival at 8:20 and departure at 3:50 for two participants.
2. Mark one participant absent (hospital) for Wednesday; show the run sheet.
3. Bill the week for a participant with two funders and an authorisation.
4. Show a rejected line and how you correct and resubmit it.
5. Write a daily note; show the audit trail after an edit.
6. If AI drafting exists: draft from three short entries and show how the
   draft is marked until approved.
7. Export attendance and billing for last month as CSV.
8. Remove a user and show what they can still see.

Scoring what you saw

Score each step 0 to 2 (0 failed or "later", 1 worked with workarounds, 2 worked cleanly). Eight steps give a maximum of 16. In the example, three vendors might score 14, 11 and 9. The 14 may also cost the most; compare score against total cost per active participant. A product that scores 11 and costs 30 percent less may still win if its weak spots are ones you can live with. What you should not do is pay for features you did not see work.

A worked comparison for the 28-participant centre

Suppose the administrator's baseline is 14 hours a week on attendance, billing and paperwork, which at an assumed $20 an hour is about $280 a week or $14,560 a year. A product that brings that down to eight hours would save about $6,240 a year in time; if the quote is $450 a month plus a $900 set-up fee, the annual cost is $6,300 in the first year. On those invented numbers, it roughly breaks even on time alone in year one ($6,240 of time against $6,300 of cost), and the extra benefit comes from fewer rejected claims and cleaner records, which you can measure by counting rejections for three months before and after. Run the same sum on a flat published price such as ElderSuite's $299 a month with no set-up fee ($3,588 a year) and the time saving covers it with room to spare, provided the product passes the demo script; a cheaper product that fails the billing step costs more in rejected claims than it saves. Be sceptical of any projection that assumes the time saved becomes cash; it becomes a calmer week, and perhaps space for another participant.

Switching without losing records

Run the old and new systems in parallel for a month. Import the participant list, rates and authorisations first, then attendance for the current month only; archive older records in a folder and keep the export. Train staff in two short sessions on the daily screens, and give the driver their own half-hour with the run sheet. A common mistake is trusting the import: check five participants line by line against the paper file, including their funding rules, before going live. Another is leaving staff to discover the care-note screen on their own, which is how note quality drops in week one.

If you want a second view of your shortlist, a 1:1 call about your attendance and billing workflow is part of what my AI implementation consultation covers. For a wider view of how care businesses phase in new tools, a 90-day AI plan for a home care agency sets out a safe order.

Questions small centres ask before buying

Do we need dedicated adult day care software or will a spreadsheet do?

A spreadsheet works for roughly ten participants with one funder and simple billing. Past that, or once two or more payers, transport runs and care plans are involved, mistakes in manual attendance and billing usually cost more than a monthly subscription.

Does adult day care software include AI?

Some products now offer AI drafting for care notes or summaries, but features and wording change often. Ask for a live demonstration on made-up data, and confirm where the text is sent, whether it is kept, and that staff can edit and must approve before saving.

Can AI write care notes for participants?

It can turn a staff member's own short entries into readable notes, but the staff member must check and sign every one. It should not invent observations, and no participant details should go into a general chatbot outside your approved software.

What should we ask about moving our data out later?

Ask for a full export of participants, attendance, notes and billing history in a standard format such as CSV, at no extra charge, and ask what happens to your data if you cancel. A vendor who hesitates on this is telling you something.

How long does switching take for a small centre?

Plan for four to eight weeks from signing to full use: set-up, importing participants and rates, staff training and a month running old and new side by side before the old records are archived.

Further reads

• AI for Care Homes: A Registered Manager's 90-Day Implementation Plan — A 90-day plan for a neighbouring care setting.
• Mental Health Services AI: Intake, Waitlist and Referral Admin Jobs — Intake and waitlist admin in another care-related service.
• Brightwheel vs Procare: Which Daycare Software Has Real AI? — How to separate real AI features from marketing in childcare software.
• Daycare Late Pickup Policy: Can AI Word the Fees Fairly? — Fair fee and policy wording, useful for private-pay families.
• Daycare Inspection Checklist: Prepare Your Records With AI — Getting records ready for an inspection.
• Which Pharmacy Tasks Should Never Be Handed to AI? — A model for drawing the line around tasks that stay human.
• Private Practice Policy and Procedure Manual: A Therapist's AI Draft — Drafting policies that cover AI use and records.
• After School Club Booking System: Bookings and AI Reminders — Compare free, generic and dedicated booking tools for an after school club, then use AI to draft reminders without exposing children's details.
• Child Care Subsidy Billing: Can AI Match Payments to Attendance? — How a daycare can match subsidy remittances to attendance with AI-built formulas, find shortfalls and write top-up notices without names.
• NDIS Incident Report Template: Can AI Draft It? What a Manager Checks — A fill-in NDIS incident report template, how AI can tidy the facts, and the manager's checks: reportability, 24-hour and 5-day clocks, privacy.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: ElderSuite pricing page, CareTap and MyAdultDayCare home pages (checked 4 November 2026). Other vendors' prices and AI features vary; ask for a written quote and a live demonstration.