In development

You are welcome to use it on real jobs. Feedback shapes what gets built next, and beta testers keep their pricing fixed for life.

In development · Beta pricing fixed for life

Solutions · Campus

Campus and multi-building

Eighty buildings is not eighty projects. Graftix uses a parent project with child sites underneath, so each building has its own drawings, tasks and team while the programme, the materials and the money roll up into one picture.

Talk to us Book a demo

The problem

Most tools break somewhere around building twelve

They were designed around a single site with a single drawing set. Run an estate through them and you end up either with one unmanageable project or dozens of disconnected ones, and no way to answer a simple question about the whole thing.

One project, unusable

Every building in one flat list. Thousands of tasks, no meaningful structure, and an engineer who cannot find today's work without scrolling for a minute.

Many projects, disconnected

One project per building. Clean to work in, useless to report on. Every estate-wide question becomes a manual exercise in a spreadsheet.

Materials float free

Kit ordered centrally, consumed per building, reconciled never. Nobody can say where the last two hundred units went.

The structure

Parent above, buildings below

The parent project holds the contract, the budget and the estate-wide programme. Each child site holds one building, block or zone with its own drawings, tasks, kit and team. Work happens at the child. Reporting happens at the parent.

A child site per building, block or zone, with its own drawing set
Engineers see their building, not the whole estate
Progress, programme and cost roll up automatically to the parent
Area portal pins jump from the site plan into any building

See project structure

Shot 19

Parent and child campus site tree

1600 × 1000

Shot 09

Portfolio financials across every building

1600 × 1000

Materials and money

Order centrally, consume locally, reconcile automatically

Material pools sit above the buildings and decrement as tasks in any child site claim from them. Every claim is logged against the task that used it, so the estate-wide stock figure is real rather than a periodic stocktake.

Pools that decrement as work is assigned across any building
Purchase orders raised centrally, consumption tracked per site
Contract value, cost codes and spend rolled up across the estate
Resource allocation visible building by building

See materials and financials

Graftix Live · from £10 per device per year

Built during a real campus refresh

The parent and child structure exists because an eighty-plus building infrastructure refresh needed it. So does Graftix Live, which pulls device status from the network estate onto the drawing so verification stops requiring a site visit and a phone call.

How Graftix Live works

Shot 17

Live device status across a campus building

1600 × 1200

Campus

Estates are where this earns its keep.

If you are running work across more than a handful of buildings, the structure matters more than any single feature. Tell us what the estate looks like.

Get in touch All solutions