GESPRO: what the project manager needs to know about this platform to avoid letting documents circulate outside the official channel — and losing traceability of progress statements and FTMs
“Send via GESPRO,” “upload to GESPRO,” “submitted to the MOE via the GESPRO platform by the 22nd of each month.” GESPRO isn’t just a GED: it’s a platform that manages technical documents, financial progress statements, and change order sheets (FTM) all at once. If a contractor sends its progress statement by email instead of through GESPRO, payment can be delayed by a month.
Type | Phase | Actors | Impact | Stakes | Where |
|---|---|---|---|---|---|
Document | Execution | MOE (project manager), Client (MO), OPC (scheduling coordinator), Contractor | High | contractual | general notes of the CR, each trade’s section |
1. Operational definition + common mistake
GESPRO is a digital project- and site-management platform that centralizes document exchanges, progress statements, change order sheets, and sign-offs in a single interface. Unlike a pure GED (which focuses on managing drawings and sign-offs), GESPRO also integrates financial tracking (monthly progress statements, FTM approval, amendment distribution).
In this CR, GESPRO is used as the exclusive channel for: submitting progress statements (by the 22nd of each month), distributing approved FTMs (e.g., “FTM 04_002 distributed via GESPRO”), uploading execution drawings for sign-off, and contractors submitting technical documents. Not using this channel has an explicit contractual consequence: “any failure or delay in submitting a progress statement would expose the contractor to having their payment delayed by one month.”
Many assume GESPRO is just one of many file-sharing tools — in reality, on contracts that require it, GESPRO is the official contractual channel. A document submitted by email or on a USB drive instead of via GESPRO can be considered as not submitted at all.
2. Where it appears
In a site meeting report — recurring mentions in the general notes (usage rules) and in each trade’s section. In this CR:
“Progress statements must be drawn up on a cumulative basis, broken down identically to the detailed price breakdown (DPGF). They must be submitted to the project manager via the GESPRO platform by the 22nd of each month at the latest.”
“Execution drawings must be uploaded to GESPRO for review or sign-off at least 2 weeks before any execution begins.”
“FTM 04_002 — approved by the client, distributed via GESPRO.”
3. How to read this entry in the CR
If you read “Submit via GESPRO” → this is a contractual obligation. Check that the contractor actually has access to the platform and knows how to upload the document there.
If you read “to be uploaded to GESPRO” with REMINDER status → the contractor hasn’t used the platform. Alert them: if the monthly progress statement isn’t on GESPRO before the 22nd, their payment will be delayed by a month.
If a document is received by email outside GESPRO → require it to be resubmitted on the platform before processing the request.
4. Who does what
Actor | What GESPRO means to them | Concrete action |
|---|---|---|
MOE | Administrator of the document and financial workflow | Configure access from start-up; train the contractors; check submissions before deadlines |
Contractor | The mandatory channel for all contractual deliverables | Upload progress statements, execution drawings, and FTMs to GESPRO on time |
Client (MO) | Approval of progress statements and FTMs | Access GESPRO to approve progress statements and change order sheets |
Scheduling coordinator (OPC) | Tracking of the document workflow | Check that documents needed for the schedule are actually on GESPRO |
5. What this changes in practice
A project manager who rigorously enforces and monitors GESPRO use can trace every contractual exchange and prove submission delays in the event of a dispute. A project manager who tolerates parallel channels (email, USB drive) loses the single source of traceability and risks disputes over submission dates.
Failure scenario: the HVAC contractor submits its progress statement by email on the 22nd because they’ve had no GESPRO access for a week. The MOE accepts it “just this once.” In July, the contractor claims a payment delay. Without a GESPRO submission, the transmission date is disputable.
6. Example of real wording
“They must be submitted via the GESPRO platform by the 22nd of each month. Any failure or delay in submission would expose the contractor to a one-month payment delay.”
“FTM 04_002 — approved by the client, distributed via GESPRO.”
7. Points of caution
GESPRO is not a generic GED: it’s a contractual platform with financial consequences if not used.
Access should be opened as soon as the contract is notified, not once works start.
Subcontractors must also have access if their documents fall within the workflow.
A drawing uploaded but not yet signed off is not authorized for use.
Other platforms (Procore, AXELOR, ePLAN) work the same way: the principle is identical, only the name changes.
8. Not to be confused with
Related term | Key difference |
|---|---|
GED | Electronic Document Management — GESPRO is an enhanced version with integrated financial tracking |
Distribution email | An informal exchange — doesn’t count as a submission on the contractual platform |
Site extranet | A generic term — GESPRO is an extranet with added financial-tracking functions |
Shared drive | A storage tool with no sign-off workflow or contractual traceability |
9. Related terms
Same phase (execution): GED · Sign-off (VISA) · Progress statement · FTM · Execution drawings
Same actor (MOE/MO): Approval workflow · Compte prorata · DPGF
<-
BACK TO FULL GLOSSARY