An independent laboratory network built around practical collaboration

Start with the capability gap, not a contact list

A collaboration need might be a method outside your scope, a sample matrix your team does not routinely handle, an instrument outage or a customer project spanning several disciplines. Define that gap before approaching another laboratory. Separate temporary overflow from permanent outsourcing: they require different capacity, communication and continuity arrangements.

Prepare a concise capability brief that distinguishes routine services from development work. Explain matrices, method families, reportable ranges where applicable, sample handling constraints and the limits of your own service. A network profile or conversation is a starting point, not evidence that a laboratory can perform a particular project.

• What work is needed, and what result will the customer use?
• Which capability is missing, and which tasks will remain with your laboratory?
• Who is authorized to approve external testing and share project information?

Make referrals useful and accountable

A useful referral gives the customer a reason to consider a provider and a clear next step. Ask permission before passing contact details, sample information or a project brief to another organization. State whether you are making an introduction or managing subcontracted work; do not imply that an introduction transfers responsibility for the result.

If your laboratory will issue the final report, agree how externally produced results will be identified and reviewed. Check any customer, contractual or applicable quality-system requirements before placing work. Confirm the other laboratory's current method-specific capability and, when required, the relevant accreditation scope directly with the appropriate source—not from Alliance participation.

Discuss capacity without promising availability

Instrument access alone does not establish usable capacity. Staff competence, maintenance, calibration, sample preparation, quality control, report review and existing commitments all affect whether overflow work can be accepted. Treat a stated opening as a conversation to reconfirm, not guaranteed turnaround.

For a small pilot, agree an acceptance decision, sample handoff, pricing and payment responsibilities, expected reporting format, and escalation contact. Decide what happens if samples arrive unsuitable or the method cannot answer the customer's question. Review the pilot before committing to recurring work.

• Reconfirm capacity and realistic milestones for each project.
• Document custody, storage and disposal expectations.
• Agree who communicates delays, deviations and complaints.
• Protect customer relationships without restrictive peer coordination.

A regional network is not a commercial guarantee

Mountain West conversations may help independent laboratories compare needs across different locations and disciplines. Distance, sample stability and transport requirements still matter; a nearby contact is not automatically the best technical match. A remote provider may be more appropriate for a specialized method.

The Mountain West Laboratory Alliance is forming an interest list for possible expertise exchange, peer discussions and host-approved visits. There is no promised referral volume, preferred-supplier status or confirmed membership. Participants should not share competitively sensitive pricing, customer allocations or confidential bid information in peer forums.