™
The Filing — one tree per project
00THE HUB
01INBOX / UPLOADS IN
02OUTPUTS ISSUED
03DAILY DIARY
04PROGRESS PHOTOS
05DRAWINGS
06ORDERS & PROCUREMENT
07DELIVERY TICKETS
08SURVEYS & REPORTS
09HEALTH & SAFETY
10QUALITY EVIDENCE
11COMMERCIAL
12WEEKLY REPORTS
13MEETINGS & MINUTES
14PUNCH CARDS
15CONTRACT & CLIENT
16HANDOVER & O&M
17ARCHIVE
18TEMPLATES
Lands ready-made on your shared drive — SharePoint, OneDrive or Google Drive. AI-ready from day one.
The Universal Construction Hub™
The Universal Construction Hub™
Built on transparency and collaboration
One workbook, one record.
Built on 35 years of construction knowledge,
running on live work today.
Any job, any scale.

One workbook, one record.

Built on 35 years of construction knowledge and running on live work today.
Any job, any scale — one plot or a hundred, housing or commercial.
Priced per development — no per-user fees; optional services extra.

Facts drive the hub. Judgement is recorded and labelled, never passed off as fact.

Ask for a priceWhat it does
PROGRAMMESpre-con · construction · lookaheadsDELIVERYdaily record · punch cards · trackersCONTRACT & STATUTORYplanning · RFIs · risk registerQUALITY → HANDOVERITP · snags · O&MREPORTS & BOARDSweekly pack · comms log · document controlCOMPLIANCERAMS · registers · golden threadCOMMERCIALprocurement · CVR · cash flowTEAM & RACIcommunication · collaborationDASHBOARDlive · read-only · reads every tabearly warnings · act on redAI-READY · HUMAN-APPROVEDONE WORKBOOK · 70+ LINKED TABS · ONE LIVE DASHBOARD · SELF-CHECKING · AI-READY
Conception to completion.
70+ linked tabs · one live dashboard · self-checking
35 yrs in constructionproving on live workAI-ready · AI-optionalpriced per development
Ask for a price
Why it's different

Three things nobody else will say.

Yours for good

The industry rents its software by the user, by the month, forever. DCMS sells a one-off licence for one development, from conception to completion. No per-user or per-seat fees. Or have DCMS run it as a managed service: a monthly fee per development, no tie-in, cancellable on 30 days’ notice. Your job's record is yours, kept on your drive.

One workbook, one record

Programme, commercial, compliance, quality, health & safety, the daily record — one connected workbook. A fact is keyed once, at source, and ripples everywhere it's needed. No modules that scatter the job across five systems.

Zero-adoption technology

It's Microsoft Excel. No logins, no training courses, no implementation programme, no IT gatekeeping, no macros to block. It works offline in the cabin. We're not asking the industry to change — we've organised what it already does.

The product

One licensed workbook, configured to your development.

The Hub is one Microsoft Excel workbook plus a shipped drive filing system and full documentation, configured to one named development from your declaration. No internet required to operate. No add-ins. No macros. AI operation optional — never required.

1
Connected workbook
70+
Linked tabs, configured to your job
1
Live dashboard

Front Door

Welcome, navigation, project setup, directory, dashboard, drive map and search.

Programmes

Pre-construction and the construction programme with dropline, frozen contract baseline, trade lookaheads — dates compute from your declared stages and lead-times.

Delivery Engine

Punch cards and returns, daily site report, progress record, plot tracker, weekly progress, action tracker.

Commercial

Orders, call-offs and procurement, materials, hired assets, budget & CVR, cash flow, prelims, variations, subcontractor tracking, contract administration.

Compliance Station

RAMS, inductions, permits, statutory inspections, fire, COSHH, temporary works, waste — register-and-evidence, paired to the drive. Golden-thread discipline by design.

Contract & Statutory

Planning conditions, statutory agreements, utilities, warranties, risk register, information required, drawing register.

Quality → Handover

ITP & quality, setting-out, photo trackers, snags, handover, O&M, aftercare and lessons learned.

Boards

Weekly report pack, monthly report, key dates, delay tracker, comms log, document control, RACI.

Self-Checking

Live system health checks, with the user manual, troubleshooting and input rules built into the workbook itself.

