With multi-attribution enabled, every person who clicks Submit Scorecard gets permanently credited as a contributor even if someone else submitted before or after them.
Here's exactly how that works.
How each submission works
When a user opens the scorecard, they see the current collective state: the most recent version of all fields (notes, ratings, questions, decision). They can edit any part of it and click Submit Scorecard.
On submission, Recruiterflow does three things:
Adds the submitter's name to the attribution list (if they're not already on it).
Stores a full snapshot of the scorecard in version history capturing exactly what it looked like at that moment.
Updates the "last submitted" timestamp.
The scorecard then displays all contributors' names alphabetically: "Bharath Prakash, Manan, and Rohit (Last Submitted On 30 Mar 2026)"
Where contributor names appear
Candidate profile → Scorecards tab: All names listed alphabetically next to the interview stage, with the last submission date in parentheses.
Scorecard submission page header: "Submitted by Bharath Prakash, Manan, and Rohit | Last Submitted On 30 Mar 2026"
PDF export: "Submitted by Bharath Prakash, Manan, and Rohit" in the header.
Reports: Each attributed user gets their own row/count in Recruiting Activity Report and Advanced Reports.
Client Portal: Client-side contacts see all contributors listed (but not the version history).
What happens when the same person submits again
If a user who already submitted edits the scorecard and clicks Submit again, they are not duplicated in the attribution list. Their name stays listed once. However, a new version snapshot is stored in history so you can see what changed between their first and second submission.
Example: Three interviewers on one scorecard
Manan submits first with a "Strong Yes" decision. Rohit opens the scorecard next, updates the Python rating from 3 to 5 stars, and submits with a "Yes." Bharath opens it last, adds a note, and submits "Strong Yes" as the final call.
The Scorecards tab now shows: "Bharath Prakash, Manan, and Rohit (Last Submitted On 30 Mar 2026)" - all three credited, alphabetically, with the date of Bharath's submission as the "last submitted" marker.
Anyone on the internal team can click the history icon to see Manan's original submission, Rohit's updated version, and Bharath's final version, each as a separate snapshot.
Things to know
Autosave does not add a name to attribution or create a version snapshot. Only clicking Submit Scorecard does.
A client-side contact (via Client Portal) who submits a scorecard for a shared stage is also added to the attribution list.
External Recruiters cannot view or submit scorecards. They are not applicable to this feature.
Submitting without making any changes still counts as a submission. The submitter's name is added to the list and a snapshot is stored.
Names are always displayed alphabetically (A–Z), regardless of submission order.
Each submission triggers a separate notification and a separate activity feed entry (the same as current behavior).