Handling WordPress projects: audits, scope and hand-over
Run a site audit, report findings by urgency, manage a project from discovery to care, handle changes and problems, with a real scripted audit.
In this lesson you will
- Run a site audit
- Write a client report
- Manage project stages
- Handle scope changes and problems
About 17 minutes
Starting from the facts, not the feelings
A client says, ‘My site is slow and I think it was hacked.’ What do you do first? A professional does not start fixing; she starts by looking. A repeatable site audit turns a vague worry into a list of facts. It also makes a handover document, shows the client what you found and gives you a base to price the work. This lesson teaches the audit and the way a project should flow.
A scripted audit, run for real
A short script asked the test site twelve questions that an auditor would ask: search visibility, permalinks, plugin and theme counts, administrators, the default ‘admin’ username, HTTPS, stored revisions, autoloaded options, drafts, pending comments and the file editor. The output is real:
Search visibility WARNING: discouraged
Permalinks OK (/%postname%/)
Plugins 3 installed, 1 active -> 2 inactive to review
Themes installed 4 (active: Skills in Minutes)
Administrators 1 OK
Default "admin" username WARNING: exists
HTTPS site URL WARNING: not https (fine on a local test)
Revisions stored 219 rows
Autoloaded options 127 options
Drafts waiting 0 posts
Pending comments 0 to moderate
File editor disabled OK
checks run: 12
Read it as an auditor. Search visibility is discouraged, which is correct for a development copy and wrong for a live site. Two of three plugins are inactive and worth reviewing. The ‘admin’ username exists, which is a small warning because attackers guess it first. The site is not on HTTPS, which is fine on a local test but a clear fail on a live one. Hundreds of stored revisions suggest tidying. Some findings are about the test site itself, and a good audit says so: context decides whether a result is a problem.
What to check besides the numbers
- Speed, using a tool, on the home page and a typical inner page.
- Mobile layout on a real phone.
- Forms: send a test message and an order if there is a shop.
- Broken links and missing images.
- Backups: exist, recent, and restorable.
- Accounts and ownership: domain, hosting, email and the WordPress admin.
- Policies: privacy, cookies, terms, returns.
The life of a project
| Stage | Output |
|---|---|
| Discover | Goals, audience, scope, audit |
| Plan | Pages, features, timeline, price |
| Build | Staging site, content, features |
| Test | Checklist on phones and browsers |
| Launch | Go-live steps, backups, monitoring |
| Care | Updates, reports, improvements |
Keeping a project under control
- Write the scope in plain words and get it agreed.
- Break the work into small tasks with dates.
- Use one shared place for files, passwords (in a password manager) and decisions.
- Review progress every week with the client.
- Log every change request, and say what it costs in time.
- Test on staging; launch at a quiet hour with a backup ready.
- Hand over: logins, guide, backup plan and care options.
When things go wrong
- Client changes the scope: record the change, price it, agree it.
- Client is silent: send a polite reminder with a deadline from your agreement.
- A launch error: roll back to the backup, then fix on staging.
- A hack: contain, restore, clean, find the cause and report honestly.
- Disagreement: return to the written scope and the facts.
Reports clients understand
After an audit, write one page: what you checked, what you found in three colours of urgency (fix now, fix soon, nice to have), what you recommend and how long each item takes. Use plain words. A clear report wins more work than a clever technical one.
Practice
Run the audit by hand on a site you know, using the twelve questions above. Write the one-page report with urgent, soon and later items. Estimate the time for each and add up a price using your own rate.
Most audits reveal the same quiet issues: old plugins, weak access control and no tested backup. Fix those first, since they cause the most damage for the least effort.
Fixing before diagnosing. You may change the wrong thing and lose the evidence. Audit first, then plan.
A sample one-page audit report
| Urgency | Finding |
|---|---|
| Fix now | Two outdated plugins with known problems |
| Fix soon | No tested backup; admin username guessable |
| Nice to have | Old revisions; large images on the home page |
Under the table, write one plain sentence for each row: why it matters and how long it takes. Close with a price range for fixing everything, and a clear next step such as ‘reply yes and I will start Monday’. Short reports are read; long ones are filed away.
Handling a hacked site calmly
If the site is already compromised, keep notes of every step, change passwords, restore a clean backup if you have one and look for unknown administrators and unfamiliar files. Tell the client what happened in plain words, and describe what you changed so it does not happen again.
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What should come first on a troubled site?
- Deleting plugins
- A redesign
- A new host
- An audit of facts
Diagnose before fixing.
Which audit result is expected on a local test site?
- Missing backups on a shop
- Not on HTTPS
- Search visibility discouraged on a live site
- Weak admin passwords
Context matters.
What belongs in a report to a client?
- Only technical terms
- Only screenshots
- Findings by urgency, with advice and time
- Nothing
Plain words win.
What do you do when scope changes?
- Record, price and agree the change
- Ignore it
- Work for free quietly
- Delete the scope
Written scope protects both.
Where should you test before launch?
- On the live site
- On nobody’s site
- On a staging site
- In email
Launch with a backup ready.
Summary
- Audit first, then plan.
- Report by urgency in plain words.
- Test on staging, launch with a backup.
- Control scope in writing.
Questions
How long should an audit take?
A first pass on a small site takes one to two hours. Bigger sites take longer.
Should I fix things during the audit?
No. Report first, agree the work, then fix on staging.
What tools help with projects?
A simple task board, a shared folder and a password manager are enough for most small projects.
