Planning delivery that holds the record.
Four things Certadian does today. Each one exists because of something that went wrong on a real scheme.
OVERVIEW
Open it on Monday and know where you stand.
What is waiting on you, what is late, and the next date that matters. Late items say what they put at risk rather than only that they are late, because a date on its own is not information.
DELIVERABLES
Chasing that keeps track of itself.
Every deliverable carries its owner, its approver and its current version. When one slips, Certadian shows what it holds up and drafts the chase. It shows whether the last one was opened and whether anything followed.
PACK
The pack closes when everything in it is approved.
Four sign-off gates, each recording who signed and the exact version they saw. On close the pack is zipped, the manifest is written, and both are stored permanently. Every later attempt keeps its own snapshot, so what you submitted in September is still what you submitted in September.
VERIFICATION CHECKS
Gateway 1 says one thing, the latest drawing says another.
Certadian reads the documents in the pack against each other. When the Fire Statement describes a different building from the architect’s latest revision, it says so and drafts the note that sorts it out. The discrepancy stays with the block, so when Gateway 2 comes round the reason is already there.
What it covers
Certadian is configured to the consents your scheme actually needs before you go live.
COVERED TODAY
GATEWAY 1
GLA REFERRAL
LOCAL AUTHORITY REFERRAL
ON THE ROADMAP
AUDIT
CONDITIONS
SECTION 106
GATEWAY 2
The questions that come up first.
We keep it all in SharePoint.
SharePoint, Dropbox, shared drives, personal email and a spreadsheet are fine for storing files.
Two problems. Nothing joins up, so nobody sees that a late report is holding up a pack. And it holds together only while the same people stay. When a development manager leaves, the current version in their inbox leaves with them.
We use a project tool.
A tracker only knows what someone remembered to type in. Nobody creates a task called "check the Fire Statement still matches the drawings".
Certadian reads the documents themselves, and what it finds becomes dated, attributed evidence rather than an answer you have to take on trust. Held in the UK, kept separate from every other client's, written down as it happens.
Do we have to run this ourselves?
No. Some clients hand almost the whole process to their planning consultant and only want to see two or three things a month. Others approve every document themselves. Certadian works either way, and you set the exact points where you want to be brought in.
See it on one of your own applications.
Thirty minutes on a live scheme of yours is the fastest way to judge whether this fits the way your team already works.
Book a walkthrough