Quick answer

Record both dates, the exact result, the format, the purpose and any convention applied. Five fields make the calculation auditable.

What a complete record contains

Five elements make an age calculation reproducible. The date of birth and its source. The reference date and why that date governs. The exact result. The format or convention applied, if any. And the purpose — the instrument, policy or decision the age was calculated for.

Any reviewer with those five can rebuild the number without contacting you. Missing any one of them and they are guessing. The most commonly omitted is the reference date, which is also the one that makes the record decay silently as time passes.

Use this guide with the right tool: Open the Chronological Age Calculator for chronological age on an assessment date. If the question shifts, compare it with the Age on a Date Calculator or the Test Age Calculator.

Screenshots are not documentation

A screenshot of a calculator result shows the output and often not the inputs. It cannot be searched, cannot be re-run, and cannot be checked against a corrected date of birth if one later emerges.

Record the values as data. Where you want a durable pointer to the exact calculation, the shareable result link encodes the inputs in the address, so opening it reproduces the calculation rather than an image of it. Keep the link alongside the recorded values, not instead of them.

Note the unusual, not the routine

Documentation that records everything at equal weight is hard to read. What deserves an explicit note is anything a reviewer would not assume: an estimated date of birth, a multi-session administration, a nonstandard reference date, an applied rounding rule, a boundary case, or a discrepancy between two source records.

Routine calculations need only the five fields. It is the exceptions that generate the questions, and a one-line note at the time costs far less than a reconstruction eighteen months later.

Corrections and version history

When a date of birth is corrected, every age derived from it becomes wrong. A record that lists the source of each date makes that a tractable problem — you can find the affected calculations. A record that lists only results does not.

Where a figure is revised, keep the original alongside the correction with dates for both, rather than overwriting. An audit trail that shows a value changed and why is stronger than one that appears to have always been right.

Worked example

A complete entry reads: DOB 12 February 2018 (from birth certificate on file); assessment date 16 August 2026 (first session, per manual §2.3); chronological age 8;06;04; exact calendar method, no rounding applied; calculated for norm-table selection. Any reviewer can rebuild that from the record alone.

Substitute your own dates and follow the instructions that actually govern your situation. Where a result sits close to a cutoff, verify the underlying date and rule independently before relying on it.

Common mistakes to avoid

  • Recording the result without the reference date. The age is only true on one date. Without it the record cannot be verified and quietly goes stale.
  • Storing a screenshot instead of the values. An image cannot be searched, re-run or corrected. Record the data and keep any link as a supplement.
  • Overwriting a corrected figure. Keep the original and the correction with dates for both. A visible trail is stronger than a clean one.

Use the right calculator

Each of these runs in the browser, states its assumptions, and links to the neighbouring calculation when the question turns out to be a different one.

Chronological Age Calculator
Clinical & AcademicChronological Age Calculatorchronological age on an assessment date
Age on a Date Calculator
Universal ChronologyAge on a Date Calculatorchronological age on a past or future date
Test Age Calculator
Clinical & AcademicTest Age Calculatorcalendar age at the date a test is administered
A note on your inputs: they stay in the tab. The calculation happens in your browser, which is also why the tools keep working if your connection drops mid-session.

Frequently asked questions

How much detail is too much?

Record the five core fields always, and add a note only for anything a reviewer would not assume. Uniform verbosity makes files harder to use.

Should I record the calculation method?

Name it if it is anything other than exact calendar age, and always if a rounding or padding convention was applied.

What if two records give different dates of birth?

Record both, note the discrepancy and its sources, and use whichever the governing authority accepts. Do not silently pick one.