THE RADARYNO NOTEBOOK

Track Which Resume Version You Used for Each Job

A clear application record helps you answer a simple question later: which resume did I actually send for this job? Keep the job identity, submission date, reviewed resume file, and any cover letter reference together. This approach reduces confusion when several versions look similar or when an employer contacts you weeks later. The Radaryno Resume Kit includes a local application tracker for recording application details and keeping documents on your computer. It does not submit applications, search for jobs, or contact employers, so you remain responsible for confirming what was sent.

01

Define the application record before you apply

Choose a small set of facts that will identify an application later: employer, role, job reference or posting link if available, application channel, submission date, status, submitted resume filename, and cover letter filename when relevant. These are user-maintained notes, not fields you should assume the kit provides automatically. Keep the record close to the saved documents so you can verify it without relying on memory. If an application is still in progress, label it as a draft or planned application rather than treating it as submitted. The goal is a reliable connection between a job and the documents you actually used.

02

Create a distinct name for each resume file

Use a filename that tells you who the document was for, which role it addressed, and which revision it represents. For an illustrative filename, “Northstar_Product_Support_Resume_Reviewed” is more useful than “resume-final.” If you produce another version later, save it as a separate file rather than replacing the earlier document. The Radaryno Resume Kit can write HTML and PDF resumes in the offer language, with four designs available: default, classic, compact, and modern. Record the format and design only as additional context; the exact file that was sent remains the primary reference.

03

Verify what was actually sent

Before marking an application complete, compare your intended document with the evidence available from the application channel. Check the uploaded filename, email attachment, sent-message record, or confirmation page. If the evidence is unavailable, state that uncertainty in your notes instead of guessing. The tracker is for recording application details; it does not submit applications or contact employers. This distinction matters because a prepared document, an attached document, and a successfully submitted application are different events. Record the file that left your computer or was accepted by the application process when you can establish it.

04

Save the document reference with the application

Once the submitted file is confirmed, place its exact filename in the application record and keep the file unchanged. If you sent an optional cover letter, record its filename alongside the resume so the pair can be reconstructed later. You may also note the resume design or language as useful context, but avoid replacing the exact file reference with a broad label such as “support version.” Keep the documents and records on your computer in a way you can understand later. Local storage keeps the files on the buyer’s computer, while AI provider access remains separate from the one-time kit purchase.

05

Handle revisions without changing history

When you improve a resume after applying, create a new file and leave the submitted version intact. Update the new file’s revision label and use it only for a later application unless you deliberately replace the earlier record with verified evidence. If you discover that the wrong file was sent, correct the application note transparently rather than silently renaming a different document. For future use, review the record before preparing documents so you can avoid accidental reuse of an old version. This process remains manual: the kit helps create documents and includes a local tracker, but it does not automate submission or employer communication.

Illustrative records for distinguishing submitted resume files
Application situationDocument evidence to checkRecord to keepWhy it helps
Application sent through an employer siteUploaded file name or confirmation attachmentEmployer, role, submission date, exact resume fileSeparates the submitted file from later revisions
Application sent by emailSent-message attachment and message dateRecipient, role, email date, attached resume fileShows what left your mailbox
Application started but not submittedSaved draft or incomplete formJob identity, status, last reviewed filePrevents an unfinished application from being treated as sent
Several versions reviewedFinal attachment or upload confirmationExact submitted file plus optional cover letter filePreserves the document pair used for that application

A worked example: resolving an uncertain record

  1. Illustrative example: Maya prepares a resume for a product support role and saves two local files with similar names. She later notices that the application record says only “updated resume,” which is not enough to identify the document. She checks the employer confirmation and finds the attached file name, then compares it with the files on her computer.

  2. She changes the record to include the employer, role, submission date, and exact submitted filename. She also notes that the compact design was used and records the cover letter filename when one was sent. These details describe the completed application rather than a preferred draft.

  3. A week later, Maya creates a revised file after correcting a project description. She keeps the original submitted file unchanged and saves the revision under a new name. The record now distinguishes the document used for the application from the document available for a future application.

  4. This example is illustrative, not a claim about a Radaryno tracker screen or automatic file naming. The useful principle is to verify the sent document from available evidence and preserve a stable reference to that file on the buyer’s computer.

Put it into words

Before and after

Fictional examples: not real people.

Before

Illustrative before: “Resume sent to Northstar.”

After

Illustrative after: “Northstar, Product Support Specialist, submitted on the application date, Northstar_Product_Support_Resume_Reviewed.pdf, cover letter not sent.”},{

Before

Illustrative before: “Modern version used.”

After

Illustrative after: “Uploaded Northstar_Product_Support_Resume_Modern.pdf; confirmation checked; application submitted.”

A few details

Frequently asked questions

What should I record for each application?

Record the employer, role, submission date, application channel, status, and exact resume filename. Add a job reference or posting link when available. If you sent a cover letter, record its filename too. These details create a durable connection between the application and the document pair you used. Keep planned, drafted, and submitted applications clearly distinct.

What if I cannot remember which resume I sent?

Do not choose a file based only on its name or modification date. Check the employer confirmation, application history, sent email, attachment record, or another document that shows what was uploaded. If no evidence remains, mark the record as uncertain and explain what you checked. A transparent uncertainty note is more useful than a confident but unverified file reference.

Can the kit submit applications for me?

No. The Radaryno Resume Kit includes a local application tracker for recording application details and keeping documents locally, but it does not submit applications, search for jobs, or contact employers. You must complete the application and verify the submitted attachment or upload yourself. The tracker supports record keeping rather than acting as an application service.

Does local storage mean the AI works without internet access?

No. Files and generated documents stay on the buyer’s computer, but local file storage does not mean offline AI inference. Access to an AI provider is separate from the one-time Radaryno purchase. Treat the local document record and the AI service connection as separate parts of the workflow, and avoid assuming that a saved file proves how the document was generated.

RADARYNO RESUME KIT

Your experience, selected for each offer.

A downloadable kit for Claude Code or Codex. Gaps stay visible.

See the kit