Start with the accreditation scope, because accreditation alone proves little. An ISO/IEC 17025 certificate covers a defined list of tests, and the standard you need has to appear on that list at the revision you need. Accreditation bodies publish each lab's scope, so check it before the first enquiry goes out.

Then check 3 practical things. The lab has tested products of similar size, energy and complexity. It has capacity before your milestone. It can deliver what your customer or type approval authority will ask for, which might include witnessed tests, raw data in a specific format or a report template already accepted by your quality team.

Many large organisations keep an approved supplier list for test labs. Add the lab's scope, recent assessment date and any open findings to that record so the next programme team starts from facts.

Labs on the other side of this conversation carry their own pressure. A government crash test facility once took bookings through calls and spreadsheets, with equipment, test dummies and instrumentation tracked in separate systems and certification reports assembled from disconnected data. Every incomplete enquiry meant manual checks across all of those before anyone could promise a date. Once the facility connected booking, scheduling, execution and reporting

The first email or portal submission does most of the work. These are the fields a lab needs to quote without a follow-up call, shown for a battery module headed for an 800V vehicle pack.

Labs running a customer booking portal turn that table into required fields. TITAN's portal captures the customer account, test service and test article details such as serials, documents and specifications at intake, routes the request through an approval workflow and produces a cost and resource estimate automatically.

Most labs follow the first request with a short technical call. Treat it as the moment to close gaps before they turn into change orders.

If several standards could apply, state the target markets and the customer requirement driving the test, then let the lab confirm the plan. UN 38.3 sample quantities, for example, depend on battery mass and test sequence, so ask the lab to confirm the count before shipping. Bring the engineer who owns the design. Questions about cell configuration, BMS behaviour or firmware version need an answer on the call, and a second call costs a week.

A good quote lists each test, setup charges, witness time, report fees and disposal costs separately. Labs with integrated quotation and invoicing can tie each line to the booking so the final invoice matches what was quoted and what purchasing approved.

The test plan matters more than the price. It confirms the sequence, the sample allocation and any deviation from the standard. Read every line with the design owner. Approving a plan with the wrong IP rating or the wrong standard revision is an expensive way to find a typo, because the lab will run exactly what you approved.

When the samples arrive, the lab logs serial numbers, photographs their condition and confirms they match the request. Ask for that receipt record and file it with the test. Your customer or auditor will eventually want to know which serials were tested, and the inwarding record is the first link in that chain.

Ship spares. A damaged module or a failed setup with no spare means waiting weeks for a replacement build and losing the slot.

Dangerous goods paperwork deserves its own check. Lithium modules need the correct UN number, packaging and state of charge declared, and a shipment that arrives with the wrong documents can sit in quarantine at the courier depot for days. Send the lab a copy of the shipping documents before the pallet leaves.

Expect status updates at agreed points and an immediate call if a deviation or failure occurs. A failure on the T5 external short circuit test, for example, needs a fast decision about whether to continue the remaining samples and that decision should come from the engineer who owns the design.

Watch the purchase order during this conversation. Retests and added samples can push a programme past its PO without anyone noticing. An independent proving ground discovered missed PO limits only after the fact until it linked bookings to billing in one live system. Ask the lab how it tracks spend against your PO and when it will warn you.

Witnesses should arrive or join early and ask the technician to show the device label, serial number and setup before the test starts. Note the time of each event observed. Those notes help if a result is ever questioned and cost nothing to keep.

The final report should match the request on device description, serial numbers, design level, standard revision, deviations and results. Check every field before the report goes to a customer or authority. Raw data and photographs should arrive at the same time, along with confirmation of sample disposal or return.

If you find an error, ask for a formal amendment with a new report number and revision. A corrected PDF sent by email with no revision history creates 2 versions of the truth, and a customer quality team will eventually find both.

Every gap in a lab request turns into a delay, a change order or a retest further down the programme. The best labs know this, which is why they push hard for complete requests and reward the customers who send them.

Write the first request as if it will be audited, because one day the results it produced will be. Name the standard and revision, state the samples and serials, give a hard end date and say who approves. Labs running modern test lab management confirm requests like that within a day, and that day often decides whether the programme milestone holds.

A third-party lab booking sets several things in motion: sample preparation, equipment allocation, technical reviews, purchase orders and programme milestones. Missing information at the start can delay each of them.

Before submitting a request, confirm the test standard and revision, identify every sample, share the required deliverables and agree on the dates and approval responsibilities. Keep the approved quote, test plan, sample receipt records, deviations and final report connected to the same booking.

For testing labs, structured intake and connected workflows make it easier to assess requests, allocate resources and provide customers with timely updates. For engineering teams, they create a clearer record of what was requested, what was tested and what the results establish.

The goal is simple: give the lab everything it needs to confirm the booking, execute the test and deliver evidence your team can trust.