Laboratory

Which laboratory are you, and who is holding the sample?

"Laboratory" covers businesses that have very little in common online. A contract lab testing drinking water for municipalities, a materials lab doing tensile and failure analysis for manufacturers, a food microbiology lab serving processors, and a clinical lab drawing blood from patients all need different websites. Before you plan any pages, settle two things.

First, who physically has the sample? A plant QA manager, an environmental consultant out in the field, a product developer at a startup, a patient sent by their doctor. That person's day decides most of what follows.

Second, how does work actually reach you? For most contract and analytical labs, nobody "buys" on the website. A technical person confirms you can run the test, asks for a quote, gets it approved by someone else, then sends samples with a chain of custody form. After that, the relationship is repeat work: the same client sending samples every week or every quarter for years.

This guide is written mainly for that kind of lab, the business-to-business testing lab. If you serve patients directly, most of the advice about clarity and preparation still applies, but your visitors care more about locations, hours, insurance, preparation instructions and getting results, and much less about method numbers.

The site therefore has two jobs. It has to let a careful, sceptical technical buyer answer "can this lab do my work properly?" without phoning you. And it has to make life easy for the clients you already have, so they keep sending samples instead of drifting to the lab with the easier portal.

The question every new visitor arrives with: can you run this test?

The person looking at your site almost always has a specific analysis in mind. They are not browsing. They want to know if you test for a certain contaminant in a certain material, by a method their regulator or customer accepts, at a detection limit low enough to matter.

That makes the test menu the most important part of the site, and also the part most labs handle worst. A page that says "We offer comprehensive chemical, microbiological and physical testing" tells this visitor nothing. They will leave and look for a lab that names the test.

A useful test menu lets people find a test the way they think about it. Different visitors start from different places:

• The analyte or property ("lead", "Listeria", "hardness", "PFAS")
• The sample type or matrix ("soil", "wastewater", "dairy", "polymer", "pharmaceutical raw material")
• The method reference their spec or permit names
• Their industry or regulatory programme

You do not need all four on day one, but you do need search, and at least two ways to browse. For each test or test group, the details a buyer is checking are:

• The method or standard it is performed to
• The matrices you have validated it for
• Reporting or detection limits, where that is meaningful
• Standard turnaround
• Sample quantity, container and preservation requirements
• Whether it falls under your accreditation scope

That last point matters more than labs sometimes admit, and it gets its own section below.

If your menu runs to hundreds of tests, resist the temptation to publish it only as a PDF. A PDF price list or test catalogue is fine as a download, but it cannot be searched well on a phone, it goes out of date quietly, and it hides your capabilities from anyone who has not already decided to dig. Treat the menu as structured information that lives on the site and can be updated in one place.

If a test is not on the list, say what to do about it. Many labs do custom method development or can subcontract unusual analyses. A short note on the menu page, "Don't see your test? Tell us the analyte and matrix and we'll tell you if we can run it or recommend someone who can", turns a dead end into an enquiry. Be honest about subcontracting; buyers and auditors expect to be told when work goes to another lab.

Accreditation is a document, not a badge

For many clients, accreditation is not a nice-to-have. Their permit, their customer's supplier requirements, or their own quality system may require that results come from a lab accredited for that specific test. In many testing fields this means accreditation to ISO/IEC 17025 by a recognised accreditation body, and some regulated programmes also have their own certification or approval schemes.

The common mistake is a row of logos in the footer. A buyer who knows what they are doing does not trust the logo. They want the certificate and, more importantly, the scope of accreditation: the list of exactly which tests, methods and matrices the accreditation covers. A lab can be accredited and still not be accredited for the test the visitor needs.

So give accreditation its own page that includes:

• Each accreditation, certification or regulatory approval you hold, named precisely
• The accrediting or certifying body
• The certificate and scope documents as downloads, with their dates
• A plain-English line explaining that accreditation applies to the tests listed on the scope

Then connect it back to the test menu so each test shows whether it is covered. That single detail saves your client services team from answering the same question repeatedly, and it signals that you understand what the buyer's auditor will ask.

