1. LandOffer
  2. Blog
  3. All articles
  4. Predictive Index Behavioral Score ID: Reuse an Assessment Without Creating a Duplicate Record

Job search

Predictive Index Behavioral Score ID: Reuse an Assessment Without Creating a Duplicate Record

Current PI2 documentation and two completed fictional record audits distinguish existing assessment results, person records and application requirements.

9 min readLandOffer team

A Predictive Index Behavioral Score ID can let you reuse existing Behavioral Assessment results, but it does not guarantee that every import avoids a new candidate record. Before starting again, identify who is entering the ID: you through a candidate invitation, or the hiring team through Add by BSID. Current PI2 employer-import documentation explicitly says Add by BSID creates a new record, including when a person already exists. The candidate invitation documentation does not establish automatic person-record deduplication.

We reviewed public Predictive Index documentation on October 20, 2026, including its candidate-result and record-management guidance. We did not open a private invitation, retrieve anyone's assessment, sign in, submit a score ID or change a hiring record. The completed examples below are fictional record decisions, not tested account workflows. LandOffer publishes this guide; browse recent roles on LandOffer.ai while keeping each employer's application and assessment evidence separate.

Editorial illustration of a candidate locating an existing result key while keeping the employer invitation and candidate record distinct.

Identify what the ID actually represents

PI's Behavioral Score ID explanation describes a BSID as the identifier for a particular set of Behavioral Assessment results. It gives a ten-digit format grouped as XXX-XXXX-XXX. This is a result identifier, not a job requisition number or a universal confirmation that a hiring process is complete.

The same page points to the assessment completion email and to available reports in PI software as ways to locate it. Search the inbox originally used for the assessment for the completion message, then retain the ID privately. If the assessment belonged to a former employer and you cannot recover it, PI directs you to that administrator rather than promising to disclose another client's data.

Avoid searching public profiles for somebody else's identifier or copying a sample from a screenshot. The format tells you how an ID is presented; matching the format does not establish ownership or validity. This article uses labels such as BSID-A instead of functioning-looking numbers so its examples cannot be mistaken for reusable results.

Choose the route before entering the ID

The candidate invitation guidance describes a checkbox for someone who has already taken the Behavioral Assessment and wants to enter a previous BSID. A valid ID can be used to submit those existing behavioral results without taking the assessment again. The checkbox initially defaults to unselected; its presence and the relevant invitation matter.

Read the identity shown in your invitation before proceeding. That guidance says a name and email sent through PI can be prefilled and not editable by the candidate. If the details are wrong, ask the hiring contact to correct the record. Ask about the existing record before changing identities or attempting another assessment. A new email does not establish that the hiring team resolved the original association.

This is a documented route, not a report from a private candidate account. We did not observe an individual successful import, an invalid-ID error or a particular employer's completion screen. Keep the current invitation's instructions and the employer's confirmation as the evidence for your own case.

The employer import route can create a duplicate

PI's Add a candidate via BSID article describes the employer-side Hire workflow. Its FAQ currently says adding a BSID always creates a new candidate record. It specifically warns that adding an internal candidate that way results in a duplicate. This contradicts any blanket promise that knowing the ID alone prevents duplication.

The page mentions a planned ability to associate the ID with an existing record. A tentative future release is not evidence that the capability is available in the account being used. For someone already in the employer's system, the hiring team should inspect the existing record and current supported route before making another one.

The same article says BSID imports contain behavioral results, not Cognitive Assessment results. Do not use a reused behavioral result as proof that a cognitive assessment was completed or transferred. If the employer requested both, keep two separate status questions instead of treating the shared PI brand as one requirement.

Check both the assessment result and the person record. An organization can retrieve a previous result while still creating a second representation of the person. Avoiding unnecessary assessment work and avoiding duplicate records are related goals, but neither proves the other succeeded.

Completed route audit: three different record situations

The following original cases show how to decide which question to resolve first. They are hypothetical, with stipulated facts. No candidate result, employer directory or account was inspected for these cases.

Fictional situation Completed route decision Confirmation still needed
Nadia has BSID-A from an earlier employer and a new employer invitation with correct identity details Use the invitation's documented existing-result option if offered; do not repeat the assessment merely because the organization is new New employer confirms the behavioral requirement is associated with the intended application
Omar already has a record in the same employer's Hire system and is considered for another job Ask the hiring team to inspect and move or associate the existing candidate through its supported workflow before using Add by BSID Correct job association, person record and results used by the hiring team
Tess is an employee applying internally and someone proposes Add by BSID Flag the documented duplicate-record warning and ask the authorized hiring team to choose the current internal-candidate route Employer confirms the intended employee/candidate association without an unintended second record

Nadia's case concerns moving her own existing result into the new employer's assessment context. Omar's case concerns a person record the organization already holds. Tess's case adds an employee relationship. Treating all three as “paste the ID and continue” hides the issue each person actually needs resolved.

