GITNUXSOFTWARE REVIEW
Construction & InfrastructureTop 10 Best Tunnelling Software of 2026
Editorial roundup comparing tunnelling software tools for planning and reporting, with options like Asite, Jira Software, and Confluence.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy
Asite is the best pick for delivery teams needing controlled tunnel document lifecycles because its versioned, API-accessible workflows tie approvals to RBAC-governed records, whereas Jira Software fits teams that want issue state transitions to drive automation and integrations through its REST APIs.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Asite
API-accessible workflow lifecycle tied to versioned document records and RBAC-governed approvals.
Best for: Fits when delivery teams need workflow automation and controlled document lifecycles tied to site governance.
Jira Software
Editor pickWorkflow rules plus Jira REST API and automation events combine to control issue state transitions with traceable governance.
Best for: Fits when Jira issue data must drive workflow automation and external system sync with governance and auditability.
Confluence
Editor pickAtlassian Automation with Confluence triggers and actions, combined with REST APIs and webhooks for governed workflows.
Best for: Fits when teams need wiki collaboration plus auditable API-driven integration and permission-controlled content automation.
Comparison Table
Asite
enterprise constructionConstruction contract and document workflow platform with permissions, audit logs, and configuration options that support controlled intake and automated routing.
API-accessible workflow lifecycle tied to versioned document records and RBAC-governed approvals.
Asite provisions and administers connected tunnelling project workflows, linking document control, approvals, and task execution to construction data. The data model centers on structured site objects, permissions, and versioned records, which supports controlled configuration across projects and packages.
Asite exposes integration options through API-driven access and automation hooks for provisioning, syncing metadata, and routing lifecycle events. Governance is enforced through RBAC-style permissions and audit trails that track changes across documents and workflow steps.
- +Project-scoped configuration ties document control to workflow state
- +API supports automation for provisioning and metadata synchronization
- +Structured permissions and change history improve auditability
- +Workflow-driven approvals reduce manual handoffs between roles
- –Schema customization can require careful mapping to internal systems
- –Automation depends on available event coverage for each workflow step
- –Cross-project analytics are constrained by the underlying data model
- –Integration setup can take effort to align permissions and objects
Site teams and subcontractors
Log snags and assign closure tasks
Auditable closure of site issues
Asset handover teams
Package approved handover records
Traceable handover documentation
Show 2 more scenarios
BIM and design consultants
Govern design models in workflows
More controlled design information
Store and review design files and models under controlled project workflows with governed exchange.
Document controllers
Route submittals through approvals
Traceable submittal register
Track submittals through review, approval, revision, and release stages while preserving response history.
Best for: Fits when delivery teams need workflow automation and controlled document lifecycles tied to site governance.
Jira Software
workflow automationIssue and workflow engine for construction coordination, with automation rules, webhooks, and API surfaces to map tunnel project tasks to controlled processes.
Workflow rules plus Jira REST API and automation events combine to control issue state transitions with traceable governance.
Jira Software fits teams that need structured issue workflows tied to reporting, releases, and operational visibility. It uses a configurable data model built around projects, issue types, fields, workflow states, and permissions that govern how work moves.
Automation rules and a documented REST API let administrators connect Jira events to external systems and enforce consistent workflow changes. Deep integration with Atlassian ecosystems adds linkages for plans, CI signals, and change tracking tied to the same issue records.
- +Configurable workflow engine with states, transitions, conditions, and validators
- +REST APIs support issue lifecycle operations and event-driven integrations
- +Automation rules cover field updates, approvals, routing, and time-based triggers
- +RBAC via projects, roles, groups, and issue-level security supports granular access
- –Workflow customization can become hard to reason about at scale
- –Automation rules can create hidden coupling between workflows and external actions
- –Custom fields and schemes can drift without strict admin governance
- –Data model extensibility relies heavily on configuration and mapping discipline
Mission control teams
Track commands and alarms as issues
Traceable operational decisions
Project program managers
Monitor milestones and overdue queues
Improved schedule visibility
Show 2 more scenarios
Engineering delivery managers
Compare estimated versus delivered effort
Planned versus actual analysis
Store story points and time estimates and then track actual work to analyze planned versus actual effort.
Engineering governance teams
Enforce approval paths for changes
Recorded approval history
Use gated workflow transitions with validators and permissions to control changes to delivery artifacts.
Best for: Fits when Jira issue data must drive workflow automation and external system sync with governance and auditability.
Confluence
documentation platformTeam workspace for engineering documentation with configurable permissions, audit visibility, and extensive automation and API options for structured content workflows.
Atlassian Automation with Confluence triggers and actions, combined with REST APIs and webhooks for governed workflows.
Confluence lets teams publish and update wiki pages, then expose that content through REST APIs and event webhooks. It supports a structured data model via page types, labels, and content properties, with schema-like constraints implemented through content permissions and templates.
Confluence Automation and REST APIs enable provisioning, enrichment, and cross-tool synchronization using rule triggers, workflow actions, and external app calls. Administrative controls cover space-level permissions, Atlassian account RBAC, audit logging, and governance patterns for app installation and content access.
- +REST API supports content CRUD, metadata, and attachments for integration.
- +Webhooks and automation rules enable event-driven workflows across tools.
- +Fine-grained space permissions and content restrictions support least-privilege.
- +Extensibility through Connect and Forge adds UI modules and custom logic.
- –Large-scale automation can hit rate limits during bulk sync.
- –Complex permission inheritance can increase admin overhead during reorganizations.
- –Content properties require careful schema conventions for consistent querying.
- –Some operations need multiple API calls, which raises integration round-trips.
Enterprise knowledge teams
Maintain tunnelling knowledge spaces
Searchable permissioned knowledge
Quality and process teams
Run procedure reviews with templates
Consistent procedures
Show 2 more scenarios
Compliance reporting teams
Draft and review compliance evidence
Traceable reporting preparation
Centralize evidence and disclosure drafts into structured pages with collaborative comments and revision history.
Engineering project teams
Connect decisions to execution documentation
Connected delivery evidence
Link requirements, decisions, plans, and runbooks to delivery work so project context stays attached to execution.
Best for: Fits when teams need wiki collaboration plus auditable API-driven integration and permission-controlled content automation.
Autodesk Build
construction platformConstruction infrastructure management for submittals, RFIs, and model-backed project workflows, with integrations and configurable permissions for controlled collaboration.
Model-linked issue and markup workflows that attach revisions to specific project elements.
Autodesk Build connects field actions to a structured data model of project elements, so issues, tasks, and reviews can reference the same underlying objects used in coordination. Markups and reports maintain traceability across who submitted a change, what was changed, and where it applies in the project context. Integration depth is practical for teams working with Autodesk models, since model-linked context reduces manual cross-referencing.
- +Model-linked tasks and markups keep field work traceable to project elements
- –API automation depends on consistent schema mapping for external systems
Site engineering and inspectors
Manage model-referenced field markups
Reduced rework from unclear context
General contractors
Coordinate multi-trade punch and closeout
Faster issue closure cycles
Show 2 more scenarios
Project controls administrators
Enforce RBAC and audit trails
Clear accountability across stakeholders
Administrators control who can edit workflows and review history for compliance evidence.
Construction ops automation teams
Integrate external systems via API
Higher throughput on field coordination
Automation pulls and updates workflow objects while mapping external identifiers to the schema.
Best for: Fits when project controls teams need model-linked tasking with governance and auditability.
Aconex
construction documentsConstruction document and workflow system with access control, audit logging, and integration capabilities for structured submittal and correspondence processes.
Aconex audit log ties document and workflow events to user identity and timestamps for traceable governance.
Aconex centers tunnelling project delivery around a governed document and workflow system with role-based controls and auditable changes. Integration depth is driven by structured project entities for drawings, RFIs, transmittals, and approvals that map to a consistent data model.
- +Project entity data model links drawings, RFIs, approvals, and transmittals
- +RBAC permissions support role scoping across projects and documents
- +Audit log tracks workflow actions and document state changes
- +API and integrations support provisioning and external system synchronization
- –Workflow configuration can be heavy for highly specialized tunnelling stages
- –Schema alignment work is required when integrating legacy document structures
- –Reporting depends on how projects are modeled and governed
- –Automation breadth is limited by workflow and permission configuration boundaries
Tunnel owners and project controls
Run governed workflows for tunnel design changes
Reduced approval cycle time
Engineering document controllers
Maintain consistent document status across contractors
Fewer document version conflicts
Show 2 more scenarios
Systems integrators and automation teams
Provision data and events via API
Automated document and workflow updates
API support enables system-to-system provisioning and workflow event handling for tunnelling workstreams.
Project managers and quality leads
Enforce role-based access for tunnel deliverables
Improved compliance and traceability
Permission controls and audit visibility manage who can act on approvals and change governed records.
Best for: Fits when large tunnelling programs need strict governance, audited workflows, and API-backed integration with planning and document systems.
Autodesk Construction Cloud
workflow platformDocument and workflow platform for construction coordination with role-based access controls, audit trails, and automation hooks for connected project processes.
Workflow automation ties issue and document states to configured rules across projects.
Autodesk Construction Cloud is distinct for tunnelling use because it ties project records to spatial and document artifacts that teams already manage in Autodesk workflows. The data model organizes projects, locations, and related records into a consistent schema that reduces manual mapping between estimating, field updates, and document control. Workflow automation can move items between states based on configured rules, and the API supports integrating external systems for data entry, issue creation, and status synchronization.
- +Configurable project data model links assets, documents, and work status
- +Automation rules drive state changes for issues, approvals, and work packages
- +API supports bidirectional integration for issues, documents, and project records
- +RBAC and audit trails help control access to regulated project artifacts
- –Schema alignment work is required to map tunnelling processes cleanly
- –Complex custom logic may need external systems alongside workflow rules
- –Throughput can drop when teams rely on unstructured document-centric updates
Program controls teams
Automate tunnelling work package status updates
Fewer manual status reconciliations
QA and compliance teams
Control NCRs and approval evidence
Audit-ready evidence trail
Show 2 more scenarios
Owner and contractor integrators
Sync field events through API
Single source for decisions
The API ingests external sensor logs or field forms into structured project entities and issues.
Design and documentation managers
Coordinate tunnelling deliverables across disciplines
Lower revision mismatch
Document workflows keep revision state consistent while automation routes approvals to the right roles.
Best for: Fits when tunnelling teams need schema-driven document control and automation with API integration.
OpenText Project Collaboration
enterprise governanceProject collaboration and document management with configurable governance, enterprise permissions, and integration surfaces for automated information exchange.
RBAC-driven governance with audit log coverage across workspace access and workflow actions.
OpenText Project Collaboration fits organizations that need tight governance over shared project workspaces, document lifecycles, and cross-team collaboration. Integration depth centers on connecting project artifacts to OpenText content and enterprise systems through defined connectors, metadata, and controlled workflows.
- +Workspace and document controls align with enterprise content governance
- +Configurable workflows cover document states and approval routing
- +Integration connectors map project metadata to external systems
- +Role-based permissions support RBAC at space and object levels
- –API documentation and schema discovery can require platform familiarity
- –Complex permission models can add admin overhead across many workspaces
- –Workflow automation changes may need careful testing to avoid drift
- –Extensibility breadth depends on available connectors for target systems
Project management office teams
Standardize workspace governance across projects
Reduced policy and access drift
Enterprise document stewards
Enforce document lifecycle and retention
Lowered risk of unmanaged documents
Show 2 more scenarios
IT integration and automation teams
Provision content via integration APIs
Faster onboarding of project work
Uses workflow configuration and integration connectors to move content based on metadata and events.
Cross-team program coordinators
Coordinate approvals across departments
Timelier signoffs across teams
Supports configurable schemas and workflows that align approvals with project roles and access rules.
Best for: Fits when regulated teams need RBAC, audit trails, and workflow-driven document control across interconnected project systems.
Trimble Connect
engineering collaborationCloud collaboration for engineering and construction data with structured project spaces, access controls, and data exchange designed for repeatable workflows.
API and data model integration for synchronizing model-linked assets, documents, and issues across tunnelling workflows.
Trimble Connect is a construction collaboration system with a project-centric data model and model-aware document workflows for tunnelling projects. It supports schema-driven asset and location data via its data model, then ties that information to 3D views, issues, and uploaded deliverables.
- +Project data model links assets, locations, and deliverables to shared 3D context
- +Document and issue workflows connect review states to model-referenced items
- +API surface supports automation for project objects and metadata synchronization
- +RBAC-style access controls restrict edit and manage actions per project
- –Automation needs careful schema mapping between external systems and Connect entities
- –High-volume throughput can require batching to avoid slow sync windows
- –Governance relies on per-project configuration that can increase admin overhead
- –Extensibility depends on API coverage of specific object types and fields
Design managers and PMs
Distribute and approve controlled drawings
Controlled drawing traceability
Field crews and site managers
Capture feedback with file context
Feedback linked to project context
Show 2 more scenarios
BIM managers and designers
Review federated models in 3D
Coordinated issue actions
Review multi-discipline models together and record coordination comments in spatial context for tunnelling work.
Multi-office construction organizations
Provide centralized model access
Less file chasing across locations
Share the current models and documents across offices and sites so distributed teams reduce file chasing.
Best for: Fits when tunnelling teams need model-linked documentation and API-driven automation with governed access.
Bentley iTwin Design Collaboration
model integrationWeb-based environment for design data collaboration with model-driven workflows that integrate engineering models and expose APIs for automation and governance.
Element-level collaboration objects tied to the iTwin model data model for traceable issue and review workflows.
Bentley iTwin Design Collaboration provides model-based collaboration where issues, comments, and review status attach to elements inside the iTwin model. The integration depth is driven by an iTwin schema that supports domain entities such as alignments, construction elements, and related metadata, so governance can be applied at element level rather than by document. API and automation access focuses on iTwin model read, collaboration object management, and webhook style event handling patterns that allow external systems to react to review and moderation events. Admin control typically includes RBAC, project scoping, and audit trails that record who changed what review state and when.
- +Element-scoped reviews attach to iTwin model structure and metadata
- +RBAC and audit logging support governance for distributed tunnelling teams
- +API and event patterns support automation around review state and moderation
- +Schema-driven data model reduces mismatch between markup and model versions
- –Accurate review attachment depends on stable element references in the iTwin schema
- –External automation requires mapping between internal systems and iTwin collaboration objects
- –Governance setup can add overhead for small projects with few stakeholders
Tunnel design coordinators
Review alignment and lining changes
Fewer mismatches in design feedback
Program governance teams
Control access across project work packages
Traceable approval and moderation
Show 2 more scenarios
Engineering automation owners
Sync review status to internal systems
Higher throughput for reviews
API-based automation updates external workflows when collaboration state changes.
Site construction reviewers
Validate as-designed vs latest model
Faster decisions on change impacts
Model-based viewing supports consistent spatial context for construction field verification.
Best for: Fits when tunnelling teams need model-linked reviews with RBAC, audit logs, and API-driven automation.
SharePoint Server
enterprise contentSelf-hosted document and workflow foundation with RBAC, audit logging, and extensibility through Microsoft automation and integration tooling for controlled operations.
Event-driven automation with REST and CSOM over lists, documents, and permissions within an audited RBAC data model.
SharePoint Server provides a deep integration surface for intranet content, document libraries, and collaboration sites with a controllable data model. Its schema-driven lists, document metadata, and managed paths map to tenant-like site collections, enabling predictable provisioning and RBAC scoping.
- +Granular RBAC on site, list, folder, and item levels
- +Schema-driven lists and content types support predictable metadata models
- +REST and CSOM enable automation across lists, documents, and permissions
- +Audit log captures access and configuration changes for governance
- –Workflow and extensibility options can fragment across technologies
- –Eventing and permissions changes require careful testing to avoid side effects
- –Throughput tuning for high-frequency automation needs performance engineering
- –Complex governance often depends on disciplined provisioning practices
Tunnelling project administrators
Provision RBAC-scoped collaboration sites
Consistent permission scoping
Document control teams
Track access to controlled document types
Controlled access to documents
Show 2 more scenarios
Compliance and audit teams
Audit who accessed which content
Audit-ready access records
Rely on access auditing to record how users interact with content types and integration outputs.
Integration and workflow engineers
Trigger workflows from content events
Automated responses to changes
Use REST and CSOM APIs plus event-linked workflows to automate actions tied to list and content changes.
Best for: Fits when enterprises need SharePoint-integrated tunnelling patterns with strict RBAC, audit logging, and schema-aligned automation.
Conclusion
After evaluating 10 tunnelling software, Asite stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Frequently Asked Questions About Tunnelling Software
Which tunnelling platform should be chosen for model-linked design review with RBAC and audit logs?
How does model-linked tasking differ between Autodesk Build and Autodesk Construction Cloud?
What integration path fits teams that need API-driven synchronization of model-linked assets, documents, and issues?
Which tool is better suited for schema-driven document control and workflow automation across projects via an API?
How do admin controls and audit visibility typically work in Aconex versus OpenText Project Collaboration?
What security and identity features matter most when consolidating controlled access across documents and content paths in SharePoint Server?
Which platform fits a wiki-to-automation workflow where page changes trigger external systems via webhooks?
When migrating existing tunnelling workflows and data models, how do admin configuration patterns compare across tools?
What common integration problem appears when connecting issue systems to model or document workflows, and how do these tools address it?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
How to Choose the Right Tunnelling Software
What separates tunnelling software options is how they handle field-to-model workflows: from face and survey inputs to design outputs, the gap shows up in data lineage, automation, and repeatable outputs. When we compare products, we focus on mapping, traceability, and how each tool turns project changes into consistent design sets.
Survey and model import formats
Why it matters
In tunnelling work, teams rarely start from a blank project. This criterion matters because import friction can break your alignment between as-built survey data and your tunnel geometry.
How to check
Ask the demo team to import a sample point cloud or alignment file plus a basic tunnel geometry definition. Then check whether the software preserves coordinate systems and lets you review mismatches before running outputs.
Construction sequence and staging tools
Why it matters
Tunnelling decisions depend on when excavation and support occur. Strong construction sequence handling reduces rework when you change excavation timing or support parameters.
How to check
Have them build a simple staged workflow (e.g., excavation advancing then lining/support installation) using the demo’s editor. Confirm you can generate results per stage and compare outputs side-by-side.
Change propagation and batch runs
Why it matters
Tunnelling projects evolve, and manual rework slows decisions. This criterion matters because automation and change propagation keep design outputs consistent across iterations.
How to check
Provide a small change (advance distance or support timing) and request regeneration of outputs. Check whether batch runs can re-create the whole set and whether the UI shows what changed.
API and report export control
Why it matters
Teams need to feed tunnelling outputs into broader project workflows without copying numbers. This criterion matters because an automation-friendly API and repeatable reports reduce transcription errors.
How to check
On the demo, ask for an API call or automation script that exports key results and a configurable report. Verify you can choose outputs, naming, and units, and re-run it with a different project input.
Geology-to-alignment mapping support
Why it matters
Real tunnelling faces geology variability. This criterion matters because geology mapping affects where support and investigation assumptions apply along the alignment.
How to check
Ask them to attach geology information to an existing alignment and then preview where it projects along chainage. Check whether the mapping is editable and whether the tool flags holes or overlaps.
Assumptions traceability across outputs
Why it matters
When results differ, the team needs a clear audit trail from assumptions to outputs. This criterion matters because traceability reduces time spent hunting settings and assumptions during design reviews.
How to check
On a demo model, change one setting (e.g., a support or lining assumption) and then inspect an output record to see what references updated. Ask where you can export an audit-style summary for review.
Red flags
- Imports silently shift coordinates or units without clear warnings
- Regenerating after a change does not update all dependent outputs
- Exports don’t capture which assumptions produced each result
Fit by situation
- If your team relies on point clouds and alignment files from surveys, prioritize survey and model import formats.
- If you often revise excavation and support timing, prioritize construction sequence and staging tools.
- If you must re-run outputs for many design options with minimal manual steps, prioritize change propagation and batch runs.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Construction & Infrastructure alternatives
See side-by-side comparisons of construction & infrastructure tools and pick the right one for your stack.
Compare construction & infrastructure tools→