PCB prototype lead time: planning from approval to arrival

PCB prototype lead time is only useful when its start and finish are explicit. A bare-board fabrication estimate, an assembled-board shipment estimate and the date hardware arrives at your desk describe different schedules. For a demonstration, you need the last of these plus time to load your application and check the assembled system.

Ohmbo's current estimate is shipment in 10–15 working days after engineer approval, with courier transit additional. That clock does not begin with the first prompt or free preview. Confirm the current estimate, order scope and delivery destination before payment, then plan the work before approval and after arrival separately.

Ask what the quoted turnaround includes

Write the beginning and ending event beside every estimate. Does production begin after file review, after parts are available, or after order confirmation? Does “complete” mean ready for assembly, ready to ship, or delivered?

For example, JLCPCB defines build time as the interval from the start of physical production to production completion, ready for transfer to the shipping center. That definition is useful when reading its quote; it should not be treated as an end-to-end schedule for an Ohmbo order. Source checked: 2026-10-19.

Ask which working-day calendar applies and how closures are handled. Do not convert “10–15 working days” into “two weeks to my door.” The estimate needs a confirmed starting event, and transportation remains a separate stage.

Separate the stages of an assembled PCB prototype

Use a short schedule with an owner and an exit condition for each stage. Avoid assigning dates to unresolved tasks merely to make the plan look complete.

Stage	Evidence needed to move forward	Question to resolve
Requirements	Board brief, interface list and mechanical constraints	Who can answer missing specifications?
Design and engineer review	Approved schematic, layout and BOM revision	Which open issues prevent approval?
Order readiness	Confirmed scope, payment arrangements, parts and test responsibilities	Are any substitutions or customer-supplied items outstanding?
Fabrication and assembly	Boards populated to the approved revision	What update will confirm progress?
Testing	Per-board results against the agreed plan	Who decides what happens after a failure?
Shipment and receipt	Dispatch information, delivery and incoming checks	Who receives and evaluates the boards?

Some work can overlap. Application development can continue while boards are made if the interface contract stays fixed. Other work has a dependency: a test that needs a particular firmware build cannot be completed before that build and its instructions arrive. Ask the supplier to identify the dependencies for your order rather than assuming every row runs in sequence.

Work backward from the demonstration

Start with the date of the actual demonstration. Reserve time before it to install the boards, load your application, attach peripherals and repeat the intended demonstration. This is your integration work, even when the supplier has already completed its agreed functional tests.

Next, account for transit and receiving. Use a destination-specific shipping estimate and discuss what happens if delivery is delayed. Then work back through the confirmed production window to the required approval date. Leave requirements clarification and design review before that date.

This is a planning method, not a guaranteed calendar. The amount of contingency depends on how much is changing and what a missed demonstration would cost you. If no hardware substitution is possible, tell the team that before approving the order. An early feasibility conversation is more useful than marking every task urgent near the deadline.

Remove avoidable waiting before approval

Prepare the exact component list, required connectors, enclosure constraints and accepted substitutions. A substitute can affect the footprint, firmware or test procedure; name who is allowed to approve it. Record the answer in the order rather than leaving it in a chat message someone may miss.

Agree on the test plan while the design is being reviewed. Specify who provides firmware, peripherals and any fixture. Keep loading instructions with the firmware revision so a supplier can reproduce the intended check without guessing.

A concise handoff can prevent a queue of unanswered questions:

• One named decision-maker for design and component changes.
• An approved set of schematic, layout and BOM files with matching revisions.
• Written acceptance criteria and responsibility for test firmware.
• Confirmed shipping destination and a contact who can receive the delivery.

These items reduce ambiguity; they do not eliminate component shortages, rework or shipping delays. Treat unresolved inputs as open schedule risks until someone closes them.

Keep design changes visible after approval

If a connector changes or a new feature is requested after approval, ask which artifacts and tests must change. Get an updated quote and schedule where necessary. Do not assume a small visual change leaves production unaffected.

When testing finds a failure, request the result, proposed corrective action and revised shipment estimate. Retesting against the agreed criteria matters more than preserving an obsolete date. A batch summary should still identify each board and its final result, including any rework.

The prototype cost guide helps distinguish included work from a new scope request. Keep schedule decisions with that scope so the quoted price and delivery expectation refer to the same revision.

Questions about PCB prototype lead time

Does payment start Ohmbo's 10–15-working-day estimate?

The published estimate starts after engineer approval. Orders and payments are manually confirmed. Ask the team to record the approval date and current expected shipment window for your order; do not infer either from a payment receipt.

Does “tested” mean ready for my investor demo?

It means the boards were checked against the agreed written test plan, firmware and acceptance criteria. Your application, enclosure, external devices and demonstration sequence may require additional integration checks after receipt.

Can a free online preview reserve production time?

Do not treat it as a production booking. Each account gets one free online design preview; physical prototypes require a confirmed order. Discuss the deadline and feasibility with the team before making commitments based on the preview.

Confirm a date tied to a revision

Record the approved design revision alongside the PCB prototype lead time, expected dispatch and integration dates. Send your target demonstration date with the board brief through contact, and use how it works to confirm the order stages. Keep the approval event, transit estimate and remaining open items visible in the same plan.