Process documentation: a guide for federations

2026-07-18 — Eric Vanier

The digital transformation of cooperative federations raises a fundamental question: how can we ensure that a new computer tool will actually serve field teams, rather than imposing a logic that is foreign to their way of working? The answer, often overlooked, can be summed up in one word: document.

This process documentation guide for federations, based on a working document developed as part of a cooperative sharing portal, offers a simple and proven approach. We present here its key principles, adding our field perspective and advice that can be immediately applied in your organization.

The main idea is clear: a tool that does not respect the way people work will eventually be abandoned, no matter how technically good it is. Documenting first is building on a solid foundation.

Why document before automating

Too many technology projects fail because they start with the solution before understanding the reality. In the world of federations — where volunteers, managers, boards of directors and external partners coexist — processes are often carried by the memory of one or two key people. This dependence weakens the organization and complicates any evolution.

Putting current practices in writing brings three immediate benefits:

• Reveal duplicates and fragile steps, often invisible in everyday life;
• Prioritize what needs to be tooled first, rather than trying to computerize everything at once;
• Provide the technical team with an accurate picture to evaluate each integration into the portal, without reinventing anything.

An important point: it is not necessary to be exhaustive or perfect. A form filled out 80% by the person who experiences the process is infinitely better than a perfect description written by an outsider. Grey areas themselves are valuable information.

A three-step approach that is easy to follow

The guide proposes a deliberately light method, designed to be carried out at the pace of each federation, without mobilizing costly external expertise.

Step 1: List your processes

As a team, make a raw list of everything the federation does on a repeated basis: budgets, real estate reserves, inspections, training, memberships, compliance reports, etc. One line per process, without prioritizing at this stage. The goal is to put everything on the table.

Step 2: Fill out a form for each process

The standard form contains eleven questions and takes about 20 minutes per process. Each form should be given to the person who actually experiences the process, not to a manager who observes it from afar.

Step 3: Rank the top ten priorities

Using an evaluation grid, identify the ten processes that deserve to be worked on first. This ranking becomes the common roadmap for your pooling project.

The standard form: eleven structuring questions

The core of the approach is based on a standardized form that guides thinking without locking it in. Here are the eleven questions that make it up:

1. The name of the process — a short and concrete title;
2. What it is used for — the expected result, in one sentence;
3. Who triggers it, and when — schedule, event or request;
4. Who participates, and who decides — internal and external actors;
5. The current steps, in order — as they actually happen;
6. The tools used today — spreadsheets, emails, systems, paper;
7. The information needed as input — and its source;
8. What comes out of it, and for whom — deliverables and recipients;
9. The approval cycle — usual order and deadlines;
10. What is problematic today — irritants, errors, dependencies;
11. What is specific to your federation — what will become a setting in the portal.

The eleventh question is particularly strategic: it distinguishes what is universal (common to all federations) from what is specific to yours. It is this distinction that enables the sharing portal to offer a common foundation while respecting local specificities.

Our analysis: pitfalls to avoid

After supporting several federations in this type of exercise, we regularly observe the same pitfalls. Here are three to watch out for closely.

Assigning documentation to the wrong person

A form written by a manager who thinks he knows the process, but does not experience it on a daily basis, produces an idealized description — not reality. As a result, the final tool does not fit the field. Always target the person who actually performs the steps.

Wanting to document everything at once

Some federations try to map thirty or forty processes simultaneously. Energy is depleted, quality drops. It is better to complete ten solid forms than fifty poorly completed ones.

Neglecting the issue of irritants

Question 10 ("what is problematic today") is often the richest, but also the quickest to be dealt with. Take the time to devote a real moment to it: frequency of the problem, time lost, dependent people. This information determines the return on investment of any future tool.

Practical advice for federations

To maximize your chances of success, here are some recommendations based on our experience:

• Block dedicated time: 20 minutes per form, but scheduled in the calendar, not squeezed between two meetings;
• Work in pairs: the person who experiences the process describes it, another asks questions and transcribes. This avoids forgetfulness;
• Use field vocabulary, not that of consultants. If your team says "the reserve", don't write "capitalized contingency fund";
• Have a peer review it: someone who knows another similar process in another cooperative;
• Date your forms: processes evolve, so does documentation.

Key takeaways to take action

Process documentation is not an administrative formality: it is the foundation of a successful digital transformation. It protects your organization against individual dependencies, clarifies priorities, and ensures that tomorrow's tools will fit your field realities — rather than the other way around.

Remember three key things:

• An imperfect form filled out by the right person is better than a perfect form disconnected from reality;
• Eleven questions, 20 minutes, one person: that's the winning formula;
• The distinction between what is universal and what is specific to your federation is the key to a shared portal that works.

This article is based on a reference document produced as part of a cooperative sharing portal. If your federation wishes to undertake this documentation exercise, prioritize its processes or evaluate the possibilities of integration into a shared tool, do not hesitate to contact us. We support federations at every stage, from the first inventory workshop to the final roadmap.