ENNL
Menu
← All articles

Prevent chaos in your coaching practice: version control in 6 steps

Prevent chaos in your coaching practice: version control in 6 steps

The coach checks which versions of the client's documents exist

Work from one central place for all your coaching documents, with clear statuses (draft, approved, final) and preserved history. This prevents you from sending a wrong or outdated version to a client and gives you control during an audit. Practice software like Exantur supports this because documents stay linked to the correct client file.

In short:

  • Without formal version control, you run the risk of sending outdated or incorrect documents to clients or being unable to demonstrate during audits which version was valid.
  • Cloud storage automatically saves every change, but does not show which version had the official status, which means extra structure is necessary for compliance.
  • Setting up a simple document structure with statuses, responsibilities and retention periods helps prevent errors and confusion in a small practice.
  • When you work with privacy-sensitive data, multiple staff members or files, a structured document management system is essential, not just cloud storage.
  • Exantur supports this by keeping intake forms and reports linked to client files, which increases clarity and prevents errors.
Exantur
Keep coaching documents organised
Exantur links intake forms, documents and reports to the correct client file within one integrated workspace.
View Exantur

Table of contents

What version control is and why the difference between history and status matters

Version control is the systematic recording of changes in a document, so that you always know which version is the correct one and can retrieve older versions. That is the essence of what version control entails: not just preserving, but also restoring.

This is where things often go wrong. A cloud program like Office 365 automatically saves every version you store. Handy, but that is not formal version control. What's missing is a status that says which version is officially valid.

  • Technical history (cloud): every saved change is automatically preserved, without anyone approving it.
  • Formal version control: a document goes through statuses like draft, approved and final, with a responsible person who determines that.

Suppose that during an audit you have to demonstrate which intake form you used in March. Cloud history then only shows when something was saved, not which version was considered final at the time. That difference is exactly why many coaches, after a while, do develop a need for something sturdier than just a cloud folder.

Why version control is important for your coaching practice

Without clear agreements, errors creep in. You accidentally send a client an old version of an assignment, or you yourself work with an outdated procedure because you no longer know which file is the latest.

The risks are concrete:

  • A client receives the wrong version of an intake form or exercise.
  • You yourself use an outdated procedure or template during a session.
  • In the event of a complaint or inspection, you cannot demonstrate which version was valid.

Good document management prevents staff members or coaches from working with outdated documents and keeps manuals and working documents traceable. For solo coaches and small teams, this is no less important than for large organisations. You may have fewer documents, but the consequences of a mistake hit your client just as hard. Calm in your administration is also calm in your head during the session itself.

Checklist: setting up version control in six steps

You don't have to set up a complicated system right away. Start with these six steps.

  1. Choose one central storage location. Determine which folder, which file or which system is the only correct source. All other copies are temporary and are discarded afterwards.
  2. Define simple statuses and a version format. Work with draft, review and final, and a simple number such as 1.0, 1.1, 2.0.
  3. Appoint a responsible person. Someone who determines when a document goes to "final", even if that is simply yourself.
  4. Plan revisions and retention periods. Agree on how often you review a procedure or form and how long you keep old versions.
  5. Set basic access rules. Who may edit, who may only read, and record who changed what and when.
  6. Communicate the rules. Explain to clients and colleagues where they find the current document and why older copies are no longer valid.

Pro tip: *For small practices, use one "final" folder and one "draft" folder.

Example rules for naming, review and restoring

Good naming already prevents a lot of hassle. Put the version number at the end of the file name, for example "intakeform_v1.2", and use the date of the last change as an additional check.

The workflow itself usually follows a fixed order:

  • Someone requests a change (a client, yourself, or a fellow coach).
  • You create a draft and adjust the content.
  • A responsible person checks the draft, that is the review step.
  • After approval, the document becomes final and replaces the old version.
  • The old version does not disappear, but is given the status "archived".

Want to find an earlier version? Keep archived documents in a separate folder or label, along with a short revision form: who changed what, and why. That way, if in doubt, you can always go back to the previous version without having to guess which one was the correct one. For the longer term, a fixed archiving routine helps, for example cleaning up your documents once a quarter and removing old drafts that no one uses anymore.

When cloud storage is enough and when you need more

Standard cloud storage does a few things well. You get automatic history, can collaborate in real time and quickly see who last changed something.

But there are limits. Cloud storage does not track a formal status, does not provide evidence for an audit, and does not automatically link documents to the correct client file.

Switching to practice software or a document management system (DMS) is worthwhile as soon as you:

  • Manage privacy-sensitive client information that must remain attached to a specific file.
  • Have multiple coaches or staff members who work with the same documents.
  • Need to be able to demonstrate which version was valid at which moment.

For a solo coach with a handful of fixed templates, a simple cloud folder with clear agreements is often enough. As soon as your number of clients grows or you work with assessments and reports that belong to a file, structured document storage linked to the client file becomes more valuable than a loose folder.

Real-world example: how version control brought calm to my practice

Real-world example: how version control brought calm to my practice — overview diagram

A coach once told me how she worked for years with loose versions of her intake forms, scattered across email, a laptop and a cloud folder. One day she accidentally sent an outdated questionnaire to a new client.

After that incident, she created one central folder with three statuses: draft, review, final. She appointed herself as the responsible person and took ten minutes a month to check whether everything was still correct. The result was not spectacular, but it was noticeable: less searching, less doubt, and clients who always received the correct document.

— Martijn

How Exantur helps with version control and documentation

Exantur is the way to keep your documents and version control in one place, without having to build a system of folders and rules yourself. Instead of loose cloud folders and Word files, you get a workspace in which intake forms, assessments, assignments and reports stay automatically linked to the correct client file.

That solves exactly what an ordinary cloud folder does not offer: an overview per client, instead of an overview per file. Your session notes remain searchable and recorded as observations, insights and action points, so you don't have to search for "the latest version" of a conversation. For coaches who want to work in line with the GDPR, Exantur hosts data within the EU and works with security that takes privacy-sensitive client information into account.

Want to see what that looks like in practice? Check out the coaching software for coaches in the Netherlands and start the 14-day trial period free of charge.

How Exantur helps with version control and documentation — overview diagram

Sources

For those who want to dig deeper: Qlink Software clearly explains the basics of version control, CloudCompagnon describes why cloud history is not the same as compliance, and Kwaliteit in Bedrijf connects document management to audits. These sources formed the basis for the checklist in this article.

Frequently asked questions

What is a normal hourly rate for a coach?

Hourly rates for coaches vary widely, depending on specialisation, experience and region. There is no fixed national rate, so if in doubt, ask for references or compare providers in your field.

What are the most commonly used coaching techniques?

Commonly used techniques include the GROW model, active listening, asking powerful questions, goal setting with accountability and reflection exercises such as the Wheel of Life. Which technique works best depends on the coaching goal and the client.

How much does one-on-one coaching cost?

The price of individual coaching varies per coach, session length and programme, and there is no fixed national rate. Ask the coach directly for a concrete quote for your situation.

What are important skills for inspiring coaching?

Strong coaches combine active listening, clear questioning, empathy, bringing structure to conversations and monitoring progress between sessions. Good documentation of sessions supports that last skill, because you then don't have to remember agreements and insights by heart.

Is version control only needed for large coaching practices?

No. Solo coaches also benefit from simple agreements about statuses and one central storage location, precisely because mistakes with the wrong document versions cause just as much damage with one client as with a hundred.

Recommendations