Skip to main content

Understanding How Roof Wizard Works

An overview of the core workflow in Roof Wizard, from creating accurate 3D roof models to generating full material and labour reports.

D
Written by Daniel Smith
Updated over 6 months ago

The Core Process

Roof Wizard is built on a simple principle:

Accurate roof geometry leads to accurate estimates.

Everything begins with creating a 3D model of the roof. From that model, the software:

  • Calculates roof areas

  • Simulates material layout

  • Generates complete material and labour estimates

The 3D model gives you confidence — because you can see, verify, and trust it.


The 5-Step Workflow

Every job in Roof Wizard follows the same five steps:

  1. Define the roof geometry

  2. Check that the geometry is accurate

  3. Select the roof covering materials

  4. Quantify and cost the materials

  5. Print the client-ready proposal and reports

Built-in templates let you generate reports right away. You can customise these later to match your branding and business needs.


How Roofs Are Modelled

Roof Wizard uses a form of 3D shorthand — rather than creating every detail in full CAD, it simplifies structures to lines and tags that describe what’s required. For example:

  • A single line can represent a roof edge, with attached attributes defining fascia, gutter, clips, fasteners, etc.

  • Tags attached to that line define components like fascia, gutter, clips, and fasteners

Rather than modelling every physical part, Roof Wizard defines rules for each line — so you still get highly detailed outputs without overcomplicating the modelling process, and without detailed visuals

If it can be built, it can be modelled - Including hips, valleys, dormers, gables, verandahs, atriums, barrel roofs, and skillions.


Accurate Quantities Start With Good Setup

Roof Wizard breaks components down into:

  • Area items (e.g. underlay, tiles)

  • Linear items (e.g. battens, flashings, gutters)

Each item is measured based on how it is supplied and installed:

  • Per metre (or foot)

  • Per piece

  • Per end

  • Per full length

Accessories — like fasteners, brackets, or fixings — are automatically associated with the correct item based on your setup rules.

🔧 Example:
A gutter defined as 6m lengths with 1 bracket per metre will result in:

  • Exact gutter lengths needed

  • Correct number of brackets

  • Calculated wastage or offcuts, if applicable.

This is why setup is critical:
Each building component must be defined based on:

  • How it’s fabricated

  • How it’s installed

  • How it’s supplied

  • What it costs

Once defined correctly, these components are reused in every job, ensuring faster estimates and more consistent results.


Reporting & Materials

Once your roof model is built and materials are selected, Roof Wizard generates a detailed, fully itemised output — including:

  • Full material list

  • Accessories and fasteners

  • Optional labour costs

  • Client-ready proposals

  • Supplier and installer documentation

The Reporting Stage

The reporting stage is where you bring everything together:

  • Material and labour summaries are generated based on your selections

  • After reviewing pricing, you select the specific reports you want to generate

  • These reports are built from the vast amount of data Roof Wizard creates automatically during the estimating process

To extract this data, you’ll need to use the report templates included with Roof Wizard. Initially, report configuration may seem complex — but once understood, it becomes an extremely powerful part of the software. You can extract relevant, filtered information for:

  • Internal estimators

  • Site crews

  • Suppliers

  • Clients

All from the same job model.

Tip: Roof Wizard supports both Supply Only and Supply & Install workflows.
The key difference? Supply & Install includes installation labour costs. Make sure you understand both options to get the most from your output.

Reports can be printed and exported, and are fully customisable to suit your branding and workflow.

Did this answer your question?