NDIS document control for a sole trader: know which version to use

When you run a service yourself, document control can feel like a system designed for someone else's office. Yet the practical problem is familiar: there are three copies of a form, one has your old contact details, and you cannot remember which procedure was in use when an event occurred.

A small system can solve that. Its job is to identify the approved document, explain what changed and preserve records of work already done. You do not need several people signing every routine update to achieve those aims.

The setup below is a suggested method. File names, review intervals and approval roles should fit your service. They are not a universal NDIS naming convention.

Understand which obligations apply to your work

Sole trader status does not remove NDIS responsibilities. The Code of Conduct applies to registered and unregistered providers and workers. NDIS Commission: Code of Conduct.

Registration requirements and applicable Practice Standards depend on the supports and services you provide. Do not assume that every sole trader needs the same policy set or audit pathway. Check your circumstances against the Commission's registration information.

Where the Core module applies, its information-management indicators address accurate, current records and appropriate document access, storage, retrieval and retention. The workflow in this article is one practical way to organise those tasks. NDIS Commission: information management.

Separate templates, procedures and completed records

Start by identifying what each file is for. These three groups behave differently:

The distinction prevents a common mistake: replacing a completed record with a newer blank form because the old one looks untidy. That can remove the context of when and how the record was made.

A purchased template belongs in the blank-template group until you have checked and adapted it. Adding a logo alone does not confirm that its contacts, responsibilities and process match your work.

Give documents stable IDs

Choose a simple identifier that will remain useful if the title changes. For example, POL-003 can identify a complaints procedure and FRM-003 its blank record form. The numbering is your choice; consistency matters more than the prefix.

Use the same ID in the document, file name and register. Add a version and status. A file named FRM-003_Complaint-record_v1.2_APPROVED.docx is easier to distinguish from a draft than Complaint form final NEW.docx.

Do not put participant names or health details into broadly visible file names. Use your established record references and suitable access controls for completed records. The file name should help the intended user retrieve the record without unnecessarily disclosing its contents.

Keep one short control register

You can start with a single table:

This table is fictional. Choose real dates only when the relevant review and approval have happened.

If you are both author and approver, record that honestly. Do not create a fictional committee or an independent review that did not occur. Where an issue exceeds your competence or authority, arrange appropriate advice or review and record its actual scope.

The effective date matters. You may approve a change today and need time to update instructions, links or printed copies before it takes effect. Make that transition explicit rather than leaving two competing “current” versions.

Use a deliberate change sequence

Keep the working draft separate from the approved copy. Begin with the current version, record why you are changing it, and check the parts that depend on the change.

For example, changing a contact number may affect the procedure, a participant information sheet, the form footer and a stored email template. A search for the old number can help identify those copies. Review each result rather than replacing text indiscriminately in historical records.

Before approval, check that the revised instructions describe what you can actually do. Are the named responsibilities yours? Is the escalation contact available? Does the form ask for information that you genuinely need? Are any linked sources still current?

Then approve the document, record the effective date, update the control register and move the superseded blank version out of routine use. Archive it according to your retention arrangements. Do not erase it merely to make the folder look simpler.

A fictional version change, from start to finish

Imagine Riley, a fictional sole trader, finding that the current complaint form has no field for the person's preferred way to receive follow-up. Riley decides to add one after noticing that this information has been recorded inconsistently.

Riley copies version 1.0 into the drafts folder and writes a change note: “Added preferred contact method and accessible communication needs fields; no other process change.” Riley checks the wording against the actual complaints procedure and approves version 1.1 for use from the following day.

The new blank form replaces the old download shortcut. Riley checks a printed blank folder and removes the superseded unused copies from circulation. The old completed complaint records stay unchanged.

On the next relevant use, Riley checks whether the field helps record and follow the person's preference. If it does not, the next revision will address that specific problem. Adding the field alone is not evidence that communication improved.

This example shows a traceable document change and a later check of its usefulness. It does not imply that a particular form field is universally mandated.

Make corrections without rewriting the past

Completed records need a different process from blank templates. If you discover an error, retain the original entry and add a dated correction with the author and reason, using the capabilities of your approved system.

For example: “Amendment added 15 September by Riley: the call occurred at 10:20, not 10:02; corrected after checking the call record.” The amendment makes the change understandable without pretending the original entry was correct.

Avoid backdating a newly written record to suggest it was created earlier. You can record the event date and the actual writing date separately. If the information comes from later recollection, say so.

Plan for retrieval, backup and absence

Keep approved material somewhere you can access securely when you need it. A file that exists only on one laptop may become unavailable if the device fails. Use the backup and recovery arrangements appropriate to your service, and periodically check that a backup can actually be restored.

Test restoration with a non-sensitive sample file first. Confirm that the restored copy has the expected content and version. A “backup complete” message does not answer whether you can retrieve the document you need.

Consider how an authorised person would locate necessary records if you became unavailable. Document an appropriate continuity arrangement without sharing passwords casually or giving blanket access to all participant information. Keep the arrangement current as your work or support network changes.

Choose retention periods by record type

Do not apply one guessed retention period to every document. Incident records, financial records, contracts and working drafts can have different legal, contractual or professional requirements. Establish the applicable rules before setting deletion dates, and account for any complaint, investigation or other reason a record must be preserved.

Your document register can identify the retention category and owner without becoming a legal schedule itself. If a requirement is uncertain, mark it for clarification rather than automating deletion on an unsupported assumption.

Do a simple retrieval check this week

Choose one frequently used procedure and its blank form. Confirm that:

• The file name, document header and register show the same version.
• The approved copy is easy to distinguish from drafts.
• Shortcuts and printed blank copies point to that version.
• The last change has a reason and real approval date.
• A completed record made with the older form remains intact.
• Access and backup arrangements work as intended.

Start with those two documents, then extend the same method as you use other parts of your system. Consistent small decisions are easier to maintain than a large register assembled once and left untouched.

To explore how documents connect with quality actions and retained evidence, watch the ProviderQMS walkthrough.

Official sources reviewed 13 September 2026. This is a practical organisation method; confirm the requirements applicable to your service and record types.