The pipeline — one spine carries the whole job

Pre-Con

RIBA 0–4 · tender · lead-ins

Set Up

project setup · directory · programmes

Delivery

RIBA 5 · registers live · reports

Handover

RIBA 6 · O&M · snags closed

Completion

RIBA 7 · final account · lessons

GREYnot in play
LEMONfeed me
AMBERin motion
GREENnailed
REDalarm

One language, five words — every role, same colours: lemon asks · amber moves · green banks · red shouts. Red means alarm, nothing else — act on red.

Document control

One tree per project. Document control without the department.

The Hub drives; the drive stores. A numbered folder structure lands ready-made on the shared drive your business already runs — SharePoint, OneDrive or Google Drive — so every document the project produces has one home. The Hub logs and links; the folders hold the copies; the registers stay the truth.

Permissions built in

Your inner team sees everything. Each subcontractor is shared only their folders. Consultants and subcontractors join free on their own accounts — no per-seat cost, ever.

Ships complete

Numbered folders including the Compliance Station, a templates library, setup guides and an ISO 19650 naming kit — plus your Licence Pack, fingerprinted at delivery so you always know your file is the genuine one.

One habit protects it all

A dated copy of the Hub into its folder at the end of each week — last week is always safe. Structured, connected, AI-ready — and on record.

The tree — nineteen folders, one per project
00THE HUBthe workbook — one workbook, one record · AI-ready
01INBOX / UPLOADS INthe front door — four lanes, swept daily
02OUTPUTS ISSUEDwhat left the building
03DAILY DIARYthe day, dated the day it happened
04PROGRESS PHOTOSdated, geotagged originals
05DRAWINGSCurrent / Superseded — only Current is built from
06ORDERS & PROCUREMENTthe commercial paper trail
07DELIVERY TICKETSevery ticket, named by date
08SURVEYS & REPORTSwith valid-until discipline
09HEALTH & SAFETYthe Compliance Station — inspector-ready
10QUALITY EVIDENCEhold points · Part L photos · warranty items
11COMMERCIALCVR backup · valuations · cost evidence
12WEEKLY REPORTSFriday's issued packs, week by week
13MEETINGS & MINUTESdecisions transposed same day
14PUNCH CARDSthe capture loop's paper trail
15CONTRACT & CLIENTinstructions in writing or they didn't happen
16HANDOVER & O&Mthe finish line builds from day one
17ARCHIVEsuperseded anything — nothing is deleted
18TEMPLATESthe blanks library — copy out, never edit

The one rule: everything arrives through the front door, is logged, and is filed to its subject home. The register is the index; the folders are the shelves — and the Hub's log row finds any file forever.

The front door & the job mailbox: everything lands in 01 INBOX — four lanes: mail · voice · paper · third-party — swept daily. One job mailbox per development, on your domain, owned by you: CC the job on every project email and the chronology builds itself. Permissions: your team sees everything; each subcontractor sees only their folders — free, on their own accounts. And it's built for AI from the first file: at the AI tiers, your chosen AI drafts the register rows straight from these lanes — a named person approves every one.

How it works

You answer a questionnaire. We do the rest.

1

Declare

You complete the declaration — a plain-English questionnaire about your development: plots, stages, trades, dates. That's your part done — and the build clock starts the day it's complete.

2

We build

Your Hub is configured from your declaration — programme dates computed from your stages and lead-times, registers set to your job.

3

Delivered

The workbook, the drive filing system and your Licence Pack arrive together, ready to run. No implementation programme. No training course.

4

Run the job

Key a fact once; the Hub carries it everywhere it's needed — and support stands behind you per your chosen door.

WHAT THE DECLARATION ASKS — A TASTE

Plots and house types · stages and sequence · trades and packages · key dates and lead-ins · construction method (masonry · timber frame · light-gauge steel) · higher-risk building, yes or no. Plain English, no surveys, no site visit — what you already know about your own job.

DELIVERY DAY ALSO SETS UP

Your job mailbox (ten minutes, your domain, you own it) · drive permissions configured to your declaration · your AI posture declared — self-run, monitored or managed — with every grant named, revocable and on the record. AI-ready from day one; AI-optional forever.

