Gather the project record
Start with a bounded collection of material from the completed project. Include items that show your actual involvement, such as tickets, pull requests, design notes, test results, release records, feedback, or dated personal notes. Record where each item came from and what period it covers. Avoid beginning with a polished description of the project, because that can blend team activity with your own contribution. The goal is to create a reviewable evidence set, not to produce application wording. If a source is unavailable, note that absence rather than reconstructing its contents from memory. Keep the original material unchanged and add your working observations separately.
Record confirmed changes
Write concise source notes for information that the evidence supports. A useful note states what changed, your role, the relevant context, and when it happened. Include tools, methods, systems, or responsibilities only when the records support them. Keep the language descriptive rather than promotional. If a result is documented, preserve the wording and scope of the source; if it is not documented, do not add a metric or outcome because it sounds likely. Add the new note beside the relevant existing information so the history remains understandable. This creates a dependable source for later selection without turning the note into a finished resume entry.
Mark uncertainty and open questions
Review every new note for details that are incomplete, inferred, or dependent on another person’s confirmation. Label those details as uncertain rather than placing them among verified facts. Write a specific question explaining what remains unknown, such as the exact measurement, ownership boundary, release scope, or name used at the time. Record what source or person could resolve the question, without assuming that confirmation will arrive. This distinction prevents an attractive but unsupported version of the project from entering your long-term notes. It also gives a later assistant a clear signal to ask rather than invent when information is missing.
Preserve history and add the update
Do not overwrite older notes simply because the project has ended or terminology has changed. Add a dated update that explains what is new, what was corrected, and whether the earlier wording still describes the historical situation. Keep past application documents and their supporting notes intact so you can understand what was known and used at that time. If a correction affects a recurring fact, link the new note conceptually to the older one through a clear explanation rather than silently deleting the original. This approach supports accurate future documents while preserving an honest record of how your experience was previously described.
Review for consistency before reuse
Read the updated notes as a source record, not as an application draft. Check that role, dates, tools, ownership, and outcomes do not conflict with nearby notes. Where two records differ, preserve both statements temporarily and describe the conflict instead of choosing the more favorable version. Confirm that uncertainty labels remain visible and that any resolved question has a supporting source. If you use Radaryno later, its stated workflow can select relevant experience, report gaps, and ask rather than invent from the buyer’s career notes. The kit does not remove the need for this review, and the quality of generated documents depends on the information you maintain.
Keep the update separate from future applications
Treat the maintained notes as a reusable evidence source and each application as a historical output. A new project fact may become relevant later, but it should not automatically alter documents already sent. Save the updated source notes separately from generated HTML or PDF documents and any optional cover letter. Radaryno generates documents on the buyer’s computer from buyer career notes, and its local application tracker lets users record application details while keeping documents locally. It does not submit applications, search for jobs, or contact employers. Local storage also does not mean offline AI inference, so consider provider access separately from the kit purchase.
| Information type | How to record it | Evidence to retain | Future use |
|---|---|---|---|
| Verified fact | State the event, contribution, context, and date in plain language | Source document, record, or link kept locally | Available for later selection when relevant |
| Uncertain detail | Label it as unconfirmed and write the question that remains | The incomplete source and the needed confirmation | Prevents unsupported claims |
| Interpretation | Separate your conclusion from the observed event | Reasoning and supporting observations | Can be reviewed before being treated as a fact |
| Correction | Keep the old wording visible, then add the corrected version and reason | Original note plus correcting source | Preserves an audit trail |
| Historical application detail | Do not replace it with the new note; add a dated update | Saved application document and note | Keeps past applications understandable |
Worked example: turning project memory into maintained evidence
Fictional: true — After a project closes, Maya remembers that she helped improve a reporting service. Instead of writing a polished achievement, she gathers the delivery record, a code review, a test summary, and a note from the project discussion. The first draft records only observable facts and leaves the size of the improvement unconfirmed.
Fictional: true — Maya separates her direct work from the wider team outcome. She records that she changed a query, added a test, and reviewed a deployment checklist. She does not claim ownership of the entire service or attach a performance figure because the available records do not establish either point.
Fictional: true — A later conversation confirms the affected report and the release date but not the exact reduction in processing time. Maya updates the confirmed context, keeps the performance claim marked as unresolved, and adds a question identifying the person or record that could verify it.
Fictional: true — When an older application refers to the service using its former name, Maya leaves that historical document unchanged. She adds the current terminology to her source notes with a date and explanation, so future documents can use the correction without rewriting the past.