Resources

Implementation templates

Readiness checklist, data-ownership matrix, and go-live acceptance checklist referenced during a Forge launch.

Readiness checklist

What a Blueprint conversation confirms before a launch is scoped, regardless of which launch path you choose.

Current-software inventory — every system in use today, with monthly cost, active users, and overlapping capability noted
Named owner for each system slated to connect, consolidate, or be retired
Access confirmed for each system that needs to connect (API credentials, admin access, or export capability)
Existing data cleaned or flagged for migration — duplicate contacts, stale records, inconsistent statuses
A decision on Guided Launch vs. Managed Launch for your team

Data-ownership matrix

The same source-of-truth principle applied per launch, stated as a checklist item rather than a table: for every connected system, confirm which side is authoritative before go-live.

Which system remains the authoritative record for this data domain after launch?
Does The Forge read this domain, write to it, or both?
What happens on a conflict — which side wins?
Who is notified when a sync fails for this domain?
Is this domain regulated or otherwise restricted from leaving its system of record?

Go-live acceptance checklist

Confirmed before a Managed Launch is called complete, or before a Guided Launch milestone is approved.

Every in-scope system is connected at its agreed setup classification
Customers, jobs or accounts, staff, and history have been migrated and spot-checked
Role-based access matches the org chart confirmed during the Blueprint
Existing systems remain available and unaffected until the customer approves the switch
Reporting and dashboards reflect the connected operating view, not partial data
Training completed for the roles who will use The Forge daily

Launch paths

Both templates above apply under either launch path — the difference is who executes each item.

Guided Launch: Work through a structured launch and earn Forge Credits as your team completes each onboarding milestone.
Managed Launch: You provide access, context, and approvals. Our team configures, connects, migrates, tests, trains, and launches The Forge remotely.

Implementation overview Forge Blueprint Forge Blueprint scope

More resources

Forge Core — plan documentation Forge Pro — plan documentation Forge Operations — plan documentation Integration guide Security documentation All resources

Have a question this page doesn't answer?

Get My Forge Plan Start My Blueprint

The $500 Blueprint credits toward implementation if you move forward within 30 days.