The contact list is in a spreadsheet. The latest briefing is in a shared drive. The meeting notes are attached to an email. The decision is in someone’s notebook. Each location may make sense on its own. Together, they leave the secretariat doing the work of connecting the pieces.
Before adding another tool, agree where each type of information belongs, who maintains it and how people find it.
Notice the questions that keep coming back
Fragmentation becomes visible in ordinary requests: “Is this the latest version?”, “Who has the list?” or “Did the working group approve this?” A small secretariat can answer these questions quickly, which makes the underlying problem easy to overlook.
But each answer relies on someone knowing where to look. That becomes harder when a policy officer is away, a new colleague joins or several consultations land at once. Staff become the search function for a collection of disconnected records.
For an association working across Brussels and national capitals, the information may also travel between member companies, national federations and several committees. A familiar folder to one group can be invisible to another.
Map one workflow before reorganising everything
Take a recent working group meeting and follow the information from preparation to follow-up. Record where the agenda, papers, attendance list, comments, decisions and actions were kept.
Look for moments when people copied information, recreated something that already existed or asked a colleague to confirm its status. These are useful places to start because they reveal an actual coordination problem rather than a theoretical preference for tidiness.
- Which record is authoritative at each stage?
- Who is responsible for keeping it current?
- Who needs access, and at what point?
- What should happen when the information changes?
Give each kind of record a clear home
You do not need every activity inside the same application. You do need a shared understanding of where to go. Member-facing documents may belong in a member portal; stakeholder relationships may belong in a dedicated relationship tool; finance may remain in an accounting system.
Write a short information map. For each category, name the location, the responsible person and the publishing rule. Keep it short enough to use during onboarding.
For example: approved policy briefings live in the member library; working drafts stay with the policy team; the briefing includes a link to related meeting records. That distinction can prevent a useful draft from being mistaken for an agreed position.
Reduce duplication at the point of sharing
Once a reliable home exists, share links where appropriate. Avoid maintaining several live copies of the same member-facing document. When a separate copy is necessary, make its date and status explicit.
Archive superseded material in a way that preserves context without confusing readers. Review permissions as part of the workflow, particularly when a document moves from a restricted group to the wider membership.
Start with one policy area and review how it works after the next meeting cycle. The aim is not a perfect folder structure. It is fewer occasions when the team must reconstruct what is true, current and available.
ONE PRACTICAL STEP
Start here this week.
Draw the path of one working group’s information from agenda to follow-up. Mark every place where the same document is copied. Agree one authoritative home for the final outputs.
PUTTING IT INTO PRACTICE
Members Cloud can provide the member-facing home for documents, updates and discussions. The starting point is deciding which information your members should find there.