QBCC's 2026 Licensing Changes Mean More Documentation. Here Is How to Keep It Off Your Desk

The QBCC Amendment Regulation 2026 took effect on 1 February. It clarified the difference between application fees and licence fees, introduced new infringement notices, and shifted QBCC’s primary communication channel to email. For most builders, the practical effect has shown up somewhere quieter than the fee schedule: the licence application itself now asks for more.

What Actually Changed Under the QBCC Amendment Regulation 2026

The fee changes and communication shift are administrative housekeeping on their own. The part that lands on a builder’s desk is the application process itself. QBCC builder licence applications now lean more heavily on referees validating detailed work history portfolios, rather than the shorter standalone referee statements that used to satisfy the requirement.

That means an applicant needs a fuller, better-documented picture of past project work, and referees who can speak to specific projects with enough detail to support the application.

Under the previous process, a referee could often sign a short statement confirming they knew the applicant and vouched for their competence. Under the current process, the referee needs to be able to speak to specific completed projects, including scope and timeframes, which means the applicant needs to have that project detail ready to hand to them before they can provide a meaningful statement. If the underlying project records are scattered across old invoices, texts, and memory, the referee cannot do their part until someone reconstructs it first.

The New Referee and Work-History Requirement, and Why It Adds Admin Load

For a builder who has kept loose records, this is where the process slows down. Pulling together a work history portfolio means going back through past projects to confirm scope, value, dates, and the client or supervisor who can verify each one. Referees need to be contacted, briefed on what QBCC is asking for, and followed up when their statements are incomplete or late.

A licence renewal that used to take an afternoon can now stretch into a week of chasing, because the underlying project records were never centralised in the first place.

Where Licensing Applications Usually Stall

The pattern is consistent. A builder starts an application, realises they need detail on a project from eighteen months ago, and has to dig through old emails or ask a former client for confirmation. A referee agrees to help, then goes quiet for two weeks because nobody is following up. QBCC sends a query by email, and it sits unread in an inbox that isn’t checked daily, pushing the application past its window.

Take a typical renewal. A builder has completed four projects since their last licence review, but only kept detailed records for two of them. Tracking down the value, dates, and a contactable referee for the other two means calling former clients who have moved on, or digging through a project management platform that was retired eighteen months earlier for a different tool. What should be a two-day task stretches into three weeks, and the application goes in later than planned, with QBCC’s email query on the outstanding documents adding another week while nobody notices it in a shared inbox.

Each of these is a small delay. Together, they are the difference between a licence renewal that goes through cleanly and one that drags on for months while the business operates under time pressure it didn’t need to create.

A Licensing Admin Workflow That Holds Up Under the New Rules

The fix is a standing system maintained year-round. That means a project record kept current as each job finishes. It means a referee list maintained year-round, with contact details and a note on which projects each referee can speak to. It means someone checking QBCC correspondence daily and drafting responses within the timeframe QBCC expects, rather than discovering a query a week after it landed.

Builders who keep this running as a background process rarely experience the same application delays. The information exists before QBCC asks for it. A project history file updated within a week of each job’s completion, with scope, value, dates and a named contact, means a renewal application is a matter of pulling existing records together rather than reconstructing them. A referee list reviewed quarterly, with a note on which projects each referee can speak to and their current contact details, means nobody is chasing a phone number that’s three jobs out of date.

What Moves Off Your Desk

A licensing admin specialist can own the parts of this that are coordination and documentation. That includes maintaining a running project history file with scope, value, dates, and contact details for each completed job, keeping the referee list current and reaching out ahead of renewal windows, formatting and assembling the work history portfolio to QBCC’s current requirements, and monitoring the QBCC inbox daily to flag and draft responses to correspondence.

This is the work that eats a builder’s week without needing a builder’s judgement. Someone else keeps it current, so it’s ready well before renewal time rather than assembled under pressure.

What Stays With You and Your Accountant or Lawyer

Interpreting what QBCC’s rules mean for your specific licence class, resolving a dispute over an infringement notice, or making a call on how a complex project should be classified in your application stays with you, your accountant, and where needed, a lawyer who specialises in construction licensing. An admin specialist supports that work with accurate, current documentation, alongside the professional advice you get from your accountant or lawyer.

Where HIPPO Fits

HIPPO places offshore licensing and compliance admin specialists with Queensland builders and contractors, and builds the project history and referee tracking system with you before the role starts. The person we place learns your project types and your referee relationships, so the paperwork is ready well before your next renewal.

Book a Connect Session