One workbook, every seat

One keeper. The whole team.

One person keeps the record — that's why it stays trustworthy. But the Hub is built for every seat on the job, and the seats off it: client, consultants, supply chain. The drive is where they all meet.

Feed it

Trades and supervisors feed the record from the field — punch cards and returns, captured once, at source. A fact is never re-typed.

Say it

Communication has one home: every instruction, reply and decision runs through the logged comms channel — team-side and out to client, consultants and supply chain. RFIs and information required tracked to a name and a date. If it matters, it's in writing, and it's in the record.

File it

Evidence lives on the shared drive — photos, certificates, permits, deliveries — filed to numbered folders the whole team can reach, each one paired to its register in the Hub.

Read it

The job publishes itself: the weekly report pack, boards and registers go out to the team, the client and the boardroom — everyone working from the same record.

The user guide

Self-taught in five minutes.

The pattern behind everything: file the document, log the line — the Dashboard does the rest. Five habits run the whole system, and the full operating guide ships with every Hub.

1

File it

Every document into its numbered folder on your shared drive.

2

Log the line

A date in, a tick when done. Ten seconds a job.

3

It reads itself

The Dashboard pulls every register live. Nobody types the reports.

4

Act on red

Early warnings flag while there's time — every flag gets an owner and a date.

5

Friday copy

A dated copy of the Hub into its folder — last week is always safe.

Four rules. That's the training.
1
HIDE, NEVER DELETE

The Dashboard's formulas reach into every tab — deleting one breaks them. Right-click → Hide; unhide any time.

2
THE PASTE RULE

Enter or paste VALUES into input cells only — never tabs, rows or formula blocks, never over shaded formula cells. Copying FROM the Hub is always safe.

3
PACKS RUN ALONGSIDE

Packs are separate workbooks with zero formula links to the Hub — add or remove any time; results go into the Hub's normal input cells.

4
KEEP FILE NAMES AS DELIVERED

The folder structure and the Friday-copy habit rely on names staying put. Rename nothing you didn't create.

THE CAPTURE LOOP — every route, same five beats: capture → drop → transpose → approve → land — and every landed row points at its evidence. Prompt cards for voice and mail ship in the templates library and work with any AI you already use. AI drafts — a named person approves. AI-ready. AI-optional.

The reports

Nobody types them.

Every Monday the weekly progress report already exists — built from the same lines the team entered through the week. Every month-end, cost and value reconcile from the same live numbers the job runs on — not a comfortable version.

A named person reviews and issues; issued copies file to the drive, so every week's position is on record. The RAG board (red–amber–green) carries a rule the trade will recognise: no amber without a why — and the report ends with the ask, because a report that doesn't ask for a decision is just weather.

Entries are typed or spoken: at the optional AI tiers, a voice note from the site walk becomes drafted diary rows and report commentary — and a named person approves every word before it stands. At the AI tiers, typing is optional — the record isn't.

THE WEEK — EVERY ROLE ON ONE PAGESPECIMEN · ISSUED FRIDAY
SITEdiary complete 7/7 · photos logged · 2 punch cards closed
PROGRAMMEweek on plan · lookahead issued · brickwork plots 14–17
COMMERCIALvaluation submitted · 3 orders raised · CVR updated
DESIGN / RFIs2 RFIs answered · 1 open (9 days) — chased
COMPLIANCERAMS current · scaffold inspection logged · zero open actions
CLIENT / CONTRACTinstruction logged · early warning raised: lead time
DCMS UNIVERSAL CONSTRUCTION HUBspecimen page — illustrative entries

Not one voice — the team's week. Every line traces to a keyed fact with a date and a name; the report assembles itself from the registers, and nobody writes it twice.

The Hub's weekly construction progress report — specimen with illustrative values: RAG board, programme status, early warnings, commercial summary and decisions needed
The Hub's Weekly — specimen, illustrative values
The AI layer

AI-ready. AI-optional. Human-approved.

The Hub is AI-ready by design — named registers, one connected structure, an AI manifest shipped in the drive — so whenever you choose to switch it on, the AI reads a system built to be read. And it is the whole product with no AI at all — fully functional, offline in the cabin. When you want the back office, you choose the tier: AI reads your Hub and prepares — reports, summaries, checks — and a person approves before anything stands. That's the rule at every tier: AI prepares, a human decides.

