Requirements First: What a Technology Consultant Uncovers Before US Municipal Parks and Recreation Directors Commission a Custom Registration Platform

This article is part of our series on Rebuilding Twice Is the Default: How Early Consulting Prevents US Appraisal Management Company Executives From Paying for a Custom Panel Management Platform Twice

Introduction: In a Municipality, Requirements Are the Procurement

A private company that writes poor requirements can adjust during a build. A municipality usually cannot, which is why recreation software requirements carry a weight here they do not have elsewhere.

Public procurement means the requirements document becomes the solicitation, the solicitation determines who bids, the bids are evaluated against stated criteria, and the resulting contract is what the department gets. Changing it afterwards means a change order process, and sometimes it means starting again.

Which makes requirements work in this sector not preparation for a project but most of the project’s outcome, decided months before anybody writes code.

And the requirements that matter most here are the ones that look like policy rather than technology: how places are allocated, how waivers work, what accessibility means in practice.

A consultant’s contribution is largely in surfacing those before they are written down wrongly. This is the decision layer of the full custom software development guide to recreation platform development, whose public face is resident registration portals.

The Exercise to Run First

Take last year’s three most oversubscribed programs and answer four questions about each.

How were places allocated. Where is that method published. Who decided it. And what happened to the families who did not get a place.

Most departments find the answers uncomfortable. The method was whatever the current system does. It is not published anywhere a resident would find it. Nobody decided it in a meeting that produced a record. And the families who missed out received nothing.

That exercise takes an afternoon and produces the single most important of all the recreation software requirements, because once a department has consciously chosen an allocation method it can specify it, defend it and change it.

A second question is worth asking at the same time: how many families received a fee waiver last year, and would a volunteer coach printing a roster be able to tell which ones.

Neither question is technical and both change what gets built.

What Requirements Work Should Establish

The Allocation Policy

Programs categorized by whether demand exceeds capacity, with a deliberate method chosen for each and taken to the governing body if the department does not already have authority. This is policy work a consultant surfaces rather than performs, and it is the requirement everything else depends on.

Registration Day Measured

Actual concurrent load from last year’s peak morning, how the current system behaved, and what families experienced. Numbers rather than impressions, since the capacity requirement in a solicitation needs a figure.

The Accessibility Position

The current registration path assessed with assistive technology and with the jurisdiction’s accessibility coordinator, and the applicable obligations and timelines established with the attorney. This frequently surfaces work required regardless of any procurement.

The Waiver Design

How the current process works, who can see a recipient’s status, and what the department wants instead. A short conversation that changes a specification materially.

The Municipal Integration Map

What finance needs, whether residency can be verified against municipal data and who must agree, whether single sign-on exists, and what the retention schedule requires. These involve other departments whose timelines drive the project. The obligations requirements work must establish are set out in ADA Program Accessibility, Background Screening for Youth Program Staff, PCI-DSS, Public Records Retention and Refund and Cancellation Ordinances.

What the Department Receives

An allocation policy document per program category, ready to take to a board and to publish.

A measured capacity requirement from real peak data, expressible in a solicitation.

An accessibility assessment with the current gaps and the applicable obligations, including anything requiring attention regardless of procurement.

A waiver workflow specification covering the visibility rules explicitly.

A municipal integration map with the other departments identified and their requirements captured.

A product evaluation against the established recreation platforms, documented to the standard a council will expect.

A requirements specification suitable for a solicitation, written so that evaluation criteria follow from it.

A transition plan covering resident account creation ahead of a registration period, which is the operational risk. A costed comparison of at least three paths, adopting a product, adopting a product and building the municipal integration layer, and building fully, with annual operating cost stated in each. And the material a director needs for a public meeting, which is a deliverable in this sector and rarely treated as one. The budget requirements work protects is detailed in The Real Price of a Custom Parks and Recreation Registration Platform.

Reading the Recommendation

Adopt a product when the evaluation shows one covers the operation, which for most departments it does, and where proven registration-day capacity across many customers is itself a strong argument.

Adopt a product and build the integration layer when the gap is connection to municipal finance, identity or residency data rather than recreation functionality. This is a much narrower project and a common right answer.

Build fully when transaction pricing compounds substantially at large scale, when the jurisdiction’s requirements are genuinely unserved, or when the department is part of a municipal platform strategy.

Fix the policy without new software when the exercises show the problem is that allocation was never decided and waivers are handled visibly, both of which are addressed by decisions and process rather than by a build.

One consideration whichever path is chosen: the accessibility gaps and the waiver visibility findings are obligations and failures existing now, independent of any procurement, and both should be acted on this season.

A consultant who recommends a product and documents why has given a director exactly what they need for a council.

What a Consultant Should Know About This Sector

Four questions establish whether a consultant has worked with municipal departments.

Ask who decides how an oversubscribed program allocates places. The answer should be the department under its governing body, never the software. Anyone proposing a default allocation method has made a policy decision they had no standing to make.

Ask about registration morning. A consultant who has worked in this sector raises peak load unprompted and asks what last year’s numbers were. One who treats it as a normal web application has not seen a camp registration open.

Ask how fee waivers should appear on a coach’s roster. The right answer is that they should not appear at all. Anyone who has not thought about it has not considered the child in the question.

And ask about accessibility. A consultant working in the public sector will raise obligations for public entities and the recent rulemaking, and will treat it as a design constraint rather than a testing phase.

Red Flags in the Conversation

Requirements work offered free and contingent on winning the build, which in a public procurement also raises its own issues. A fixed price before peak load is measured. Accessibility scheduled as a testing phase. No product evaluation. Annual operating cost absent from the figures. Procurement timeline unaccounted for. No conversation with finance or the attorney.

And the ones that should end the conversation: a default allocation method proposed as a feature; paid priority or early access offered as a revenue option; waiver status visible on rosters or participant views; accommodation information used to screen registrations; and any suggestion that the system approve or disqualify a volunteer based on a screening result.

The strongest positive signal is a partner who asks to be present on your next registration morning.

Conclusion

Decide your allocation policy before writing requirements, since in a public procurement the requirements become the contract and this one is policy rather than configuration.

Measure last year’s registration morning so the capacity requirement is a number. Assess accessibility now, because the obligation exists regardless of procurement. And evaluate the established products properly, since a council will ask and the answer should already exist.

That is a fair standard for any set of recreation software requirements, and for the software companies in the United States on your shortlist.

If you are weighing a custom platform, answering how your three most oversubscribed programs allocate places and where that is published is the afternoon to spend before writing anything.

Frequently Asked Questions