How it works
One meeting goes through the same steps every time. The software does not let a step be skipped, and it locks earlier work once a later step is done.
The steps and who acts
| Step | Who | What is locked afterwards |
|---|---|---|
| 1. Set up the meeting Committee, members, date, venue, agenda submission date. | Controller or administrator | After attendance is recorded, the date and committee cannot change. |
| 2. Enter agenda items | Users | Items are editable until the agenda is finalised. |
| 3. Approve or reject | Manager, then controller | A decided item cannot be decided again. |
| 4. Finalise the agenda | Controller | Users and managers can no longer add, edit or delete items. |
| 5. Record attendance | Controller | Needs a finalised agenda. A chairman and at least one member present are required. |
| 6. Update the minutes | Controller | Needs attendance. Every item must be saved at least once. |
| 7. Finalise the minutes | Controller | Members, attendance and chairman cannot change. |
| 8. Generate and confirm | Controller | Confirmed minutes cannot be edited. |
Minutes reports list only meetings whose minutes are finalised or confirmed.
Installed on your server
BMMS is delivered as a web application and a set of numbered database scripts. It is installed on your own server by Gashpy Software or by your IT team, and checked with a built-in check that shows which steps are installed. Your meeting records stay in your own database.
The software runs on a Windows server with IIS and Microsoft SQL Server, and needs a mail server for notices and alerts. Write to us for the current requirements and the installation process.