Keep these documents current. An expired certificate on your own website is worse than no certificate, because the people who check will notice and the people who notice are the ones whose business you most want.

If you take part in proficiency testing programmes, say so and say in which areas. You do not need to publish scores, but mentioning participation tells a technical reader you check yourselves against other labs.

Turnaround, rush work and price: say as much as you honestly can

After "can you do it", the next questions are "how fast" and "roughly how much". Many labs avoid both online, and the reason is understandable: turnaround depends on workload and price depends on volume and contracts. But silence pushes buyers toward labs that give at least an indication.

For turnaround, publish your standard turnaround per test or test group, state when the clock starts (receipt of sample, or receipt with complete paperwork), and explain rush options and how to request them. If rush work carries a surcharge, say so in principle even if you don't list figures. Someone with a production line on hold is your best rush customer, and they need to know within seconds whether you offer same-day or next-day work.

For pricing, decide which of these fits your business:

• Published list prices for standard tests, with a note that volume pricing is available
• Price ranges or "from" prices for test groups
• No public prices, but a clear statement of how quickly quotes come back

Any of these is defensible. What is not useful is a vague "contact us for pricing" with no indication of when they will hear back. If you can commit to returning quotes within a business day, put that next to the quote button. A promise about response time often does more work than a price.

Getting the sample to you: the page that saves the most phone calls

This is the page labs underestimate. A good one reduces rejected samples, missed hold times, incomplete paperwork and the phone calls that come with all of them.

The person reading it may be standing in a field, a plant or a loading dock, on a phone. Write it for them. It should cover:

• How to request containers, coolers or sampling kits, and how long they take to arrive
• Container, preservation and temperature requirements, linked from each test where possible
• Hold times, explained plainly, so people understand why a sample collected on Friday afternoon might be a problem
• The chain of custody or sample submission form, as a fillable download, with a short example of a correctly completed one
• Your receiving address, receiving hours, weekend and holiday arrangements, and what to do if a delivery will arrive outside those hours
• Courier or pickup service, if you run one, and the area it covers
• Drop-off instructions for anyone bringing samples in person, including where to park and which door to use

The example of a completed form is worth singling out. The most common reason samples get delayed is missing information on the paperwork, and seeing a filled-in example fixes much of that without anyone needing to call.

If you have separate requirements for different departments or sample types, organise this page by those, so a microbiology client is not wading through instructions for metals in water.

Writing for the auditor and the procurement officer, not only the scientist

The scientist or QA person chooses the lab, but they rarely work alone. Before your first invoice is paid, someone in procurement will need you set up as a supplier, and someone in quality will need to approve you as a vendor. Sometimes that's a long questionnaire. Your website can shorten that process considerably.

Consider a page or section, perhaps called "For quality and purchasing teams", that collects the things these people usually ask for: your accreditation documents, a summary of your quality system, your standard terms and conditions, how you handle data confidentiality and sample retention and disposal, and how to request supplier paperwork such as tax forms or proof of insurance. You don't need to publish sensitive documents openly. A clear list of what's available and a direct contact for requesting it is enough.

Include a sample report. A redacted example of a real certificate of analysis or test report lets buyers see exactly what they will receive: how results are laid out, whether units and limits are clear, whether it shows method references, who signs it. For clients who load results into their own systems, mention the electronic data formats you can provide. To some buyers that is a deciding factor and they will not think to ask until late in the process.

Who signs the report

Clients are trusting your people's judgement, not your building. A team page matters here more than it does for many businesses, but it has to show the right things.

The people a technical buyer wants to see are the ones responsible for the quality of the result: the laboratory director, the quality manager, technical leads for each department, and whoever they would speak to about a puzzling result. For each, give their role, relevant qualifications and areas of expertise. A line about the kinds of problems they are good at solving is more useful than a long career history.

Photographs of real staff in your real lab help. Stock images of people in goggles holding a coloured pipette are instantly recognisable as stock, and to a scientist they often look wrong in small ways (no gloves, wrong equipment, nonsensical setups). Equally, photos of your actual instruments do some quiet work: a technical visitor will recognise the type of equipment and draw conclusions about your capability.

