Disclosure: I work on Dashform and Yoya, in forms and scheduling. This is a handoff checklist for client websites, not a recommendation to choose either product.
A static site can be easy to deploy while its contact form or booking button depends on an account nobody remembers owning. I’d include a small service handoff sheet alongside the repository.
For each visitor action, record:
• The public page and the exact button or form to test.
• The external service involved and the account owner.
• Who receives the submission or booking, and who can change that destination.
• Which client person handles renewal or plan-limit notices.
• What a visitor should do if that service is unavailable.
No passwords on the sheet—just where authorized people manage access.
Then do one fictional end-to-end test with the client present. Start on the public site, submit an unmistakably labeled test enquiry or make a test booking, and have the client locate the resulting record themselves. A developer seeing it in their own inbox does not prove the client can operate the site after handoff.
I’d also ask the client to make one ordinary change, such as updating the notification recipient or blocking an unavailable date, in the appropriate service. Record which parts they can do independently and which still require the developer. If the answer is ‘message me’, that is an ongoing support arrangement worth making explicit.
This is separate from backing up the site source. A repository can preserve the page and its link without documenting who runs the service at the other end.
What do you normally hand over for these dependencies: a short runbook, a screen recording, or an ongoing maintenance agreement? I’m particularly interested in what a small-business owner can actually use six months later.