Aller au contenu

Registre des rôles

Télécharger ce modèle

Généré le 2026-08-31 · Télécharger tous les modèles

Vue d'ensemble

Which ongoing jobs have a name and a person, rather than being everybody's and nobody's?

Clauses RCOS 7.1.1, 7.1.2, 7.1.4, 7.7.1
  • 7.1.1 Toutes les responsabilités continues DOIVENT être assignées à des rôles explicites et nommés plutôt qu'à des attentes implicites ou des accords informels.
  • 7.1.2 La communauté DOIT maintenir un Registre des rôles qui inclut, au minimum :
  • 7.1.4 Aucune responsabilité continue NE PEUT exister sans un rôle explicite, et aucune personne NE PEUT être tenue responsable de responsabilités qui ne sont pas formellement assignées à un rôle.
  • 7.7.1 Les responsabilités continues NE DOIVENT PAS exister sans un rôle explicite.
Pourquoi exiger qu'un rôle nommé existe pour chaque responsabilité ?
Comment remplir ce document

Ce qu’il faut couvrir

  • Which ongoing responsibilities do we have today, and does each belong to a named role — or is some of it still done by whoever happens to notice?
  • What makes a role operational (it may act for the community within set limits) rather than functional (it does work but carries no special say)?
  • What does ‘in good standing’ mean for anyone who wants to take on a role?
  • What must every role entry contain — purpose, scope and authority, boundaries with other roles, who is eligible, term, and how holders are appointed, reviewed and removed?
  • How do we make sure nobody is held responsible for work that was never assigned to their role?
  • How often do we check the registry against the work actually being done, and who does it?

Exemples

Every ongoing task belongs to a role in this registry; if it is not listed, nobody can be held to it, and whoever notices proposes a role for it. Operational roles may act for the community within limits set in the Decision Matrix; functional roles do work but carry no extra say. A member is in good standing if they are up to date on agreed contributions and not suspended. Each entry lists purpose, scope and authority, boundaries, eligibility, term, and appointment, review and removal. Stewards check the registry every six months.

Des exemples, pas des recommandations. Vos réponses vous appartiendront.

Tableau récapitulatif

Rôles opérationnels

For each role that keeps things running, what is it answerable for and who reviews that?

Clauses RCOS 7.1.2, 7.1.3
  • 7.1.2 La communauté DOIT maintenir un Registre des rôles qui inclut, au minimum :
  • 7.1.3 Chaque rôle DOIT inclure un mécanisme de redevabilité explicite définissant :
Pourquoi définir la redevabilité pour l'autorité déléguée ?
Comment remplir ce document

Ce qu’il faut couvrir

  • Which operational roles do we need, and for each: what is it for and what is it responsible for?
  • For each role: which decisions may it take without a community vote, and where are its limits (for example, a spending cap)?
  • For each role: who is eligible, how long is the term, and how is the holder chosen?
  • For each role: how, how often and by whom is the holder's work reviewed?
  • For each role: what happens if the work is not getting done or the holder is overloaded — and how can the role be reassigned?
  • For each role: what must be handed over before the holder leaves it?

Exemples

Finance Steward: keeps the accounts, pays agreed bills and reports the balance monthly. May approve spending up to €500 per item within the budget; anything more needs a proposal. Any Full Member in good standing may stand for a two-year term, chosen by Strategic vote. The Operations meeting reviews the role every six months, and any member can raise a concern. If the holder is overloaded, the deputy takes over payments; persistent failure leads to reassignment by Strategic vote. Before leaving, the holder hands over bank access, open invoices and the reporting checklist.

Des exemples, pas des recommandations. Vos réponses vous appartiendront.

Rôles fonctionnels

Which roles exist for a function rather than for daily work, and what are they for?

Clauses RCOS 7.1.1, 7.1.2
  • 7.1.1 Toutes les responsabilités continues DOIVENT être assignées à des rôles explicites et nommés plutôt qu'à des attentes implicites ou des accords informels.
  • 7.1.2 La communauté DOIT maintenir un Registre des rôles qui inclut, au minimum :
Pourquoi séparer les rôles fonctionnels des rôles opérationnels ?
Comment remplir ce document

Ce qu’il faut couvrir

  • Which functional roles do we have — for example facilitator, note-taker or welcomer — and what is each for?
  • For each role: what does it do, and which other roles does it work with?
  • For each role: who may take it on, and is saying ‘I'll do it’ enough?
  • For each role: what does it not include — which decisions can it not make on the community's behalf?
  • For each role: how does someone step down, and what must they brief the next person on?

Exemples

Facilitator: prepares and runs meetings so everyone is heard and the agenda finishes on time. Any Full Member may take it on by announcing it in the members' channel; no vote is needed, and it carries no extra say in decisions. A facilitator who is a party to a conflict on the agenda steps aside for that item. They may step down at any time after briefing the next facilitator on upcoming meetings and open actions.

Des exemples, pas des recommandations. Vos réponses vous appartiendront.

Registre de ratification

Nous aimerions compter les visites avec Google Analytics. Les cookies ne sont déposés que si vous acceptez ; refuser ne change rien d'autre sur le site. Politique de confidentialité