Make it easy to reach a technical person, not only a general inbox. Many enquiries are really technical questions ("Is your method suitable for this sample with high fat content?"), and getting an answer from a chemist rather than a receptionist is often what wins the work.

Proof that respects confidentiality

Labs face an awkward problem with case studies. Your most impressive work is often for clients who would never let you name them, and the results themselves are confidential. That doesn't mean you have nothing to show.

You can describe the problem and the approach without naming the client: "A food manufacturer was seeing intermittent off-flavours in a product line. We developed a method to identify the compound responsible and traced it to a packaging component." That tells a prospective client far more about your capability than a list of logos.

Other honest forms of evidence include the industries and types of client you serve, the volume or range of samples you handle if you can state it accurately, method development or validation work you've done, publications or conference presentations by your staff, and how long you have been operating. Testimonials can work if clients agree to them, but they're less persuasive here than in consumer businesses. A technical buyer trusts detail more than praise.

The quote request form, and what it should ask

The quote form is where the site turns interest into work, and its design decides whether you receive a useful enquiry or a vague one that needs three emails to clarify.

Ask for what you actually need to quote: the tests or analytes, the sample type, approximate number of samples, how often they will come (one-off or ongoing), the required turnaround, and any method or regulatory requirement. Let people attach a specification or a permit page, since many will be working from a document that lists exactly what they need. Then ask for contact details.

Don't make every field mandatory. Someone who isn't sure which method they need is exactly the client who benefits from your expertise, and a form that forces them to choose will lose them. A free-text box labelled something like "Describe what you're trying to find out" catches those enquiries.

Next to the form, say what happens next and how quickly. Also offer the phone number, because some buyers would rather have a five-minute conversation with someone who knows the subject.

Existing clients come back for different reasons

A large share of visitors to an established lab's site are existing clients. They are not there to be persuaded. They want to log into the results portal, download a fresh chain of custody form, check receiving hours before a holiday, order more containers, or find the right person to call about a result.

Put these where they can be found in one click from every page, usually in the header. "Client login", "Submit samples" and "Order supplies" are typical. If returning clients have to scroll past your marketing to find the portal, it's a small daily irritation, and small daily irritations are how labs lose long-standing accounts to competitors with smoother systems.

Use the site to tell clients about things that affect them: holiday closures, changes to receiving hours, new tests, new accreditation scope. A simple news or notices area that is actually kept up to date is enough.

Where a template will let you down

Many lab owners start by looking for a laboratory website template, and a template can be a perfectly sensible starting point for layout and visual design. Just be aware of what most templates are built for. They are designed for brochure sites: a big hero image, three service boxes, an about section, a contact form.

A lab's real needs sit mostly outside that shape. A searchable test menu with consistent fields for method, matrix, limits, turnaround and accreditation status. Document downloads that are easy to replace when certificates are renewed. A prominent client login. Sample submission instructions that can be linked from individual tests. A quote form with file uploads. Most "science" templates offer none of this, and the service boxes they do provide encourage exactly the vague language that technical buyers ignore.

So if you use one, judge it by whether it can hold your test menu as organised, searchable information, and whether your staff can update documents and notices without calling a developer. The look matters much less than that.

What the home page has to do in the first few seconds

With everything else in place, the home page becomes simple. It needs to tell a visitor, quickly, what kind of testing you do, for which industries or sample types, and under what accreditation. A headline like "Accredited environmental testing for consultants, utilities and industry" does more than an image of a microscope with a slogan about excellence.

Below that, give the three or four routes that cover nearly every visitor: find a test, request a quote, submit samples, and client login. Add a short line on turnaround, a link to your accreditation page, and a phone number that reaches a person during business hours.

That's really it. A laboratory website succeeds when the careful, sceptical person holding a sample can find their test, check your accreditation covers it, understand how to get it to you, and ask for a quote, all without needing to ring you first. And it keeps succeeding when that person, now a client, can find the portal in one click every week for the next ten years.