Setup and handover checklist

Audience: the administrator responsible for a new setup or handover. Outcome: an agreed record of what is installed, configured, tested and assigned. This is a product setup checklist; hosting, credentials and implementation details are handled privately with the responsible person.

1. Confirm the scope and product baseline

Record the union’s live website, any review website and the person approving changes. Confirm UnionWP and UnionWP Pro versions in the installed-plugin list or the product’s details. Pro requires active UnionWP.

List the actual workflows and connected services in your agreement. A preview or available module does not prove it has been configured. Check Products and availability for the documented baseline and planned features.

Arrange installation, migration and updates through the responsible administrator. Deactivating Pro can remove the runtime controls used by existing forms and integrations. Keep the existing dependencies and independent membership delivery safeguards in place during a handover.

2. Confirm accounts and ownership

Identify who can submit staff requests, review private records, publish public content and manage Pro settings. Give each person the appropriate sign-in and tool links. Record the contacts responsible for mail delivery, hosting, monitoring and security.

Have staff follow Sign-in and access. A staff account does not automatically need administrator privileges.

3. Review existing forms and mappings

1. List the existing membership and optional forms by title and identifier.
2. Confirm the protected membership mapping and published contact fallback.
3. Review form pages, anchors and disabled-form behavior using Map forms and pages.
4. Review the master and individual choices in Form Controls.
5. Inspect the public page and contact fallback without submitting live records unnecessarily.
6. Record which optional forms are intended to be open at handover.

Mapping does not create or publish a form. Shared pages need their existing content and section behavior preserved.

4. Verify notifications and reports

Review staff alerts, approved recipients and independent application email routing. Use a coordinated synthetic or controlled workflow test only when needed. Record what was actually verified: connection acceptance, receipt or complete submission handling.

Open Email Delivery, Site Insights, Backups and Uptime, and Security. Confirm the correct website, connection and timestamps. Assign any missing setup to its owner rather than treating a visible card as completed configuration.

SMS and credit purchases remain unavailable. Do not include an active SMS balance, campaign capability or checkout in the handover.

5. Complete the handover record

Record approved tool links, owners, active/paused forms, recipient responsibilities, tested outcomes, remaining setup and the support route. Keep credentials and private application data out of the public record.

Ask a staff user to complete an appropriate first task using First-day checklist. The handover is useful when that person can find the correct tool, complete the task and recognize the expected result.