Gather the two records
Open the existing application details and the record you are considering adding or reviewing. Compare the information already recorded rather than relying on memory. Collect the employer name, role title, role reference or requisition identifier, listing location if available, dates connected with the application, and any confirmation or receipt details. You can also note whether the listing appears to be the same, reposted, corrected, or materially changed. Keep the original records unchanged while gathering this information. The local application tracker is intended for recording application details and keeping documents locally; it does not fetch job listings or submit applications.
Normalize comparable details
Compare equivalent fields in the same way. For example, distinguish the date a listing was saved from the date an application was submitted, and distinguish a role title from its role reference. Preserve the wording found in the source document or confirmation when it matters. If a field is missing, mark it as unknown in your notes instead of treating the absence as a match. Small differences in punctuation, abbreviations, or title wording may not matter, but a changed requisition, location, or submission event can change the conclusion. This step creates a clear basis for comparison without inventing details.
Compare the employer and role reference
Begin with the strongest identity clues: the employer and the role reference, requisition, or other identifying text. A matching employer and identical role reference support the possibility that both records concern one listing, but they do not prove that only one submission occurred. A similar title with a different reference may indicate a separate opening. Also check location or arrangement when those details are recorded, because the same title can appear in more than one opening. Write the comparison beside the records so another review can follow the reasoning without guessing what the match meant.
Check dates and submission evidence
Next, determine whether the records point to the same submission event. Compare the application dates with any confirmation, receipt, or saved submission detail. One record created later may simply duplicate an earlier entry, especially if both point to the same confirmation. Conversely, separate dates accompanied by separate confirmations support separate submissions, even when the employer and title are similar. Do not treat a listing date, document creation date, or tracker entry date as proof of submission by itself. If the evidence is incomplete, record the uncertainty and avoid claiming that a duplicate has been confirmed.
Classify the relationship
Use the comparison to answer two separate questions: whether the records concern the same opportunity, and whether a submission is confirmed. Matching identifiers and a shared confirmation suggest a duplicate record. A different role reference may identify a different opportunity, but it does not prove that either application was submitted. Call submissions separate only when the records establish distinct submission events. If evidence is incomplete, mark the record relationship or submission status unresolved. Keep the originals and explain the evidence for each decision. A repost can have a separate listing history without creating a confirmed new application.
Preserve originals and cross-reference
When the records appear to describe the same submission, choose a primary record for future reference and add a concise cross-reference in your own notes. Retain the original details rather than deleting one record, because the older entry may contain useful context about the listing or document used. When the records represent separate submissions, keep both and note the difference, such as a changed role reference or separate confirmation. If the result remains unresolved, keep both records and state what evidence is missing. The Radaryno kit keeps files and generated documents on the buyer computer, but local storage does not make the comparison automatic or remove the need for your judgment.
| Comparison area | Likely duplicate signal | Likely separate record signal | Practical treatment |
|---|---|---|---|
| Employer and role reference | The employer and identifying role reference match closely. | The role reference, requisition, location, or employment arrangement differs. | Keep both until the role reference and other evidence are checked. |
| Application dates | The records point to the same application date or the same submission event. | The records show distinct submission dates with separate confirmations. | Cross-reference the records and preserve the confirmed events. |
| Submission evidence | Both records refer to one confirmation, receipt, or saved submission detail. | Each record has its own confirmation or other distinct submission evidence. | Treat separate confirmed events as separate submissions. |
| Listing status | The same listing appears with unchanged identifying details. | The listing was reposted, corrected, or materially changed. | Record the relationship and keep the original details intact. |
Worked comparison: one listing, two records
In this fictional illustration, a user finds two local records for a Product Support Specialist role at Northstar Tools. Both records contain the same employer and role reference. One was created from a saved confirmation dated in early May, while the other was created after the same confirmation was reviewed again. The matching evidence suggests that the records may describe one submission rather than two.
The user compares the saved role reference, employer name, application dates, and confirmation details without changing either original record. The second record contains no distinct submission evidence and points to the same listing details. The user marks the records as related in their notes and chooses one record as the primary reference, while retaining the other for traceability.
In a different fictional illustration, two records concern the same employer and similar role title, but each has a different role reference and a separate submission confirmation. The user keeps both records because the evidence supports separate submissions. A similar title alone is not enough to merge or delete either record.