Plus2 Resource Build QA and Go-Live Handover

Problem

Before bookable resources go live, the build team needs to build them in the right order, check every resource, block booking and site against a checklist, and hand ownership over to the site.

Resolution

1. Follow the build sequence

   • Build the resource hierarchy before any live bookings, in this order:

     Confirm site + naming standard → create/copy calendar (if used) → create resource products
     → create booking sheet (resource product group) → add products → verify display and availability
     → test booking → approve for live use

   • Test in the test database before applying to live.

2. Check each resource

   • Correct site is active
   • ID follows the naming standard
   • Description is clear and customer-ready
   • Site group is correct
   • Calendar and standard-week hours are correct (independent calendars where the site uses them)
   • Bookings resource type is correct
   • On the right booking sheet, in a usable order
   • A test booking succeeds in an open slot and fails in a closed one

3. Check each block booking

   • Right account, dates, recurrence, exclusions, all resources and no extras, billing, approved credit limit, product, quantity, price, tax not assumed exempt, full series visible, conflicts resolved before confirming.
   • For Go Operator block bookings, also confirm the billing grouping period and itemisation before creating, as they can't be changed.

4. Check multi-site set-up

   • Site prefixes are documented and unique
   • Shared products are intentionally shared
   • Site-specific products can be managed independently
   • Descriptions expose nothing internal or customer-specific
   • Changes tested at every affected site

5. Hand over before go-live

   • Publish the approved naming convention.
   • Record which calendars are shared and which are independent.
   • Assign owners for creating resources, calendars, booking sheets and block bookings.
   • Train staff to check the active site before changing anything.
   • Train finance on cost centres, departments, invoicing, credit limits, tax treatment and the finance extract.
   • Name who approves credit-limit and tax overrides.
   • Provide a controlled test script for new configurations.
   • Keep a change log of renamed, copied, closed or retired resources.

Notes

• The full block-booking checklist is in Block Bookings (Plus2 Hosted Reservations) and Invoicing; Go Operator block bookings are covered in Block Bookings in Go Operator (Centre Management).
• Related: Naming Conventions for Plus2 IDs and Descriptions; Configuring Multiple Sites in One Plus2 Database; Creating Resource Products in Plus2; Creating Booking Sheets in Plus2; System Specification – Building a New Site.

This page as markdown · All pages · llms.txt