Skip to content
Consulting + software · Project decisions, claims and arbitration

The decision and evidence layer
for major projects.

On a major project, every trade-off settled in committee ends up on someone’s table one day: the client’s, the expert’s or the arbitral tribunal’s. SherpaPM costs its impact on time and money before you decide, then keeps dated evidence of what you knew when you decided. On top of your tools, with experts at your side.

Primavera, SAP, document systems and models stay in place: SherpaPM connects to them.

What SherpaPM reads, links and checks
Models, drawings, schedules, contracts: every decision linked to its records.

A laptop opens to SherpaPM. IFC 3D models, 2D drawings, the Primavera schedule, SAP costs, contracts, email and meeting notes converge into the software, each record with its source. The screen shows schedule health, the cash position, then schedule quality scored 91.9 out of 100. A fictitious logistics warehouse under construction assembles discipline by discipline: structure, ventilation, power and the HV/LV room, sprinklers, among the site’s lifts. SherpaPM finds five clashes between the fire main and the roof rafters, then the view switches to the 2D drawing, where revision B is overlaid on revision A and the interface decisions go back to review. Finally, the decisions screen ranks the delays that drive the finish date by financial exposure, shows who pays and what acting would gain; options are costed, the decision is checked before it is recorded, and the project history is ready for a claim or arbitration.

What SherpaPM can read

  • 3D models (IFC)
  • 2D drawings (PDF, DXF)
  • Primavera P6
  • SAP / Finance
  • Contracts / documents
  • Outlook / Gmail
  • Meeting notes

Two moments when a decision gets expensive

When you have to decide, and when you have to justify it.

Deciding without costing means paying later. Justifying without dated records means negotiating from weakness. We start from a real decision on your project, never from a tool roll-out.

01

RECOVER YOUR DIRECTION

Get a struggling project back on track.

Every week of slippage has a price. Isolate the cause that really consumes the float, cost your options at P50 and P80, and decide before the next committee.

Explore project recovery
02

SECURE THE TRADE-OFFS

Support your project from start to finish.

Every trade-off is prepared, costed and recorded with its reasons. When a change calls it into question, it goes back to review before it takes effect, not after.

Explore end-to-end support
03

RECONSTRUCT THE FACTS

Reconstruct the project’s history.

A claim received or to bring, a defence, arbitration proceedings: recover the dated thread of facts and records, for and against, before the other party writes it for you.

Explore reconstruction

Why SherpaPM

Not another tool. A layer that decides and proves.

Primavera, SAP, document systems, models: your tools record what was done. The reason behind each decision gets lost between two committees. SherpaPM connects to them and keeps what happens between them: clashes, decisions, records and financial consequences.

01

Technical and contractual memory

Each fact carries two dates: when it happened, then when it became known. Records are chained by fingerprint, any alteration shows, and the decision history can be replayed on any date.

02

A non-intrusive layer

IFC models, PDF and DXF drawings, Primavera, SAP, document systems: SherpaPM reads what exists, computes clashes between disciplines and flags the decisions a new revision calls into question.

03

Costed trade-offs, checked decisions

Simulated impact on time and cost, earned value, compared options. An incomplete decision (missing source, single option, open contradiction) is not recorded.

04

Claims, disputes and arbitration

Notice periods tracked, sourced chronology, allegations tested against the records, for and against: a structured file for your counsel and experts. The legal position remains theirs.

Competitive edge

  • Automatic cross-checkingEvery email, schedule, amendment or cost received is checked against the rest of the file: contradictions, threatened milestones, notice deadlines, cost drift or silent activities surface without anyone searching.
  • Computed, sourced, partitionedCross-checking runs without generative AI: each alert cites its records and what was known on its date. A record reserved for one organisation stays invisible to the others.
  • Decisions prepared, never imposedAn alert becomes a candidate decision: options drawn from the records, simulated effects on time and cost, cost of doing nothing. The call stays human.
  • Interfaces held through to archiveDated agreements between packages, joint validation, frozen definitions, reminders and sealed archive: a technical interface no longer falls between two contractors.

