Build one confirmed source of career facts
Gather the notes that describe what you actually did, not only the wording used in a previous application. Include role names, dates, responsibilities, tools, deliverables, stakeholders, and outcomes when they are confirmed. Separate direct observations from interpretations such as “this could support analysis” or “this sounds relevant to operations.” Keep uncertain details marked for review. The goal is a reusable source that can support more than one direction without silently inheriting claims from an old document. If your notes are incomplete, record the missing detail as a question. This source can remain on your computer and be reused with the Radaryno Resume Kit, which works with Claude Code or Codex on Windows, macOS, and Linux.
Define the two role directions separately
Write a short description of each direction before selecting evidence. For an operations direction, consider coordination, process control, service continuity, documentation, and stakeholder communication. For an analysis direction, consider data preparation, checking, comparison, reporting, and evidence-based recommendations. These descriptions are selection rules, not new qualifications. Avoid forcing every note into both sets. A responsibility may be central for one direction, supporting context for the other, or irrelevant to both. Keeping the directions separate prevents a shared career history from producing two documents that make the same broad claim with different job labels.
Classify each note by evidence strength
Review each source note and assign a practical status: direct evidence, transferable context, or gap. Direct evidence describes the activity in a way that matches the direction. Transferable context shows a related behavior but does not establish the full requirement. A gap means the notes do not confirm the requested experience, tool, method, or level. This classification is especially important when moving between operations and analysis. Reporting may be relevant to both, while a specific analytical tool may belong only in the gap list. Do not add a stronger verb or technical method merely because it would make the document sound closer to the role.
Select evidence for the operations direction
Create the operations selection from notes that show how work was coordinated, maintained, documented, or improved. Give priority to recurring responsibilities, handoffs, issue resolution, process changes, and communication with affected people. Include reporting when it demonstrates dependable updates or helped others make decisions, but do not imply that reporting alone proves a different specialty. Keep analytical details only when they support an operational outcome. Check that the selection presents a coherent direction rather than a mixed list of every task you have performed. If a requirement is not supported, leave it visible as a gap for your review instead of hiding it through broad wording.
Select evidence for the analysis direction
Build the analysis selection from notes that confirm how information was gathered, cleaned, checked, compared, summarized, or used to guide a decision. A report title is not enough; the notes should support the underlying activity. If your history contains operational reporting, describe only the analytical elements actually recorded. Transferable context can show familiarity with structured information and stakeholder questions, but it should not be presented as direct experience with an unconfirmed tool or method. Keep the strongest evidence near the top and preserve gaps for a later decision about training, application fit, or additional documentation.
Generate and review each document separately
Use the two evidence selections as separate inputs when preparing application documents. Review the generated HTML and PDF versions for factual accuracy, readable single-column structure, and consistent wording. The Radaryno Resume Kit can select relevant experience, report gaps, and ask rather than inventing. It can also create an optional cover letter in the offer language. Compare each document with its own evidence selection, then compare both against the original notes. A statement that is acceptable for operations may be misleading in an analysis document if the underlying activity is not confirmed. Make corrections in the source notes when the fact itself is wrong, and make corrections in the selection when the interpretation is too broad.
Record the application context locally
Keep the final document, selected direction, offer language, and review notes together with the relevant application record. The kit includes a local application tracker for recording application details and keeping documents locally, but it does not submit applications, search jobs, or contact employers. Local storage means the files and generated documents stay on your computer; it does not mean that AI inference is performed offline. Access to an AI provider is separate from the one-time kit purchase. Recording which evidence selection you used helps you understand why two documents differ and makes later corrections easier without rebuilding your history from memory.
| Source note | Operations direction | Analysis direction |
|---|---|---|
| Coordinated recurring service work across several teams | Emphasize scheduling, handoffs, issue tracking, and process consistency | Use only as context for data gathered from recurring work |
| Prepared regular status reports for internal stakeholders | Emphasize clear updates and decision support | Emphasize data preparation, trend identification, and reporting accuracy |
| Improved a recurring workflow | Describe the change, affected process, and confirmed outcome | Connect it to analysis only if the notes identify the method and evidence used |
| No confirmed experience with a requested analysis tool | State the gap and retain adjacent reporting evidence | Do not present the tool as used; identify it for review before applying |
Worked process: separating one history into two evidence selections
Begin with one source note about coordinating recurring work. For an operations direction, the useful interpretation concerns scheduling, handoffs, exceptions, and process follow-through. For an analysis direction, the same note is weaker unless it also records data preparation, trend review, or reporting decisions. Keep the source wording unchanged, then write a separate interpretation for each direction.
Next, review a note about producing recurring reports. The operations version can focus on stakeholder communication and dependable updates. The analysis version can focus on how information was gathered, checked, compared, and presented, but only when those actions are confirmed in the notes. If the method is absent, leave it as an open question rather than filling it in.
Finally, compare both selections against the role requirements. Retain direct evidence in both where appropriate, move context to the less relevant direction, and show gaps plainly. This creates two honest documents from one maintained history without suggesting that one job title or task proves experience in another field.