What happens when your firm stops managing projects on spreadsheets and half-read emails
I spent seven years watching architecture firms drown in version confusion, missed RFIs, and schedules that existed only in someone's head. Then the industry started moving toward centralized portals, and one tool kept coming up with real traction: Revolutionizing Architectural Project Management With Acadis Portal. I'm not going to sell you on it. I'm going to tell you what it does, how to set it up without breaking your existing workflow, and where it quietly falls apart. Acadis Portal is a cloud-based project coordination platform built specifically for the architecture, engineering, and construction ecosystem. It sits between your design software and your construction administration process. The core idea is simple: centralize drawings, documents, RFIs, submittals, and meeting notes in one place so everyone on a project — architect, contractor, consultant, client — is looking at the same thing at the same time. Here's how the setup actually works, because the documentation on their site glosses over the messy parts.
First, you create a firm account and set up organizational roles. There are four main role tiers: Administrator, Project Manager, Team Member, and External Guest. The Administrator controls billing and global settings. The Project Manager assigns users to specific projects. Team Members get access to deliverable folders. External Guests — this is where most people mess up — should only be given View or Comment permissions, never Edit. I watched a firm accidentally give a structural engineer full edit access to a completed MEP coordination set. Took three days to recover from that one. Once roles are defined, you create your first project. You'll set the project type (architectural, renovation, interior, etc.), assign a project manager, and configure the document structure. The portal comes with a default folder hierarchy based on AIA document standards, but you can customize it. I recommend starting with the default structure and only modifying it after you've run at least two projects through the system. Customizing upfront almost always leads to structural confusion later. Next step is connecting your drawing tools. Acadis integrates directly with Autodesk BIM 360/ACC, Revit, and AutoCAD. The integration pulls in your file tree automatically, but there's a catch: it only syncs files that are properly published to the cloud from your source software. If your team still keeps final PDFs locally and emails them, the portal won't see them. This is the single biggest implementation failure I've seen. Firms buy the license, think the integration is broken, and go back to emailing PDFs. It's not broken. Your workflow is.
How it changes day-to-day work on a live project
The main value isn't in storing drawings. It's in the workflow layer on top of those drawings. Here's what shifts. RFI management becomes trackable instead of existential. On my last project before switching, we had 47 open RFIs. Twelve of them were stuck in email chains between the GC and the architect. The GC claimed they were never sent. The architect claimed they were sent Tuesday. Nobody could produce a timestamped record. With Acadis, every RFI is logged with a date, assigned discipline, priority level, and status. When a GC says an RFI was never received, you pull the record. It shows exactly when it was submitted, when it was acknowledged, and who read it. This alone justifies the subscription for most firms. Submittal tracking works similarly but has more moving parts. A submittal enters the system from the contractor, gets routed to the appropriate consultant for review, and comes back with an approved/rejected/pending status. The portal handles the routing automatically based on the discipline codes you assign during setup. Before Acadis, I was manually forwarding Excel sheets to five different consultants and chasing responses via phone. Now the system does the chasing and logs it.
Get the Full Details
Document control is where Acadis actually earns its keep. Version numbering, transmittals, revision clouds — these are all built in. When you upload a new drawing set, you flag it as a revision, and the system maintains the full history. You can see what changed between V3 and V4, which consultant reviewed it, and whether the contractor has acknowledged receipt. This eliminates the "I thought I was looking at the latest issue" conversations that waste billable hours on every project. There's also a meeting minutes module that ties directly to action items. You draft minutes after a OAC meeting, assign follow-up tasks to specific team members with due dates, and the portal tracks completion. No more "I didn't know that was assigned to me." The task appears on the recipient's dashboard with a highlighted due date.
A problem I ran into and how I solved it
Two years ago, I hit a real wall with Acadis on a hospital renovation project. We had over 300 drawings across twelve disciplines, and the cloud sync was dropping files intermittently. The issue wasn't Acadis itself — it was our Autodesk construction cloud sync settings. Files larger than 50MB would time out during the background sync, appear as pending in Acadis, and then silently fail. The portal would show the file as uploaded, but the actual document wasn't there. Contractors would pull what looked like the latest revision, and it was actually a corrupted or partial transfer. The workaround was straightforward but undocumented. I had to switch our sync from the automatic background mode to manual triggering through the Autodesk dashboard, batch the uploads in groups of twenty files, and verify each batch in Acadis before moving to the next set. It added about forty minutes to our weekly upload routine, but it eliminated the silent failures. I also set up a weekly audit where I cross-referenced the file count in our BIM 360 folder against what was showing in Acadis. The discrepancy count should always be zero. Any nonzero number means something got dropped in transit. If you're dealing with large drawing sets, don't assume the integration is handling everything invisibly. Verify it periodically. Five minutes a week saves you from a month of damage control.
Things nobody tells you about Acadis Portal
Here are a few counter-intuitive facts that only come up after you've been using this for a while. Guest access is more dangerous than it looks. When you add an external consultant as a guest, they can comment on any document in the project unless you've configured folder-level restrictions. Most firms create one project per building phase and invite everyone to it. That means the landscape architect can see structural calculations and the MEP subcontractor can see interior finish schedules. The data isn't exposed externally, but internally it creates noise. The fix is to segment by discipline in separate project folders and control guest access at the folder level, not the project level. The reporting feature is powerful but underutilized. Acadis generates weekly dashboard reports automatically — open RFIs, overdue submittals, upcoming milestones. Most project managers ignore these because the default formatting is dry. But if you customize the report template to include your firm's branding and a brief narrative summary, these reports become valuable client communication tools. I send mine every Friday morning with a one-paragraph overview. Clients stop asking for updates because they're already getting them.
Export capabilities are limited for audit purposes. If your firm needs to produce a complete project archive for legal or insurance reasons, Acadis doesn't offer a one-click export of everything in a project. You have to use the bulk download function, which pulls documents individually and can take hours on large projects. I learned this the hard way during a dispute on a 2022 project where we needed every transmittal, RFI response, and revision record compiled within forty-eight hours. The portal exported 80% of what we needed, but about sixty files were inaccessible because they'd been deleted from the source BIM 360 repository before we realized they were missing. The workaround is to maintain a parallel local backup of all critical project documents throughout the construction phase. Don't rely on the portal as your sole archive.
Where it breaks down
I need to be honest about the limitations. Acadis Portal is not a cure-all. It doesn't handle scheduling or cost management. You still need Primavera, MS Project, or a separate cost control tool. Acadis references project milestones, but it doesn't build or maintain the schedule itself. If you're looking for an all-in-one platform that covers scheduling, billing, and project coordination, this isn't it. For that, you'd need something like Procore, though Procore's learning curve is significantly steeper and the pricing scale is higher. It struggles with non-standard project types. The default folder structure and workflow templates assume traditional design-bid-build or CM-at-risk delivery methods. If your firm works frequently in design-build, IPD, or progressive construction delivery, you'll spend significant time reconfiguring workflows to match your actual process. The flexibility is there, but the initial setup time is substantial.
There's also a mobile experience gap. The Acadis mobile app is functional for viewing documents and checking RFI status, but it's not suitable for field coordination work. You can't upload shop drawings from a job site tablet, annotate drawings on location, or kick off an RFI from the field. If your project team expects to do meaningful field work through the app, you'll be disappointed. The desktop experience is solid. The mobile experience is adequate. Pricing is another consideration. At the time of writing, Acadis charges per project per month, and the cost scales with the number of active projects and team members. For a small firm running three to five projects simultaneously, it's reasonable. For a mid-size firm on fifteen concurrent projects, the subscription cost becomes noticeable. I'd recommend getting the enterprise quote rather than self-quoting, because the per-project discount tiers kick in faster than the pricing page suggests.
Getting started without disrupting your current projects
If you decide to implement this, don't roll it out on an active project. Use an upcoming project or a completed project as your test case. Import the drawing set, set up the RFI and submittal workflows, and run the project through one phase using the portal as the single source of truth. Document where the friction points are. Adjust your folder structure, permission settings, and integration configurations based on what you learn. Then roll it out to your next project with a documented standard operating procedure. The learning curve for a typical architecture firm is about two to three weeks for basic proficiency and six to eight weeks for full workflow mastery. Factor that into your implementation timeline. Expect a productivity dip during the transition period. It's temporary, but it's real. One practical tip: designate a single portal administrator on your team, ideally someone who isn't a primary project manager. This person handles role assignments, integration troubleshooting, and weekly audits. Without a dedicated owner, the portal tends to drift into disuse because no one feels responsible for maintaining it. I've seen this happen at three different firms. It's always the same pattern — great setup, gradual decline, eventual abandonment.
Acadis Portal won't fix bad project management. If your team doesn't have clear roles, consistent communication habits, and disciplined document control, the portal will just make those problems more visible. But if your firm already operates with decent processes and just lacks the centralization to support them at scale, this tool can genuinely improve project outcomes. The RFIs get tracked. The drawings don't go missing. The stakeholders stop arguing about what version they're looking at. Those are small things individually but they compound over a year of projects.
