Are these tools a substitute for legal, audit, actuarial, or finance review?

No. These tools are operational planning aids for reporting workflows. Retirement systems should continue to rely on counsel, auditors, actuaries, finance teams, and other professional advisors for formal review and opinions.

What should a retirement system gather before a 37Act workflow assessment?

Start with the source-file calendar, owner list, recurring validations, exception log, prior-year audit requests, actuarial data requests, GASB support schedules, and a sample board packet.

How do these tools connect to the 37Act product?

They preview the same operating model the platform is designed to support: fiscal-year source intake, validation, exception resolution, evidence retention, review status, and board-ready exports.

37Act Guide

Practical tools for a cleaner 37 Act reporting cycle

Practical 37 Act reporting tools for source file inventory, exception logs, audit evidence, GASB support, actuarial requests, and board packet readiness.

Audit packet checklist and board packet readiness materials for a 37 Act reporting cycle

The 37Act tool layer should help retirement-system teams think through their reporting cycle before they buy software. The tools should be practical, narrow, and evidence-aware: a source-file inventory, validation map, exception log, GASB support checklist, actuarial request packet, and board packet readiness review.

The goal is not to publish generic public pension worksheets. The goal is to create artifacts that mirror the product architecture and make the design-partner conversation easier. If a team can fill out the tool, the same structure can become a governed 37Act workspace.

Tool design principles

Start from real outputs. Every tool should connect to an actual annual reporting deliverable: actuarial package, GASB support, audit evidence, contribution reconciliation, financial statement support, or board materials.
Capture source lineage. A useful checklist should ask where the data came from, who owns it, when it was reviewed, and what evidence supports it.
Separate support from certification. 37Act can organize reporting operations and evidence, but it should not claim to certify legal compliance, actuarial opinions, audit opinions, or finance judgments.
Create product inputs. The best public tools should double as pilot intake forms for the eventual workspace.

Tool library

Start with the reporting artifacts teams already rebuild every year.

The first useful tools are not generic calculators. They are structured planning aids for the annual reporting cycle: who owns each input, what needs validation, what evidence supports each output, and what remains unresolved before board or audit review.

SRC

Source-file inventory

List payroll, contribution, member, employer, finance, actuarial, audit, and board-packet inputs by fiscal year, owner, due date, source system, and expected format.

VAL

Validation rule map

Document recurring checks for totals, missing periods, status changes, contribution mismatches, roll-forward issues, and assumptions that require human review.

EXC

Exception log template

Track open questions, assigned owners, evidence links, comments, reviewer decisions, and resolution timing so unresolved items do not disappear into email.

GASB

GASB support checklist

Map the schedules, source references, employer-support materials, reviewer signoffs, and export history needed for GASB 67 and GASB 68 support.

ACT

Actuarial request packet

Create a repeatable package for valuation extracts, assumptions, reconciliations, supporting schedules, and change notes sent to actuarial partners.

BRD

Board packet readiness review

Confirm executive summaries, exhibits, exception status, appendix files, public-facing narrative, and review approvals before materials move to board circulation.

Workflow assessment

A practical path from current-state chaos to a pilot-ready workspace.

These steps can be run as a design-partner intake before any software migration or integration commitment.

Step 1

Inventory the reporting cycle

Capture recurring outputs, source files, source systems, responsible teams, deadlines, dependencies, and known pain points.

Step 2

Mark the review gates

Identify where finance, operations, actuarial, audit, legal, executive, and board-support review happens — and where evidence is currently stored.

Step 3

Score repeatability

Separate one-off cleanups from workflows that repeat every fiscal year and deserve a controlled product surface.

Step 4

Pilot the highest-friction slice

Choose one output chain — for example contribution reconciliation to actuarial package, GASB support, audit evidence, or board packet production — and build the first 37Act workspace around it.

Tool posture

Useful planning tools should increase clarity without implying certification.

37Act can be specific and helpful while preserving the professional-review boundary that public retirement reporting requires.

Current state

Avoid

!Compliance guarantee calculators
!One-click audit approval language
!Legal or actuarial advice disguised as automation
!Generic spreadsheet downloads with no source lineage

With 37Act

Build instead

✓Operational checklists tied to source files and owners
✓Exception and evidence templates that preserve review context
✓Readiness scores that identify open work, not compliance status
✓Pilot intake tools that translate directly into product modules

Turn your current reporting cycle into a pilot map.

Bring one annual reporting output and the files, owners, validations, exceptions, evidence, and approval steps behind it. 37Act will map the workflow before proposing a software pilot.

Request a workflow assessment