<aside> <img src="/icons/location_lightgray.svg" alt="/icons/location_lightgray.svg" width="40px" />
Navigation
<aside> <img src="/icons/flood_orange.svg" alt="/icons/flood_orange.svg" width="40px" />
Home
</aside>
</aside>
<aside> <img src="/icons/location_lightgray.svg" alt="/icons/location_lightgray.svg" width="40px" />
Curriculum
<aside>
</aside>
</aside>
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d51f9247-0f4b-4e69-a914-76b31421c4e1/BLANK_PNG.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d51f9247-0f4b-4e69-a914-76b31421c4e1/BLANK_PNG.png" width="40px" />
Most Construction Project Managers and VET Trainers in Australia are stuck at Claude Levels 1-3.
But there are 5.
They open Claude. They ask a question. They close the tab.
That’s the floor.
I’ve spent 400+ hours inside Claude across Chat, Cowork, and Code. There are five distinct levels. Each one unlocks more hours saved per week, a different category of work, and a different ceiling on what you can charge (or bill your clients/RTOs) — whether you’re running construction projects, delivering Cert III/IV training packages, or both.
Here’s the full ladder. Every feature, every cheat code, and every reason tradies, PMs and trainers stall at each level.
TL;DR
→ Level 1: Chat as a search bar. Save 30 min/day. Cheat code is your first project.
→ Level 2: Projects + memory + connectors + real Excel/PPT files + native Office add-ons. Save 5+ hours/week.
→ Level 3: Cowork runs on your machine with file system access. Skills, scheduled tasks, mobile control, Cloud Design, plugins, and computer use. Save 10+ hours/week.
→ Level 4: Claude Code with parallel sessions. claude.md, plan mode, sub-agents, worktrees, MCP, verification loops, custom slash commands. $5K to $15K freelance/consulting work.
→ Level 5: Cloud routines, hooks, channels, headless mode, Agent SDK, remote control, autodream, task budgets, agent teams. The stall isn’t technical. It’s trust.
</aside>
Open Claude. Ask a question. Get an answer. Close the tab.
Maybe draft a variation order. Maybe a quick site induction script. Maybe an explanation of AS 3000 or a SWMS you just read.
That’s level 1.
Quick upgrade: paste screenshots. Claude reads images. Half the people stuck here type out what a screenshot of a drawing or a non-conformance would show in two seconds.
Why do people stall here forever? They don’t realise Claude can hold context across conversations, organise work into projects, or plug into the tools you use every day on site or in the training room. They keep treating it like a search bar that returns paragraphs.
It’s useful. It’s also the floor. Save maybe 30 minutes a day on small things.
Pick something you keep coming back to — your current construction job, a VET program you run every semester, recurring compliance work. Drop in a few reference docs (company quality manual, sample SWMS, apprentice assessment templates). Write a quick system prompt about who you are, how you run projects or deliver training, and how you want Claude to respond.
Now every chat in that project starts pre-loaded.
That single move is the doorway into level 2.
If you created your first project, you’ve already taken the biggest step. Projects are the spine of this level.
Picture this. You open a fresh chat next Tuesday inside your project and ask, “What was the thing we decided about the concrete pour sequencing last week?” Claude pulls it up, cites the conversation, and picks up right where you left off.
Suddenly Claude isn’t a stateless tool. It’s continuity.