Test Request Management: Taking a Request from Intake to Test-Ready in an Engineering Lab
Author
Neerav Singh
Technical Product Specialist
Author
Neerav Singh
Technical Product Specialist
Reading Time
5 min read
Test Request Management: Taking a Request from Intake to Test-Ready in an Engineering Lab
A seat belt anchorage test under UN Regulation No. 14 can run as a static pull on a strength rig or as the dynamic sled test that the regulation's Annex 7 allows as an alternative. The two routes need different equipment, fixtures and crews. One line in the original request usually decides which route applies. When that line is missing, the lab finds out on the morning the body-in-white arrives.
Clinical laboratories studied this problem long before engineering labs did. Research by Mario Plebani at the University of Padova estimates that errors made before analysis account for up to 70% of all mistakes in laboratory diagnostics. Anyone who has chased a missing seat mass through an email thread will recognise the pattern. This guide follows a test request from intake to the point where it is ready to run.
What Is Test Request Management?
Test request management is the process an engineering lab uses to capture, review, approve and prepare requests for testing. It records what the requester needs, whether the lab can deliver it and which equipment, people and test articles must be in place before the first channel records data. It forms the front end of test lifecycle management.
Labs often blur 3 separate records:
- Booking or commercial request: the customer's order, which can hold several tests, equipment rentals and fees.
- Test request: the execution record for one test, carrying the procedure, dates, assigned resources, data and report.
- Work order: a supporting task such as test article inspection, fixture preparation or disposal, with its own owner and due date.
A single type-approval booking might produce 4 test requests, 3 work orders and a few fees, each needing its own status.
Why Intake Is Where Test Labs Lose the Most Time
Requests arrive as emails with drawings attached, phone calls followed by PDFs and notes from supplier meetings. Labs that depend on email-based booking carry that variety into every downstream step. A McKinsey Global Institute survey reported by HuffPost found that employees spend about 28% of their day on email and 19% searching for and gathering information.
Spreadsheet trackers add risk. Raymond Panko's research at the University of Hawaii, summarised by Computerworld, found errors in 49 of 54 audited spreadsheets (91%). A request log passed between sales, planning and the lab is that kind of file, and the problems with manual test tracking build quietly until a test slips. Together these gaps push risk to the most expensive place to fix it: an idle test rig with a technician waiting.
The Path from Intake to Test-Ready
Labs that handle intake well complete 7 checkpoints before a technician is booked.
Capture the technical facts the rig needs
A sales engineer accepts a seat anchorage booking for an M1 passenger car. The request names the regulation and a tentative week and leaves out seat rows, seat mass, belt configuration and test method. Without the seat mass, the test engineer cannot confirm that the force application device has enough capacity or choose the right fixture.
A service catalogue that lists each test with its required inputs prevents this. Intake details vary by part as well: one emission test on a seat, a steering wheel and a dashboard needs different information for each. Independent labs can share these lists as guidance on what to send when booking a third-party test lab.
Review the request against capability
ISO/IEC 17025 clause 7.1.1 requires a procedure for reviewing requests, tenders and contracts. An accreditation checklist from SADCAS asks labs to show that requirements are defined, documented and understood, and that the lab has the capability and resources to meet them. ANAB calls it one of the standard's most significant areas. A named technical reviewer should approve, rework or reject each request before a quotation goes out, leaving a record that supports end-to-end digital traceability for ISO/IEC 17025.
Lock the scope and record every change
In week 2 of a durability programme, the customer phones to add a test day and video recording. The engineer updates the plan and leaves the quotation untouched. 2 months later, the invoice and the purchase order disagree by a full rig day. Clause 7.1.4 requires differences to be resolved before work starts, and clause 7.1.8 requires review records, including significant changes, to be retained. A versioned quotation with a dated reason for each revision satisfies both.
Convert one request into executable work
Take a type-approval package with 4 mandatory items (the test, test article handling, authority fees and a homologation report) and 2 optional items (a detailed report and post-test storage). At confirmation, the test becomes a test request with a unique ID, and handling and storage become work orders with owners and due dates. Fees stay on the commercial record. Technicians see executable work, and finance sees every chargeable line.
Match equipment by specification
A humidity cycling test on a dashboard assembly needs a chamber of at least 600 litres. The calendar offers the first free chamber, a 400 litre unit, and the mismatch surfaces at loading. Writing equipment requirements into the test procedure and keeping specifications current on each equipment record prevents this. Define scarce, expensive and long-running equipment first, because that is where booking conflicts cost the most.
Sequence tests that share a test article
A prototype seat needs 3 tests, and the planner books all 3 in one week across 3 rigs. The seat can only be on one rig at a time. Tests that share a test article need a finish-to-start relationship, where test B begins only after test A completes. Capturing that dependency at intake keeps the schedule honest.
Confirm the test is ready to run
A readiness review before the slot starts should confirm:
- Test article received, inspected and labelled, with build state recorded
- Fixtures prepared and verified
- Instrumentation calibrated through the test dates
- Operator qualification valid for the method
- Drawings, delivery notes and technical data on file
- Witness attendance confirmed where the contract requires it
A test that fails this review goes on hold with an expected release date.
3 Scenarios Where the Request Is Not Ready Yet
The quotation is needed before a test date exists. A customer needs a price 4 months ahead, and the prototype has not been built. Many labs quote duration and an indicative month against a tentative internal window, then schedule the test only on confirmation. Those windows also feed finite capacity planning.
The test article arrives late. Placing the test on hold with an expected release date lets planning offer the slot to another request and tells sales that capacity has opened. A live test lab scheduling plan makes that possible.
A long test does not need the equipment continuously. A 72-hour climatic exposure can run as 36 hours in one week and 36 in the next. Reserving equipment by actual use frees capacity that a block booking would lock away.
Internal Labs and Independent Labs Approach Intake Differently
An OEM's internal validation lab and an independent testing, inspection and certification (TIC) lab run the same checkpoints with different emphasis. A PJLA webinar on clause 7.1 notes that reviews for internal or routine customers can be performed in a simplified way.
| Aspect | Internal OEM or Tier 1 lab | Independent TIC lab |
|---|---|---|
| Typical requester | Programme or design engineer | External customer through a sales contact |
| Commercial step | Cost centre or programme budget | Quotation, packages and optional add-ons |
| Priority driver | DVP gate dates and programme milestones | Contract dates and customer commitments |
| Review depth | Can be simplified for routine requests | Full contract review for each new scope |
Internal labs inherit the quality of the verification plan behind each request, which is why so many DVP&R processes collapse before the first test runs. Tier 1 suppliers running multi-customer validation need both models at once. For TIC labs, every unclear request eats into billable rig hours as test volumes grow.
Following One Seat Anchorage Request Through TITAN
Here is the anchorage request from the opening moving through TITAN.
It enters through a portal built for requesters.
The customer submits through a booking portal that shows only booking functions, or sales enters it on their behalf. Selecting the anchorage service pulls in its requirements: vehicle category, seat rows, seat mass, belt configuration and method.
Technical approval comes before the price goes out.
The request routes to a technical reviewer who approves it or sends it back for rework. Permissions can hold the quotation until that review is complete, and an activity log records each decision for ISO/IEC 17025 compliance.
Quotation revisions keep their history.
Quotations are built from catalogue pricing rules, emailed from TITAN and logged with how the customer approved them. An added test day becomes a new version with the earlier one preserved.
Confirmation creates the work.
Each test line becomes a test request with a unique ID, and supporting tasks become work orders. A barcode on the folder that follows the seat lets staff identify the record with one scan.
Planning starts from the test procedure.
The procedure lists the rig and instrumentation the test needs, and planners assign equipment and people to the slot. Technician qualifications carry validity dates with alerts before expiry, and reservations can be split into separate intervals.
Readiness and execution share one record.
Reusable checklists are completed on a tablet at the rig, with photographs and digital sign-offs from a witness or certifying officer. A late seat puts the test on hold, releases the slot and tells sales that capacity is free. Labs can also block closure until the test report is uploaded.
Each lab keeps its own working environment.
A seat lab, a crash lab and a tire lab can each run a separate portal with their own forms and workflows while sharing equipment and staff. Configuration needs no code, and TITAN runs on-premises or in the cloud.
To Summarize
Every hour a technician waits at a rig for a missing seat mass traces back to a request that was accepted before it was complete. Labs that work through these 7 checkpoints catch the gap at a desk, where fixing it takes minutes, and build the records ISO/IEC 17025 expects along the way.
Ready to Bring Structure to Test Request Intake?
Bring request capture, technical review and resource readiness together with TITAN.