Who keeps track of it all when everyone is a volunteer?
A group agrees on something one evening, and six weeks later nobody can say who took it on. ProcesOS holds the decisions, the tasks and the shared fund in one workspace your group runs itself.

Your first steps
How does a group decide together when no single person holds every thread? Here is the path a neighbourhood group takes, from its first members to a working group it founds by vote.
-
Found the group
Found your group's workspace as a community. Its capability tree shows the community wheel.
-
Open the door
Switch on a public profile. Neighbours find the group and ask to join, and you approve each one.
-
Name a circle
Name the small circle that decides for the group and give it its seats.
-
Talk it through
Start a thread in the forum and let neighbours reply.
-
Put it to the circle
Add a poll for the circle with a working group as its outcome. Only the circle votes, and the others in the thread are told.
-
The working group exists
Once the circle approves, you found the working group as a team under your group. You invite the people who will work in it.
Four questions a community asks before it organises
- Who keeps track when everyone volunteers?
- Each task runs as a quest with a name against it, and a second person confirms when it is done.
- Who may vote on what, and who counts?
- A poll names its voters: all members, the holders of a role or a seat, or the holders of a credential your group or its network issues.
- Where is the money, and who can see it?
- The group declares its own fund, and every member sees the balance and each movement.
- How do you see what each member can actually do?
- Each member's skill profile grows from the work they finished, written in the European skills taxonomy.
Decisions that stay findable
A thread sits next to the process it is about. Half a year later the reason for a decision is still there, with the people who made it.
See how decisions are recordedWork someone can pick up
Post a task a member can pick up. When the work is checked in a validation session, the bounty on it is held until the session accepts it, so neither side has to trust the other first.
Not built yet Bounties on tasks confirmed by a photo or a signature, released after the confirmation.
See how a bounty is paid outLearning that happened elsewhere
A member's profile already carries the credentials your workspace issued and the courses finished in the Academy.
Not built yet Course records brought in from Andamio, a learning platform many community programmes already use, so a member keeps one profile instead of three.
Open the AcademyWho can take on what
Every member has a skill profile written in the European skills taxonomy. It grows from the work they did, and nobody fills in a form for it.
See how skills are recordedA shared fund everyone can see
Your group declares its own community fund. Members see the balance and every movement, and nobody has to hold the money on your behalf.
Start a workspace and open oneA village template to start from
One workspace with fourteen processes already drawn. Aquaponics is among them, the practice of raising fish and plants together in one water cycle.
Browse the templatesTwo groups, told step by step
A neighbourhood group
Neighbours want to share what they have and decide things together.
- They create a community workspace in the workspace wizard.
- Their capability tree opens on the community wheel, with areas from energy to coordination.
- Neighbours ask to join through the public profile, and the owner approves each request.
- A poll in the forum asks all members whether to found a repair team.
- Once the poll passes, one press founds the team inside the community.
Result: The group decides in the open, and the team it decided on exists the same day.
A repair café
Volunteers fix things every Saturday, and nobody remembers who fixed what.
- The café posts each repair as a task and says what counts as done.
- A volunteer takes the task on.
- They submit a photo of the result as evidence.
- A second organiser confirms the result, and the one who submitted it can never confirm it.
- Not built yet A small bounty on a task confirmed by a photo, held when the task is posted and paid out after the confirmation.
Result: Every repair has a name, a photo and a confirmation behind it.
Start your group's workspace
The forum, the quests and the shared fund are there today. Federation between groups is next.