The completed audit does not prohibit an employer from creating a record when its process requires one. It identifies the point at which a new record should be a deliberate, reviewed action. A candidate should not try to manipulate an employer's directory or merge records they cannot inspect. Ask the hiring contact whether your existing person record can be used for this job before another record is created. That question gives the administrator a concrete issue to inspect.

Reassessment does not automatically replace displayed results

PI's current multiple-candidate-assessment guidance says an organization retaining an older candidate record can use its existing results for a newly opened job. If it chooses to reassess instead, the new result does not automatically replace the oldest result shown. PI Support assistance is described for setting the intended candidate result active.

That page also distinguishes organizations: another employer's results do not appear automatically in a new client's Hire account. A candidate can provide their own BSID through the assessment route, but a hiring team cannot simply recover another client's behavioral data. A result's existence somewhere is therefore different from its presence in this hiring process.

Employee documentation describes a different management workflow with authorized controls for active results. Do not apply employee-screen instructions to a candidate or assume a candidate can select which result an employer uses. If multiple attempts already exist, give the hiring team the relevant dates and ask which assessment is associated with the application. Do not retake again simply to see whether the display changes.

Older support material may use different navigation or discuss deleting old results. Verify the product and record type before following it. The objective here is correct reuse and record reconciliation, not choosing the most favorable profile or coaching answers to manufacture a particular result.

Editorial illustration of a private result archive and an application ledger, with an unresolved association held for review rather than silently duplicated.

Completed application ledger: a recovered ID leaves one task open

Evan is a fictional software engineer applying to Harbor Systems for role HS-214. He previously completed a Behavioral Assessment for another employer and has privately retained its completion email, labeled BSID-A here. The new invitation contains his correct name and email and requests behavioral and cognitive assessments. The scenario contains no actual score or answer data.

He initially writes “PI complete” next to the job because he found the old email. That entry collapses several different facts. His completed paper review separates four records: the old result, Harbor's behavioral requirement, its cognitive requirement and the HS-214 application acknowledgment. It produces this ledger:

Record item in Evan's scenario Evidence available Correct status and next action
Prior Behavioral Assessment Old completion email and BSID-A Existing result located; no claim about Harbor's application yet
Harbor HS-214 behavioral requirement Correct invitation and existing-result option described in its instructions Route identified; completion remains unconfirmed until the employer-side association is verified
Cognitive requirement Included in the new invitation; no completion evidence supplied Outstanding; BSID-A does not establish that it transferred
Main job application Separate employer acknowledgment for HS-214 Application received in this fictional record; this does not settle either assessment

The result is a useful incomplete record, not a fabricated successful submission. Evan retains the old result privately, keeps the current invitation with HS-214 and marks the cognitive task outstanding. Finding BSID-A resolves retrieval only. It does not close the behavioral association or the overall application requirements.

His unsent clarification draft reads: “For HS-214, I have an existing PI Behavioral Assessment ID and the current invitation shows my correct details. Please confirm the supported reuse route for this application and whether any cognitive assessment remains required. I want to avoid an unnecessary new candidate record or a repeated assessment.” The message names the record problem without embedding a full behavioral report or pretending the administrator already confirmed it.

In a real exchange, use the verified hiring contact and the organization's designated channel. Provide only the identifying details necessary to locate the case. Do not post the ID, report or invitation link on a public forum. If a representative requests the identifier, verify the recipient and purpose before sharing it. No message or identifier was sent for this article.

Recover missing results without inventing an access shortcut

PI's results-recovery page says information stays with the company administering the assessment and directs candidates to its administrator for results or a BSID. A shared Behavioral Report may also contain the identifier. The page does not establish that every applicant receives a report or that a new PI account grants access to a past employer's assessment.

Start with the email and documents you legitimately hold. If they are unavailable, record the administrator, approximate completion date and the application affected. Ask the current hiring team how to proceed when the old ID cannot be recovered. A fresh assessment may be appropriate under its instructions; this guide does not promise reuse when the needed identifier is missing.

Keep deadline questions separate from retrieval questions. Locating an old result can take time, while an invitation may expire under employer settings. Ask about the actual deadline rather than assuming a support request extends it. Do not allow a pending recovery attempt to become an unsupported “done” entry in your application tracker.

Verify the result, the record and the application

Before marking the task complete, distinguish three confirmations: you located the intended behavioral result, it is associated with the correct candidate and job in the current organization, and all separately requested application requirements are satisfied. Keep the employer's response or completion evidence beside the relevant job identifier.

If any confirmation is missing, label the missing part precisely. “Behavioral reuse awaiting association confirmation” gives a clearer next action than “PI broken” or “assessment complete.” Use LandOffer.ai alongside employer application records to maintain the wider search, while keeping private assessment details in an appropriate restricted place. Reusing a result can avoid an unnecessary retake. Confirming the employer's record route can help identify duplication before another record is created; the ID by itself is not a deduplication guarantee.

Sources and Further Reading