Create a separate record for every role
Start with the employer, then identify the exact role connected to the application. Add the role title, department or location when useful, application date, and any requisition reference shown in the posting. If two roles have similar names, add a short distinguishing note rather than combining them. Keep one record per submitted application, including applications made through the same portal. The goal is to preserve role identity before you add statuses or messages. The local application tracker is intended for recording these details; it does not submit applications, search jobs, or contact employers.
Assign a document reference to each application
Connect every record to the files used for that specific submission. Note the resume design, language, and date, plus the cover letter when one was included. Radaryno can write an HTML and PDF resume and an optional cover letter in the offer language, but the tracker should still identify which files you sent. Do not rely on a generic label such as “latest resume,” because that label can change after another application. A simple descriptive reference makes later review easier while keeping documents on your computer.
Set a role-specific initial status
Choose a status that describes only the selected role, such as draft, submitted, screening, interview, paused, withdrawn, or closed. Use the same vocabulary across employer records so that later reviews remain understandable. Record the date of the status change and a short source note, such as an email or portal update. Avoid assigning a status to the employer as a whole. A response about one role is not evidence that another role has the same status, even when the messages come from the same recruiting team.
Log updates without overwriting history
When a role changes, add the new status with its date and preserve the earlier state in the record or notes. A brief entry can explain what happened: a recruiter call was scheduled, an application was withdrawn, or a portal showed that the role was closed. Keep uncertain information marked as unconfirmed rather than turning an assumption into a fact. Do not copy an update across every application for the employer unless the employer explicitly refers to all of them. This keeps separate application paths visible.
Review duplicate or conflicting entries
Check for records that share an employer but differ in role, date, or document reference. A duplicate may be accidental, while a similar title may represent a real second application. Compare the submission date and files before merging anything. If you cannot establish that two entries refer to the same application, keep them separate and add a note explaining the uncertainty. This approach protects the history needed to answer follow-up questions and prevents a later status change from erasing the path of another role.
Review the employer history before follow-up
Before sending a follow-up yourself, read the relevant role record and its history rather than scanning only the employer name. Confirm the application date, current status, last update, document references, and any note about contact. The kit does not contact employers, so any outreach remains your responsibility. A local record can help you choose the correct role in a message, but it does not confirm that an employer portal or recruiting system matches your notes. Keep the review focused on the selected application and do not infer progress for other roles.
| Scenario | Before | After | Why it helps |
|---|---|---|---|
| Fictional:true, two roles submitted in the same week | Acme application — submitted | Acme — Support Engineer — submitted on Monday; Acme — Systems Analyst — submitted on Thursday | Each status belongs to a role and date. |
| Fictional:true, one role has a recruiter call | Northstar — interview | Northstar — Product Operations Associate — recruiter call; Northstar — Operations Coordinator — submitted | A role-specific update avoids implying that both applications reached interview stage. |
| Fictional:true, different document versions were sent | Brightpath — resume sent | Brightpath — Data Platform Specialist — modern design, English resume; Brightpath — Technical Writer — classic design, English resume | The document reference identifies what was actually submitted. |
| Fictional:true, an older application is closed | Harbor Labs — rejected | Harbor Labs — QA Analyst — closed after rejection; Harbor Labs — Release Coordinator — awaiting response | Closed history remains separate from an active application. |
A worked review of one employer record
fictional:true, Begin with the employer name, then split the history by role rather than by conversation or department. A record for a Platform Support Engineer should not absorb a later Application Support Analyst entry merely because both belong to the same company.
fictional:true, Add the role identity, application date, source or portal note, and document references for each entry. If a requisition reference exists, include it; if not, use a clear role label and date instead of inventing an identifier.
fictional:true, When a message arrives, compare its wording with the relevant role before changing anything. Record the new status only on the matching entry, while preserving the previous status and any note that explains the change.
fictional:true, Review the employer history by asking whether every active entry has a distinct role, date, status, and document reference. This review reveals accidental overwrites without claiming that the employer system has synchronized with your tracker.