Planning
WBS, approved schedule, calendars and weekly assignments.
Implementation
Agree the workflow, data and acceptance criteria before rollout
For a pilot project, list the workflows, source files, users and approval responsibilities, then run the chain from plan to inspection and payment. The agreed scope, data preparation and integrations are the basis of the rollout plan.
Pilot project / Acceptance planIMPLEMENTATION
01ScopeWorkflow · owners · acceptance
02PrepareSource files · mappings · access
03RehearseWBS → PO → WO → QA → IPC
04AcceptEvidence · issues · agreed scope
Illustrative rollout sequence · not a promised implementation duration.
Phases
Four phases, each with an acceptance result
- 1
Agree the workflow
Choose a project and a complete chain of records. Name who prepares, checks and receives each record, including exceptions such as returned materials, changed drawings or incomplete payment files.
Accepted whenProcess, scope and decision makers agreed
- 2
Data and configuration
Review source files, identifiers, calendars and approval limits. Map imports and integrations, and test faulty and duplicate records too.
Accepted whenTest load and permissions checked
- 3
User acceptance
Run the workflow with the people responsible: through procurement, site, inspection and finance. Check sources, corrections, approvals and permission limits.
Accepted whenResults confirmed, open items listed
- 4
Cut-over and support
Reconcile opening data, walk users through the process and agree how issues are handled. Extend the scope after the agreed scope is accepted.
Accepted whenCut-over list and support owners
Discovery session
Bring the records each team uses today
Procurement and site
A material request, purchase order, receipt, work order and site diary.
Documents and commercial
Drawing revisions, inspection records, payment applications and related invoices.
Organisation and systems
Roles, approval limits, data owners and systems to integrate.
Questions
Before you start
Can we start with one workflow?
Yes. Choose a workflow with clear inputs, handovers and acceptance results, and involve the teams that hold the records before and after it.
How is spreadsheet data moved?
Review representative files, map columns and codes, then test-load and reconcile. Unsupported or unclear data is agreed before cut-over.
What decides the schedule?
Scope, data quality, integration needs, configuration and the time users can give. This website does not replace a project plan or service agreement.
Book a demo with your own project data
Send us a sample schedule, work order or payment file. The demo walks through that process in ACMS with your team.