Mission 01Diagnosis · Scenarios · Recovery

When a milestone slips, what needs to change?

Add people, postpone a delivery or revise the scope? SherpaPM first isolates the cause that really moves the milestone: the one consuming critical-path float. Then we cost each option with you, including its uncertainty (P50, P80), before you commit to a new course.

Discuss your recovery plan
The mission on film48 s · in French · illustrative example

Animated film. A commissioning milestone slips by 42 days. Of three delays, only the one exceeding the float on the critical path moves the milestone. Three options are costed and compared: resequence the work, add targeted resources or postpone. Project management selects targeted resources; the decision is recorded, then turned into dated actions with owners. In this example the trajectory is recovered at 5 days instead of 42.

The recovery planFrom the first variance to an action plan

ESTABLISH THE FACTS

What is causing the delay?

We compare the baseline schedule with progress reported by the teams. Critical-path analysis separates delays absorbed by float from the one that moves the milestone. Causes still to be checked are listed.

  • Baseline schedule
  • Field observations
  • Documented gaps

What you getA recovery plan with clear priorities, owners and dates.

Mission 02Scoping · Trade-offs · Handover

A decision taken today will be reread fourteen months on.

From the outset, we help your team identify which decisions are due and at which reviews. SherpaPM keeps the memory of each decision. When a substitution or a new model revision challenges it months later, it goes back to review before it takes effect.

Secure your trade-offs
The mission on film50 s · in French · illustrative example

Animated film. A major project is shown as a climb from camp to camp up to handover. At launch, each decision role is set. At each review a decision is linked to an owner and a due date. A field report leads to rescheduling an intervention and the proof returns to the file. A technical substitution proposed during execution challenges a decision taken fourteen months earlier, so it goes back to review. At handover, the operator receives the decisions, open reservations and commitments to transfer.

The decision logFrom scoping to handover

AT LAUNCH

Who decides, and when?

We agree milestones, responsibilities and a review schedule. Your team identifies decisions ahead of time so they can be addressed before they hold up the work.

  • Milestones
  • Decision owners
  • Review calendar

What you getThe memory of decisions, with their rationale and records, handed to the team taking over.

Mission 03Claims · Disputes · Arbitration proceedings

In a dispute, the party with the dated facts leads the discussion.

What was planned. What happened. What was decided. SherpaPM reconstructs the project’s history from available records. Each fact keeps the date it happened and the date it became known, and any alteration of a record shows. Deviations and contradictions come into focus, for and against. The legal position remains your counsel’s.

Let’s prepare your case
The mission on film58 s · in French · illustrative example

Animated film. A claim arrives: 25 days of extension and 0.9 million euros of extra costs. Thousands of records are scattered. The schedule set acceptance on 18 June, the site on 21 June, and the contract requires the test report: the contradiction is shown, not decided. Records are placed back in time with the date each event occurred and the date it became known. Each allegation is set against the records that support it and those that contradict it. Each record carries a fingerprint that reveals any alteration. Three files take shape: claim, defence and arbitration proceedings; the legal position remains the counsel’s.

Your project’s storyReconstruction journey

THE STARTING POINT

What was planned.

The contract, baseline schedule and original commitments establish a common starting point for understanding the project.

  • Contract
  • Baseline schedule
  • Commitments

What you getA sourced chronology. Facts linked to their records, ready for your counsel’s review.

Fictitious case · logistics warehouse

An electrical room frozen too early: from a coordination clash to a site instruction.

The HV/LV package is awarded late. The general-works contractor has already closed its design to start on site. Coordination freezes the electrical room without regulatory and maintenance requirements. Here is how SherpaPM works the case, step by step.

Illustrative view of the electrical room after initial coordination: HVAC duct in the switchboard clearance zone, narrow door — fictitious data

01 · The problem

A coordination clash nobody has seen yet.

