A contact form needs clear labels, server-side validation, spam controls, safe message handling, and a useful confirmation. Never rely on browser validation alone. ## Step-by-step instructions 1. Ask only for details needed to answer the enquiry. 2. Add visible labels and clear required-field instructions. 3. Validate and sanitise inputs on the server. 4. Add proportionate spam protection and rate limits. 5. Send notifications through authenticated email delivery. 6. Test valid, invalid, duplicate, and failed submissions. ## Final checks - Test the result in a realistic situation before relying on it. - Keep a note of any settings or decisions that need future review. - Recheck the process when your tools, hosting, or requirements change.
Developer handover checklist
- Keep source code in version control and document setup and configuration.
- Store secrets outside source code and restrict access to credentials.
- Test important business rules, validation, permissions, and failure paths.
- Log diagnostic details without exposing passwords, tokens, or personal data.
- Document deployment, rollback, backup, and recovery steps.
Verify before deployment
Test changed workflows in staging where possible. Check server logs, browser errors, response codes, and key user journeys after release. Measure the bottleneck before introducing complex optimisation.