First-of-series (1er de série): what the project manager needs to know about this prototype to avoid approving a build with no snag list — and finding defects across 200 workstations
You visit the prototype meeting room. The architect is satisfied. So is the client. But if you don’t formalize the snags in a dedicated table, if missing technical data sheets (FT) haven’t been approved, and if the visit’s CR isn’t distributed, the visit is worth nothing contractually.
Type | Phase | Actors | Impact | Stakes | Where |
|---|---|---|---|---|---|
Procedural | Execution | MOE (project manager), Client (MO), Architect, Contractor | High | contractual | dedicated section of the CR, snag-list tracking table appendix |
1. Operational definition + common mistake
A 1er de série (“first-of-series”) is the prototype build of a typical space (office, meeting room, restroom, event space) before rolling it out across all the relevant surfaces. It lets the client, the architect, and the MOE check, at full scale, the compliance of materials, finishes, technical layout, interfaces between trades, and aesthetic result — before committing to procurement and full-scale execution.
In this CR, two categories of first-of-series are managed in parallel: the Event Room (a specific space) with its own sample-tracking table, and “offices and restrooms” corresponding to lower floors already completed (“dito PREIM” = matching the previous floors). The process includes sample presentation steps (first an informal one with the MOE, then an official one with the client), a snag-list tracking table, and approval milestones.
Many assume the first-of-series is just a presentation visit — in reality, it’s a contractual act whose CR and snag-list table constitute the formal evidence of points to correct before roll-out. A first-of-series with no visit report and no signed snag-list table cannot be enforced against the contractor in the event of non-conformity at handover.
2. Where it appears
In a commercial site meeting report — in a dedicated “First-of-series” section, often accompanied in an appendix by a sample-tracking table and a snag-list table. The typical process: preliminary list → informal presentation (MOE + architect) → official presentation with the client → approval table → visit report with snags → snag resolution before roll-out. In this CR:
“16/04 – presentation of first-of-series for the lower floors - DONE / 27/04 – sample presentation with MOE (FACTORY) - DONE / 05/05 – sample presentation with MOE and client (EY) - DONE”
“Set up a snag-tracking table via PYI: Office floors: 19 snags / Restrooms: 4 snags”
3. How to read this entry in the CR
If you read “First-of-series — presentation to be organized” → check that the sample list is finalized and that missing technical data sheets have been identified.
If you read “Snag-list table: X snags” → each snag must be referenced, assigned to an owner, and have a resolution date.
If you read “dito PREIM” → this means the space must match an existing reference space. Organize a comparative visit to confirm compliance.
4. Who does what
Actor | What first-of-series means to them | Concrete action |
|---|---|---|
MOE | Technical approval before roll-out | Draft the visit report with the snag-list table; identify missing technical data sheets; set resolution dates |
Architect | Aesthetic approval and design compliance | Sign off on the coordination drawings; confirm material choices |
Client (MO) | Approval of final choices | Approve or amend specifications at the official presentation; don’t launch procurement without approval |
General contractor | Building the prototype | Submit all technical data sheets before the presentation; correct the snags before roll-out |
5. What this changes in practice
A project manager who rigorously manages the first-of-series can block unapproved procurement and avoid discovering non-conformities across 200 workstations at handover. A project manager who lets a first-of-series go by with no formal report or snag-list table cannot enforce corrections at handover.
Failure scenario: the first-of-series visit goes “well” but with no formal report or snag-list table. The general contractor installs 150 acoustic panels. At handover, the acoustic consultant finds the acoustic test reports for the PVC panels were never approved. With no written record of the first-of-series, the contractor disputes any correction.
6. Example of real wording
“Visit carried out on 16/04 – Report to be drawn up + sample approval table dito PREIM”
“Set up a snag-tracking table: Office floors: 19 snags / Restrooms: 4 snags”
7. Points of caution
A first-of-series with no visit report doesn’t exist contractually: the visit must always be documented.
Missing technical data sheets at the time of the visit should block approval: never approve a first-of-series with outstanding technical data sheets.
The snag-list table must be as precise as a handover snag list.
Approving the first-of-series doesn’t prevent later changes via an FTM — but it sets the contractual reference point.
“Dito PREIM” doesn’t mean “automatically identical”: a comparative visit is always necessary.
8. Not to be confused with
Related term | Key difference |
|---|---|
Sample | A material or product submitted for approval — the first-of-series is a full space built using these samples |
Prototype | A general term — the first-of-series is the prototype formally approved by all three parties |
Handover snag list | Snags recorded at project completion — first-of-series snags occur before roll-out |
Coordination drawings | A design document — the first-of-series is the physical execution of these designs |
9. Related terms
Same phase (execution): Sample · Technical data sheet · Sign-off (visa) · Coordination drawings · FTM · Hold point
Same actor (MOE/architect/client): Snag-list tracking table · GED · Progress statement
<-
BACK TO FULL GLOSSARY