Collect the two source records
Open the saved job posting and the exact career notes used to create the report. Preserve the wording of each requirement, including qualifications, responsibilities, preferred items, and contextual phrases. Do not rely on a summary, memory, or an edited copy of the posting. Confirm that the notes represent the person’s current source of truth rather than a resume draft that may already contain omissions. If the Radaryno Resume Kit was used, its generated documents and source files remain on the buyer computer, so the review can be performed from those local records. Record any missing source material before judging the report.
Extract every requirement from the posting
Create a review list that captures each distinct requirement in the posting. Include technical capabilities, domain experience, responsibilities, education or credential language, communication expectations, and any stated level of experience. Preserve whether the employer presents an item as required, preferred, or descriptive, without deciding its importance yet. Combine only exact duplicates; keep requirements separate when similar wording could carry different meanings. This list is the control against omitted requirements. A report that looks detailed can still fail if it never evaluated one section of the posting or collapsed several requirements into a vague category.
Trace each report row to both sources
Review every row or claim in the report and connect it to a specific phrase in the posting and a specific passage in the career notes. A valid match needs support from both sides. A report claim is not sufficiently supported merely because the wording sounds similar, and a missing finding is not established merely because a term does not appear in the notes. Use a short trace note for each row, such as the posting phrase, the note location, and the reason for the classification. Keep unresolved items visible instead of forcing a binary match or gap.
Find omitted and falsely missing requirements
Compare the complete posting list with the report rows, then inspect every missing finding against the career notes. Omitted requirements need their own review row even when no evidence exists. Falsely missing findings often arise when notes use different terminology, describe the work without naming a product, or place evidence under an adjacent project. These cases require clarification, not automatic correction. Distinguish an absent requirement from an absent phrase. The report should state what the sources show and what they do not show, without turning a limited knowledge base into a negative claim about the person’s background.
Test the strength of each claimed match
Inspect positive matches for overreach as carefully as you inspect gaps. A match should reflect the scope, level, and context stated in the sources. For example, exposure to a database is not automatically evidence of administering it, and helping colleagues is not automatically evidence of formal procedure writing. Check whether the report added a tool, credential, responsibility, duration, or level that the notes do not state. When the evidence is partial, change the finding to qualified or unresolved rather than preserving a confident claim. This protects later documents from unsupported additions.
Resolve uncertainty with targeted questions
Turn unresolved findings into concise questions for the person who owns the career notes. Ask about the specific requirement, the context in which it was used, and the evidence that could be safely recorded. Avoid leading questions that assume the answer. A useful question might ask whether a particular database was used in a named project, rather than asking the person to confirm a match. If the answer is no or remains unknown, keep the requirement marked as unverified. The purpose is to improve source accuracy, not to fill every row with a positive result.
Write the final audit record
Summarize the review in a coverage matrix or equivalent record with one row per requirement. Include the posting wording, the report finding, the career-note evidence, the audit decision, and the follow-up question or source note. Make clear which items were matched, omitted, falsely marked missing, unsupported, or unresolved. Do not hide disagreements by replacing the original report. Keep the audit alongside the local source documents so later resume or cover-letter work can distinguish confirmed information from open questions. If AI provider access was used, remember that local file storage is separate from the provider’s access and does not itself mean the AI process was offline.
| Report finding | Evidence in the sources | Audit decision | Next record |
|---|---|---|---|
| Matched | The posting requirement and relevant career note are both clear | Keep the match | Record the supporting note |
| Missing | The posting requirement is present, but the notes contain no related evidence | Unverified, not proven absent | Ask whether experience exists |
| Omitted | A requirement appears in the posting but has no report row | Add a review row | Trace it before using the report |
| Unsupported match | The report claims a match, but the notes do not support it | Remove or qualify the match | Record the missing evidence |
| Ambiguous | Wording or source context allows more than one interpretation | Hold for clarification | Note the competing readings |
A worked audit from source text to decision
Illustrative scenario: a posting asks for PostgreSQL, data exports, and experience documenting internal procedures. The report lists PostgreSQL and exports but omits documentation. The omission is a report defect, even if the candidate has no documentation evidence yet. Add the requirement before deciding whether it is a gap.
Illustrative scenario: the report marks PostgreSQL as missing because the career notes mention database work without naming the system. That is an unresolved finding, not proof of absence. Check the original notes for project context, then ask for confirmation if the database technology remains unclear.
Illustrative scenario: the report says the person has documentation experience because a note mentions helping colleagues. That match is too broad unless the notes connect the activity to written procedures, guides, or another form of documentation. Qualify or remove the match when the source does not support it.
Illustrative scenario: a requirement appears in the posting more than once with different wording. Consolidate it for review while preserving the original phrases, then record whether the report covered both meanings. This prevents duplicate rows from hiding a missing interpretation.