Define the source boundary
Gather the career notes that you personally treat as evidence before reviewing any generated resume text. Include facts such as employers, dates, responsibilities, tools, credentials, languages, project scope, and measurable outcomes only when you can stand behind them. Separate direct facts from interpretations, memories that need checking, and wording copied from an older draft. Label each entry with its origin, such as personal note, employment record, portfolio material, or later confirmation. Do not treat a previous resume, cover letter, or AI response as verified merely because it was used before. The purpose of this step is to establish what the drafting process may draw from and what must remain an open question.
Build a fact-to-draft ledger
Create a simple ledger with one row for each meaningful claim. Record the source fact in plain language, the draft sentence that uses it, and the review status. Useful statuses include supported, partly supported, unresolved, and rejected. Add a note when a sentence combines several facts, because combined wording can introduce a new claim about ownership, sequence, scale, or causation. Keep the source wording visible beside the polished wording so a reviewer can compare them without relying on memory. A ledger does not need a special application or a prescribed file location; it can be maintained in the buyer’s existing notes as long as the distinction remains clear and consistent.
Run a confirmation loop
Review each unresolved or partly supported sentence by asking a narrow question about the missing evidence. Ask whether the responsibility was personal or shared, whether a result was measured, which tool was actually used, or whether a date and title are accurate. Avoid one broad request such as asking whether the entire resume is correct, because broad approval can hide several assumptions. Record the answer as a new source fact or as a limit on the existing fact. If no confirmation is available, narrow the wording or remove it. The Radaryno Resume Kit can report gaps and ask rather than invent, but the buyer must supply or approve the factual resolution.
Approve reusable evidence
Once a sentence has been checked, separate the approved claim from the draft style around it. The approved claim should preserve the confirmed scope, timing, tools, and outcome without adding stronger language. Keep a short provenance note showing which source entries support it and which wording was intentionally excluded. This is especially important when the same career notes produce several resume designs or documents in different offer languages. Translation or formatting may change phrasing, but it should not change the underlying evidence. Treat an approved claim as reusable only within the boundaries you confirmed; a new interpretation, metric, or ownership statement requires another review.
Audit the final documents
Before using a generated resume or optional cover letter, compare its substantive claims with the ledger rather than proofreading style alone. Check titles, dates, responsibilities, tools, results, credentials, and reasons implied by the wording. Review omissions too: a document may leave out a qualification without changing the truth of its remaining claims, while a polished sentence may create an unsupported connection between two real facts. If the kit generates HTML or PDF files, inspect the final files as delivered because formatting can change how a qualification or date is understood. Keep application records separate from the evidence ledger; recording where a document was used does not prove that its claims are accurate.
| Ledger entry | What it records | Review decision |
|---|---|---|
| Source fact | A dated role, responsibility, tool, result, credential, or language supplied by you | Keep as evidence when the wording is accurate and specific |
| Draft sentence | Resume or cover-letter wording proposed by an AI system | Compare with source facts before approval |
| Open question | A missing date, scope, metric, title, tool, or relationship between facts | Confirm, narrow, or remove |
| Approved claim | A draft checked against the source and accepted by you | Allow reuse while preserving its source reference |
| Rejected wording | An unsupported inference, exaggeration, or mistaken combination | Do not return it to the source notes |
Worked provenance review
Begin with a source note that says a fictional:true operations coordinator reconciled monthly invoices using spreadsheets and reduced duplicate entries after introducing a review checklist. The note does not state a percentage, team size, software brand, or formal project ownership. Those absences matter. They prevent a later draft from being treated as a fuller account simply because it sounds polished. Record the source wording and its limits before asking for a resume sentence.
Next, compare the proposed sentence with the ledger. A fictional:true draft saying “reconciled monthly invoices and introduced a spreadsheet review checklist” stays within the source. A sentence saying “led a finance automation project that cut errors by thirty percent” adds ownership, automation, and a measurement that were never supplied. Mark the second sentence as unresolved rather than editing it into the source notes.
Then ask a focused confirmation question for each unresolved element. The fictional:true user may confirm the percentage from an internal report, reject the leadership claim, and clarify that spreadsheets were used rather than a named application. Each answer becomes a separate source entry with its own wording. This prevents one broad approval from validating several hidden assumptions at once.
Finally, approve only the narrow sentence supported by the confirmed entries. Keep the original draft, the accepted wording, and the reason for rejecting unsupported additions in separate ledger fields. If a later document repeats the rejected claim, compare it with the ledger again rather than assuming repetition proves accuracy. The ledger protects evidence integrity; it is not an application-outcome log.