Software

Organization platform: membership, sessions, learning and dues

A membership and operations back office: rosters, scheduled sessions, learning records and dues. Built for an organization that already ran these jobs on paper and chat groups.

Meeting room used in a membership and organization operations platform

Background

Rosters, session notes, learning attendance and dues sat in different notebooks and group chats. Month-end meant copying names between files. Nobody had one place to see who still owed a payment or who missed a session.

What we shipped

Admin for membership, scheduled sessions, learning records and dues — with tasks instead of informal reminders.

What was breaking

  • Member lists and payment lists did not share an ID.
  • Session write-back waited until someone had time to type notes.
  • Learning and dues reminders lived in chat, then disappeared.
  • Headquarters could not see branch activity without asking for a spreadsheet.

Approach

We put people, units, sessions and dues on one membership record. Operators schedule sessions, record attendance and learning, and collect dues against the same roster. We do not publish participation rates we did not measure.

Modules

  • Membership roster and org units
  • Session calendar and attendance
  • Learning records
  • Dues ledger and reminders
  • Operator console with roles

If membership, sessions and dues still live in chat, start from custom software at /en/software/.

See the service Discuss a similar project