For modular home builders in Australia

Every module, from consent to handover, on one record.

ModuHaus keeps the approvals, the factory checks, the photographs and the open questions for a modular build in one place - so the certifier, the factory and the site are reading the same job, and nothing waits on an email nobody answered.

Create an accountI have been invited

Written around the path a modular job actually takes here: development consent, construction certificate, the factory, transport, the site, and the occupation certificate.

The overview of a job: gates not ready, serious issues, unowned tasks, and what is waiting on whom.

What it keeps together

The registers a modular job runs on, linked to each other rather than kept in five spreadsheets and an inbox.

  • Gates

    What has to be true before a module moves on - to the factory, onto a truck, onto site. Each gate lists what is still missing and who is chasing it, and a blocking gate stops the move it is about.

  • Approvals and their conditions

    The consent and the certificates, each condition with the gate it holds and the question asked about it. Upload the notice of determination and the conditions are read out page by page, for a person to check.

  • Factory QA and evidence

    Inspection checkpoints per module, hold points that must be seen before they are covered, and the photographs and certificates filed against the gate that asks for them.

  • Issues, RFIs and variations

    Every open question has somebody chasing it and a date it is needed by. The overdue ones lead; the ones nobody owns are counted until somebody does.

The gates of a job, each with what is missing, who is chasing it and when it is due.
Gates, on a test job. Every number opens the rows behind it.

Everyone on the job, seeing their part

Access is granted to a company, not a person, so it outlasts somebody leaving - and each company sees the registers its role needs. The limits are enforced by the database, not by hiding a button.

  • The builderRuns the job: every register, every gate, who else is on it.
  • The certifierApprovals, requirements and conditions, and the evidence to review.
  • Engineers and consultantsDrawings, and the questions sent to them to answer.
  • The factoryThe modules, the specification and the inspection plan.
  • Transport and installersThe delivery and site boards, and the evidence that goes with them.
  • The ownerA page of their own: progress, photographs, and what was chosen.

The owner sees their home, not your paperwork

Invite the owner and they get one page, on their phone: where the build is up to, each module's stage, the photographs you choose to share, and the finishes you confirmed with them. Nothing is shown until you switch it on, and nothing internal is ever on it - the page reads only what it is allowed to, column by column.

A photograph is shared per photograph, not per job.

The owner's page on a phone: the job, where it is up to, and each module's stage.

It records what a person did

ModuHaus never says a thing complies. A condition is discharged by somebody, on a date; a checkpoint is passed by an inspector, with the photograph; a gate is overridden by a named person, with the reason. Judging compliance stays with the people accountable for it - the record just makes sure they have everything in front of them.

One pack for the certifier

When the certifier asks, print the certification pack: every condition and requirement with what answers it, every file on record and the verdict it was given, dated and attributed. It is the same record everybody has been working from, not a document assembled the night before.

Start with one job

A name is enough to start a project. Add the checklist, the modules and the documents as the job gives them to you; nothing needs a document to exist first. Invited by somebody already on ModuHaus? Sign in with the address the invitation was sent to.

Create an accountSign in