And the process is on show, not in the small print: speak the site walk and the diary drafts itself · CC the job mailbox and the correspondence log builds itself · every draft lands as rows for a named person to approve — capture → drop → transpose → approve → land. Five beats, any AI you choose; with a cloud AI, data leaves your drive only under the service you chose.

Your choice, not a condition

From zero AI to a full AI back office — declared at order, changed when you choose. The product never depends on it.

Nothing phones home

No telemetry, no cloud dependency, no data leaving your drive unless you choose a cloud AI tool. The Hub runs on your file, in your Excel, on your machine.

Your file is protected

Every Hub ships with its rights notice embedded — text-and-data-mining, training and inference rights expressly reserved. DCMS does not use your job's record to train any AI model.

Read before buying

What it deliberately doesn't do.

These are design decisions, not omissions. Published plainly, because that's how we price as well.

Pricing

Priced per development.

In a market where the subscription tier won't print a number, you get yours in writing — for your development, before work starts.

One licence, one development

Priced per development from your declaration and confirmed in writing before the build starts. For the life of the job, conception to completion. No per-user fees, no renewals.

AI-ready at no extra cost

Every Hub ships with the capture kit — voice and mail prompt cards for the AI you already use. Optional monitored and managed AI tiers are quoted from your declaration; AI prepares, your named person approves.

Ask, and it's in writing

Tell us the development and the stage it's at. You'll have a price in writing, not a tier to decode, and the declaration that fixes it. Ask for a price.

Why

Why I built the Universal Construction Hub.

Thirty-five years in construction — from the tools to senior management, cabin to boardroom — and one thing never changed. The information was always there. It was the finding of it that cost the job.

Every seat on a job has felt it: the hours spent hunting for a drawing issue, re-typing figures already typed somewhere else, chasing a date confirmed in a meeting nobody minuted, then writing it all up for someone who needed it yesterday. The Hub turns that time around. The job's record is live, so the report is already written by the time you'd normally start it.

“The information was always there. The Hub is what finally connected it.”

The hours come back

To where they count, for every seat. The site on H&S and quality inspections and solving problems while they're still small. The commercial team on the numbers, not the paperwork. The designers on the answers, not the chasing. The directors and the client on decisions, with the facts already in front of them.

One RAG language

Green, amber, red — the same meaning on every tab, and unconfirmed is never green. Open the dashboard and the job tells you where to look. Early warnings flag before a date slips, not after, and anything red carries a name and an action beside it. No training course. It's Excel, it's colour, and it's honest.

Every owner feeds the Hub

It runs on the team, not on one person. The site reports the progress, the QS keeps the commercial lines, the designer answers the RFIs, the client sees the status. Every RFI carries a name and a close-out date. Every risk links to the question whose answer retires it. Nobody chases; the record does.

One workbook holds the programme, the registers and the evidence. When the day's progress goes in, the programme moves, the lookahead moves, the percentages move and the report moves — because they are the same numbers. Nothing is typed twice. Nothing waits for Friday. The programme is built from what the site actually knows — declared stages, real lead times, the sequence the trades will work to — so it is realistic on day one and honest every day after. Move a date and every task that depends on it tells you what it costs. Site to boardroom, one conversation.

AI is how it got built. No software house, no IT department. Thirty-five years of site knowledge, structured by AI into a linked system — thousands of formulas, every tab reading every other, tested hard and proved on live work. The judgement is mine. The architecture is the machine's. The record is yours.

Everyone reading the same page, on the same day. Your drive. Your hub. One workbook, one record.

The mission: flow the whole construction process — unify teams, site to boardroom. Authenticity first — we all win together, nowhere to hide. One workbook, one record.

About DCMS

Built by the trade, for the trade.

DCMS was founded by a builder with thirty-five years in UK construction — cabin to boardroom, every seat on a job at one time or another. The Hub is that experience, cast into a system: not software imposed on the industry, but the industry's own way of working, organised and connected. And it isn't a demo — it's running on live work today, and every function on this page is tested there before it's offered to you. Housing, commercial or refurbishment, one plot or a hundred: the method is the same, the scale is yours.

