Employer Matches Table: Schedule-Ordered View and Interview Location Column

When you're running a live recruiting event, every extra click to find basic information is friction you don't need. Flo has always believed that, and as the fastest shipping company in the legal talent industry, we act on it fast. This update to the Employer Matches table is a direct result of what our clients told us wasn't working.

The problem

Employers and recruiting teams managing interview days kept running into the same wall: the Matches table didn't reflect the actual order of the day. Interviews weren't sorted by time, so coordinators had to mentally reconstruct the schedule themselves or cross-reference a separate table to find interviewer contact information and room locations. For in-person and hybrid events especially, that was a real operational headache.

We kept hearing that the table showed the right data but in the wrong shape. The location of each interview, critical for in-person days, was nowhere to be found in the table, meaning another trip somewhere else in the product to piece things together.

What we shipped

The Employer Matches table now defaults to schedule order, sorted by interview date and time. A new Interview Location column sits right at the front of the table, next to the interview schedule and before the interviewer contact, so the most operationally relevant information is visible first.

• Interview Schedule is now the first column, sorted by date and time by default.
• Interview Location is a new column, immediately following the schedule column.
• Interviewer Contact follows, keeping the full picture together in one view.

All of these changes carry through to column management, CSV export, and keyword search, so however your team works with this data, the improvements follow.

Why it matters

For anyone running an in-person, virtual, or hybrid interview day, this is the difference between a table you can actually work from and one you have to work around. Coordinators can now see who is interviewing, when, and where, all in one place, in the order things actually happen. The CSV export reflects the same structure, which means the file you pull for day-of logistics is already organized the way you need it. No post-export reformatting required.

This one came directly from what you told us about running live events. If there's something else in the table, or anywhere else in the product, that still makes your day harder than it should be, keep telling us. That's exactly how this gets built.

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.