Profile reviewed
Company, contact, service area, production model, systems, scale and references were checked for completeness and internal consistency.
Partner verification standard
Verified must describe evidence—not a marketing badge.
BuildAcross uses staged, dated and scope-specific partner statuses so agencies can distinguish submitted information from checked documents and observed delivery.
Three status levels
Profile, documents and delivery are different evidence states.
Status is intentionally narrow. A company may have its identity and insurance checked without BuildAcross having observed its production or site performance. The label must never imply more than the underlying review supports.
Documents verified
Defined documents such as legal identity, insurance, certifications or reference evidence were reviewed and dated for the stated scope.
Delivery verified
BuildAcross recorded performance on a completed project, including agreed scope, communication, checkpoints, handover and material exceptions.
Project qualification
A verified company still has to fit the actual project.
Historical evidence does not prove current availability. Every invitation requires a date-specific check covering city, venue, workshop capacity, project manager, crew, logistics, subcontractors and the design technologies involved.
The decision record separates evidence from assumptions. Any missing item receives an owner and deadline before production release rather than being silently treated as included.
Identity and cover
Contracting party, required insurance and relevant certifications.
Capacity and ownership
Named project management, workshop route, crew and subcontracted work.
Technical control
Venue review, drawings, materials, services, approvals and production evidence.
Commercial clarity
Scope lines, exclusions, allowances, payment milestones, changes and warranties.
Agency boundary
Confidentiality, branding, client-contact rules and approval authority.
Site recovery
Decision path for delay, damage, changed access or incomplete handover.
Governance
No pay-to-rank status and no permanent verification.
A listing fee cannot purchase a higher verification state. Commercial participation and verification evidence are kept separate. Project matching remains based on fit for the actual brief.
A status can expire, narrow or be suspended when documents lapse, capabilities change, evidence cannot be reconfirmed or delivery creates a material unresolved concern. The review date is part of the claim.
Public evidence record
A public status needs a readable evidence record.
A verification label is useful only when an agency can see its boundary. When BuildAcross publishes a partner status, the accompanying record should state the reviewed scope, the evidence category, the review date and what the status does not establish. It must not turn a partial check into a blanket recommendation.
Scope reviewed
The relevant service, location or venue class, and the partner’s role in production, installation or project control.
Evidence category
Whether the status is based on profile information, dated documents, reference evidence or an observed completed delivery. Confidential files are not published by default.
Review date and recheck trigger
When the evidence was reviewed and what can require a narrower, expired or renewed status, such as an insurance lapse, a changed capability or later project evidence.
Limits of the status
What remains unproven: current availability, suitability for every country or venue, and responsibility for a project that has not yet been scoped and contracted.
Publication permission
What can be named publicly and what remains protected because the document, client reference or delivery detail is confidential.
How to choose a European stand builder
Use the project-specific checks that remain necessary after any public verification status.
↗Pilot evidence standardSee how completed delivery evidence is recorded and reviewed during the pilot.
↗Partner qualification scorecardReview evidence groups, unresolved questions, owners and decisions before appointing a supplier.
↗Working files
Frequently asked questions
Verification questions
Does verified mean BuildAcross guarantees a builder?
No. Verification reports the evidence reviewed for a defined scope and date. Contract terms, warranties and project-specific responsibilities remain explicit for each engagement.
Can a partner pay to become verified?
No. Payment or commercial participation cannot replace required evidence or observed delivery.
How often is status reviewed?
Document expiry and material capability changes trigger review. Delivery status is also reconsidered after relevant completed work or an unresolved performance issue.
Is subcontracting a failure?
No. Subcontracting can be appropriate when the performing party, price, schedule and accountability are transparent.
Can an agency see the documents used to verify a partner?
A public evidence record can describe the reviewed evidence category, scope, date and limits. BuildAcross does not publish confidential documents, client references or commercial details by default. Any document sharing requires the relevant permission and a project-specific reason.
Why might a partner not have a delivery-verified status?
Delivery verification requires recorded evidence from a completed project observed by BuildAcross. A profile or document status can still be accurate without that evidence. The absence of a delivery label is not a negative verdict; it means the public record must not claim observed delivery.
BuildAcross
Apply against a visible standard, not a vague promise.
European production partners can submit a capability profile and supporting files for an initial scope-specific review.
Request capability review