Surveys for ABA Reporting Are Now in Flo (Phase 1)

ABA reporting has long lived outside the tools law school career services teams use every day. That gap is closing. Flo is the fastest shipping company in the legal talent industry, and this release marks the first concrete step toward full ABA reporting support built directly into the platform, no workarounds required.

The problem

Every year, law school administrators go through the same painful cycle: collecting employment outcomes data from graduates, reconciling responses across spreadsheets and third-party forms, and trying to get it all into a format that satisfies ABA reporting requirements. None of that work happened inside the tools admins were already using to manage recruiting and career services.

The ask we kept hearing was straightforward: bring this into Flo so we are not jumping between systems to pull together data that should all live in one place. That is what we are building toward.

What we shipped

University admins now have access to a new Surveys tab under the Reporting section in the left navigation. This is Phase 1, focused on giving admins early visibility and the ability to set things up ahead of full student-facing functionality.

With this release, admins can:

• Create a survey by adding a title, a description, and selecting a form type. The ABA Employment Outcomes form is the first type available.
• Set a survey schedule by defining an open date and a close date. A close date is required. If no open date is set, the survey opens immediately.
• View all created surveys in a single list from the Surveys tab.
• Preview the survey exactly as students will eventually see it, so admins can get comfortable with the experience before it goes live.

The ABA Employment Outcomes form includes conditional logic that adapts based on each student's situation. Students who indicate they are employed see a tailored set of employment-related questions. Students who indicate they are unemployed see a different set. Personal details and demographics sections are consistent for all respondents, and a final review and submission step closes out the form.

Why it matters

This release is designed to put admins ahead of the curve. Because the Class of 2026 reporting cycle is already underway, this phase is about preparation: giving teams time to explore the survey, understand what students will see, and share feedback before full functionality rolls out in time for the Class of 2027.

Having the survey infrastructure inside Flo means that when student-facing functionality ships, admins will already know the tool. There is no scramble, no last-minute learning curve. The groundwork is laid now. It also means the feedback loop starts earlier. Anything that feels off, any question about how the form maps to ABA requirements, any friction in the setup flow, all of that can be surfaced now, while there is still time to act on it before it matters most.

This is the first piece of something bigger, and it gets better the more you push back on it. If something about the survey setup, the form structure, or the scheduling logic does not match how your team actually works, tell us now. That is exactly the kind of input that shapes what ships next.

If you're a Flo client and want to dig in, or you're new to Flo and curious how it works, book a demo and we'll walk you through it.