Autodesk Forma Implementation — Getting Your Whole Team Actually Using It.
Your Autodesk Forma environment is built. The licences are active. The workflows look right on paper. But three weeks into the first live project, your site team is back on WhatsApp, your subcontractors are emailing drawings and two senior engineers never logged in. That is not a configuration problem. That is an implementation problem — and it is a completely different service from customisation. Accienta manages the full journey from a correctly built environment to a team that cannot imagine delivering a project without it.
Six Things Implementation Handles That Customisation Never Touches
This is where most GCC firms lose money — they pay for customisation, call it an implementation and wonder why their team reverted to email and WhatsApp within three weeks. Customisation builds the right environment. Implementation is everything between "the environment is built" and "every single person in your project team is using it without being chased."
Data migration from wherever you are right now
Your team has project data somewhere — SharePoint, shared drives, Aconex, ProjectWise, email chains or a combination of all five. Customisation builds where that data needs to go. Implementation moves it there — auditing the existing library, cleansing duplicate and superseded files, mapping the old structure to the new one and migrating every drawing, specification, RFI record and correspondence item without disrupting live delivery. A perfectly configured Autodesk Forma folder structure is useless if your team's five years of project history is still in SharePoint.
Customisation creates the destination. Data migration is the active, managed process of moving thousands of real files from real legacy systems into that destination — a separate operation requiring audit, cleansing and verification.
Getting subcontractors and consultants into the platform
Your Forma environment is configured with permission levels for 40 engineers, 20 subcontractors across 8 trades and 3 consultant firms. Customisation set those permission levels. Implementation gets every individual from every company actually onboarded — inviting users, walking subcontractors through the access process, resolving login issues and ensuring every external party knows what they are expected to do, where and by when. The subcontractor who keeps emailing drawings because they find the portal confusing is an implementation problem. Customisation cannot fix a human who was never properly shown how to use the platform.
Customisation creates the subcontractor access portal. Implementation gets the subcontractor actually using it — a people-management challenge that correct configuration alone cannot solve.
Managing the team members who do not want to change
In every GCC project team there are engineers who have worked the same way for fifteen years and see no reason to change. Customisation builds the right workflows. Implementation manages the resistance — identifying who is not adopting, understanding why, addressing specific concerns and working with project leadership to establish that using the new platform is an expectation, not a suggestion.
Customisation cannot change human behaviour. Identifying resistance, building internal champions and making adoption expected are implementation functions — they require people management, not platform management.
Active monitoring during the first live project cycle
Most GCC Autodesk Forma deployments fail not at go-live but in weeks two to six of the first live project — when project pressure increases and the team starts reverting to tools they know. Customisation is finished before this happens. Implementation continues through the first live cycle — monitoring platform activity, identifying who is and is not using the configured workflows, intervening when reversion patterns emerge and resolving the specific friction points causing non-adoption before they become permanent habits.
Customisation is complete before the first user logs in. Everything that happens after go-live — monitoring, intervening, resolving reversion — is exclusively an implementation responsibility.
The outcome review — did it actually work?
After the first live project cycle, Accienta and your team measure what the implementation actually achieved — did RFI response times improve, is snagging running faster, is the team using the platform without workarounds? This review produces two outputs: documented evidence of improvement for your management and a plan for the next phase based on what live project delivery taught your team.
A customisation engagement ends at delivery. The outcome review — measuring, adjusting and planning forward — is an implementation function that only becomes possible after a full live project cycle.
Connecting Autodesk Forma to your wider technology stack
Most GCC construction firms use Autodesk Forma alongside ERP systems, project controls platforms, Power BI reporting environments and other tools that need to exchange data with Forma. Customisation identifies where these integrations need to exist. Implementation manages them — ensuring data flows correctly between Forma and every connected system, that the integration points work under live project conditions and that your team does not end up double-entering the same information into two systems.
Customisation configures Forma internally. System integration — connecting Forma to external platforms in your technology environment — is an implementation and integration activity that requires understanding your full technology stack.
Five Phases — From Where Your Team Is Now to Full Adoption
Every Accienta implementation follows the same structured sequence. It starts with the reality of your team's current situation — not a generic kickoff agenda — and ends when there is measurable evidence that your team is using Autodesk Forma the way it was built to work. Go-live is a milestone inside this process, not the end of it.
Phase 1 — Current State Assessment and Migration Planning
Before Accienta touches anything in your Autodesk Forma environment, we spend time understanding exactly where your team is right now. We audit your existing document management approach, locate every piece of project data, map every tool your team currently uses and identify both the people who will drive adoption and the people who will resist it. We assess your existing data for migration — how much exists, where it lives, what condition it is in and what needs cleansing before it moves. We map every integration point between Forma and your current technology stack. The output is a specific implementation plan built around the actual state of your team — not a generic project timeline that assumes a clean starting point your team does not have.
Customisation assumes a clean starting point. Implementation starts from where your team actually is — with years of legacy data, established habits and real people who need to change how they work on a live project.
Phase 2 — Secure Data Migration From Legacy Systems
Accienta manages the controlled migration of your existing project data from wherever it currently lives into your configured Autodesk Forma environment. This is not a copy-and-paste operation. It is a managed process — auditing your existing document library, removing duplicates and superseded files, mapping your current folder structure to the new ISO 19650-aligned structure, maintaining data integrity and executing the migration without disrupting live project delivery. For GCC projects with years of drawing history across multiple disciplines, hundreds of RFI records and correspondence archives scattered across multiple systems, this migration is one of the most complex and most important steps in the entire programme — and it is a step that customisation never gets close to.
Customisation builds the destination folder structure. Data migration is the active operation of moving thousands of real files from real legacy systems into that structure — a completely separate activity that requires its own planning, sequencing and verification.
Phase 3 — Stakeholder Onboarding Across Every Party
Accienta manages onboarding for every stakeholder who needs access to the Autodesk Forma environment — main contractor team members, design consultants, subcontractors, client and authority review teams. This is not a bulk invitation email and a help centre link. It is a managed onboarding process for each party type — walking subcontractors through the access process step by step, delivering role-specific training sessions for each discipline, resolving every login and access issue that arises and ensuring every individual from every company understands exactly what they are responsible for in the platform, how to do it and by when. The subcontractor who keeps emailing drawings because they found the portal confusing is Accienta's problem to resolve — not a problem you manage while simultaneously running a live construction programme.
Customisation creates permission levels for each party. Onboarding gets every individual from every company trained, active and using the platform correctly — a people management challenge that no amount of correct configuration addresses on its own.
Phase 4 — Managed Go-Live With Active Adoption Monitoring
Go-live is a milestone inside the implementation — not the end of it. Accienta monitors platform activity during the first live project cycle, tracking which workflows are being used, which team members are bypassing the platform and which processes are generating friction. When Accienta detects non-adoption — an engineer logging observations on paper instead of the mobile app, a consultant sending drawings by email rather than through transmittal, a subcontractor reverting to WhatsApp — we intervene immediately. We do not wait for the project manager to notice six weeks later that the adoption that looked promising at go-live quietly died under live project pressure. This active monitoring during go-live is what separates a successful implementation from a software deployment that statistically most GCC firms are not fully utilising twelve months after purchase.
Customisation is finished before the first user logs in. Every decision, intervention and adjustment that happens after go-live — including the ones that determine whether the platform survives live project pressure — are implementation.
Phase 5 — Outcome Review, Measurement and Future Planning
After the first live project cycle, Accienta and your team conduct a structured outcome review — measuring whether the implementation delivered what it was designed to produce. Did RFI response times improve? Is snagging running faster? Is every party using the platform without workarounds? Are the integrations functioning correctly under real project data volumes? This review produces two outputs: a documented record of what improved — important for firms that need to justify digital transformation investment to management or report to a client on digital delivery performance — and a specific plan for the next phase based on what the first live project actually taught your team. Implementation does not end with a go-live event. It ends when you have evidence the change worked and a clear plan for what comes next.
A customisation engagement ends at delivery. The outcome review is what closes the loop — measuring whether the whole programme worked, producing the evidence your management needs and planning what happens next.
The Four Most Common Autodesk Forma Implementation Failures in the GCC
These are not hypothetical risks. They are the patterns Accienta encounters most frequently when GCC firms call us to rescue a failed Autodesk Forma deployment — one attempted by the firm themselves, by a generic reseller or by a global team with no GCC project context. Every one of them is preventable.
A reseller configures Autodesk Forma, hands over the login and leaves. The project team is expected to learn the platform while simultaneously delivering a live construction programme. The platform is never properly adopted because learning it is always less urgent than the next site problem, the next client deadline or the next overdue RFI — and that priority order never reverses on a live project.
Role-specific training is a non-negotiable phase in every Accienta implementation — delivered on the live configured environment before the first user is given production access.
Autodesk Forma goes live. The drawings stay in SharePoint. The new platform handles new items but the team constantly refers back to the old system for historical data — and within three months both systems are running in parallel, doubling the administrative overhead and making the business case for the new platform impossible to demonstrate to management.
Data migration is a defined phase in every Accienta implementation with a clear retirement date for the legacy system — agreed before the migration begins and enforced when migration is verified complete.
The main contractor team is using Autodesk Forma. The subcontractors are still emailing drawings and submittals because nobody managed their onboarding and the portal confused them on their first attempt. The document controller now manually uploads every subcontractor submission into the CDE — which doubles their workload and defeats the entire purpose of the implementation.
Subcontractor onboarding is a separate workstream in every Accienta implementation — with dedicated walkthroughs, issue resolution and post-onboarding monitoring for every trade package.
The implementation was declared complete at go-live. Six months later an internal audit reveals that three senior engineers are maintaining their own Excel drawing registers alongside Forma, the site team stopped using the mobile app after two weeks and the cost module has never been touched. The platform is technically live. The implementation never finished.
Accienta's post-go-live monitoring phase runs for the full first project cycle — identifying non-adoption before it becomes entrenched and intervening with the specific user or workflow causing the bypass.
What a Complete Accienta Implementation Actually Delivers
Not a go-live date. Not a training attendance record. Not a handover document. Six concrete outcomes — measurable, documented and lasting.
Every existing project file in Autodesk Forma
Every drawing, specification, RFI record and correspondence item migrated from your legacy systems — verified correct and the old system formally retired.
Every stakeholder actively using the platform
Main contractor, consultants, subcontractors and client — every party trained, onboarded and using Forma workflows instead of email, WhatsApp and paper.
Forma connected to your technology stack
Every integration point between Autodesk Forma and your existing systems functioning correctly — no double-entry, no manual data transfer, no disconnected reporting.
Measured evidence of improvement
Documented outcome review showing what changed — RFI response time reduction, snagging admin improvement, elimination of email document sharing — so you can report the ROI to your management.
A team that owns the platform independently
Your BIM manager, document controller and project manager can administer Forma without calling Accienta for every change — the implementation leaves capability, not dependency.
A clear plan for what comes next
The outcome review produces the next phase plan — the next optimisation cycle, the next Forma product scope or the next project phase — so the implementation is a foundation, not a one-time event.
Autodesk Forma Implementation — Answered Directly
The questions GCC project managers, IT directors and BIM managers ask before engaging Accienta for implementation services.
Your Team Has the Licences and the Configuration. Accienta Gets Every Person in Your Project Actually Using It.
Every week your team runs on parallel systems — Forma for some things, email and WhatsApp for the rest — is a week of contractual risk, version confusion and wasted investment. A 30-minute discovery call with Accienta will tell you exactly what your specific implementation requires and how long it will take. Free. No commitment. The only honest starting point.