ACC Issues allows issues to be imported from Excel using the standard ACC Build template, which is helpful for creating issues in bulk, but today those imported issues cannot be automatically placed in the model viewer. Even when issues originate from coordination tools like Revizto, Navisworks, Solibri, or Resolve—and already include coordinates, camera views, or other spatial context—that information is lost during import, forcing teams to manually re‑pin every issue in the model. This adds unnecessary effort, introduces risk of mis‑location, and discourages use of Excel import for model‑based coordination. Enabling Excel imports to support optional spatial data (such as XYZ coordinates, view context, or interpretable location fields) would allow issues to appear directly in the ACC model viewer upon import, preserve spatial intent from upstream tools, reduce manual rework, and significantly improve interoperability while keeping the existing template and workflows intact.
