From forecast to proof, in five steps.

Step 1 · Connect

A read-only door into your CDE

Someone with the right to do so connects ScanCDE to the system the project already uses. The access is read-only: ScanCDE can see what is there, and cannot add, change or delete anything.

It works with the systems your projects already use: Autodesk Construction Cloud, SharePoint, M-Files, Procore, Aconex, Dalux, Asite and others. If yours is not on the list, we add it on request. A project can use more than one.

Step 2 · The plan

Load the forecast

Each delivery partner's register (the MIDP or TIDP) says which documents will be delivered, to which status, by when. ScanCDE holds that plan, including your own order of statuses, such as S3, then S5, then A1 and beyond.

Partners keep their own register in one controlled place, see only their own company's documents, and every change records who made it and when.

Step 3 · Scan

Read every document, once and carefully

ScanCDE walks the folders, reading file names, statuses, dates, uploader names and a link back. It does not copy drawings or models. It matches each file to the plan by its document number.

If a scan cannot read everything, because a system was slow or unreachable, it says so and keeps the last complete result. It never reports something missing just because it could not look.

Step 4 · Judge

Where should it be, and where is it?

For any gateway, or for today, every forecast document is judged, actual against forecast, on its planned steps and dates. The result is plain: on plan, behind plan, or not in the CDE. It also flags naming problems and duplicates.

Judge the same scan as at Gateway 1, Gateway 2 or today, without scanning again.

Step 5 · Evidence

A result you can put your name to

See it for one project or across a programme, company by company. Export it as Excel or PDF in your own logo and colours for a gateway pack, a client meeting or an auditor. Scheduled scans keep it current, so the answer is ready before anyone asks.