Quick answer
Read 8;06;04 as eight completed years, six completed months and four days. Never treat the separators as decimal points, and follow the manual's padding convention.
Three fields, not one number
The semicolon format exists because chronological age is three separate counts, not a single quantity. Years, months and days each roll over on their own schedule, and none of them converts cleanly into the others. Writing them as distinct fields keeps that structure visible.
The most consequential misreading is treating the format as decimal. 8;06;04 is not 8.64 years and not 8.06 years — it is eight years, six months and four days, which is roughly 8.51 in decimal terms. A record that has been silently decimalised is very hard to detect later, because the number still looks plausible.
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 Pearson Age Calculator or the Assessment Age Calculator.

Padding conventions differ
Some manuals require two digits in the months and days fields, giving 8;06;04. Others accept 8;6;4. A few use a hyphen or a colon instead of a semicolon. None of these is more correct in general; what matters is matching the instrument you are scoring against, because the scoring table is indexed that way.
Where you control the record — a case file, a spreadsheet, an internal template — pick one convention and hold it. Mixed padding within a single dataset is a reliable source of sorting errors and of values that fail a later import.
What the days field means
The days field is the remainder after complete months have been counted, so it ranges from 0 to 30 depending on the length of the boundary month. It is not a thirtieth of a month, and it does not represent a fixed fraction.
This is why the borrow step in manual calculation produces so many errors. Borrowing a flat thirty days when the boundary month has 28 or 31 gives a days field that is off by up to two, which is enough to matter near a band boundary. Calendar-aware arithmetic uses the real length of the month being borrowed from.
Storing it so it stays usable
A Y;M;D value alone is not reproducible. Store it with the date of birth, the reference date and the name of the instrument or purpose it was calculated for. Those four together let any reviewer recreate the number without asking you.
For anything that will be sorted, filtered or analysed later, store the two source dates as proper date fields and derive the Y;M;D string for display. A text field holding "8;06;04" sorts alphabetically, which puts 10;00;00 before 8;06;04 and will eventually cause a problem.
Worked example
A second record: borrowing across February
A child born 20 December 2017, assessed on 10 March 2026, is recorded as 8;02;18. The years field is 8, to 20 December 2025. The months field is 2, to 20 February 2026. The days field is the 18 days from 20 February to 10 March. Worked by hand, the days column is where this record earns its keep: 10 minus 20 will not go, so a month is borrowed — and the month being borrowed is February 2026, which has 28 days, not 30. The borrowed sum is 10 plus 28 minus 20, which is 18. A flat thirty-day borrow, the shortcut the earlier section warns against, gives 20: a days field wrong by two, produced by the commonest version of the commonest error in this format.
The cross-checks agree. The interval is 3,002 days, which divided by 365.2425 gives a decimal age of about 8.22. Hold that against the misreadings of the string: read as 8.02, the record understates the child by about a fifth of a year; read as a decimal straight off the digits, it invites a figure near 8.218, close to the truth here only by coincidence of these particular digits. Neither misreading announces itself, which is the recurring theme of this format — the errors are silent because every version of the number looks like a plausible age.
The same record family shows the opposite days-field behaviour. A child born 31 May 2020, assessed on 30 June 2026, is 6;01;00. The month completes by clamping — 31 May plus one month is 30 June, the last day available — so the days field is 00 even though thirty days separate the two dates at that step. A days field of 00 does not mean the dates were adjacent, and a days field in the high twenties does not mean an error: both are ordinary outputs of calendar arithmetic at month boundaries.
The band boundary is where these small errors stop being academic. Norm tables are commonly banded in six-month steps, so take a boundary at 8;06;00. The child in this guide's worked example, at 8;06;04, sits four days inside the band above it. A second child, born 14 February 2018 and assessed on the same 16 August 2026, is 8;06;02 — two days inside the same band. Score that second record with a three-day borrow error and it reads 8;05;30, below the boundary, in a different band, compared against a different norm group. Nothing about the child changed; a borrowing slip in a February-adjacent subtraction moved the comparison group. This is why the days field, the smallest-looking of the three, is the one the format exists to protect.
Reading a calculator result against a hand-kept record: the Chronological and Pearson age calculators on this site borrow with real month lengths, so where a paper record and the tool disagree by one to three days in the days field only, suspect the paper record's borrow before suspecting the tool — and check which month was borrowed, because a February or a 31-day month in that position explains the whole gap.
Common mistakes to avoid
- Reading the separators as decimal points. Y;M;D is three counts, not one number. The decimal equivalent is materially different and the error is invisible once copied.
- Swapping the months and days fields. 8;04;06 and 8;06;04 are two months apart. Confirm field order against the manual before transcribing.
- Borrowing a flat thirty days. Borrow the real length of the boundary month, or the days field can be wrong by up to two.
Use the right calculator
Chronological Age Calculator gives age on an assessment date, Pearson Age Calculator formats calendar age for Pearson-style workflows, and Assessment Age Calculator gives age on a testing date.
Frequently asked questions
Is Y;M;D a standard?
Not a formal one. It is a widely used convention in assessment practice, with padding and separator details varying by publisher.
How do I convert Y;M;D to a decimal age?
Calculate the decimal separately from the two source dates rather than converting the string. Converting introduces an approximation the original did not have.
Should the days field ever exceed 30?
No. Once it reaches the length of the boundary month it becomes another complete month. A value of 31 or more indicates a calculation error.


