What is the best first implementation scope?

A focused pilot around one fiscal-year reporting cycle, a defined set of source files, and a few high-value outputs such as actuarial data packages, GASB support, audit evidence, or board packet materials.

How should a retirement system prepare?

Prepare a source inventory, current reporting calendar, sample files, recurring exception examples, reviewer list, and final packet or schedule outputs.

37Act Guide

A low-risk implementation path for a high-stakes reporting cycle

A practical implementation path for 37 Act reporting software: workflow assessment, source map, pilot workspace, validation, exports, and annual platform rollout.

Public-sector reporting team planning an annual reporting implementation

A 37Act implementation should feel safer than a major government software replacement. The product promise is not “rip out your existing systems.” The promise is “make the annual reporting cycle visible, governed, repeatable, and easier to defend.”

Recommended first scope

The best first scope is a narrow, high-trust reporting workflow such as:

actuarial valuation data preparation,
contribution and payroll reconciliation,
GASB 67/68 support schedules,
audit evidence binder creation,
board packet exhibit production, or
a full fiscal-year reporting workspace for a small set of recurring outputs.

The implementation page should help administrators understand that 37Act can begin with their actual files and workflow before asking them to commit to deeper system integration.

Pilot roadmap

Move from workflow assessment to repeatable reporting operations.

The site should make the next step feel concrete and safe for a public-sector administrator.

Week 1

Workflow assessment

Map reporting calendar, source systems, owner matrix, current pain points, recurring exceptions, and final outputs.

Weeks 2–3

Source model

Define fiscal-year entities, expected files, validation checks, reviewer states, evidence fields, and output requirements.

Weeks 4–6

Pilot workspace

Configure intake, exception queue, evidence binder, actuarial/GASB support views, and board packet draft materials.

Then

Operational rollout

Train reviewers, refine validation rules, document governance, and prepare the next annual reporting cycle.

Implementation deliverables

What a design-partner pilot can produce.

The deliverables should sound tangible even before a full enterprise rollout.

MAP

Reporting source map

A documented map of systems, files, owners, due dates, reviewer roles, and downstream reports.

RULE

Validation rule catalog

A first set of completeness, contribution, fiscal-year, reconciliation, and exception rules tailored to the system.

QUEUE

Exception workflow

A practical review queue for unresolved items, owner assignment, notes, evidence, and final disposition.

PACK

Output prototypes

Prototype exports for actuarial requests, GASB support, audit evidence, and board packet exhibits.

GOV

Governance notes

Role definitions, approval states, file retention practices, and review cadence for annual reporting.

Expansion roadmap

A prioritized integration and automation roadmap based on the pilot’s highest-value bottlenecks.

Start with one reporting cycle, not a multi-year software migration.

Bring sample source files, outputs, and pain points. We will map the annual cycle and propose a pilot workspace around the most expensive reporting bottlenecks.

Book implementation call