Board portals vs. pension administration software
A retirement system searching for board software gets three unrelated categories back in the same results: the administration suite that runs the plan, the portal that runs the meeting, and the record of what the board decided. They solve different problems and rarely substitute for each other. This page separates them so you can work out which one you are actually short of.
Pension administration software runs the plan
This is the largest system a public retirement system buys, and usually the one procurement knows by name. It holds member records, contributions, service credit, and benefit calculations, and it feeds the portals members and employers sign in to.
The vendor pages read that way. Sagitec describes Neospin in terms of automated workflow, dashboards over member and employer data, reporting, and self-service portals. Tegrit describes Arrivos as modular components covering imaging, employer and member portals, reporting dashboards, and automated workflows. Board meetings, motions, and votes are not part of what either of those pages describes, which is appropriate: administering benefits and governing the system are separate jobs done by separate people.
If your gap is benefit calculation, member self-service, or employer reporting, this is the category you need, and nothing on this page substitutes for it.
Board portals run the meeting
The second category assembles and distributes the meeting: board books, agendas, document libraries, and minutes. Most portals now include some form of voting or polling, and several draft minutes from a transcript.
This is a document and meeting layer. It answers what was circulated and what was written down. Two of these products are covered in detail elsewhere on this site, with the sources linked: OnBoard and Boardable.
The decision record is a third thing
An auditor asks a retirement board how a specific action was approved, who was eligible to approve it, whether the record has changed since, and what follow-up work it created. That is a register, and it behaves differently from a document library.
SteadyState is that register. Each decision carries a category and an owner. Each eligible trustee's approval is recorded against it. A plugin that runs before the database transaction opens refuses every update and delete on an approved record, so a refused edit never reaches the database. The refusal is the same whatever tool makes the attempt, including administrator tools and spreadsheet connections. A later change is a new decision, voted like the original, and the original stays in the register marked superseded. Follow-up actions carry owners and due dates, and overdue items surface on the home dashboard.
It installs into the system's own Microsoft 365 tenant and stores records in your own Dataverse, so retention, backup, and access policies you already run apply to them.
Which category does which job
The administration column reflects the vendor pages linked above, read on July 25, 2026. The board portal column reflects the two products we examined in detail, OnBoard and Boardable, where each claim carries its source. Portals vary, so treat that column as a starting point for questions rather than a statement about every product in the category.
| Job | Pension administration suite | Board portal | SteadyState |
|---|---|---|---|
| Member records, service credit, benefit calculation | The core of the category | No | No |
| Agendas, board books, and minutes | No | Yes – including minutes drafted from a transcript in the products we checked | Minutes are a field on the meeting record; no packets in v1 |
| Recording who approved a board action | No | Commonly, through voting or polling | Each eligible trustee's approval is recorded against the decision |
| Preventing a change to an approved action | Not applicable to the category | Not something we found described on the pages we checked | The database refuses every update and delete on an approved record, whatever tool attempts it |
| Change by amendment that supersedes | Not applicable to the category | Not something we found described on the pages we checked | The amendment is voted like the original, which stays in the register marked superseded |
| Where the records sit | Set by your contract and deployment; ask the vendor | Typically the vendor's platform; ask each vendor | Your own Microsoft 365 tenant, in your own Dataverse |
Member records, service credit, benefit calculation
- Pension administration suite
- The core of the category
- Board portal
- No
- SteadyState
- No
Agendas, board books, and minutes
- Pension administration suite
- No
- Board portal
- Yes – including minutes drafted from a transcript in the products we checked
- SteadyState
- Minutes are a field on the meeting record; no packets in v1
Recording who approved a board action
- Pension administration suite
- No
- Board portal
- Commonly, through voting or polling
- SteadyState
- Each eligible trustee's approval is recorded against the decision
Preventing a change to an approved action
- Pension administration suite
- Not applicable to the category
- Board portal
- Not something we found described on the pages we checked
- SteadyState
- The database refuses every update and delete on an approved record, whatever tool attempts it
Change by amendment that supersedes
- Pension administration suite
- Not applicable to the category
- Board portal
- Not something we found described on the pages we checked
- SteadyState
- The amendment is voted like the original, which stays in the register marked superseded
Where the records sit
- Pension administration suite
- Set by your contract and deployment; ask the vendor
- Board portal
- Typically the vendor's platform; ask each vendor
- SteadyState
- Your own Microsoft 365 tenant, in your own Dataverse
Working out which one you are short of
Most systems already have an administration suite and are not replacing it. The live question is usually the board layer, and there the useful test is what happens when someone asks about an action from four years ago.
- If the answer is a search through email and a staff member's memory, you are short of a decision record.
- If the answer is a PDF of minutes that someone could have edited afterward, you have a document layer without a record layer.
- If the answer is a locked record showing which trustees approved it and what superseded it since, you already have what SteadyState provides.
- If the question is about a member's benefit rather than a board action, that is the administration suite, and neither a portal nor SteadyState answers it.
The vertical page for this audience is SteadyState for pension boards, which covers board structure, committee workspaces, seat counts, and the audit findings that tend to drive this purchase.
See it before you decide
The interactive demo runs the full lifecycle, including the moment the database refuses an edit to an approved record. It takes a few minutes and does not require an install.
- Try the demo at /explore
- Or contact us and we will walk your board through it
Questions boards ask
- Does SteadyState replace our pension administration system?
- No, and it does not overlap with one. Member records, service credit, contributions, and benefit calculations stay where they are. SteadyState records what the board decides.
- Can SteadyState calculate a benefit or produce a member statement?
- No. It has no member data model and no calculation engine. If a disability determination comes to the board, SteadyState records the board's action on it, by case number, without the medical detail.
- We already have a board portal. Do we need this as well?
- Only if the approval record itself is the gap. Keep the portal for board books and minutes, and ask two questions about your current setup: can an approved action still be edited, and can you show who was eligible to approve it. If both answers are comfortable, you may not need a third system.
- How does voting work in SteadyState?
- Each committee sets its own policy: unanimous consent, majority of votes cast, or two-thirds. Members approve, reject, abstain, or recuse on the decision, and the Chair or Secretary can record an absence against their name. When the vote closes the tally is stamped on the locked record – "Carried 6–3 · 2 abstentions · 1 recusal · 1 absent · 13 eligible (majority of votes cast)." A rejection requires a written reason.
- Does SteadyState publish agendas or minutes to the public?
- Not in v1. There is no public transparency portal. Systems with a public posting obligation keep whatever they use for that job today.
- Where do the records live?
- In your retirement system's own Microsoft 365 environment, in your own Microsoft database. SteadyState operates no service that holds them, so your existing security, backup, and retention policies apply.
- Our city clerk already posts our agendas. Is that not the same thing?
- Posting an agenda establishes that a meeting happened and what was on it. It does not establish who approved an action, whether the approval record has changed since, or what follow-up work it created. Those are the gaps a decision register fills.
SteadyState Technologies LLC is not affiliated with, endorsed by, or sponsored by Sagitec, Tegrit, or Microsoft Corporation. Neospin, Arrivos, and Microsoft 365 are trademarks of their respective owners, and both companies are named here as examples of a software category rather than as competitors. Every claim about their products was read from the linked page on July 25, 2026.