An Assistive Technology Review Checklist Before a Subscription Renews

A subscription renewal is a useful point to ask whether an assistive technology tool still supports the person’s goals. The review should consider access, reliability, cost, support and what happens to important work or communication materials if the plan changes. It should happen early enough to make a considered decision.

This checklist is for users, families and teams reviewing software or app subscriptions. It does not recommend cancelling a particular service or guarantee a refund. The account holder, provider and any school or funding arrangement may each have a role in the decision.

Identify exactly what is renewing

Record the service name, plan, billing period, renewal date and confirmed price. Check whether the charge comes from an app store, the software company, a school or another provider. The name shown inside an app may not identify the organization handling payment.

Apple’s cancellation guidance advises checking receipts to identify the Apple Account involved and, where Apple is not the biller, contacting the company that bills for the subscription. This is a practical reason to verify the purchase route before trying to manage a plan.

Clarify who is authorized to change the subscription. A student may use an account paid for by a parent, institution or funding program. Include the user in the access decision while coordinating billing changes with the appropriate account holder.

Review the tasks the tool actually supports

Start with the purpose for which the tool was chosen. Ask the person which activities it helps them complete and which remain difficult. A subscription can be valuable even if used for one essential task, while frequent use does not automatically mean every paid feature is needed.

Choose a few recent examples rather than relying only on memory or usage statistics. Could the person read a required document, participate in a conversation, prepare notes or complete an assignment? What setup or assistance was needed?

Ask what has changed since the last review. A new course, device, communication goal or access need may affect suitability. Do not cancel a useful tool simply because the original trial goal no longer describes the person’s current life.

Check current access and reliability

Review the workflow with the person’s usual input and reading methods. Include sign-in, navigation, editing, correction, saving and help. A service may have added features while an important control became harder to use.

Discuss recurring problems and the response from support. Record whether issues are resolved, manageable with an agreed workaround or still blocking essential use. An unresolved support ticket should not disappear from the renewal decision just because the charge is automatic.

Consider practical continuity: internet requirements, available devices, permitted school use and the ability to work when a service is temporarily unavailable. The review should identify the support the person needs, not place responsibility for every technical failure on them.

Use a renewal checklist

Mark unanswered questions clearly. If the renewal deadline is close, contact the provider or responsible institution promptly to clarify the available options. Do not assume that a pause, extension, refund or downgrade is offered unless the applicable terms confirm it.

Check what a backup or export includes

Identify important notes, recordings, communication page sets, custom vocabulary and access settings. Ask which file or backup type preserves each item and whether the result can be used after the subscription ends. Downloading a file is not proof that another application can interpret it.

Tobii Dynavox’s TD Snap backup explanation illustrates why file types matter: a user backup includes user-level preferences, while a page-set file has a different scope and a page bundle contains selected pages. The documentation also identifies limitations such as voices not being embedded in a user backup. Check the current instructions for the actual system rather than assuming every export is complete.

Test a permitted sample in the intended destination and confirm that essential structure, links and access features remain usable. Coordinate with the relevant support team when the content is part of a communication system. Keep the person’s established communication available during any transition.

Separate cancellation from other actions

Google Play’s subscription guidance explicitly states that uninstalling an app does not cancel its subscription. Its instructions also depend on the correct account. This is one clear example of why deleting an icon should not be treated as a billing action.

Check separately what cancellation does to future charges, when paid access ends and what happens to stored content. Account closure, data deletion and a refund request can involve different processes. Use the provider’s current terms for the particular plan and region.

After an authorized change, retain the confirmation and verify the displayed status or end date. If the result is unclear, contact the biller. Do not assume a failed payment is a controlled way to cancel a service that the person relies on.

Compare alternatives around the same task

If another tool appears suitable, compare it using the same representative activities and access methods. Include setup, training, data transfer and any required accessories. A lower subscription price can still involve substantial transition work.

Check whether an institution already provides access to an appropriate tool, while confirming who is eligible and how long that access lasts. Do not assume a school licence covers home use, another device or the period after a course ends.

Give the person time to express a preference and learn a proposed replacement. A functioning communication or learning arrangement should not be removed before its alternative has been checked and the transition agreed.

Record the decision and next review

Write a short note stating whether the plan will renew, change or end, why that decision fits the person’s needs and who will complete any remaining action. Include the relevant dates and support contact, without storing payment credentials in a shared document.

If the plan continues, identify any unresolved issue and a review point. If it ends, confirm continuity and the separate handling of personal information. A clear record prevents the same uncertainty from returning at the next billing cycle.

A practical example

In this fictional example, Ben uses a paid note-taking service for college. Before renewal, Ben and a support contact review recent tasks and discover that one paid feature is essential, while several advertised extras are rarely useful.

They confirm the biller and current plan terms, test a sample export and ask about an unresolved keyboard-navigation problem. An alternative app looks cheaper, but its export and access workflow has not yet been tested.

Ben chooses the next step using that evidence and his preferences. The decision is recorded with a review date, rather than being made solely because an automatic charge is approaching.

Common questions