Insurance site audit, delivered as developer task sheets

The problem

An Australian insurance company needed a full audit of their WordPress site — built on GeneratePress with Gutenberg blocks and RankMath for SEO — but the audit had to be usable by their own development team, not just by me. A long narrative report is easy to write and hard for someone else's engineers to act on.

What I built

I audited the site end to end — theme configuration, block structure, SEO setup, and the usual list of performance and accessibility gaps that accumulate on a site maintained by more than one team over time. Instead of writing up the findings as a single report, I delivered them as prioritized developer task sheets: discrete, actionable items ordered by priority, each scoped so a developer unfamiliar with the audit could pick one up and complete it without needing to read the whole document first.

Outcome

The client's own team received a task list they could work through directly, rather than a report that would have needed a second pass of interpretation before anyone could start fixing anything.

Why it mattered

An audit is only as useful as what happens after it's delivered. Structuring the findings as task sheets rather than prose was a deliberate choice to hand off work cleanly to someone else's team — proof that the output of an engagement can be built for the client's engineers to execute, not just for the client to read.