This article walks you through the key actions your team should complete before your deployment of Forwood One to all users. Following this checklist helps ensure your rollout is smooth and successful.
Start with the end in mind:
1. Define your Success Criteria and KPIs
Why it matters: Clear KPIs help track success and value from day one.
What to do:
Set targets for adoption, usage, and performance
Decide how and when to review results
Document success metrics and share with leadership
When: Before deployment to all users
Who: Internal Project Lead / Senior Management
2. Configure your Forms
Why it matters: Helps frontline teams complete high-risk tasks safely and consistently.
What to do:
Identify top high-risk tasks
Create forms in the system and review with operations
Validate with key users and publish before launch
When: 4 weeks before deployment
Who: Operational Lead / System Admin
3. Test the system
Why it matters: Testing confirms that the system works as expected for your workflows and data. It also validates that you can meet your success criteria.
What to do:
Complete testing for your modules and features in both the portal and mobile app
Test SSO access and make sure it works for representative test users
Validate configuration (taxonomy, forms, any integrations)
Document and fix any issues before launch
When: Start testing 2–4 weeks before deployment
Who: Internal Project Lead + Key Users
Tip: Ask your CSM for testing templates
4. Communicate the Change
Why it matters: Helps teams understand what’s changing, why it matters, and what’s expected.
What to do:
Share a company-wide announcement (video from CEO recommended)
Create and localise materials (e.g. Pre-Start boards, posters, digital signage)
Set up a countdown campaign with clear steps ("7 days to go", etc.)
When: from 4–6 weeks before deployment; with regular communications leading up to deployment date
Who: Internal Comms, Site Leads, Supervisors
Tip: Keep the messaging visual and consistent across all channels.
5. Set up users and access
Why it matters: Ensures the right people have the right permissions from day one.
What to do:
Create user accounts with required roles and permissions
Include contractors or temporary staff if needed
Test login for at least one user per role
Confirm mobile app access for relevant users
When: 1-2 weeks before deployment
Who: System Admin / IT
Tip: you can create users in advanced with status "disabled" and activate prior to deployment
6. Train your Teams
Why it matters: Training builds user confidence and reduces risk.
What to do:
Identify training groups (admins, field users, managers)
Deliver Fundamentals training for managers and superintendents
Delivery in-field training for supervisors and operators
Assign a Forwood One Coach at each site
Record attendance and offer Q&A follow-up sessions
When: Training complete 1 week before deployment
Who: Project Lead / Training Coordinator
7. Monitor with Reports
Why it matters: Forwood One reports help you track KPIs, adoption and fix issues fast.
What to do:
Choose key reports for usage and accuracy tracking
Assign owners and define reporting cadence
Share a reporting schedule with teams
Review reports daily for the first month
When: Starts at deployment
Who: Project Lead, System Admin, Report Owners
🚀 Ready to deploy?
Once all steps above are complete, your team is ready for deployment! Still have questions? Reach out to your Client Success Manager.