Why 37 Act reporting becomes a spreadsheet fire drill
The recurring operational reasons 1937 Act retirement reporting gets rebuilt in spreadsheets — and the workflow layer that can make it repeatable.
Annual retirement reporting is high-accountability work, but the operational system behind it is often fragmented: source exports, one-off spreadsheets, reviewer notes, actuarial deliverables, audit requests, board exhibits, and file folders that only a few people understand.
For 1937 Act systems, that fragmentation is more painful because the reporting cycle is specialized and recurring. Government Code section 31453, for example, requires actuarial valuations at intervals not to exceed three years, and boards must turn actuarial and financial information into decisions and public reporting.
The repeatable product opportunity
A focused reporting workspace can transform the process from annual reconstruction to controlled cadence:
- import and normalize source files;
- validate contribution, member, and actuarial data;
- track exceptions and owner assignments;
- preserve assumptions and review history;
- generate GASB-supporting schedules and board exhibits;
- retain the audit-supporting trail for the next cycle.
The market does not need another generic dashboard. It needs a tool that understands the annual reporting job to be done.