Exclusive and qualified work requests

Quality before noise

A good request helps the artisan quickly understand the project: work type, commune, urgency, property context and customer availability.

• The customer describes the need before routing.
• The request stays tied to the trade actually searched.
• Priority goes to artisans able to work in the area.

A selective logic for artisans

MeilleurArtisan is not meant to accept every profile. The promise only works when the partner can respond quickly, well and locally.

• An artisan without area fit does not strengthen the network.
• Responsiveness is part of perceived customer quality.

Assess the situation before choosing a solution

A useful request starts with facts: work area, commune, building, access, occupancy and the observable situation. It does not replace a site visit, but supports a relevant first assessment.

• Separate observations, assumptions and checks.
• State access, occupancy and coordination constraints.
• Plan a visit when safety, substrate or measurements are decisive.

Prepare, compare and coordinate

Compare scope, checks, exclusions and trade interfaces. Every contractor should receive the same brief so their responses remain understandable.

• Ask what is included, excluded or to be confirmed after a visit.
• Identify interfaces with other trades.
• Inform occupants about real site constraints.

Acceptance, maintenance and boundaries

At acceptance, check the result, open items, records and next steps. This page never replaces a professional assessment, permit or diagnosis.

• Check the result against the original brief.
• Keep guidance and records useful for maintenance.
• Report reservations or outstanding checks promptly.

Define an unambiguous scope

A clear scope states the result, areas, protection needs, known conditions and remaining checks. Observations never replace professional diagnosis.

• Describe the expected result first.
• Report anomalies as observations.
• Ask which checks are needed at the visit.

Prepare a useful site visit

For a useful visit, prepare records, access details and known constraints. Photos complement a visit; they never replace it.

• Do not present incomplete information as certain.
• Confirm access and occupancy constraints.
• Keep a short record of checks and interfaces.

Decide using useful criteria

Compare scope, open assumptions, checks, interfaces, responsibilities and delivery conditions.

• Compare operations and exclusions.
• Identify an owner for every trade interface.
• Distinguish start conditions from confirmed steps.

Follow the project without replacing the professional

The client helps with access, information and traceable changes. Technical decisions and required checks remain with qualified professionals.

• Report a change before it alters the work.
• Keep a trace of approved adaptations.
• Leave safety decisions, checks and permits to qualified people.

Trades related to your project

These pages support the same project when several trades or interfaces are involved.

Frequently asked questions

Why mention exclusivity?

Because a serious customer should not become a scattered file. Controlled routing protects the quality of the exchange.