Which planning tools does it work with?

It reads programmes exported as Microsoft Project XML, Primavera XML or Primavera XER, and writes Microsoft Project XML. Microsoft Project opens that natively, and both Asta Powerproject and Primavera P6 import it. A CSV of planned against actual is produced alongside for anything else.

Can photographs go into the programme itself?

No planning format can hold a photograph, so nothing that claims to embed one is telling the truth. What goes into the programme is the actual dates, a note naming the evidence and a link to it. The photographs travel alongside in an evidence pack under ISO 19650 container names, each with a SHA-256 so anyone can verify the copy they were sent.

Where do the actual dates come from?

Either from your programme, or derived from the first and last evidence captured against the activity. Derived dates are labelled as derived everywhere they appear, because evidence of work on a date is not by itself proof the activity started or finished on it. You can also turn the derivation off and export only the dates your planner asserted.

Programme export

Planned against actual, with the proof attached.

Your programme knows when the pile caps were meant to be poured. The record knows when they were, who was there and what it looked like. Bring the two together and every variance on the bar chart has a photograph, a timestamp and a checksum sitting behind it.

Start on one site Why it matters on a claim

Beta · Works with Primavera P6, Asta Powerproject and Microsoft Project

What you get

A programme that carries its own evidence

Actual dates against the baseline

Import the programme from your planner. Every activity comes back with its actual start and finish set from what was captured on site, and the variance in days against the plan.

The evidence attached to the activity

Each activity gains a note naming what was captured against it and a link straight to it. Open the programme, click the activity, see the photographs from the week it slipped.

ISO 19650 names, end to end

Every item in the pack carries its ISO 19650 container name alongside its original filename, who captured it and when. Status and revision stay as metadata, never in the name.

A checksum on every item

The pack is a set of copies, and copies prove nothing on their own. A SHA-256 against each file lets the other side hash what they were sent and check it themselves, which is what turns a copy back into evidence.

Nothing quietly left out

Before you download anything, you are told how much of the record actually attached to an activity, and anything that did not is listed with the reason. A tool that only ever reports success is no use in a dispute.

By download or by API

Pull it from the portal when you need it, or have your planner fetch it on a schedule. The API returns the same coverage figures, so a drop in capture shows up before it reaches a submission.

How it works

From programme to evidence pack

Export your programme

From Primavera P6, Asta Powerproject or Microsoft Project, as XML or XER. Each import is kept as its own revision, so an earlier baseline stays readable.

We match the record to it

Photographs, messages and diaries are attached to the activity that was live when they were captured, with what was said narrowing it where several were running at once.

Check the coverage

See how much attached before you produce anything, and what did not, and why.

Take the pack

The programme file, planned against actual, and the evidence under ISO 19650 names with a checksum each. Ready to open, or to hand over.

In beta, and what that means. The export is built and tested, and the file is valid against Microsoft’s published schema, but it has not yet been opened in every version of every planner. If you are an early user we want to hear how it lands in yours, and we will fix what does not. Beyond that: no planning format can hold a photograph, so the evidence travels beside the programme rather than inside it. Where an actual date is derived from what was captured, it says so: a photograph on the third proves work happened on the third, not that the activity started then, and a pack that blurs those two is the one that gets picked apart. This organises and evidences a record. It does not certify compliance and it is not a substitute for the notices your contract requires.

Put the evidence where the argument happens.

The record is being captured anyway. This is what makes it usable by the person drawing the delay analysis.

Start on one site Ask us about your programme

Oracle and Primavera are registered trademarks of Oracle Corporation. Asta Powerproject is a trademark of Elecosoft plc. Microsoft and Microsoft Project are trademarks of the Microsoft group of companies. Construction Metric is not affiliated with, endorsed by or a partner of any of them. These names are used only to describe the file formats this product reads and writes.