Loading...
Loading...
Annual report microsite
Turn the approved report into accessible web pages. Give readers searchable text, usable tables and the official document in one place.
Three routes
The right route is the smallest one that meets your date. I mark the standalone microsite because it needs the least from your current site. Send your publication date first. If a route is too close to that date, I say so and name the smaller one.
You have a site your team already edits. I add the report section, the document area and the year archive to it.
Scoped in writing after the inventory.
You want the report on its own address or subdomain. I build it and test it against your fixed publication date.
Scoped in writing after the inventory.
You report every year and want no new agency project next time. It adds a documented layout library, an archive pattern, an editor guide and a practice run for your team.
Scoped in writing after the inventory.
Who does the work
Scope
The process
After the inventory, I send the scope, approval points and publication plan in writing. Work starts after you approve them.
I list the sections, tables, charts, documents and languages. We agree the fixed date, the named approver and whether AI goes on at all. The default is off.
Output: A section map, a document list, the control rules and my route recommendation.
I set up the blocks, the tables, the charts, the archive path and a private staging site. I load the approved sections and documents. You check every number against the signed PDF. I then test accessibility, links, downloads and year paths.
Output: A complete staging report, a visible change log and an acceptance checklist.
I publish after the named approver releases the report, check the live pages and hand over the editor guide.
Output: A live report, an editor guide, a rollback point and next year's archive plan.
If you want AI in it
Your comms team edits this report site. The site works with AI switched off. If you include it, these controls become acceptance requirements in the written scope.
Safeguards
A fixed publication date, pre-release numbers and legal documents carry the risk on this job. Here is what controls each one.
Questions
No. The site is the readable layer beside them. Your advisor confirms which file discharges the filing. Tagging stays with a specialist.
Your company secretary sets access rules for pre-release figures. The written scope names who can see staging and when real figures are loaded.
I build and test to WCAG 2.1 AA, with automated tools and a screen reader. Those checks sit in the written scope. An independent audit is available as extra work.
Your advisor names the standard that applies. The written scope names the version, tests and acceptance evidence.
If two languages are in scope, both versions are tested before publication. You supply approved translations. The scope names one release process for both.
Late change is normal on a report, so the build assumes it. Content sits in fields, not in artwork, so a change is an edit. We agree the cut-off in step 1. Edits up to that cut-off are part of the agreed scope. After it, we make each change together, and the log shows who changed what.
I accept a fixed-date release only when the written scope names a vetted fallback developer. If cover is unavailable, I do not accept the date.
You get a written scope with a payment schedule and my company details, in the format your finance team needs. I invoice against that schedule, not against hours. Anything outside the scope is agreed in writing before it starts.
That is the purpose of the reusable route. The scope includes the approved blocks, archive pattern, editor guide and account handover.
It stays live at its own year path. The new report goes to a new path. The old links are checked before launch, and the redirects sit in the acceptance checklist.
Yes. The documents get their own area and a checked URL list. The check runs before every release in the window, so a release cannot drop one of those URLs. The window and the check both sit in the written scope.
Send last year's PDF, the approved publication date and the accessibility standard your advisor named. I return the route, risks and approval points in writing.
Send me last year's report PDF