Create a before-and-after report for a WordPress job

Take the baseline before starting

Copy the Site Health Info export before the work and keep it privately with your project records. Take a second export after the work. If you only have the later export, produce a state record; do not invent a baseline.

Compare the two records

Import the later export into Handoverdesk. Expand Add a before / after comparison and paste the baseline. The tool compares recognized versions, the active theme, selected environment values and plugin inventory states.

An item only in one export is labeled Not listed in the other. Incomplete sections are not treated as removals. A plugin display name can change or collide, so inspect unusual entries manually.

Explain the work in client language

Write a short description of the task, what you performed and any tests actually completed. For example: “Updated the agreed components, checked the contact form, and recorded the resulting configuration.” Only use that wording if you performed those actions.

Keep the technical comparison as supporting detail. It shows observed differences between supplied inputs, not an independently verified activity log.

Avoid overclaiming

A version difference does not identify the person responsible, prove causation or establish that a defect is resolved. File edits, page content, many configuration settings and work between the snapshots may not appear.

Keep the report alongside your work notes and any actual test results. Use your existing agreement for acceptance and billing. This report does not provide legal protection.