Pension operations, with the working shown
13 flows for the work a fund’s operations team does every day: member questions, retirement applications, contributions that arrive late or short, and the reports the board reads. Every figure comes from your own systems and is quoted exactly, and anything that reaches a member waits for a person.
Your administration system, read-onlyYour plan documentsEvery run recorded with its steps, time and model costA person approves what reaches a member
The work, template by template
Open them in the catalogueEach opens in the builder as a working flow. Point it at your plan documents and your administration system, and press Test.
Member 360
Type a member number and get status, employer, contribution history and total, read from your administration database.
Support5 stepsMember service copilot
Drafts a plain-language reply to a member’s question from your plan documents, naming the section it relies on.
SupportReal run7 stepsPlan document assistant
Staff ask the plan documents, policies and FAQs a question and get an answer quoting the section it relies on.
SupportReal run4 stepsRetirement application review
Checks a retirement application against your plan rules, lists what’s missing, and drafts the reply for approval.
OperationsReal run6 stepsEnrolment completeness check
Pulls the required details from each new enrollment and stops any without a signed election for your team to chase.
OperationsReal run5 stepsAssistance application triage
Sorts each hardship application as urgent, routine or incomplete and writes it up against your criteria, never recommending an amount.
Operations10 stepsMember data quality
Finds members with no date of birth, no beneficiary or a shared identifier, and counts them by issue each week.
OperationsReal run5 stepsContribution monitoring
Every weekday at 07:00, lists employers whose contributions are late, short or missing, with shortfalls computed in the database.
Finance5 stepsPayment reconciliation
Name a period and get the employers whose payments don’t match what was due, each difference computed in the database.
Finance5 stepsInvestment performance report
On the 3rd of each month, sets each fund against its benchmark and target and names every shortfall.
FinanceReal run5 stepsExecutive briefing
Every Monday at 07:30, posts leadership a cited note: where the fund stands, what changed, what needs deciding.
Operations6 stepsMember communication drafter
Drafts a letter, email or notice to members or employers from your plan documents and holds it for approval.
Marketing6 stepsEmployer relationship brief
Name an employer and get its members, contribution record, open cases, last contact and the next step to take.
Sales4 steps
Contributions, checked before anybody asks
See the templateEvery weekday at 07:00, it reads what each employer owed against what arrived, totals the shortfall in a table step rather than in a model, and writes up the exceptions — quoting the figures, never recalculating them.
What a fund’s risk committee will ask
Answered from how the product works, not from a slide. The full list of controls is on the security page.
- Every figure comes from your systems
- A query against your own ledger or administration system, totalled by a table step in code. The model explains the result and is told never to state a number the table does not hold.
- Nothing reaches a member unapproved
- Replies to retirement applications and member communications stop at an approval step, which says what approving will do before anyone decides.
- Only the records the reader may see
- Answers are built from sources the person asking is allowed to read, and database steps use a read-only connection you set up and can revoke.
- Every run on the record
- Its input, each step’s output, how long it took, what the model cost and who decided — kept with the run, and in the audit log.
Asked in every evaluation
- Does it replace our pension administration system?
- No. It reads from your administration system through a read-only connection, and that system stays the system of record.
- Will it calculate a member’s benefit?
- No. The templates are written never to state a benefit amount, a payment date or an entitlement the sources do not give. Where a figure is needed, it quotes the one your systems already hold.
- Our database is not laid out like the template.
- The database steps carry example queries, and you point them at your own tables. The checks, the approvals and the write-up stay as they are.
- Can we see it on our own plan documents?
- Yes. We open a template in the builder, connect it to a sample of your documents and data, and run it with you.
Start with the queue that costs your team the most time
Bring one process — member questions, retirement applications or contribution exceptions — and we run the nearest template against your own material.