Set up a service-agreement review and variation tracker for support coordination

A service agreement can become difficult to follow when the original document sits in one folder, a proposed change arrives by email and the operating team updates its schedule somewhere else.

A review and variation tracker connects those events. It shows the arrangement currently in effect, what someone wants to change, whose decision is needed and the evidence of any agreement reached.

This guide gives you a practical tracker design. It does not provide contract clauses, determine whether a charge is claimable or replace legal review of an individual agreement.

For a broader review of the participant file, use the support coordination file review checklist. This tracker focuses on what changes after an agreement is in place.

Decide which agreements you are tracking

Separate your support-coordination service agreement from agreements with other providers that you help a participant understand or review. The parties, your responsibilities and your authority may differ.

The NDIA describes helping participants understand services and negotiate agreements as part of support coordination. Supporting a person's decision should not become making it for them. NDIA: helping participants connect with NDIS supports.

Include an “our service / other provider” field if both types appear in one tracker. Record what the participant has asked you to do, any relevant information-sharing arrangements and whose decision is required. Verify a representative's authority rather than assuming it from their job title or relationship.

Do not turn the tracker into a universal signature requirement

The NDIA recommends written service agreements but explains that they are not required in most cases. The relevant requirements still need to be checked for the particular service and provider. NDIA: what is a service agreement.

Where the Core module applies, its service-agreement indicators address collaboration, accessible understanding and provision of a signed copy where the agreement is written, with a record of relevant circumstances where that is not practicable or the participant chooses not to have an agreement. NDIS Commission: service agreements with participants.

Record the actual arrangement and any gap requiring attention. Do not label every unsigned file “non-compliant” or use the absence of your preferred template as an automatic reason to withhold support. The tracker supports a considered review; it does not decide the legal position.

Keep one current-agreement row and a linked change log

The current-agreement row should identify the parties, service scope, source record, current version or arrangement reference, relevant dates, owner and next review trigger.

Use a separate linked row for each proposed variation. That preserves the existing arrangement while a change is being discussed.

Keep sensitive information in the appropriate file. The tracker can use a participant reference instead of repeating a plan, health history or detailed personal circumstances.

Use review triggers that match the work

A calendar reminder is useful, but it should not be the only reason to review an agreement. A changed goal, different support request, new provider, proposed charge or concern about the service may require attention sooner.

The NDIA's agreement guidance discusses reviewing arrangements when supports, providers or plans change. It also emphasises information in a form the participant understands. How to make a service agreement.

Choose the review date from the actual agreement and circumstances. Do not invent a universal annual renewal rule. If a review finds that no change is needed, record the discussion and decision rather than generating an unnecessary new version.

A fictional variation from proposal to implementation

The following example is invented and contains no recommended price or hours allowance.

Fictional participant Morgan asks their support coordinator to replace a routine weekly email update with a fortnightly phone discussion. The coordinator opens variation DEMO-V04 against agreement DEMO-SC02.

The initial entry records the request and leaves the decision status as “discussion required.” The coordinator checks whether the proposed change affects the work being provided, expected time or any charges. They do not assume that a different contact pattern is cost-neutral or already authorised.

After an accessible discussion, the parties agree on the revised contact arrangement and confirm that the other terms remain unchanged. The coordinator records the actual agreement evidence, its date and the agreed effective date. A clear summary is provided through the agreed communication method.

The operational check then confirms that the old recurring email task has been replaced with the agreed phone-contact task. The first contact under the new arrangement is reviewed to check that it reflects what was agreed.

The tracker distinguishes four events: request, discussion, agreement and implementation. A new task being scheduled is evidence of implementation; it is not evidence that the participant agreed beforehand.

Keep price proposals separate from accepted terms

If a proposal changes price or scope, retain the previous position and describe the difference clearly. Record any supporting source used to assess it, including its date. Check the applicable pricing and claiming arrangements separately from the contract discussion.

The NDIA's current pricing update says proposed changes to existing agreements must be discussed with participants and agreed before being made. A published pricing update does not itself record the participant's agreement to a provider's proposed change. NDIA: pricing updates.

Do not automatically replace an agreed price with a published figure, or assume that available plan funding makes every proposed service or charge appropriate. Flag uncertainty for the responsible reviewer rather than letting a spreadsheet formula decide it.

Make pending and disputed changes visible

Useful statuses include proposed, discussion underway, awaiting decision, agreed, not agreed, withdrawn and implemented. Choose labels that match the actual workflow.

Leave the effective date unconfirmed while the proposal is unresolved. Record a proposed date separately if needed. An email being delivered, a document being opened or the person failing to reply should not be entered as evidence of agreement.

If only part of a proposal is accepted, record exactly which part. Preserve the declined or unresolved elements so a later worker does not apply the whole proposal by mistake.

If a complaint or dispute arises, link the appropriate record. Do not close it merely because you have filed the variation request. Any ongoing support and transition arrangements need their own considered handling under the applicable agreement and procedures.

Check that the operational record matches the decision

After an accepted change, compare the agreement evidence with the schedule, recurring tasks, service description and any authorised billing setup that the change affects. Check only the relevant systems; do not distribute the full agreement to people who do not need it.

Keep the earlier version accessible under your retention arrangements. Record who made the update, when and what was checked. If an error is found, retain a traceable correction rather than silently changing the agreement date.

For agreements with another provider, record what you have actually confirmed. “Variation requested from provider” is different from “provider accepted variation.” Support coordination does not guarantee another organisation's response time or decision.

Test the tracker with one arrangement

Choose one agreement through your authorised process and check:

• Can you identify what is currently in effect?
• Are your role and the parties' decision-making responsibilities clear?
• Is each proposed change separate from the current arrangement?
• Are costs and scope implications visible for review?
• Does accepted status link to actual agreement evidence?
• Can the person access an understandable account of the change?
• Have affected operational records been checked?
• Are pending issues and previous versions still traceable?

Start with that one record and improve the tracker before adding a large caseload. The useful result is a clear chain of decisions, not a high number of completed cells.

To see how a source issue can stay connected with a task and review, watch the ProviderQMS walkthrough.

Official sources reviewed 14 September 2026. This is an administrative workflow suggestion, not contract drafting, a claimability decision or a universal written-agreement mandate.