Browse all docs
Implementation & integrationsAdminITImplementation
Go-live checklist
Validate access, workflows, integrations, data, and support ownership before launch.
Updated July 22, 2026
Access and ownership
- Production administrators and standard users can sign in with the approved identity provider.
- Disallowed and disabled test users cannot sign in.
- Every user has the intended modules and level of access.
- Access approvals, periodic reviews, and offboarding have named customer owners.
Core lending workflow
- A sample opportunity can move from intake into a deal record.
- The team can add documents, notes, financials, and next steps.
- Underwriting calculations and approval paths behave as agreed.
- Customer-branded decision documents and exports have been reviewed.
- Closing, servicing, and monitoring steps are verified for the modules in scope.
Integrations
- The production intake mailbox forwards only the intended messages.
- A normal message, forwarded thread, and supported attachment complete intake successfully.
- Every enabled Slack workflow reaches the correct channel and any approved action writes back correctly.
- Customer-managed applications and credentials have owners, expiration dates, and renewal procedures.
- Any optional integration not ready for launch is clearly excluded from the production plan.
Data and controls
- Imported record counts and key totals reconcile to the approved source.
- Duplicates, rejected rows, and remaining corrections have named owners.
- Retention, deletion, document handling, and support procedures are documented.
- Users know not to place credentials or unnecessary borrower information in support messages.
Training and support
- Each team has practiced the workflows and modules it will use.
- Administrators know how to invite users and request configuration changes.
- The support channel, escalation path, and incident contacts are confirmed.
- The first adoption and data-quality review is on the calendar.
Approve launch
Record launch approval from the customer implementation owner and the Bridgewerks implementation lead. Include the production date, known exceptions, owners, and due dates.
If a critical access, data, calculation, or intake test fails, pause launch until it is corrected and retested. A documented exception is appropriate only when the customer owner understands the impact and explicitly accepts it.