I tend to agree, there's not a "one-size-fits-all" structured form that fits every submission you're bound to get.If we designed structured data forms, we're very likely to overwhelm submitters or confuse them. It is hard to design structured data forms for everyone that works well.
That said, I personally created a text layout in Microsoft Word that I use to create my submissions, and then copy-and-paste the result into the text submission form. This way I make sure I haven't missed a detail, but yet it is easy enough for the database admin that's working it to read and follow. It's not perfect (when I copy-and-paste there's some formatting that goes askew, but that's easy to fix before I click submit), but again, I'm trying to avoid seeing a system get posted and then realizing that I missed an important detail.
On another note, when looking at the County level page, you have the link to the Trunked Systems page, but if a Trunked System was recently updated the link to the trunked systems page is not highlighted, but once you go to the Trunked Systems page, the individual trunked system is highlighted. This means that if the history page is not followed (or there's so many changes the history rolls off), that trunked changes could get lost if one doesn't specifically drill down to the trunked system page.
RRDB 1.x County page:
RRDB 2.0 County page:
RRDB 2.0 Trunked System page:

