Tools.

Make the toolchain support delivery — not slow it down.

Your team started using Autodesk Revit for BIM, but the workflow feels inconsistent, heavy, or unclear. Organizational or tender requirements push for certain capabilities but you're unsure of which software best fit your requirements. A toolchain is not only dependent on individual solutions, but also how they work together. We can help you make informed decisions about procurement, or analyse your existing toolchain for streamlining possibilities.

NZ/AU delivery context • engineering-friendly workflows • Autodesk Recap • Civil 3D Software • Autodesk Vehicle Tracking • Navisworks • Autodesk Inventor • Autodesk Forma/BIM360 Support• Bentley ProjectWise • Revizto

Send your Situation

Who this is for.

Engineering firms and project delivery teams who need the toolchain to be reliable: project managers, BIM/digital engineering leads, coordinators, and modelling teams working to real deadlines.

Common Situations:

  • “We’ve got ACC/BIM 360, but nobody’s sure what ‘right’ looks like.”

  • “Folder structure and naming drifts every month.”

  • “Permissions/roles are messy — people can’t find the latest files.”

  • “Issues/clashes aren’t tracked consistently, so problems reappear.”

  • "We are unsure which application will fill a functional requirement, in a way that agrees with our other processes."

  • “We’re responding to a tender / BEP requirement and need a practical setup fast.”

Typical outputs (examples).

Depending on your project scope, tools support may include:

  • A simple, documented workflow your team can follow

  • A folder + naming structure aligned to deliverables (not theory)

  • Clear responsibilities (who uploads, reviews, publishes, issues)

  • Issue/coordination routines that don’t rely on heroics

  • A setup that supports training + onboarding (so it sticks)

What I help with.

I’m platform-agnostic, but I’m most often brought in around Autodesk and ACC/BIM 360-style workflows and coordination.
Typical support includes:

  • CDE / project workspace structure (folders, naming, packages, publish points)

  • Permissions and roles (who can do what, and why)

  • Model exchange workflows (Revit/IFC/DWG/PDF outputs, issue points, approvals)

  • Issue management setup (how issues are raised, triaged, closed — and reported)

  • Coordination rhythms (weekly cadence, clash/issue review routines, action tracking)

  • Template + standardisation (repeatable setup across projects where appropriate)

  • Light implementation support (hands-on setup + coaching to get it live)

Tool requirements are not always the real problem — it’s often process clarity. If the team is unsure about deliverables, responsibilities, or scope, Tools work often leads into Process (scoping + workflows + deliverables definition).

If you need deliverables/workflow definition, see: Process.

Typical Deliverables

Depending on your project scope, tools support may include:

  • Proposed folder structure + naming rules (practical, not bloated)

  • Roles/permissions matrix (simple and enforceable)

  • Issue workflow guidance (raise → triage → resolve → close)

  • “How we work” one-pager (what to do daily/weekly)

  • Optional: template workspace/project setup for repeatability

What we need from you.

Some general information you can send to kickstart the process:

  • What platform you’re using (ACC/BIM 360/other)

  • Current pain points (2–5 bullets is enough)

  • A screenshot of folder structure (where relevant)

  • Any relevant tender/BEP/deliverable requirements (if the tool requirement is a requisite for a project you're on)

Not sure Where to Start?

If you’re under delivery pressure or need the toolchain to “just work”, send a short note with what you’re using and what’s not working.
I’ll respond with a practical next step.

What are your Software Challenges?