Protecting yourself before someone else works on the site.
WHY
Not because developers are untrustworthy, but because changes go wrong and you want a known-good state.
It also protects the developer: a clear before-and-after removes arguments about what broke.
WHAT TO TAKE
A full backup, downloaded to your own computer, before any access is granted.
Note the date. If something is wrong later, you know what the site looked like beforehand.
WHAT ELSE TO DO
Give them their own account rather than sharing yours, so actions are attributable Note what access you granted and when Agree what they will change
DURING THE WORK
Ask them to work on a staging copy for anything substantial.
Take another backup at any significant milestone.
AFTER THE WORK
Take a backup of the completed state Remove the access you granted Confirm in writing what changed
IF SOMETHING BREAKS LATER
You have a copy from before the work, which makes identifying the cause straightforward.
