| 1 | Approve the page purpose, audience, site relationship, pathways, non-recruitment boundary, brand, privacy, analytics, accessibility, security and content ownership. | Digital lead and club board sponsor | Eight weeks before launch | A controlled reconnect-page charter |
| 2 | Verify each offered pathway with its owner, conditions, participant limit, next step, response time and expiry and remove anything the club cannot currently support. | Content custodian and pathway owners | Six weeks before launch | A current reconnect pathway register |
| 3 | Draft a short page around visitor questions, with clear choices for social, service, updates, rejoining and no further contact and no claim that one route suits everyone. | Content designer and former-member adviser | Five weeks before launch | A human, choice-led page draft |
| 4 | Build the page and forms with semantic structure, keyboard access, readable contrast, meaningful links, clear errors, minimal data, no preselection and equivalent telephone or offline action. | Web editor and accessibility checker | Three weeks before launch | An accessible functional page |
| 5 | Test every pathway, form, notice, response, account permission, device view and failure case with former-member and accessibility testers and fix all blocking issues. | Independent testers and response owners | Before launch | A passed content, access and response test |
| 6 | Publish under approved ownership, monitor response service and errors, review content monthly, remove expired pathways and complete correction, withdrawal, retention and annual governance checks. | Content custodian and club board sponsor | Monthly and annually | A current, supported and governed page |