Design had to close fast so the general-works contractor could start. The HV/LV package, awarded late, was left out of coordination. General works in the room are due to start on 3 June.

  • HV/LV contractor notified six weeks after the general-works design freeze
  • A general-works HVAC duct crosses the clearance zone in front of the switchboard
  • 0.90 m door: the transformer cannot be replaced

Fictitious data generated by SherpaPM. This case is not a client pilot, a real model, a certification or a regulatory compliance opinion.

Demanding projects, shared responsibilities

Who is SherpaPM for?

For leaders who make the calls on complex projects, from investment to operations. One thread of decisions and evidence, shaped around each sector and each role.

Our sectors05 / 05

Choose a badge to explore the sector’s challenges.

Scroll through the badges · Hover over or pull a badge · AI-generated illustrations

Selected sector01 / 05

Energy · Solar

Manage interfaces through to commissioning.

Photovoltaic projects: connect design, procurement and grid connection to prepare commissioning.

Points to consider

  1. 01
    Panels and inverters

    Link orders, deliveries and installation sequences.

  2. 02
    Grid connection

    Track electrical interfaces and connection prerequisites.

  3. 03
    Testing and acceptance

    Bring together inspections, outstanding items and performance commitments.

A shared view. A clear role for everyone.

OWNERS

Project owners

Maintain control of the programme, budget and key decisions.

DESIGN

Design & engineering teams

Coordinate studies, interfaces and technical deliverables.

CONTRACTORS

Construction companies

Connect execution constraints, resources and contractual commitments.

AMO / PMO

Owner’s advisory

Prepare trade-offs, quantify deviations and trace decisions.

OPERATORS

Operations teams

Prepare acceptance, commissioning and continuity of operations.

From the field to decisions

The field informs decisions. Decisions guide the field.

A fact reported by the team informs a choice. Once approved, the decision becomes an action to carry out and verify in the field.

Field⇄DecisionIllustrative example
A dated factManual navigation

Disruptions, blockers and observations come back dated, with photos and records. The fact is assessed on evidence, not on hearsay.

Information governance

From the source record to the decision.

You should be able to justify a disputed milestone without sharing the whole file. SherpaPM links project information to its source. With your IT team, you define who can use it and in which countries it may be processed.

SherpaPMFictional example

Decision file ELEC-07

Electrical works acceptance

Same package, same milestone: the schedule says 18 June and the site says 21 June. Which date can the committee use?

Evidence trail03
Shared file

Project catalogue

PLN-017Revision 03

Forecast date

18 June: the forecast acceptance date.

Record and version
Baseline schedule · rev. 03
Reference date
10 June
Owner
Planning lead
Effect on the decision
The milestone remains a forecast while the site issue is open.
Discrepancy to review

The site forecast is 3 days later than the schedule.

Follow the arbitration

Resolving conflicting evidence

Two dates for one milestone. Who decides?

Both records refer to acceptance of package ELEC-07. They disagree on the forecast date; the contract sets out what is required to confirm acceptance.

Fictional example01 / 04

Project analyst

SherpaPM presents the values and source excerpts for the same structured fact. The analyst checks they refer to the same milestone and sends both dates to the people responsible for verifying them.

Discrepancy open · no date selected
PLN-017

Document search

Find the passage behind a claim.

Start with a reference or a few words to find the relevant passage, its date and its source record.

1 millionsynthetic passages

In a local test, 20 searches for distinct references each returned the expected passage. Volume and response times must be assessed on your own systems.

Data sovereignty

A vault designed for your systems and jurisdictions.

With your IT and security leads, we assess deployment inside your systems or in a hybrid environment. We review hosting locations, the laws governing service providers and their remote access. You approve the scope before go-live.

IT environment
Geographic scope

Scoping brief

Internal ITOne country

