Separate the parties from the start
Create a record using distinct, user-chosen areas for the recruiter or agency, the possible end employer, the contact, and the role reference. Begin with the information in front of you rather than filling gaps from a company name, email domain, or familiar job title. A recruiter may be an independent person, an agency representative, or a staffing organization; the record should preserve that distinction without deciding more than the source supports. If the employer is named, record it separately. If it is not named, retain an unknown value and continue recording the opportunity without an assumption. This approach makes the application history easier to interpret when you review documents, messages, or later updates.
Capture each detail with its source
For every important field, note where the information came from. A recruiter message, agency posting, employer job page, and application confirmation can describe the same opportunity from different perspectives. Keeping the source beside the detail lets you distinguish confirmed information from a statement that has not been independently shown. Use concise notes such as the source type, date received, and relevant wording, but do not invent a source or add enrichment. If a source provides only an agency name and a role title, record only those facts. When a later source identifies the employer, add that source rather than replacing the earlier agency information. This preserves the path from introduction to application.
Keep unknowns and disagreements visible
An unknown employer is useful information because it tells you what the record does not establish. Do not convert an agency name into an employer name simply to make the record look complete. If two sources give different role titles, employer names, or contact details, keep the conflicting source notes and identify the field for review. You can use a short status such as unconfirmed or needs review, provided it reflects your own recordkeeping choice. The application tracker is for recording details and keeping documents locally; it does not verify identities, search for employers, or resolve a disagreement automatically. Clear uncertainty is safer than a polished but unsupported record.
Connect the role to the application event
Record the role reference together with the application date, submission context, and document set you used, using fields that fit your own system. This helps distinguish a recruiter-introduced opening from another opening with a similar title. If the employer is still unknown, the role reference can remain useful without forcing a company name. If the employer later becomes confirmed, add the new source and preserve the original introduction. Keep the record factual: the tracker does not submit applications, and it does not establish that an application was received unless you have a confirmation or other source. Your local documents can support review, but they should not be treated as proof of facts absent from the record.
Review before relying on the record
Before using a record to prepare for follow-up or compare application history, read the recruiter, employer, contact, and role fields independently. Check that an agency has not been copied into the employer field, that an unknown has not been silently replaced, and that each important assertion has a source. Review the document names or versions kept with the record, but do not assume a stored file proves who received it. The Radaryno Resume Kit can create HTML and PDF resumes and an optional cover letter from your career notes, but the tracker remains a place for your own application details. This review keeps the application record aligned with what you actually know.
Maintain the record on your computer
Keep the tracker entries and related documents in the local environment where you manage your applications. The kit is a downloadable Markdown, HTML/CSS, and local script kit that works with Claude Code or Codex on Windows, macOS, or Linux. Its local file storage keeps records and generated documents on your computer, but local storage does not mean offline AI inference; access to an AI provider is separate from the one-time kit purchase. Treat provider access and your own recordkeeping as separate considerations. The kit does not search jobs, contact employers, or submit applications, so any confirmation or communication must come from the sources you personally receive.
| Record area | What to capture | When it is unknown | Useful source |
|---|---|---|---|
| Recruiter or agency | Name, agency, and role in the introduction | Leave unconfirmed if no identifying detail was provided | Recruiter message or agency posting |
| End employer | Organization named as the hiring employer | Use an unknown value rather than an assumption | Employer posting or application page |
| Contact | The person or channel that sent the opportunity | Keep blank if no contact was supplied | Email, message, or posting |
| Role reference | Job title, reference, and application date | Record only the parts you can verify | Job description or confirmation |
A worked record using separate parties
Illustrative fictional scenario: a candidate receives a message from Northbridge Talent about a backend developer opening. The message identifies the agency and role but does not name the organization that would employ the candidate. The record lists Northbridge Talent as the recruiter or agency, preserves the role title, and marks the end employer as unknown. The source is the recruiter message, not an inferred company.
The candidate later finds a posting that names Cedar Grove Systems and uses the same role reference. The record can now add Cedar Grove Systems as the confirmed end employer while retaining Northbridge Talent as the introducing agency. The two parties remain separate because they serve different roles in the application history.
A contact field records only the sender information present in the message. It does not turn an agency into the employer or imply that the sender is the hiring manager. If the two sources disagree about the title or organization, the record keeps both source notes and flags the disagreement for review.
This fictional scenario illustrates a recordkeeping method, not a required tracker interface or a claim about any real person, agency, employer, or application. The useful outcome is a traceable distinction between who introduced the opportunity, who may employ the candidate, and what still needs confirmation.