勛圖tv 繚 ENGINEERING & PROCUREMENT
PCB Design RFQ: Specify Inputs, Deliverables and Review Responsibilities
A PCB design RFQ requests a defined engineering service, such as schematic development, library creation, placement, routing or manufacturing release. It is different from a quote to fabricate an already designed board. A useful RFQ tells the designer what exists, what must be developed and how completion will be accepted. This guide helps buyers prepare that scope so quotations can be compared without hidden exclusions.
Your task: Declare the starting inputs. Use the pcb design scope brief to record the next decision.
Identify the starting point honestly
State whether the schematic is complete and reviewed, whether the BOM is approved and whether the mechanical definition is stable. If the project begins with a block diagram or concept, say so. A designer cannot price layout-only work reliably when major circuit decisions remain open.
Identify the source CAD system and version, available libraries and any data-conversion needs. Screenshots or PDFs can support discussion but may not replace editable source data for the contracted task.
List known problems in the existing design. A redesign to correct EMC, power or mechanical behavior has a different scope from reproducing a known working layout. The RFQ should preserve those distinctions rather than hide them under a single request for a new PCB.
Define the deliverables that will be accepted
Specify native design files, libraries created or modified, manufacturing exports, assembly outputs, drawings and review records. Include the required formats and any ownership or licensing conditions that must be agreed.
If simulations, calculations or prototype support are required, define their scope and output. A routing deliverable is not automatically a complete signal-integrity or safety validation. Similarly, a DRC report only reflects the configured rules and the data checked.
Create an acceptance list that can be reviewed objectively. For example, manufacturing exports should open correctly, match the released revision and include the required layers and drills. Avoid relying only on a subjective statement that the board looks professional.
Provide constraints before placement
Supply outline, mounting details, connector locations, height limits, keep-outs and enclosure interfaces. Identify critical electrical constraints and their source: approved stackup, interface requirements, power distribution, isolation and thermal considerations.
Distinguish mandatory constraints from preferences. If two requirements conflict, name the person who can decide the tradeoff. Unresolved constraints can create repeated placement and routing work.
Manufacturing input should arrive early enough to influence the design. Use PCB DFM for fabrication questions and design for assembly for assembly constraints. The design supplier and manufacturer should work from the same controlled requirements.
Set review milestones and response ownership
Agree useful checkpoints such as requirements review, placement review, critical routing review and release review. Define who responds to each and how comments are consolidated. Multiple reviewers can help, but contradictory feedback needs one authorized resolution.
State the expected review turnaround and distinguish customer waiting time from active engineering work. A project schedule can change when decisions arrive late even if design hours remain unchanged.
The worksheet prepares a scope and evidence brief. It does not inspect CAD files or calculate a binding design fee. Mark missing inputs explicitly rather than selecting confirmed to obtain a favorable result.
PCB design scope brief
PCB design scope brief
How to use and interpret this worksheet
Choose a narrow review boundary before filling in the worksheet. Use one product revision, one proposed build or one supplier decision. If several configurations differ, keep separate records or explain precisely which evidence applies to each. A short reference is enough; the tool does not need drawings, customer names, confidential part lists or passwords.
For every item, distinguish confirmed evidence from an unresolved assumption. Confirmed means that the responsible person has reviewed the relevant information, not merely that a document exists somewhere. Open means the decision or evidence is still missing. Not applicable requires a rationale because it is an applicability decision, not a shortcut to completion.
Record a concrete next action with an owner and a target decision point. For example, replace ask engineering with obtain the approved revision from the design owner before material release. The useful output is an actionable handoff, not a readiness percentage. No weighted score is used, because the consequence of one mandatory gap may exceed that of several completed items.
Load example only to learn the controls. Example mode remains clearly labeled even if you edit its values. Clear the form before entering your own review. Changing an input invalidates the old result and disables its download until you generate a new record. Download the current text if it helps your discussion; it is not automatically added to an enquiry.
Keep supporting approvals and measured results in the controlled project system. This worksheet stores nothing between visits and does not verify files, supplier statements or legal applicability. A completed record can support a review meeting, but the authorized team remains responsible for the release decision.
Keep a decision record with the review
Use this record to connect the discussion to supporting information. Record the source, revision and reviewer for each item. Confirmed means the responsible person has reviewed the evidence; it does not mean this website has verified it. Keep confidential documents in your approved project system.
| Review topic | Record to retain | When it remains open |
|---|---|---|
| Schematic BOM and library maturity | Identify the controlled scope and the person authorized to approve it. Keep the current reference together with the intended decision. | Clarify the boundary before treating the review as a release instruction. |
| Mechanical and electrical constraints | Reference the actual file, data source or agreed requirement, including its revision or date and the person who reviewed it. | Request the missing evidence and identify which downstream decision depends on it. |
| Native files and export deliverables | Record the conditions and assumptions that make the evidence applicable. Separate a proposed value from an approved requirement. | Keep the assumption visible and define whether the next activity may proceed under a bounded exception. |
| Review and revision boundaries | Identify responsibility for the next operation and the evidence expected afterward. Distinguish preparation from a completed result. | Assign a named role and an agreed decision point; do not turn an unanswered question into an approval. |
| Manufacturing handoff support | Record the final disposition, affected quantity or revision and the authority accepting it. Preserve the reason for any exception. | Retain the item in the action list and review its consequence before committing work or materials. |
Review the record again when the product, supplier proposal or supporting data changes. A result from an earlier revision is historical evidence, not automatic approval for the current one. If an item is not applicable, retain the reason and the person who made that decision.
Separate included revisions from scope changes
Clarify what happens when the designer corrects an error against agreed requirements and what happens when the customer changes those requirements. Define how additional features, component changes or mechanical revisions will be assessed.
A fixed-price engagement still needs a clear baseline. An hourly engagement still needs deliverables and review controls. Neither commercial model removes the need to manage changes.
For a hypothetical sensor board, changing the enclosure connector after placement may affect mechanics, routing and test access. The change should identify those consequences before the work proceeds, not appear as an unexplained addition at the end.
Compare quotations by responsibility, not just total
Check whether schematic review, library verification, stackup coordination, output generation and manufacturing support are included. Confirm what assumptions were made about circuit maturity and customer-provided data.
Use the same scope when comparing fees. A quote that excludes bring-up support cannot be treated as equivalent to one that includes a defined investigation period. Ask for optional work to be itemized where useful.
The PCB design cost guide explains effort-based budgeting. The design-cost reduction guide explains how stable inputs and timely decisions can reduce avoidable rework.
Prepare the manufacturing handoff as a deliverable
The final design package should connect the approved native files to fabrication, BOM, placement, drawings and any test or programming data in scope. Include a manifest and clear revision identifiers.
Define who resolves manufacturing questions after release. If the engagement ends before prototype fabrication, state the support available for issues discovered later. Do not assume a design fee includes unlimited assistance through production.
Altium's illustrates why design choices and the intended production route should be discussed together. It is background information, not evidence of a particular design provider's capability or current fee.
Questions when preparing a design enquiry
Can I ask for layout with only a PDF schematic? You can start a discussion, but conversion, library and verification work may need to be included explicitly.
Does a design quote include boards? Only if fabrication, components and assembly are listed. Keep engineering services and manufactured units separate.
What should 勛圖tv receive? Describe the requested design support, available inputs, constraints, desired outputs and schedule. Discuss the later PCB manufacturing route so deliverables fit the build. The existing Contact path accepts an enquiry without requiring the worksheet, and no automatic file transfer is claimed.