Portal
Set up the customer environment, roles and modules, then coordinate live operational records in the browser. The portal includes an installer and software updater for the supported deployment.
Explore the platform →Deployment & implementation
A successful rollout starts with the way your organisation delivers work. Define the scope, prepare the data, test a real workflow and give each team a clear route into the system.
Rollout path
These stages give operational, technical and commercial teams the same basis for decisions.
Choose a representative programme or job. Map intake, planning, allocation, field updates, evidence, review and closeout. Decide which teams and modules are needed for that first scope.
Agree hosting, domain, HTTPS, backups, administrators and access profiles. Identify the source of employee, customer, job, asset and document data before importing it.
Configure a small group, test the workflow end to end and confirm permissions, data and reporting. Record gaps and ownership before widening access.
Train by role, agree support contacts and launch in stages. Review the first reporting cycle and any failed handoffs, then adjust before adding more teams or programmes.
Ways to work
One deployment can support office, desktop and field working. The right mix depends on devices, roles and the workflow being rolled out.
Set up the customer environment, roles and modules, then coordinate live operational records in the browser. The portal includes an installer and software updater for the supported deployment.
Explore the platform →Plan the supported package and update channel for office devices. Confirm sign-in, uploads and notifications with the teams who will use the desktop workspace.
Explore desktop →Choose the supported Android app or installable Field PWA for assigned jobs and field tasks. Test devices, permissions and connectivity as part of the pilot.
Explore field apps →Multi-region rollout
Choose from the supported portal languages for your teams and agree the terminology they use. Set the deployment timezone and working-day hours, then test the pilot with users in each intended region.
Data & connections
Identify the owner and source of each dataset. Use sample imports to check required fields, duplicates, mapping and permissions before loading the full set.
For external services, agree which system is authoritative, what moves between them and who reviews a failed transfer. Confirm provider setup before making an integration part of day-to-day work.
Before go-live
Next step
Bring a sample workflow, approximate users, existing systems and the first programme you want to control. Stratal can use those details to shape implementation and licensing discussions.