If your “issue log” still lives in Excel, email chains, and WhatsApp screenshots, you already know the truth: it’s not a system, it’s a liability. On real jobs, design clashes, site queries, and missing details don’t just slow you down, they directly hit margin, timelines, and reputation.
That’s exactly where BIM 360 and Autodesk Construction Cloud (ACC) earn their keep. They centralize models, documents, issues, RFIs, and field coordination in one connected environment, so teams stop guessing and start executing.
Below is a practical breakdown of how BIM 360 / ACC actually helps with issue tracking, RFIs, and field coordination – beyond the marketing buzz.
1. BIM 360 vs Autodesk Construction Cloud: What you’re really using
BIM 360 started as Autodesk’s cloud-based construction management platform. It connects project teams and data from design through construction, with modules for document management, coordination, field, quality, safety, and project controls.
Autodesk Construction Cloud (ACC) is the newer umbrella platform that brings the BIM 360 capabilities into products like Autodesk Docs, Autodesk Build, and Model Coordination with tighter integrations and analytics.
In the field, most people don’t care whether the button says BIM 360 or ACC Build. What matters is this:
- One common data environment (CDE) for drawings, models, specs, and submittals
- One issue log, tied to locations and model views
- One RFI workflow, visible to everyone who needs to act
If you don’t configure these three properly, you’re just paying for cloud storage.
2. Issue tracking: from “who raised this?” to full traceability
On a live project, “issues” are not just clashes. They’re anything that can cost time or money: design gaps, access problems, damaged work, safety risks, QA failures, commissioning snags.
How BIM 360 / ACC handles issues properly:
- Standardized issue types and templates
You can define categories like Quality, Safety, Coordination, Design, and Warranty with custom fields (root cause, location, responsible company, due dates). That structure is what lets you track patterns and not just fire-fight. - Model- and drawing-based issues
Issues are pinned to sheets or 3D model locations. That means when a superintendent opens it on the tablet, they see exactly where it is on the plan or model – no “third column from the left near the staircase” nonsense. - Mobile-first capture in the field
Using the BIM 360 / ACC mobile app, field teams can create issues onsite, attach photos, markups, and voice notes, and sync back when they have connectivity. - Dashboards and filters
PMs and coordinators can filter by company, location, status, or discipline, and use dashboards to see overdue issues, high-risk areas, and recurring root causes – instead of manually compiling weekly reports.
3. RFIs: turning field questions into controlled workflows
RFIs are not just “emails with drawings attached”. They are formal project records that impact scope, cost, and schedule. Done badly, they explode into claims later. Done well, they give you a clean audit trail.
How RFIs work in BIM 360 / ACC:
- Central RFI log
The Project Management module gives you a structured RFI register – with IDs, originators, reviewers, distribution, due dates, and linked documents. - RFIs created directly from the field
For BIM 360 Build / ACC Build users, the mobile app lets field teams create RFIs onsite with specialized tools, link them to locations, and attach photos or markups. - Bi-directional link between Issues and RFIs
Autodesk connected the workflows so that an Issue can be escalated into an RFI with one click, and both stay linked. This reduces retyping, lost context, and “who raised this originally?” confusion. - Connection to documents and models
RFIs can reference specific drawings, models, or specs in Docs, so reviewers see the same source of truth instead of random PDFs.
When you set this up properly, RFIs stop being a black box. You know exactly:
- Which site issues generated RFIs
- How long reviewers took
- Which RFIs triggered design changes or commercial impacts
That’s real project intelligence, not admin work.
4. Field coordination: connecting design intent to site reality
Field coordination is where everything collides. You’re dealing with:
- Clash issues from model coordination
- Access and installation conflicts
- Sequencing constraints
- Late design changes
BIM 360 / ACC helps by pulling model coordination, issues, documents, and RFIs into one environment:
- Model-based coordination
Using coordination tools within Autodesk Construction Cloud, teams can run clash detection and convert clashes directly into trackable issues with assignees and due dates. - Latest drawings and 3D views in the field
Superintendents and foremen don’t have to guess which revision is current. They open a tablet and see the latest approved documents and model views – and raise issues or RFIs right from there. - Integration with reality capture and third-party tools
Tools like OpenSpace can push field notes into ACC as Issues/RFIs, with photos and locations automatically attached, tightening the loop between reality capture and coordination.
5. A realistic workflow: from problem on-site to resolved detail
Here’s how it should look on a job using BIM 360 / ACC well:
- Field discovers a conflict
The mechanical subcontractor finds a duct clashing with a cable tray in a congested corridor. - Issue raised in the field
Foreman opens ACC Build on a tablet, pins an Issue on the 3D view / sheet, tags it as “Coordination – Mechanical vs Electrical”, adds photos, assigns to the coordination lead, and sets a due date. - Coordination review
The coordination lead opens the same Issue in the office, jumps directly to the model location, confirms that the clash is real and not just outdated design, and decides it needs design clarification. - Issue escalated to RFI
From the Issue record, they create a linked RFI, pulling across the description, location, attachments, and impact notes automatically. - Design team responds
The RFI is routed to the designer. They upload a revised detail or mark up the model, respond with their decision (reroute duct, adjust elevation, revise hanger, etc.), and the RFI is officially closed. - Field executes with confidence
The field team sees the RFI response and updated drawing/model in the same environment, installs per the new direction, and closes the original Issue. - Data is captured for later
If there’s a change order, delay claim, or post-mortem review, you can trace exactly:
issue → RFI → design response → cost event. No story-telling required.
That’s the level of traceability owners and GCs are starting to expect as standard – especially on complex jobs.
6. Best practices to actually get value from BIM 360 / ACC
Just buying licenses doesn’t fix chaos. You need process.
Here’s what separates high-performing teams from everyone else:
- Define clear ownership
Decide who can create issues, who must triage them, who raises RFIs, and who approves responses. Set roles and permissions accordingly in Project Management and Docs. - Standardize templates early
Configure issue types, fields, and RFI templates at the start of the project. Don’t “figure it out later” – that’s how you end up with unusable, inconsistent data. - Train field teams on the mobile app
If foremen and supers don’t trust the app, they’ll default back to WhatsApp and calls. Run short, practical trainings focused on their use cases: capturing photos, marking locations, creating issues/RFIs. - Connect models, documents, and field workflows
Make sure the coordination model, sheets, and specs in Docs are actually the ones your field team uses. A “beautiful” model nobody on site sees is just a 3D file, not BIM. - Use dashboards and reports
Review open issues, overdue RFIs, and high-risk areas weekly. If leadership doesn’t look at the data, the team won’t take data entry seriously.
7. The bigger picture: connected construction, not just apps
At its core, BIM 360 / ACC for issue tracking, RFIs, and field coordination is about one thing: connected construction. Models, drawings, site conditions, and decisions live in one ecosystem instead of scattered across emails and local drives.
That doesn’t magically solve every project problem. You still need good drawings, realistic schedules, and competent teams. But when something does go wrong – and it will – a connected, BIM-driven workflow determines how fast you respond, how much you lose, and how much evidence you have to back your position.
If your current projects are still juggling RFIs in Outlook and issues in Excel, the gap is obvious. BIM 360 / ACC won’t close it on its own, but used properly, it gives you the infrastructure to turn chaos into controlled, traceable workflows – from the model, to the field, and back again.