“Unify teams, communicate, collaborate — from the site to the boardroom. We all win together, take the losses together, nowhere to hide. One workbook, one record.” Tony Dolan · Founder, DCMS
Straight answers

Asked before you order.

Does the Hub do Gantt charts?

Yes. The master and short-duration construction programmes run as a live Gantt chart in Excel, with a dropline and a frozen contract baseline — dates computed from your declared stages and lead-times, not drawn by hand. Already programmed in Asta or MS Project? Send the export — it comes into the Hub as part of the build.

Is this construction project management software?

It does that whole job — programme, progress, commercial control, compliance, quality and reporting — but as one Microsoft Excel workbook licensed per development, not a per-seat platform subscription.

Isn't it just a spreadsheet template?

No. A template is a blank grid somebody fills in on a Sunday night. The Hub is an engineered, linked system — 70+ tabs driven by formulas and one live dashboard reading them all. You don't build it; you run it.

Will my subcontractors actually use it?

That's exactly why it's built in Excel — the software your trades already open every day. No logins they'll never activate, no new platform to ignore, no drifting back to WhatsApp. Subcontractors are shared only their folders on the drive, free, on their own accounts.

Does it handle CVR and cash flow?

Budget & CVR, cash flow forecast, orders, call-offs, variations and prelims — and at month-end, cost and value reconcile from the same live numbers the job runs on.

What about RAMS, snagging and the site diary?

The Compliance Station holds RAMS, permits to work, inductions and statutory inspections. Snags have their own register. The daily site report takes one row a day.

Does it do document control and drawing registers?

A drawing register with revisions, a document control tab, and a numbered filing system that lands on SharePoint, OneDrive or Google Drive — document control without the department.

What if I can't provide all the information?

The declaration tells you exactly what's needed, in plain English — no surveys, no site visit, just what you already know about your own job. The price is firm for a completed declaration, and the build starts the day it's complete. Anything genuinely undecided is declared as unknown; when the answer lands, it's a variation at the published rate. Nobody chases anybody — the questionnaire is the gate.

Does it support the Building Safety Act — gateways and the golden thread?

The Hub's whole pattern is golden-thread discipline: every fact logged with its who, when and why; evidence filed to one controlled tree; drawings with revision history; nothing ever deleted. Records that arrive at a gateway review already organised, with their audit trail intact. The Hub records and evidences; it does not discharge your statutory duties, which stay with you. Running a higher-risk building? Say so in the declaration — the Hub is configured to the job you declare.

What build types does it suit?

Any named development — housing, refurbishment, commercial fit-out, civils. The declaration shapes the Hub to your job, including construction method: masonry, timber frame or light-gauge steel, the registers and code library speak the method you're building. One Hub per named development is the licence — and the design.

What does it cost?

Each Hub is priced per development, from your declaration, and confirmed in writing before work starts. No per-user fees. Optional services are priced separately. Fix Promise: 30 days from delivery.

Already running a Hub? Troubleshooting
A formula cell shows #REF! or the Dashboard looks broken

Almost always the paste rule or a deleted tab. Restore from the last Friday copy in folder 01 — last week is always safe — then re-key the few days since into input cells only. That habit is the whole recovery plan.

I can't find a file on the drive

Don't browse — ask the register. Every logged file has its row, and the log row finds any file, forever. If it isn't logged, it went around the front door: file it to 01 INBOX, log the line, and it's in the system.

The job has changed since my declaration

That's normal — jobs move. Small changes are handled in the Hub (hide what you don't need; never delete). Structural changes — new stages, a different method — are a declared variation at the published rate, so the engine stays true to the job.

Someone renamed or moved files and links broke

Rule four exists for this: keep file names as delivered. Put the names back and the links stand again. Nothing is lost — nothing is ever deleted — and the Friday copy covers the worst case.

Who do I contact, and how fast is the answer?

Email — a person answers, not a ticket queue, with thirty-five years on site behind every reply.

Talk to us.

A conversation costs nothing and we don't do sales calls — you'll be talking to the builder who made it. A register you run that the Hub doesn't have? Custom workbooks are built to your format, quoted within one working day.

tony@dcms.uk