System boundary
Identify the repositories that stay within your systems. List each record or extract allowed to leave that boundary.
Storage and processing
If your policy requires France, check where primary data, backups and the recovery site are located. Review support and AI service access locations separately.
Administration and keys
Identify your administrators and key custodians, and agree how support staff may intervene.
Evidence to obtain
Location map, named operators and a restore test inside the chosen boundary.

Before committing: agree access logs, restore testing, incident handling and the terms for returning or deleting records.

Three ways to start

A defined scope. A first dated result.

Each format starts from a real case. Scope, deliverables and the date of the first result are set before you commit.

01Owners · programme directors

Interface & trade-off diagnostic

Spot what will be expensive before it costs you: technical, organisational and contractual interfaces, listed and sourced.

You get

  • Interfaces between packages, sourced record by record
  • Model clashes and prerequisites to secure
  • First trade-offs costed and scored out of 100

First deliverable: the interface register

Scope a diagnostic
02Project directors · claims consultants · experts · lawyers

Pilot claim file

One dispute, one package, one period: the factual material for a claim, a defence or arbitration.

You get

  • Every fact dated twice: when it happened, when it became known
  • Contradictions, for and against
  • Missing records and notice periods

Working on a dispute for a client? Per-project access rights; the analysis and the position remain yours.

First deliverable: the sourced chronology

Scope a pilot file
03Projects in delivery

Continuous decision layer

Platform and expertise, committee after committee, through to handover.

You get

  • Every trade-off costed in time and money
  • Decisions sent back to review when a revision changes
  • Decision memory handed to the operator

From the first committee: the decision log

Plan ongoing support

Each format is quoted individually. The first conversation can take place without confidential documents.

What you can judge us on

  • Before the pilotSuccess criteria agreed together, then reviewed together.
  • Every piece of informationLinked to its source record and version; any alteration shows.
  • Every sensitive conclusionApproved by an authorised owner, never by the machine alone.
  • Recognised frameworksAACE 130R-23 for cumulative impact, FIDIC- and CCAG-type claims.

Before you commit

The questions that matter for your project.

Can you step in on a dispute that is already open?

Yes, starting from a narrow scope — one dispute, one package, one period — and the records available. The first deliverable is a sourced chronology that surfaces contradictions and missing records, prepared for review by your counsel and experts.

Does SherpaPM give legal advice?

No. SherpaPM organises facts, records and analyses, and flags what is established, disputed or missing. Liability, final quantum and strategy remain with your counsel, experts and lawyers.

How does SherpaPM differ from a scheduling tool, a document system or a BIM platform?

Those tools remain the reference in their field, and SherpaPM connects to them. It keeps what happens between them: which model clash affects which interface, which decision depends on it, which records it rests on and what was known when it was taken. An incomplete decision is not recorded, and its history stays verifiable.

Which model and drawing formats does SherpaPM read?

IFC models (IFC2x3 and IFC4) and PDF and DXF drawings. Revit, CATIA or 3DEXPERIENCE, DWG or DGN files are kept on file; analysing them requires an IFC, PDF or DXF export from your design software. Schedules are imported from Primavera P6 (XER) or connected through Primavera Cloud.

What budget should we plan and what does the service include?

The proposal defines consulting, deliverables and the role of software, along with configuration or data connection needs. The quote specifies costs, exclusions and change conditions for the agreed scope before signing.

Do we need to replace our tools or re-enter all our data?

Scoping starts with your existing tools and files. We check formats, data quality and import or connection options. Any preparation or specific connections are identified in the proposal; scenarios are developed within SherpaPM.

How do we protect our data and govern AI use?

Before sharing sensitive records, your representatives approve confidentiality, hosting, access, any AI processing, retention and data return conditions. These points are documented in the relevant agreements. The first conversation can take place without confidential documents.

The next step

Tomorrow’s disputed decision is prepared today.

Describe the trade-off to settle, the claim you received or the dispute to defend. We shape the mission that answers it with you.

contact@sherpapm.fr

Prepare our conversation

Your email app opens with your message prepared.

Let’s talk about your project