THE RADARYNO NOTEBOOK

Record Verified Metrics in Your Career Notes

A metric is useful only when its meaning and origin remain clear. This guide shows how to preserve measurable career evidence as structured notes: define the measure, record its period and baseline, name the source, state the unit, and separate personal contribution from team results. The aim is not to estimate missing outcomes or compose achievement statements. It is to create dependable evidence that can later support application documents without changing the underlying facts.

01

Define the metric precisely

Write a plain-language definition before recording the value. State what is counted, excluded, or grouped, and distinguish an output from a rate, percentage, duration, cost, or quality measure. “Requests closed” is different from “requests received,” and “average resolution time” is different from “same-day resolution rate.” If the original source uses a specialized term, preserve that wording and add a short explanation. Avoid turning a broad phrase such as “improved delivery” into a number without evidence. The definition should let another reader understand the measure without relying on memory or a polished application sentence.

02

Add the period and baseline

Attach a time period to every metric, even when the source seems obvious. Record a month, quarter, project phase, release window, or other supported interval. Then identify the baseline used for comparison, if there is one. A baseline may be a prior period, an agreed target, an initial measurement, or no comparison at all. Do not describe a value as an improvement when the earlier value is absent. Preserve the original dates or labels so a later writer does not confuse a reporting period with the date the note was created. If periods are not comparable, explain why and avoid calculating a change.

03

Capture source, unit, and calculation

Record where the metric came from and how it was calculated. A source can be a dated report, approved project record, service dashboard, budget document, or another career note that preserves the original evidence. State the unit beside the value: requests, hours, dollars, percentage points, percent, defects, or another supported unit. Keep input values when a result is calculated, and record the rounding approach. Do not replace missing source data with an estimate or treat a percentage-point change as a percentage change. If the source cannot be checked, mark the metric as unverified and retain the uncertainty.

04

Separate individual attribution from shared results

A team metric and an individual contribution are different records. Write the shared outcome first, then describe the person’s verified role, such as preparing a report, closing a documented subset of cases, changing a process, or coordinating a measured activity. Use attribution only when the source or first-hand record supports it. Avoid assigning the full result to one person because they participated in the project. When the contribution cannot be quantified, preserve the qualitative role and the team measure separately. This produces a more accurate evidence trail and prevents later documents from overstating personal ownership.

05

Audit gaps before reuse

Review each record as evidence rather than prose. Check that the definition, period, baseline, source, unit, calculation, and attribution agree with one another. Look for hidden assumptions: a percentage with no denominator, a target presented as an achieved result, a total copied from a forecast, or a team outcome described as personal work. Add a question for every missing field and preserve the original wording where interpretation is uncertain. This audit is complete when a reader can tell what is known, what was calculated, and what still requires confirmation. Do not promote an unchecked value into a verified metric.

06

Use the verified notes in the Radaryno workflow

Once the records are reviewed, keep them as buyer-maintained career notes and use only the supported evidence when preparing application documents. The Radaryno Resume Kit uses the buyer’s career notes, selects relevant experience, reports gaps, and asks rather than inventing. It can produce HTML and PDF resumes and an optional cover letter in the offer language, with a single-column ATS-friendly layout. The kit works with Claude Code or Codex on Windows, macOS, and Linux, but local file storage does not mean offline AI inference; provider access is separate. Do not expect the kit to submit applications, search for jobs, or contact employers.

Illustrative fictional comparisons for preserving metric evidence
Record areaClear entryWeak entryWhy it matters
DefinitionResolved support requestsImproved supportThe reader can identify what was counted.
Period and baselineQuarterly total; prior quarter used as comparisonHandled many requests recentlyThe change has a defined time frame and reference point.
Source and unitService report; requests closedInternal data; better performanceThe value can be checked and its unit is explicit.
AttributionPersonally closed 48 of 120 requests; team total was 120Reduced the team backlog by 40%Personal contribution is separated from the shared result.

Worked example: preserve the evidence before writing

  1. Start with a fictional service record stating that a support group closed 120 requests during a quarter, compared with 90 in the preceding quarter. The definition is requests closed, the period is one quarter, the baseline is the preceding quarter, and the unit is requests. The source is a dated service report. Keep these fields together rather than copying only the increase into a separate note.

  2. Calculate only what the recorded values support. The change is 30 requests, and the relative increase is 30 divided by 90, or 33.3 percent when rounded to one decimal place. Store the unrounded inputs and the rounding rule. Do not infer that the fictional contributor caused the entire change unless the source establishes that connection.

  3. Add attribution separately: the fictional contributor personally closed 48 requests, while the group closed 120. This supports a personal count of 48 and a team outcome of 120. If the source does not show how the contributor affected the remaining 72 requests, leave that relationship undescribed rather than assigning credit.

  4. Record unresolved details as questions, such as whether reopened requests were included or whether the comparison periods had equal operating days. A later document can use the verified fields after those questions are answered, but it should not convert an incomplete record into a stronger claim.

Put it into words

Before and after

Fictional examples: not real people.

Before

Illustrative fictional note: “Improved service performance.”

After

Illustrative fictional note: “Requests closed: 120 during the quarter; prior quarter: 90; source: dated service report; unit: requests; personal share: 48 closed; reopened-request inclusion: unknown.”

Before

Illustrative fictional note: “Cut processing time by 20%.”

After

Illustrative fictional note: “Average processing time fell from 50 minutes to 40 minutes between two comparable monthly periods; source: workflow report; calculation: 10-minute reduction, or 20%; individual contribution not yet confirmed.”

Before

Illustrative fictional note: “Saved $15,000.”

After

Illustrative fictional note: “Estimated annual cost difference: $15,000; source: approved budget comparison; status: estimate, not realized savings; personal contribution: prepared the comparison, ownership of the outcome not established.”

A few details

Frequently asked questions

What makes a metric verified?

A verified metric has a clear definition, a supported value, a stated unit, and a source that can be identified or checked. It also has a measurement period and baseline when a comparison is claimed. Verification does not require every field to be complete, but missing fields must be marked as unknown rather than silently inferred.

Should I record a percentage when I only know the totals?

You can calculate a percentage only when the numerator, denominator, and comparison context are supported. Keep the original totals beside the calculation and state whether the result is a percent or percentage-point change. If the denominator is missing or ambiguous, record the totals and leave the percentage unresolved.

How should I handle a team metric?

Record the team result as a shared outcome and add a separate attribution field for the individual contribution. A person may have led a workstream, completed a documented portion, or supplied a process change without owning the entire result. If the evidence does not connect the individual action to a measured effect, preserve that limitation.

What if the source is no longer available?

Keep the value only if you can identify its origin and explain why it cannot currently be checked. Mark it as unverified, preserve the original wording, and avoid presenting it as confirmed evidence. A later source may resolve the status. Do not recreate a missing report from memory or replace it with an approximate value.

Can a target count as a result?

No. A target is a planned or expected value, while a result records what occurred. Store the target and achieved value as separate fields with their dates and sources. If only the target is available, label it as a target and do not calculate achievement, attainment, or improvement without the actual result.

Does local storage mean AI processing is offline?

No. The Radaryno Resume Kit keeps files and generated documents 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 kit purchase. Check that access separately before using career notes in the workflow.

RADARYNO RESUME KIT

Your experience, selected for each offer.

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

See the kit