QClad
QClad
Settings Demo 58 people · QClad Services Pty Ltd
Accounting connected Thu 13 Aug 2026

System

Settings

Company details, the commercial defaults every calculation reads, who sees what, and connected systems.

Company

Legal name
QClad Services Pty Ltd
ABN
62 138 704 915
Licence
QBCC 1174 320
Trading since
2004
Address
Unit 2/9-11 Lenco Cres, Landsborough QLD 4550
Postal
PO Box 292, Landsborough QLD 4550
Telephone
07 5474 4966
Facsimile
07 5474 4977
Email
admin@qclad.com
EFT
NAB Caloundra
BSB 084-462 · 5813 02947
Innovation Quality Excellence

Commercial defaults

Every calculation in the system reads these.

GST
10%
Retention
5%, half released at PC
Payment schedule due (BIF Act)
15 business days
Payment due (BIF Act)
25 business days
Loaded field hour
$94.00
Site on-cost on measured work
24%
Financial year
1 July - 30 June
Locale
en-AU · AEST (Brisbane, no DST)

People & permissions

58 seats, 12 on the desktop and 46 in the field, plus subcontractor logins at their own level. Access is set per person against the role below.

RolePeopleWhat they see
Director 2 Everything, including margin on every job, and the approval on variations and claims. Nathan Carter · Adam Doyle
Business Manager 0 Contracts, claims, invoicing, payroll extract, subcontractor compliance. Not tender margins.
Estimating 2 Tenders, the pricing schedule and its cost build-ups, historic project margins by rate. Dylan Fraser · Priya Raghavan
Project Management 2 Their own projects end to end: schedule of rates, variations, claims, timesheets, purchasing, ITPs, diary. Marcus Deng · Cameron Hale
Contracts Administration 1 Claims, variations, retention, invoicing, BIF clocks across every job. Janelle Roe
HSEQ 1 Health and safety, ITPs, tickets, inductions, incidents. Read-only on the commercial side. Sam Kirkwood
Procurement 1 Materials, purchasing, suppliers, receipting. No project margins. Toby Ellison
Document Control 1 Transmittals, drawings, handover packs, warranties. Grace Lindqvist
IT & Systems 1 Everything, plus the schema, deployments and the migration console. Wes Nakamura
Leading Hand 4 Their crew's day cards to approve, the site diary, Take 5s, SWMS sign-on, and raising purchase orders on site. Blake Tuiala · Mitch Ravenscroft · Zeb Marchetti · Dom Falzon
Field crew 42 Their own day card, their own tickets, the SWMS for the job they are standing on. Nothing commercial.

Crew 1, Rail

12 people · lead Blake Tuiala

QJ2041

Crew 2, Bowen Basin

11 people · lead Mitch Ravenscroft

QJ2044

Crew 3, FIFO West

11 people · lead Zeb Marchetti

QJ2006

Crew 4, FIFO North

12 people · lead Dom Falzon

QJ2039

Integrations

Systems QClad exchange data with. Named, because they are QClad's systems rather than generic ones.

  • Xero

    Invoices post out, payment status reads back. Last sync 2026-08-05 09:14, 18 documents.

    Connected
  • Primavera P6

    Activity IDs join to the job. Programme dates read in both directions.

    Integration
  • Zoho

    19 source systems, 983,406 records inventoried for migration.

    Console →
  • Xero payroll

    Approved day cards produce the pay run, awards and site agreements applied. Every allowance pushes on the API except the hourly crib allowance, which Xero will not accept and is flagged on each run for manual entry.

    Partly connected
  • SharePoint

    Documents stay in QClad's own tenancy. This system holds the register, the revision history and the issue record; the file never leaves their control, which is also the answer on Defence work.

    Connected
  • Flight tracking

    Departure and arrival times against every booking on the travel register. Paid travel time is one hour before departure and thirty minutes after landing, computed from these rather than entered.

    Integration
  • Location tracking

    Off, deliberately. You turned it off because it reported the wrong location and most of the team had location services disabled anyway. Nothing here depends on it: a day card is proved by the job and cost centre it books to, not by a coordinate.

    Off
  • Head contractor platforms

    Several clients require QClad to work inside the client's own system and report in the client's format: SCJV Fieldwise, South32 vendor portal. That does not go away. QClad keep their own copy of everything here so the two agree.

    Client side

Hosting and data

Where everything physically sits, which is a contract question on Defence and resources work rather than an IT one.

Application
Cloudflare, served from the edge node closest to whoever opens it. Australian users are served from Australian nodes.
Database
One region, Australia. It does not replicate offshore, and the region is fixed rather than chosen automatically.
Documents and photos
QClad's own SharePoint tenancy. The file never enters this system; this system holds the register, the revision and the issue record.
Backups
Point-in-time recovery on the database, inside the same region. SharePoint retention is QClad's own policy, unchanged.
Access
Per person, by role. The role selector at the top of the sidebar is the same mechanism: what somebody sees and what they may approve both come off it.
Intellectual property
QClad's. The source is handed over at the end of the build; Praxa host and support it at a fixed monthly fee, and that arrangement can end without the system doing so.
Third parties
None in the request path. Nothing here calls an external service to render a page, which is also why nothing here can be taken down by one.

Session

Role
Director
Leads with
Contracts, margin and exposure
Purchase approval limit
No limit
Date
Thu 13 Aug 2026
Migration dry runs
0