How to Create a Go-Live Deployment for Hospitality & Tourism
A controlled procedure for deploying event deliverables into the production or live environment, including pre-deployment checks, execution, validation, and rollback planning.
Purpose
To ensure that deployments to the live environment are executed in a controlled, predictable manner with minimal risk of disruption, and that clear rollback procedures exist if issues are encountered.
Scope
Covers the go-live deployment process from the final pre-deployment preparation through to the post-deployment validation and stabilisation period.
Prerequisites
- Acceptance testing has been completed and formal acceptance obtained
- Deployment plan and rollback plan have been prepared and reviewed
- All required approvals for the production deployment have been obtained
- Communication to affected stakeholders and end users about the deployment has been sent
Includes food safety compliance (HACCP), RSA requirements, liquor licensing documentation, and tourism accreditation record keeping.
Step-by-Step Procedure
Conduct Pre-Deployment Checks
Perform all pre-deployment verification steps to confirm readiness, including environment checks, backup verification, and team availability.
- 1.1Verify the production environment is in a known good state and all prerequisites are met
- 1.2Confirm that a current backup of the production environment has been taken and verified
- 1.3Verify that all deployment team members are available and aware of their responsibilities
- 1.4Confirm the rollback procedure has been tested and can be executed if needed
Notify Stakeholders of Deployment Start
Send formal notification to all affected stakeholders and end users that the deployment is about to begin, including expected timeline and any service impacts.
- 2.1Send the pre-deployment notification to the agreed distribution list with the expected start and end times
- 2.2Activate any planned service notification banners or maintenance pages if applicable
Execute the Deployment
Carry out the deployment steps according to the approved deployment plan, documenting each step and its outcome.
- 3.1Execute each deployment step in sequence as documented in the deployment plan
- 3.2Log the start time, end time, and outcome of each step
- 3.3Monitor for errors or unexpected behaviour at each step before proceeding to the next
- Have the rollback plan readily accessible and designate a team member to initiate it if the go or no-go decision is to roll back
Perform Post-Deployment Validation
Execute a defined set of validation checks to confirm that the deployment was successful and the live environment is functioning correctly.
- 4.1Run the post-deployment smoke test suite to verify core functionality
- 4.2Check system monitoring dashboards for any error patterns or performance anomalies
- 4.3Have key end users perform critical business processes to confirm operational readiness
Make the Go or Rollback Decision
Based on the post-deployment validation results, make a formal decision to confirm the deployment as successful or initiate the rollback procedure.
- 5.1Review the validation results with the deployment team and event manager
- 5.2If all checks pass, formally confirm the deployment as successful
- 5.3If critical issues are identified, initiate the rollback procedure according to the pre-approved plan
Notify Stakeholders of Deployment Outcome
Communicate the deployment outcome to all stakeholders, confirming success or explaining any issues and the actions taken.
- 6.1Send the post-deployment notification confirming the outcome to all stakeholders
- 6.2Include any known issues, workarounds, or follow-up actions in the notification
- 6.3Deactivate any maintenance pages or service notification banners
Monitor the Stabilisation Period
Maintain enhanced monitoring of the live environment during the defined stabilisation period to catch any issues that were not immediately apparent.
- 7.1Keep the deployment team on standby during the agreed stabilisation period
- 7.2Monitor system performance, error logs, and user-reported issues with increased frequency
- 7.3Resolve any emerging issues promptly and document them in the deployment log
- Define clear escalation criteria during the stabilisation period so the team knows when to escalate versus handle issues independently
Quality Checkpoints
Common Mistakes to Avoid
Expected Outcomes
Percentage of go-live deployments that proceed without requiring a rollback, indicating the reliability of the deployment process
Number of incidents raised during the stabilisation period following each deployment, measuring the quality of pre-deployment preparation
Total duration of service unavailability during the deployment process, measured against the planned deployment window
Frequently Asked Questions
How long should the stabilisation period last?
The stabilisation period typically lasts one to five business days depending on deployment complexity and risk. During this time, the deployment team remains on standby and monitoring is enhanced. For critical systems, a longer period with on-call arrangements may be appropriate.
When is the best time to schedule a go-live deployment?
Schedule deployments during periods of low user activity to minimise disruption. This varies by organisation but is often early morning, evening, or weekends. Avoid deploying on Fridays unless the team is available for weekend support, as issues discovered over the weekend may go unresolved until Monday.
What triggers a rollback decision?
Rollback should be triggered when critical business processes are non-functional, data integrity is compromised, or security vulnerabilities are introduced. The criteria should be defined in advance as part of the deployment plan. Minor cosmetic issues or non-critical defects typically do not warrant a full rollback.
Want this customised for YOUR business?
We'll tailor every step to your exact operations, tools, and team structure.