Custom Project Forms in Work Allocation

Every law firm runs its summer program a little differently, and a one-size-fits-all project form was getting in the way. Flo is the fastest shipping company in the legal talent industry, and this release is a good example of why: we heard a clear, consistent problem from recruiting teams managing summer programs, and we shipped a real fix for it.

The problem

Before this release, the project form inside the Work Allocation tool was locked. Every field was there whether you needed it or not, and there was no way to add context for the people filling it out. For firms with different workflows, different data requirements, or different levels of summer associate involvement in the process, that rigidity was a real barrier. Some firms that wanted to adopt the tool were holding back specifically because of this.

Admins couldn't hide fields that weren't relevant to them, couldn't mark which fields were truly required, and had no way to leave instructions for attorneys or associates completing the form. The tool asked for compliance with a structure that wasn't theirs.

What we shipped

Admins now have full control over the project form through a new step in the program creation flow, called Project Settings. From there, you can:

• Add instructions to the form so that anyone completing it knows exactly what you need and why.
• Choose which fields appear on the form by toggling them on or off. Project name is always required and stays put, and the attorney assignment field is always present (though you can decide whether it is required or optional). Everything else is configurable.
• Mark fields as required or optional so the form enforces the data that actually matters to your program.
• Add a Comments field for free-form details that don't fit anywhere else, with the option to keep it visible only to admins and attorneys or to expose it to summer associates as well.

Whatever you configure carries through consistently. The fields you include (or exclude) are reflected on the project form itself, the project details page, the project table, and the summer associate portal. If you hide the Comments field from summer associates, they won't see it anywhere in their view.

Why it matters

This change means the Work Allocation tool can actually reflect the way your program operates, not the other way around. Admins no longer have to ask people to ignore fields that don't apply. Summer associates see a clean, focused form with only what's relevant to them. Instructions built into the form reduce back-and-forth and set expectations before anyone has to ask a question.

For firms that had been evaluating the tool but hadn't made the move because the form wasn't flexible enough, that barrier is gone. You can now configure the project form to match your program before your first cohort arrives.

This one came directly from what recruiting teams were telling us, and it made a meaningful difference to what the tool can do. If there are other places in the program workflow where the structure is getting in your way, keep telling us. The more specific you are about what's slowing you down, the faster we can fix it.

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.