Skip to main content

Recommender Name Mismatch or Binding Issue on Common App

What to do when a recommender's name shows incorrectly on Common App and how to handle recommender binding issues discovered after an application has been submitted.

Written by MOHIT MMANGAL

This article covers what to do when a recommender's name shows incorrectly on a student's Common App account and what to do when a recommender binding issue occurs after an application has already been submitted.

Recommender name shows differently on the student's Common App account

For example, Christine Henderson is showing as Morgan Williams on the student's CA Recommender section.

The recommendation is processed and sent directly to the university. A name mismatch does not prevent sending or delivery - rest assured, the recommendation has been successfully delivered. The name displayed is tied to the Common App database record for that recommender's email address.

What to do: If the mismatch needs to be corrected for record-keeping purposes, the student or counselor can contact Common App directly and highlight the name discrepancy. Common App can update the display name on their end.

Recommender binding issue discovered after the application has been submitted

If you discover that the wrong recommender was bound to a student's application after the application has been submitted to one or more universities:

  1. If no university has downloaded the recommendation yet: Contact Cialfo support immediately via Chat with Cialfo. Provide the student's name, CAID, the affected university, and the details of the correct recommender. The team may be able to correct this before the recommendation is downloaded.

  2. If the university has already downloaded the recommendation: The document cannot be recalled. Contact the university's admissions office directly to explain the situation and ask whether a replacement recommendation can be accepted. In parallel, contact Common App support at Common App Recommender Support for guidance on their correction process.

  3. For applications not yet submitted to a university: You can still update the recommender. Navigate to cDocs > the student's profile > Recommenders section > select the affected recommender and update before sending.

Same recommender binding issue affecting multiple students

If the same recommender's email is causing binding issues across multiple students simultaneously (for example, a teacher whose email was previously used directly on Common App), the root cause is usually the same: the teacher's email is already registered in Common App's recommender database from a prior direct invitation.

How to resolve it?

  1. Identify all affected students by filtering cDocs for documents with the affected teacher's email showing as "Not Linked".

  2. Contact Common App Recommender Support to request removal of all direct invitation records for that teacher's email. Provide the teacher's name and email address. Common App can bulk-remove all associated invitation records.

  3. Once Common App confirms the removal, retry sending from Cialfo for each affected student.

  4. If urgent (deadline approaching), contact Cialfo support via Chat with Cialfo and provide the list of affected students, the team can prioritise and coordinate with Common App on your behalf.

When to contact Cialfo support ?

  • Recommender name mismatch affecting multiple students from the same teacher

  • Need to correct a recommender binding on a submitted application

  • A recommender shows as "Not Linked" across many students despite the teacher completing the form in Cialfo

  • A deadline is approaching and you cannot resolve the recommender issue via the self-serve steps above

Need More Help?

Our Client Support team is available via Live Chat 24 hours a day, Monday through Friday, so you can get help anytime during the work week through Chat with Cialfo.

If you’re unable to find a solution in our help articles or need further assistance, you can contact the Cialfo Support team via Live Chat or email us at [email protected].

Did this answer your question?