BUILD/ACROSS

Pilot evidence standard

A pilot becomes a case study only after the evidence exists.

This public standard defines what BuildAcross will document before presenting a European exhibition delivery as proof.

Minimum case record

Every published project must answer the same operational questions.

A useful case study explains what was difficult, who owned each workstream and how the route performed. It should not be a gallery of opening-day photographs with no production context.

01

Project context

Exhibition, city, venue, dates, stand area, design status and confidentiality level.

02

Role map

Agency, BuildAcross, production partner, specialist subcontractors and end-client contact boundaries.

03

Commercial scope

Normalized cost groups, material exclusions, allowances, change approvals and payment structure.

04

Control evidence

Technical release, materials, graphics, workshop evidence, dispatch, installation and handover records.

05

Exceptions

Material delay, damage, changed requirement or open issue, including owner and resolution.

06

Outcome

Completed scope, final exceptions, timing result and evidence publication permission.

Claim discipline

No invented savings, speed or coverage claims.

A saving can be published only when the baseline and normalized comparison are defensible. A response-time claim needs a defined measurement window. A country-coverage claim needs a currently qualified route, not a historic supplier contact.

Photographs must identify whether they show the actual project, a partner reference or illustrative imagery. Confidential client and agency information remains excluded unless written permission is explicit.

Learning loop

Completed work must improve the next qualification decision.

After handover, the performance record should update the partner’s observed capabilities, response quality, scope accuracy and recovery behavior. Evidence that contradicts an earlier profile takes priority over the profile claim.

The verification standard and quote template are versioned so recurring issues can become stronger checks instead of remaining informal experience.

Working files

Frequently asked questions

Pilot publication questions

Why not name the first intended partner now?

Intent is not completed evidence. A supplier is named only after the relevant capability status and publication permission are confirmed.

Can the client remain anonymous?

Yes. A case can still explain venue, scope, process and outcome while removing client and commercially sensitive identifiers.

Will unsuccessful pilots be hidden?

Material exceptions should be recorded. Public disclosure still depends on confidentiality and legal permissions, but verification decisions must account for negative evidence internally.

What counts as delivery verified?

Observed performance on a completed project with a documented scope, checkpoints, handover and material exceptions—not only a portfolio reference.

BuildAcross / 01

The first proof should come from a real delivery record.

Submit a European project that can be structured, controlled and—where permissions allow—documented against this standard.

Propose a pilot project