Delete Feedback and Feedback Requests on Projects in Work Allocation

Keeping feedback records clean matters just as much as collecting feedback in the first place. This week, we shipped a new Work Allocation control for summer program projects: admins can now delete feedback and feedback requests tied to a project.

The problem

When feedback is collected through Work Allocation summer program projects, attorneys may sometimes be included in a feedback request even if they were only loosely connected to the project.

Maybe staffing changed mid-project. Maybe someone had a brief administrative touch but never meaningfully worked with the summer associate. Either way, that attorney could receive a feedback request, and if they submitted a response, that feedback would live in the project record alongside feedback from people who actually supervised the work.

Until now, there was no clean way to fix that. Once a feedback request was sent, it stayed live. Once feedback was submitted, it stayed on the project record. That left Talent, Professional Development, and HR teams with manual workarounds when they already knew a request or response did not belong.

What we shipped

Admins can now delete feedback and feedback requests directly from Work Allocation summer program projects.

• Delete a feedback entry: If an attorney submitted feedback that is not relevant to the project, an admin can remove it from the project record entirely.
• Delete a feedback request: If an attorney has not yet submitted feedback, an admin can delete the open request. This immediately invalidates the feedback link that was sent when the project was completed, so the attorney can no longer submit a response through that link.

Both actions are admin-only and take effect immediately. No confirmation emails are sent to the attorney when a request is invalidated.

Why it matters

Work Allocation feedback is most valuable when it reflects the people who actually worked with a summer associate. When unrelated feedback sits in the same project record as feedback from real supervisors, it can muddy evaluations, complicate review conversations, and make the record harder to trust.

Deleting an open request is just as important. Without that control, a feedback link could stay live even after a team realized the attorney should not have been asked to provide feedback. That attorney could submit a response weeks or months later, after the review cycle had moved on, and the feedback would still land in the project record.

These controls give Talent, Professional Development, and HR teams a cleaner way to manage Work Allocation feedback and keep summer program project records accurate.

This update came directly from what teams told us about how summer program feedback works in practice. Staffing changes, project roles shift, and people sometimes get added to projects even when they do not end up working closely with the summer associate. Work Allocation should give teams flexibility to correct the record when that happens.

Keep telling us where your team is running into cleanup work. Those details help shape what we build next.

Want a closer look at how Flo supports Work Allocation feedback and summer program management? You can book a demo and we will walk through it with you.