Part of the issue is that the NOTAMs come from templates, contained within a document called the Contingency Manual. The NOTAM Office just issues the relevant template when requested. They're not 'written' each time, just copy-pasted (hence "INSERT NUMBER" in
this one).
The Contingency Manual is made up of sections, each of which corresponds to an ATC operational group. It's the group's responsibility to keep their section updated, e.g. when key waypoint names change or routes are re-numbered or new routes are created or airspace boundaries change etc. Changes to the maps are supposed to flow through from there.
The contingency arrangements were never designed to be used in the way they are being used at the moment, and the sheer number of these NOTAMS that are being issued means errors happen. Contributing to the problem is that a lot of groups don't have the resources to spare someone from the console to actually carry out the tedious checking, amending and checking of changes needed to update them, so they are in a lot of cases out of date or inconsistent. There's also little commonality between groups - while they might have started out as the same template over time they've diverged more and more, and beyond telling the sectors immediately adjacent to the affected groups, there's no real protocol for notification of the 'big picture' so noone can tell you the extent of things across the entire network. Hence why there are
NOTAMs for delays into Adelaide but not Parafield or Edinburgh.
The staff who looked after these things existed once, but several rounds of redundancies over the last seven or eight years have severely reduced their numbers while loading more admin workload onto the ATC groups. And as many ATCs as possible are needed on the consoles at the moment so any ATCs doing that work are "in the wrong places" (we have enough controllers
)... so it just doesn't get done.