The part of certification that catches brands out is rarely the standard itself, it is how long a result takes and how little anyone controls that once a sample is in the queue. This guide covers what drives lead times up, how far ahead to engage a testing body, and what a single courier mishap added to one otherwise faultless project.
Most brands plan certification as a task with a duration. In practice it behaves more like a queue position, and the queue belongs to somebody else.
That distinction is where schedules come apart. Below is what actually drives the wait, how far ahead to engage a testing body, and what still went wrong on a project where every other part ran to plan.
What lead time actually means
When we talk about certification lead time, the figure that matters most is the gap between submitting a sample and getting the test result back. That is the point that unblocks a project, because it is what allows a brand to talk about the product publicly and move forward, with the formal paperwork following behind it. For larger organisations the booking and administrative side carries more weight in its own right, but for most brands the result is the thing that counts.
Lead time is not a fixed number. It scales with how much testing a product needs. Most standards carry their own internal tiers and sub-tests, and the more of those a product has to pass, the longer the process runs and the more samples it requires to support it. More thorough testing is both slower and more expensive. The two move together.
What drives lead times up
A handful of factors push lead times beyond what brands expect.
Some standards require multiple rounds of testing run back to back with results averaged, which takes longer by design rather than by accident. Lab capacity is a separate issue again. A specific facility or rig can be fully booked by another company, sometimes deliberately, where a business blocks out lab time to limit outside access while its own testing is underway for IP reasons. That can mean weeks in a queue regardless of how ready your own product is. Certain tests are also inherently time-based rather than instant, monitoring how a material degrades or reacts over several days, which adds real duration no matter how efficient the lab is.
Lab size or reputation is not a reliable predictor of speed on its own. A larger, well-known testing body does not automatically move faster than a smaller specialised one, and it can go either way depending on their own workload. The more useful question is whether a lab has the right capability and standards expertise for the specific product, which is why we work with established UK bodies such as SGS and INSPEC International, chosen for fit against the standard being tested rather than for size.
If a product fails, resubmission effectively restarts the process. The paperwork is more streamlined the second time round, but the testing itself takes roughly the same length again, and it is not fast-tracked simply because it is a retest. The one genuine advantage of an established relationship with a testing body is a faster response rate in practice, through ongoing communication, though that is a relationship benefit rather than a rule you can plan against.
Planning around the uncertainty
The practical target is to start engaging a certification body around a month ahead of when a result is needed, flagging the project early and effectively holding a placeholder, so the prototype can go straight into the process the moment it is ready rather than starting cold. That lines up naturally with prototyping itself, which typically runs four to five weeks, giving a sensible lead-in window.
The complicating factor is that the whole plan depends on the prototype being ready on schedule, and prototyping is its own complex process, one that can slip for reasons nobody controls.
When things go wrong anyway
One project illustrates this well. Development had gone about as smoothly as a project can go: concept development, prototyping and manufacturing all ran to plan, the client relationship was strong, and the factory delivered early. Testing was booked, and the final prototypes were shipped from the factory in careful, heavily protective packaging.
A courier mishap in transit damaged the shipment and shattered roughly seventy per cent of the casings. There was no way to proceed with damaged samples, so the factory had to remake most of the batch before certification could begin. That single incident, outside the control of the design team, the client and the factory, added two and a half months to the timeline.
Every party had done their job well. The delay came from a link in the chain nobody could directly manage, which is the useful point: certification readiness depends on an entire chain of third parties, manufacturing, logistics and the testing body itself, and a failure anywhere in it can derail an otherwise well-run schedule.
Running certification in parallel, where possible
Certification does not have to sit purely as a bottleneck at the end of development. Some tests only need a portion of a product or a single material sample rather than a fully assembled unit, so that element can go off for testing while the rest of the design work continues. Internal design changes that strengthen a part without altering anything already tested generally do not require waiting on fresh results either, since they do not put the existing compliance position at risk.
Separately, whole categories of work sit outside the compliance process altogether and can run in parallel without constraint. Packaging design, instruction manual development and branding all proceed on their own track, unaffected by what is happening in testing.
How much of this parallel running actually happens depends on the client. Some are content to wait and see the first prototype before deciding how to proceed, particularly where intellectual property is already filed or partly protected, which gives room to move more slowly. Others need to move quickly, especially in the rarer cases where an IP outcome depends on the result of testing. Either way, the standard practice is to act around a month ahead and communicate the urgency clearly to the testing supplier, so the slot is genuinely ready when the prototype is.
What underestimating lead time costs
The common mistake is assuming the best case: that testing completes cleanly in a single pass inside a month, with no contingency for a retest or a more rigorous follow-up round. That matters because brands are usually working towards a specific window, a trade show, a retail buying cycle, a market trend, and underestimating lead time risks missing that window entirely rather than simply running a few weeks late.
There is no single correct buffer. Padding a timeline out to three or four months defeats the purpose of planning efficiently, so a realistic worst-case expectation sits around one to one and a half months, once a brand accepts that third-party bodies run on their own priorities.
On seasonal pressure, there is some truth to certain periods being busier, since most sectors have key trade shows and launch windows that companies plan around months in advance, and testing demand can be traced back from those dates. But because launch cycles and trade shows run continuously around the world, and testing capacity is similarly spread, there is rarely a single universal bottleneck affecting every brand at once. There is generally capacity somewhere.
Planning a schedule you can actually hold
Pushchairs sit among the most demanding product types to certify in this sector, and we have developed several for different brands, with the Ark pushchair the most complex example, a project that went through multiple rounds of highly rigorous standard testing. That depth of experience is what shapes how realistically we plan lead time into a client's schedule, including building in contingency for the kind of disruption that has nothing to do with the design itself. As the courier incident shows, a schedule that only works if every third party performs is not really a schedule.
Related guides: Launching a new product in the nursery and baby sector: certification, safety and realistic timelines · Why Nursery Products Fail Late-Stage Testing · Nursery and Baby Product Design: Safety, Convenience and Development
