15 / 20 Other national variants
How is a national timetable tracked?
Published Updated
Statistical classification only
Statistical classification only. This guide does not determine any reader's code. Confirm a code with the national statistical institute or the business register that holds the record. This is general information, not advice on any reader's registration.
A national timetable is tracked from the institute that publishes it, by checking the institute’s own pages for the classification, the register, and the statistical outputs, and by recording what each page states, with its date. A timetable has three parts that must be tracked separately: the date on which the classification takes effect, the date on which register entries change, and the dates on which statistical outputs move, domain by domain. Those three dates are often different, and a timetable that gives only one of them is incomplete.
A reader who tracks a timetable should record all three, with the source page for each, and should recheck the pages at intervals, because timetables are amended, and because a page checked at one date may be superseded by a later page. A timetable copied from a secondary summary, without checking the institute page, is not a tracked timetable. It is a rumour with a date attached.
What pages are checked?
Three kinds of institute page are checked. First, the classification page, which states the name, the version, and the in force date, and which publishes the structure, notes and correspondence tables. Second, the register page, which states how entries are checked, corrected, or rewritten, and on what date. Third, the statistical output pages, which state the version used in each publication, and which may state a domain timetable for the move to the new version. The European timetable, from 1 January 2025 to 1 January 2031 (FIXED range) depending on the domain, governs data transmission to Eurostat, and it is the background against which national output timetables sit. National register timetables sit separately, and they differ: France from 1 January 2027 (FIXED) for register entries, Slovenia from 1 January 2025 (FIXED) for its register, Ireland from January 2026 (FIXED) for gradual output implementation. A tracked timetable records each date with its source, and never merges register and output dates into one.
| Timetable part | Source page | What to record |
|---|---|---|
| Classification in force | Institute classification page | Name, version, in force date |
| Register entries | Register page, or institute page describing the register | Check route, correction route, change date |
| Statistical outputs | Publication notes, domain timetable | Version per publication, domain date |
The table above is a tracking checklist. It names no timetable beyond the verified examples in the body, because each country’s timetable must be checked on its own institute pages.
How is an unchecked timetable reported?
An unchecked timetable is reported as unchecked, with the words that state the position plainly. For Portugal, this cluster states that no timetable was stated on the INE pages checked. For Austria, this cluster states that no timetable was verified on a Statistics Austria page fetched for this work. For Poland, this cluster states that no timetable was verified against GUS, and that secondary dates must not be presented as the institute’s position. Those statements are the correct form for an unchecked timetable. They tell a reader what is known, what is not known, and where to check. A guide that filled the gap with a secondary date would look more complete and would be wrong. A guide that states the gap looks less complete and is honest. Honesty is the point of a register: a missing entry is recorded as missing, not invented. The same rule applies to a missing timetable. The check date, 28 October 2026, is the date on which the pages were checked for this work, and it is stated in the guides where a timetable is reported as unchecked, so that a reader knows when the check was made.
How often should a timetable be rechecked?
A timetable should be rechecked when a new institute page appears, when a register notice is published, when a statistical publication states a new version, and at least once a year, because classifications are revised rarely but timetables are amended more often. Eurostat amends domain dates through later regulations, as Destatis shows for the German introduction, and national institutes amend their own plans as implementation proceeds. A recheck should record the new page, the new date, and the old date it replaces, so that a reader can see the history of the timetable, not only its current state. A timetable without a history hides amendments, and a reader who relies on an old copy will miss them. The recheck should also confirm that the classification version has not changed: a new timetable for the same version is an amendment, while a new version is a new classification, with a new structure, new notes, and new correspondence tables.
What does tracking a timetable not decide?
Tracking a timetable does not decide the code for any reader, and it does not decide tax, licensing, funding or collective agreement questions. It records when a classification takes effect, when entries change, and when outputs move. The entry for a specific unit is confirmed with the institute or register that holds the record, on the date the entry is checked. This site holds no register and decides no entry. A timetable is a set of dates with sources. It is not an obligation, and a reader should not treat a statistical or register date as a deadline for action by a business, unless the institute or register states it as one, in its own words, on its own page.
Track the three parts separately from institute pages, record the source and date for each, report an unchecked timetable as unchecked with its check date, and recheck when a new page or publication appears.