Tools.
Make the toolchain support delivery — not slow it down.
If your team is using Autodesk Construction Cloud (ACC) / BIM 360 (or similar platforms) but the workflow feels inconsistent, heavy, or unclear — I help you set up a toolchain that people actually follow. Practical governance, clean structure, and simple routines that reduce friction and rework.
NZ/AU delivery context • engineering-friendly workflows • focused on “what gets issued” and “who does what, when”
Tell me what platform you’re using, what’s not working, and what project deliverables you’re chasing.
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 drift every month.”
“Permissions/roles are messy — people can’t find the latest files.”
“Issues/clashes aren’t tracked consistently, so problems reappear.”
“Exports/IFC/PDFs/DWGs are inconsistent — downstream teams lose trust.”
“We’re responding to a tender / BEP requirement and need a practical setup fast.”
Typical outputs (examples).
Depending on your project scope, modelling 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)
Tools is rarely the real problem — it’s usually 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.
How it works.
1) Intake (quick)
You send your situation: platform, project type, pain points, and what you need to issue.
I may also send you a short questionnaire to clarify specific issues.
2) Short working session
We map the current workflow, identify bottlenecks, and decide the “minimum rules” that will actually be followed.
4) Handover + coaching
A clear handover pack + optional training so your team can run it without me.
Deliverables (typical)
Depending on your project scope, modelling 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
Engagement options.
A Fixed outcome:
(small scope)
Define the setup, deliver the structure + rules, handover pack.
B Capacity support:
Ongoing help while your team implements and stabilises the workflow.
C Stabilise / rescue:
Get a messy workspace back under control so teams can trust the latest files again.
What I 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 (if available)
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.