TIER-1 ENGINEER
ENGINEERING AND MANUFACTURING
SIMPLIFIED
The process excels at producing large, lightweight, thin-walled parts with good cosmetic quality on one side and relatively low tooling cost. Common applications include packaging trays, blister packs, appliance liners, refrigerator interiors, automotive interior panels, medical trays, and point-of-purchase displays. These parts are typically produced in the thousands to hundreds of thousands, where injection molding tooling cost or lead time cannot be justified.
Thermoforming equipment generally consists of a sheet clamping system, a heating station, a forming station using vacuum and or pressure, a cooling stage, and a trimming operation. Tooling is typically aluminum or composite rather than hardened steel, which keeps cost and lead time low but limits precision and durability.
Thermoforming performs best when it is selected intentionally and designed honestly. Most production issues trace back to designs that assume injection-molding behavior from a process that fundamentally does not behave that way.
DESIGN REVIEW
PRACTICAL, STRUCTURED DESIGN REVIEW BEFORE PROTOTYPING, QUOTING, OR RELEASE
-FIND DESIGN ISSUES BEFORE YOU BUILD-
TIER-1
WHAT IS A TIER-1 DESIGN REVIEW?
A Tier-1 Design Review is a practical, structured engineering review focused on identifying design issues before a product moves deeper into prototyping, supplier review, quoting, or redesign.
The review looks at the submitted design package from a real-world engineering perspective, including design intent, geometry, fit, function, assembly, material assumptions, process direction, and unclear requirements.
The goal is to identify any design issues or oversights that may cause problems later in your development cycle, and recommend corrective actions to reduce the risk of costly redesigns, supplier confusion, no-quotes, and timing overruns.
No payment is required to submit. Project fit, scope, price, and lead time are confirmed first.
DR
WHY USE A TIER-1 DESIGN REVIEW
CATCH DESIGN ISSUES BEFORE PROTOTYPING, QUOTING, OR RELEASE
GET AN EXPERIENCED REVIEW OF CAD, DRAWINGS, PROTOTYPES, OR ASSEMBLIES
VALIDATE DESIGN INTENT, FIT, FUNCTION, INTERFACES, AND ASSEMBLY
REDUCE REDESIGN, REWORK, AND COSTLY DOWNSTREAM SURPRISES
PREPARE FOR PROTOTYPE BUILDS, SUPPLIER REVIEW, OR DESIGN HANDOFF
GET CLEAR, PRIORITIZED ENGINEERING FEEDBACK AND NEXT STEPS
CORE OBJECTIVES
COMMON APPLICATIONS
INDEPENDENT INVENTORS
Find design issues before spending money on prototypes or suppliers.
GARAGE PROTOTYPERS
IDENTIFY ISSUES BEFORE SPENDING TIME AND MONEY ON FABRICATION.
SERIOUS MAKERS
Check fit, function, assembly, and design direction before next buildS.
PRODUCT STARTUPS
Reduce risk before supplier engagement, quoting, or DESIGN refinement.
MECHANICAL ENGINEERS
Add an external design checkpoint for geometry, interfaces, and ASSUMPTIONS
PRODUCT DESIGNERS
Identify practical design issues before CAD release, prototyping, or handoff.
OEM ENGINEERING TEAMS
Add AN EXTERNAL review before SUPPLIER REVIEW, prototype runs, or redesign.
SMALL BUSINESSES
Get practical DESIGN feedback without RETAINING internal engineering SOURCES.
WHAT YOU GET
INITIAL DESIGN ASSESSMENT REPORT
The Initial Design Assessment Report (IDAR) is the front-end assessment report used before the full Design Review begins.
It helps the client to visualize and understand Tier-1 Engineer's assessment of the submitted project condition, available files, design maturity, review concerns, missing information, assigned Review Level, estimated lead time, review price, approved scope, and next steps.
The purpose of the IDAR is to make sure the project is properly screened and scoped before paid technical review begins. It gives the client a clear checkpoint to review what Tier-1 Engineer is proposing to review, what level of review applies, what information is still needed, and what the Design Review will include.
THE IDAR ESTABLISHES:
The current condition and maturity of the submitted design
Whether the provided CAD and documentation are review-ready
An organized overview of the submitted design requirements
Preliminary number of actionable design concerns
The appropriate Review Level based on project complexity
A clearly defined scope for the technical design review
The price and estimated lead time before work begins
Any missing information required to complete the review
A documented path into the Phase Three technical assessment
The IDAR gives both parties a clear understanding of the submitted design, identifies any missing information, and establishes the Review Level, lead time, and cost before initiating the Design Review.
DESIGN REVIEW REPORT
The Design Review Report (DRR) is the final deliverable for a Tier-1 Design Review, which contains the detailed, actionable review content.
It documents the practical design findings identified during the approved review scope, including concerns related to design intent, geometry, fit, function, assembly, material assumptions, process direction, unclear requirements, and recommended design actions.
The purpose of the DRR is to give the client a structured engineering review of the submitted design package. It identifies what may need attention, why it matters, what risk area it affects, and what actions should be considered before the design moves further into prototyping, supplier review, quoting, or redesign.
THE DRR PROVIDES:
A clear assessment of the design’s current condition
Basic manufacturability observations and process fit analysis
Review of geometry, interfaces, fit, and functional intent
Identification of design concerns and technical weaknesses
Recommendations for correcting identified issues
Prioritized findings based on their impact on the design
A logical order for completing design revisions
A determination of overall design readiness and corrective ACTION
Practical next-step guidance to inform your next milestones
The DRR gives the client a focused evaluation of the design itself, showing what is working, what requires correction, and what should happen before moving into the next stage of your design.
REVIEW LEVELS AND PRICING
WHAT IS A REVIEW LEVEL?
Not every Design Review requires the same engineering effort.
Some projects need a focused check of a single part, CAD model, prototype, or design concern. Others need a broader review of an assembly, multiple design risks, unclear requirements, fit issues, functional concerns, or supplier-readiness questions.
A Review Level is a tiered classification of the engineering effort expected to properly complete a Design Review. It accounts for factors such as project complexity, number of parts and interfaces, documentation depth, design maturity, requirement clarity, and the investigation needed to understand the design. Review Levels provide a consistent way to account for how much engineering work a particular submission is expected to require, and standardize cost and timing.
The client does not choose the Review Level directly. The level is assigned by Tier-1 Engineer based on the design condition, overall complexity, and needs of the submitted design package.
REVIEW LEVEL DRIVERS
OVERALL MATURITY OF THE DESIGN
DESIGN INTENT CLARITY
PART AND ASSEMBLY COMPLEXITY
FIT / FUNCTION SENSITIVITY
DOCUMENTATION DEPTH
PERFORMANCE REQUIREMENT CLARITY
OVERALL PROJECT COMPLEXITY
OVERALL ENGINEERING REVIEW EFFORT
REVIEW LEVELS ARE INTENDED TO STANDARDIZE AND STREAMLINE THE PROCESS WHILE PROVIDING CLARITY, TRANSPARENCY, AND SCOPE-CREEP CONTROL.
Every Review Level follows the same Design Review process and includes the same core deliverables. The assigned level reflects the anticipated engineering effort required to properly review the submitted project, based on factors such as design complexity, number of parts and interfaces, documentation depth, design maturity, and overall review scope.
A higher Review Level does not indicate a better or more complete service. It indicates THAT a project IS expected to require more engineering time, investigation, and analysis to reach the same standard of review.
Level 1 is normally assigned when the submitted design is relatively simple and can be understood without extensive investigation. The design intent is fairly clear, the documentation package is manageable, and the number of parts, interfaces, requirements, or areas requiring engineering evaluation is limited.
A Level 1 project may still contain meaningful design concerns. The classification simply indicates that those concerns can reasonably be evaluated and documented within a focused review effort.
Relatively simple part or assembly
Limited number of interfaces
Clearly defined design intent
Manageable documentation package
Few competing requirements
Focused or well-defined concerns
Lower overall review complexity
WHY A PROJECT MAY BE ASSIGNED LEVEL 1
COMMON LEVEL 1 CHARACTERISTICS
FOCUSED REVIEW
TYPICAL PROJECT CHARACTERISTICS
SIMPLE PARTS
EARLY PROTOTYPES
FOCUSED CONCERNS
SIMPLE ASSEMBLIES
REVIEW LEVEL FACTORS
LOW COMPLEXITY
LIMITED VARIABLES
CLEAR DESIGN INTENT
SMALL FILE PACKAGE
LEAD TIME
3-5
BUSINESS DAYS
$399
Level 1 is normally assigned when the submitted design is relatively simple and can be understood without extensive investigation. The design intent is fairly clear, the documentation package is manageable, and the number of parts, interfaces, requirements, or areas requiring engineering evaluation is limited.
A Level 1 project may still contain meaningful design concerns. The classification simply indicates that those concerns can reasonably be evaluated and documented within a focused review effort.
Relatively simple part or assembly
Limited number of interfaces
Clearly defined design intent
Manageable documentation package
Few competing requirements
Focused or well-defined concerns
Lower overall review complexity
WHY A PROJECT MAY BE ASSIGNED LEVEL 1
COMMON LEVEL 1 CHARACTERISTICS
FOCUSED REVIEW
TYPICAL PROJECT CHARACTERISTICS
SIMPLE PARTS
EARLY PROTOTYPES
FOCUSED CONCERNS
SIMPLE ASSEMBLIES
REVIEW LEVEL FACTORS
LOW COMPLEXITY
LIMITED VARIABLES
CLEAR DESIGN INTENT
SMALL FILE PACKAGE
LEAD TIME
3-5
BUSINESS DAYS
$399
Level 1 is normally assigned when the submitted design is relatively simple and can be understood without extensive investigation. The design intent is fairly clear, the documentation package is manageable, and the number of parts, interfaces, requirements, or areas requiring engineering evaluation is limited.
A Level 1 project may still contain meaningful design concerns. The classification simply indicates that those concerns can reasonably be evaluated and documented within a focused review effort.
Relatively simple part or assembly
Limited number of interfaces
Clearly defined design intent
Manageable documentation package
Few competing requirements
Focused or well-defined concerns
Lower overall review complexity
WHY A PROJECT MAY BE ASSIGNED LEVEL 1
COMMON LEVEL 1 CHARACTERISTICS
FOCUSED REVIEW
TYPICAL PROJECT CHARACTERISTICS
SIMPLE PARTS
EARLY PROTOTYPES
FOCUSED CONCERNS
SIMPLE ASSEMBLIES
REVIEW LEVEL FACTORS
LOW COMPLEXITY
LIMITED VARIABLES
CLEAR DESIGN INTENT
SMALL FILE PACKAGE
LEAD TIME
3-5
BUSINESS DAYS
$399
Level 2 is assigned when the design requires a broader engineering evaluation. This may result from additional components, interacting features, multiple design concerns, greater documentation, less-defined requirements, or conditions that need to be considered together rather than independently.
The Design Review itself does not change. More engineering effort is simply required to understand the project, evaluate the relevant relationships, and develop well-supported findings and recommended actions.
Multiple interacting parts or features
Greater interface complexity
Several areas requiring evaluation
Broader documentation package
Multiple functional requirements
Competing design constraints
MODERATE overall review complexity
WHY A PROJECT MAY BE ASSIGNED LEVEL 2
COMMON LEVEL 2 CHARACTERISTICS
EXPANDED REVIEW
TYPICAL PROJECT CHARACTERISTICS
DETAILED PART DESIGNS
SMALL ASSEMBLIES
MULTIPLE CONCERNS
MULTI-FUNCTION DESIGNS
REVIEW LEVEL FACTORS
MODERATE COMPLEXITY
MULTIPLE VARIABLES
BROAD DESIGN CONTENT
LARGE FILE PACKAGE
LEAD TIME
5-10
BUSINESS DAYS
$699
Level 3 is reserved for projects where the expected engineering effort extends beyond what can reasonably be represented by the standard Level 1 or Level 2 review.
These projects may involve complex assemblies, numerous interfaces, extensive documentation, substantial uncertainty, unusual design conditions, or a large number of interacting requirements. Considerably more time may be required simply to understand the design before individual findings can be evaluated and documented responsibly.
Complex or multi-part assemblies
Numerous critical interfaces
Extensive documentation
MANY INTERACTING REQUIREMENTS
Significant design uncertainty
Unusual or difficult project conditions
SUBSTANTIAL INVESTIGATION REQUIRED
WHY A PROJECT MAY BE ASSIGNED LEVEL 3
COMMON LEVEL 3 CHARACTERISTICS
ADVANCED REVIEW
TYPICAL PROJECT CHARACTERISTICS
COMPLEX ASSEMBLIES
MULTI-MATERIAL DESIGNS
HIGH-RISK DESIGNS
EXPANDED REVIEW NEEDS
REVIEW LEVEL FACTORS
HIGH COMPLEXITY
MULTIPLE INTERFACES
TIMING-SENSITIVE
DEEP DOCUMENTATION
LEAD TIME
CUSTOM
BUSINESS DAYS
CUSTOM
HOW IT WORKS
THE FOUR-PHASE SYSTEM
The Tier-1 Design Review process uses a structured four-phase system to keep the review clear, predictable, and controlled from intake through final report delivery.
Instead of jumping straight into paid review, the process first screens the submitted project, checks documentation completeness, confirms project fit, and assigns the correct review level. This helps prevent mismatched expectations, unclear scope, missing information, and surprise changes after the review has started.
The phase system gives each part of the process a defined purpose, and gives the client a clear checkpoint before committing to the full Design Review. It also keeps the review focused on the approved design package, approved concerns, and approved deliverable.
The result is a more predictable review process with clearer boundaries, cleaner communication, and practical findings delivered through the DRR.
PHASE SYSTEM ADVANTAGES
STRUCTURE PROVIDES CLARITY AND CLEAR RESPONISBILITIES
PROJECT FIT AND REVIEW LEVEL IS REVIEWED BEFORE PAYMENT
PRICE AND LEAD TIME ARE DEFINED UP FRONT
OUTLINES CLEAR DELIVERABLES AND NEXT STEPS
ANY REQUIRED MISSING INFORMATION IS IDENTIFIED EARLY
PAID REVIEW DOES NOT BEGIN UNTIL CLIENT APPROVAL OF IDAR
PROVIDES A STREAMLINED, LOW STRESS CLIENT EXPERIENCE
DESIGN REVIEW PHASES
WHAT YOU DO:
Gather required information, fill out the Design Review Project Submission form, upload documentation, and submit the form.
WHAT YOU DO:
Wait for confirmation of Project Fit and/or IDAR delivery via Email. Review the IDAR, and pay to approve and INITIATE THE FORMAL DESIGN REVIEW.
WHAT YOU DO:
WAIT FOR Tier-1 Engineer TO COMPLETE the full, detailed Design Review of your project submission package, and compile findings in the DRR.
WHAT YOU DO:
You receive the DRR, with all design findings and recommended actions. The Design Review closes, unless clarification is requested.
DETAILED PHASE OVERVIEW
WHAT YOU DO:
Gather required information, fill out the Design Review Project Submission form, upload documentation, and submit the form.
WHAT YOU DO:
Wait for confirmation of Project Fit and/or IDAR delivery via Email. Review the IDAR, and pay to approve and INITIATE THE FORMAL DESIGN REVIEW.
WHAT YOU DO:
WAIT FOR Tier-1 Engineer TO COMPLETE the full, detailed Design Review of your project submission package, and compile findings in the DRR.
WHAT YOU DO:
You receive the DRR, with all design findings and recommended actions. The Design Review closes, unless clarification is requested.
HOW TO BEGIN
GUIDED SUBMISSION METHOD
Starting a Design Review does not require a perfect engineering package or every decision already finalized. The goal is to provide enough information to understand what the design is supposed to do, how and where it will be used, what is currently known about how it will be made, and what documentation is available to support the review.
The steps below are designed to help organize that information before submission. Each section explains what to provide, what the terminology means, and the level of detail that is useful. If something is unknown, undecided, or still being developed, that is completely acceptable. Simply provide what is currently known.
A well-prepared submission helps Tier-1 Engineer understand the project faster, identify missing information early, and establish the right Review Level before paid review begins.
THE PROJECT SUBMISSION FORM
The Design Review Project Submission Form provides the context needed to understand the design before the technical review begins. CAD and drawings show geometry, but they do not always explain what the design is intended to do, how it will be used, what requirements it must meet, or what concerns already exist.
Providing as much relevant detail as possible helps reduce assumptions, limit unnecessary back-and-forth, identify missing information early, and establish the correct Review Level.
You do not need to have every answer finalized. If something is unknown or still being decided, simply say so. A complete and honest submission gives the project the best possible starting point.
EXPLORE THE STEPS BELOW TO PREPARE FOR A TIER-1 DESIGN REVIEW SUBMISSION
This establishes the purpose and functional expectations of the design. It includes the design intent, performance requirements, and any special requirements or constraints that define what the part, product, or assembly needs to do and what conditions must be satisfied for the design to be considered successful.
DESIGN INTENT
What is this part or assembly supposed to accomplish?
Design intent is the basic purpose of the design and the result it is expected to achieve. It explains why the design exists and what must happen for it to be considered successful. Understanding design intent provides the reference point for evaluating whether the geometry, features, interfaces, and overall design actually support that purpose.
EXAMPLES
-
Hold a sensor in a static position
-
Seal a fluid passage
-
Support a specified load
-
Protect internal components
-
Connect two assemblies
-
Allow repeated opening/closing
Design intent gives the review a reference point. A design cannot be evaluated effectively without understanding what it is expected to accomplish.
PERFORMANCE REQUIREMENTS
WHAT DOES THE DESIGN NEED TO WITHSTAND OR ACHIEVE?
Performance requirements are the measurable or practical conditions the design must satisfy while doing its job. These may involve strength, movement, temperature, pressure, accuracy, durability, sealing, weight, or other functional expectations. They help define what "working correctly" actually means.
EXAMPLES
-
Loads or forces
-
Pressure
-
Temperature
-
Speed or movement
-
Expected life or number of cycles
-
Required stiffness
-
Sealing requirements
-
Impact resistance
-
Weight targets
-
Dimensional accuracy
-
Expected service life
Exact values are helpful when available, but they are not required for every submission.
SPECIAL
REQUIREMENTS
ARE THERE SPECIFIC CONDITIONS THE DESIGN MUST SATISFY?
Special requirements are project-specific conditions that may not be obvious from the geometry alone but limit what can be changed or influence how the design must function. These requirements help prevent recommendations that conflict with something important to the project.
EXAMPLES
-
Maximum size or weight
-
Required mounting locations
-
Regulatory constraints
-
Customer requirements
-
Appearance requirements
-
Serviceability
-
Tool access
-
Required clearances
-
Existing mating components
-
Packaging limitations
-
Features that cannot be changed
If a requirement is important to the project, include it even if it does not seem technical.
-
This will help to establish the real-world application of the design. It includes the use environment, assembly requirements, and cosmetic requirements that may influence how the product is designed, installed, operated, serviced, or expected to appear once in use.
USE ENVIRONMENT
UNDER WHAT CONDITIONS WILL THE PRODUCT BE USED?
The use environment is the physical setting and operating conditions the product is expected to encounter during normal use, storage, transportation, or service. This includes exposure to temperature, moisture, chemicals, sunlight, contamination, vibration, impact, and other environmental conditions that may affect the design.
EXAMPLES
-
Indoor, climate-controlled use
-
Outdoor year-round exposure
-
Rain, water, or high humidity
-
Extreme heat or cold
-
Dirt, dust, mud, or debris
-
UV and sunlight exposure
-
Oil, fuel, or other chemicals
-
Salt or corrosive environments
-
Continuous vibration
-
Shock or impact
-
Automotive or underhood
A simple description is acceptable. For example:
“Mounted outdoors year-round."
INSTALLATION REQUIREMENTS
How does the design assemble, attach, OR INSTALL?
Assembly requirements describe how the part or product connects to other components and what must happen during installation, assembly, adjustment, maintenance, or disassembly. This includes fasteners, mating features, alignment, access, clearances, assembly order, tooling, and any components the design must interface with.
EXAMPLES
-
Bolts to an existing surface
-
Snaps into another component
-
Assembled without special tools
-
Requires tool access
-
Must align with existing features
-
Removable for maintenance
-
Assembled in a specific sequence
-
Must prevent incorrect assembly
-
One person assembly
Exact values are helpful when available, but they are not required for every submission.
COSMETIC REQUIREMENTS
WHAT APPEARANCE EXPECTATIONS does the design need to meet?
Cosmetic requirements define how the finished product is expected to look and which surfaces or features are visually important. These requirements may involve surface finish, texture, color, gloss, visible defects, parting lines, witness marks, fastener visibility, gaps, alignment, or other appearance-related expectations.
EXAMPLES
-
Clean visible surfaces
-
Surface texture requirements
-
No exposed fasteners
-
Minimal surface defects
-
Consistent color or gloss
-
Plated, painted, or anodized finish
-
Tooling marks are unacceptable
-
Match existing component
If appearance is not important, that is useful information too. Simply state that the design is function-first with no significant cosmetic requirements.
-
A complete design review should include general manufacturing direction for the design. This includes the planned manufacturing process, planned material, and expected production volume, at a minimum. These decisions do not need to be final. Current assumptions, alternatives being considered, or items that are still undecided are all useful information to include for the review. Often, manufacturing direction is not yet known or finalized. In that case, Tier-1 Engineer will provide manufacturing process direction through the DRR.
PLANNED PROCESS
WHAT IS THE PLANNED METHOD TO MANUFACTURE THIS PRODUCT?
The planned manufacturing process is the method currently expected to be used to physically produce the part. Different processes create parts in different ways and come with different capabilities, limitations, tooling requirements, and design considerations. If a process has already been selected or is being considered, include it even if the decision is not final.
EXAMPLES
-
Injection molding
-
CNC machining
-
Die casting
-
Sheet metal forming
-
Progressive stamping
-
Extrusion
-
Forging
-
Additive manufacturing
-
Fabrication and welding
-
A combination of processes
If the process has not been selected, simply check the "Not Sure" box.
PLANNED MATERIAL
WHAT IS THE PLANNED MATERIAL(s) of THIS PRODUCT?
The planned material is the material or material family currently intended for the part. This can be as broad as aluminum, steel, or plastic, or as specific as an exact alloy, resin, or material grade. If multiple materials are being considered, include the options currently under evaluation.
EXAMPLES
-
Aluminum
-
Carbon steel
-
Stainless steel
-
Magnesium
-
Zinc
-
ABS
-
Nylon
-
Polycarbonate
-
Polypropylene
-
Rubber or elastomer
-
Fiber-reinforced plastic
-
Composite material
If known, include the specific grade or formulation. If unknown, check the "Not Sure" box.
PRODUCTION VOLUME
Approximately how many parts do you expect to PRODUCE?
Production volume is the approximate quantity of parts expected to be produced. This may be expressed as a prototype quantity, production batch, annual volume, or estimated lifetime quantity. An exact forecast is not required. A reasonable estimate or range is sufficient.
EXAMPLES
-
One proof-of-concept prototype
-
5 to 20 development parts
-
50 to 100 units for testing
-
500 parts per year
-
5,000 parts per year
-
50,000 parts per year
-
250,000 parts per year
If the volume is uncertain, provide whatever is currently known, such as “low volume, likely fewer than 500 units per year” or “volume not yet established, but intended for eventual mass production.”
-
What would you like the Design Review to help you understand, verify, or improve?
Your questions and concerns identify specific areas of the design you want additional attention placed on during the review. These may be known problems, uncertainties, decisions you want independently checked, feedback you have received from someone else, or simply areas where you are not confident moving forward.
You do not need to diagnose the problem yourself or describe it using engineering terminology. Explain what you are seeing, what you are unsure about, or what prompted you to seek another set of eyes. These concerns provide useful context and help Tier-1 Engineer understand what matters most to you and the project. Provide as much detail as you are able, but simple statements are often enough to direct the focus of the review, such as:
-
“I am concerned this bracket may not be strong enough.”
-
“These two parts are difficult to assemble.”
-
“I am not sure if there is enough clearance between these components.”
-
“The prototype keeps failing in this area.”
-
“I want to confirm that the material I selected makes sense.”
-
“I am concerned about how these parts will fit together.”
-
“I want to make sure the design is not unnecessarily complicated.”
-
“I am preparing to order prototypes and want the design checked first.”
-
“I am preparing to send the design to suppliers for quoting.”
-
“The design works, but I want to know what I may be overlooking.”
-
“I do not have a specific concern. I want an experienced independent review of the overall design.”
NOT SURE WHAT TO ASK?
That is completely acceptable. A Design Review does not require you to already know where the problems are. If your goal is simply to have the design independently evaluated before committing additional time or money, state that in the submission. The review is intended to help identify concerns you may not know to look for.
-
Design documentation is the collection of information used to communicate the product, its geometry, requirements, interfaces, and current state of development. It may range from a complete CAD and drawing package to a few sketches, prototype photos, or written notes.
You do not need every type of documentation listed below. Submit the most current and relevant information you have. Providing multiple forms of documentation can help clarify details that may not be obvious from a single CAD model or drawing.
USEFUL SUBMISSION MATERIALS MAY INCLUDE:
3D CAD MODELS
Digital models showing the geometry of individual parts or complete assemblies. STEP and Parasolid files are preferred when available.
PREFERRED FILE TYPES
.STEP
.IGES
.X_T
2D ENGINEERING DRAWINGS
Drawings showing dimensions, tolerances, material callouts, notes, finishes, and other requirements that may not be defined by the CAD model alone.
PREFERRED FILE TYPES
.PDF
.PNG
.JPEG
ASSEMBLY MODELS OR DRAWINGS
Documentation showing how multiple components fit together, interact, move, fasten, or locate relative to one another.
PREFERRED FILE TYPES
.STEP
.IGES
.X_T
.PDF
.PNG
SKETCHES OR CONCEPT DRAWINGS
Formal or informal drawings used to explain features, mechanisms, intended changes, or design ideas. Hand-drawn sketches are completely acceptable.
PREFERRED FILE TYPES
.PDF
.PNG
.JPEG
PROTOTYPE OR PRODUCT PHOTOS
Images showing the current physical design, assembly condition, installation, failure area, or other real-world information that may help explain the project.
PREFERRED FILE TYPES
.PPTX
.PNG
.JPEG
DESIGN REQUIREMENTS
Written requirements describing dimensional, functional, performance, material, cosmetic, customer, or other project expectations.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
SUPPLIER FEEDBACK
DFM comments, markups, emails, quotations, or technical questions received from manufacturers or suppliers.
PREFERRED FILE TYPES
.PDF
.PNG
.MSG
RFQ OR QUOTING DOCUMENTS
Information previously prepared for supplier quoting that may define expected volume, material, process, tooling, or other production assumptions.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
TEST OR INSPECTION REPORTS
Dimensional reports, prototype testing, failure information, fit checks, inspection data, or other results that provide additional context about how the current design performs.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
REFERENCE DOCUMENTS OR NOTES
Any additional information that helps explain the design, its history, known problems, previous decisions, or requirements that should be considered during the review.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
WHAT SHOULD I SUBMIT?
Start with the information that best represents the current version of the design. Avoid including obsolete files unless they provide useful background, and clearly identify any older documentation that is being submitted for reference only.
If you are unsure whether a particular file is useful, include it or describe it in the submission. The initial assessment is used to determine whether the available documentation is sufficient and identify anything additional that may be needed before the Design Review begins.
You do not need a complete professional engineering package to submit. A well-defined CAD model, a prototype, photographs, sketches, or other supporting information may be enough to begin depending on the project.
Project submission is the starting point for the Tier-1 Design Review process. You will complete the Design Review submission form, provide the project information outlined in the previous steps, and upload the most relevant design documentation currently available.
Submission does not begin the paid Design Review. It gives Tier-1 Engineer the information needed to understand the project, confirm that it is a good fit for the service, and determine the amount of engineering effort expected to complete the review properly.
DURING INITIAL ASSESSMENT, TIER-1 ENGINEER WILL:
Confirm that the project falls within the Design Review scope
Review the submitted project information and documentation
Evaluate the current maturity and complexity of the design
Identify missing or unclear information that may be needed
Determine the appropriate Review Level
Prepare the Initial Design Assessment Report (IDAR)
WHAT HAPPENS NEXT?
If the project is accepted, you will receive the IDAR documenting the initial assessment, assigned Review Level, price, estimated lead time, and any additional information required before the technical review begins.
You can review the IDAR before deciding whether to proceed. No paid technical review begins until the IDAR is approved and payment is received.
If the project is not yet ready for a Design Review, additional information may be requested or a more appropriate review path may be recommended.
HOW TO BEGIN
GUIDED SUBMISSION METHOD
Starting a Design Review does not require a perfect engineering package or every decision already finalized. The goal is to provide enough information to understand what the design is supposed to do, how and where it will be used, what is currently known about how it will be made, and what documentation is available to support the review.
The steps below are designed to help organize that information before submission. Each section explains what to provide, what the terminology means, and the level of detail that is useful. If something is unknown, undecided, or still being developed, that is completely acceptable. Simply provide what is currently known.
A well-prepared submission helps Tier-1 Engineer understand the project faster, identify missing information early, and establish the right Review Level before paid review begins.
THE PROJECT SUBMISSION FORM
The Design Review Project Submission Form provides the context needed to understand the design before the technical review begins. CAD and drawings show geometry, but they do not always explain what the design is intended to do, how it will be used, what requirements it must meet, or what concerns already exist.
Providing as much relevant detail as possible helps reduce assumptions, limit unnecessary back-and-forth, identify missing information early, and establish the correct Review Level.
You do not need to have every answer finalized. If something is unknown or still being decided, simply say so. A complete and honest submission gives the project the best possible starting point.
EXPLORE THE STEPS BELOW TO PREPARE FOR A TIER-1 DESIGN REVIEW SUBMISSION
This establishes the purpose and functional expectations of the design. It includes the design intent, performance requirements, and any special requirements or constraints that define what the part, product, or assembly needs to do and what conditions must be satisfied for the design to be considered successful.
DESIGN INTENT
What is this part or assembly supposed to accomplish?
Design intent is the basic purpose of the design and the result it is expected to achieve. It explains why the design exists and what must happen for it to be considered successful. Understanding design intent provides the reference point for evaluating whether the geometry, features, interfaces, and overall design actually support that purpose.
EXAMPLES
-
Hold a sensor in a static position
-
Seal a fluid passage
-
Support a specified load
-
Protect internal components
-
Connect two assemblies
-
Allow repeated opening/closing
Design intent gives the review a reference point. A design cannot be evaluated effectively without understanding what it is expected to accomplish.
PERFORMANCE REQUIREMENTS
WHAT DOES THE DESIGN NEED TO WITHSTAND OR ACHIEVE?
Performance requirements are the measurable or practical conditions the design must satisfy while doing its job. These may involve strength, movement, temperature, pressure, accuracy, durability, sealing, weight, or other functional expectations. They help define what "working correctly" actually means.
EXAMPLES
-
Loads or forces
-
Pressure
-
Temperature
-
Speed or movement
-
Expected life or number of cycles
-
Required stiffness
-
Sealing requirements
-
Impact resistance
-
Weight targets
-
Dimensional accuracy
-
Expected service life
Exact values are helpful when available, but they are not required for every submission.
SPECIAL
REQUIREMENTS
ARE THERE SPECIFIC CONDITIONS THE DESIGN MUST SATISFY?
Special requirements are project-specific conditions that may not be obvious from the geometry alone but limit what can be changed or influence how the design must function. These requirements help prevent recommendations that conflict with something important to the project.
EXAMPLES
-
Maximum size or weight
-
Required mounting locations
-
Regulatory constraints
-
Customer requirements
-
Appearance requirements
-
Serviceability
-
Tool access
-
Required clearances
-
Existing mating components
-
Packaging limitations
-
Features that cannot be changed
If a requirement is important to the project, include it even if it does not seem technical.
-
This will help to establish the real-world application of the design. It includes the use environment, assembly requirements, and cosmetic requirements that may influence how the product is designed, installed, operated, serviced, or expected to appear once in use.
USE ENVIRONMENT
UNDER WHAT CONDITIONS WILL THE PRODUCT BE USED?
The use environment is the physical setting and operating conditions the product is expected to encounter during normal use, storage, transportation, or service. This includes exposure to temperature, moisture, chemicals, sunlight, contamination, vibration, impact, and other environmental conditions that may affect the design.
EXAMPLES
-
Indoor, climate-controlled use
-
Outdoor year-round exposure
-
Rain, water, or high humidity
-
Extreme heat or cold
-
Dirt, dust, mud, or debris
-
UV and sunlight exposure
-
Oil, fuel, or other chemicals
-
Salt or corrosive environments
-
Continuous vibration
-
Shock or impact
-
Automotive or underhood
A simple description is acceptable. For example:
“Mounted outdoors year-round."INSTALLATION REQUIREMENTS
How does the design assemble, attach, OR INSTALL?
Assembly requirements describe how the part or product connects to other components and what must happen during installation, assembly, adjustment, maintenance, or disassembly. This includes fasteners, mating features, alignment, access, clearances, assembly order, tooling, and any components the design must interface with.
EXAMPLES
-
Bolts to an existing surface
-
Snaps into another component
-
Assembled without special tools
-
Requires tool access
-
Must align with existing features
-
Removable for maintenance
-
Assembled in a specific sequence
-
Must prevent incorrect assembly
-
One person assembly
Exact values are helpful when available, but they are not required for every submission.
COSMETIC REQUIREMENTS
WHAT APPEARANCE EXPECTATIONS does the design need to meet?
Cosmetic requirements define how the finished product is expected to look and which surfaces or features are visually important. These requirements may involve surface finish, texture, color, gloss, visible defects, parting lines, witness marks, fastener visibility, gaps, alignment, or other appearance-related expectations.
EXAMPLES
-
Clean visible surfaces
-
Surface texture requirements
-
No exposed fasteners
-
Minimal surface defects
-
Consistent color or gloss
-
Plated, painted, or anodized finish
-
Tooling marks are unacceptable
-
Match existing component
If appearance is not important, that is useful information too. Simply state that the design is function-first with no significant cosmetic requirements.
COSMETIC REQUIREMENTS
WHAT APPEARANCE EXPECTATIONS does the design need to meet?
Cosmetic requirements define how the finished product is expected to look and which surfaces or features are visually important. These requirements may involve surface finish, texture, color, gloss, visible defects, parting lines, witness marks, fastener visibility, gaps, alignment, or other appearance-related expectations.
EXAMPLES
-
Clean visible surfaces
-
Surface texture requirements
-
No exposed fasteners
-
Minimal surface defects
-
Consistent color or gloss
-
Plated, painted, or anodized finish
-
Tooling marks are unacceptable
-
Match existing component
If appearance is not important, that is useful information too. Simply state that the design is function-first with no significant cosmetic requirements.
INSTALLATION REQUIREMENTS
How does the design assemble, attach, OR INSTALL?
Assembly requirements describe how the part or product connects to other components and what must happen during installation, assembly, adjustment, maintenance, or disassembly. This includes fasteners, mating features, alignment, access, clearances, assembly order, tooling, and any components the design must interface with.
EXAMPLES
-
Bolts to an existing surface
-
Snaps into another component
-
Assembled without special tools
-
Requires tool access
-
Must align with existing features
-
Removable for maintenance
-
Assembled in a specific sequence
-
Must prevent incorrect assembly
-
One person assembly
As much detail as possible is important; multi-part assemblies quickly increase complexity.
USE ENVIRONMENT
UNDER WHAT CONDITIONS WILL THE PRODUCT BE USED?
The use environment is the physical setting and operating conditions the product is expected to encounter during normal use, storage, transportation, or service. This includes exposure to temperature, moisture, chemicals, sunlight, contamination, vibration, impact, and other environmental conditions that may affect the design.
EXAMPLES
-
Indoor, climate-controlled use
-
Outdoor year-round exposure
-
Rain, water, or high humidity
-
Extreme heat or cold
-
Dirt, dust, mud, or debris
-
UV and sunlight exposure
-
Oil, fuel, or other chemicals
-
Salt or corrosive environments
-
Continuous vibration
-
Shock or impact
-
Automotive or underhood
A simple description is acceptable. For example:“Mounted outdoors year-round."
-
A complete design review should include general manufacturing direction for the design. This includes the planned manufacturing process, planned material, and expected production volume, at a minimum. These decisions do not need to be final. Current assumptions, alternatives being considered, or items that are still undecided are all useful information to include for the review. Often, manufacturing direction is not yet known or finalized. In that case, Tier-1 Engineer will provide manufacturing process direction through the DRR.
PLANNED PROCESS
WHAT IS THE PLANNED METHOD TO MANUFACTURE THIS PRODUCT?
The planned manufacturing process is the method currently expected to be used to physically produce the part. Different processes create parts in different ways and come with different capabilities, limitations, tooling requirements, and design considerations. If a process has already been selected or is being considered, include it even if the decision is not final.
EXAMPLES
-
Injection molding
-
CNC machining
-
Die casting
-
Sheet metal forming
-
Progressive stamping
-
Extrusion
-
Forging
-
Additive manufacturing
-
Fabrication and welding
-
A combination of processes
If the process has not been selected, simply check the "Not Sure" box.
PLANNED MATERIAL
WHAT IS THE PLANNED MATERIAL(s) of THIS PRODUCT?
The planned material is the material or material family currently intended for the part. This can be as broad as aluminum, steel, or plastic, or as specific as an exact alloy, resin, or material grade. If multiple materials are being considered, include the options currently under evaluation.
EXAMPLES
-
Aluminum
-
Carbon steel
-
Stainless steel
-
Magnesium
-
Zinc
-
ABS
-
Nylon
-
Polycarbonate
-
Polypropylene
-
Rubber or elastomer
-
Fiber-reinforced plastic
-
Composite material
If known, include the specific grade or formulation. If unknown, check the "Not Sure" box.
PRODUCTION VOLUME
Approximately how many parts do you expect to PRODUCE?
Production volume is the approximate quantity of parts expected to be produced. This may be expressed as a prototype quantity, production batch, annual volume, or estimated lifetime quantity. An exact forecast is not required. A reasonable estimate or range is sufficient.
EXAMPLES
-
One proof-of-concept prototype
-
5 to 20 development parts
-
50 to 100 units for testing
-
500 parts per year
-
5,000 parts per year
-
50,000 parts per year
-
250,000 parts per year
If the volume is uncertain, provide whatever is currently known, such as “low volume, likely fewer than 500 units per year” or “volume not yet established, but intended for eventual mass production.”
PLANNED PROCESS
WHAT IS THE PLANNED METHOD TO MANUFACTURE THIS PRODUCT?
The planned manufacturing process is the method currently expected to be used to physically produce the part. Different processes create parts in different ways and come with different capabilities, limitations, tooling requirements, and design considerations. If a process has already been selected or is being considered, include it even if the decision is not final.
EXAMPLES
-
Injection molding
-
CNC machining
-
Die casting
-
Sheet metal forming
-
Progressive stamping
-
Extrusion
-
Forging
-
Additive manufacturing
-
Fabrication and welding
-
A combination of processes
If the process has not been selected, simply check the "Not Sure" box.
PLANNED MATERIAL
WHAT IS THE PLANNED MATERIAL(s) of THIS PRODUCT?
The planned material is the material or material family currently intended for the part. This can be as broad as aluminum, steel, or plastic, or as specific as an exact alloy, resin, or material grade. If multiple materials are being considered, include the options currently under evaluation.
EXAMPLES
-
Aluminum
-
Carbon steel
-
Stainless steel
-
Magnesium
-
Zinc
-
ABS
-
Nylon
-
Polycarbonate
-
Polypropylene
-
Rubber or elastomer
-
Fiber-reinforced plastic
-
Composite material
If known, include the specific grade or formulation. If unknown, check the "Not Sure" box.
PRODUCTION VOLUME
Approximately how many parts do you expect to PRODUCE?
Production volume is the approximate quantity of parts expected to be produced. This may be expressed as a prototype quantity, production batch, annual volume, or estimated lifetime quantity. An exact forecast is not required. A reasonable estimate or range is sufficient.
EXAMPLES
-
One proof-of-concept prototype
-
5 to 20 development parts
-
50 to 100 units for testing
-
500 parts per year
-
5,000 parts per year
-
50,000 parts per year
-
250,000 parts per year
If the volume is uncertain, provide whatever is currently known, such as “low volume, likely fewer than 500 units per year” or “volume not yet established, but intended for eventual mass production.”
-
What would you like the Design Review to help you understand, verify, or improve?
Your questions and concerns identify specific areas of the design you want additional attention placed on during the review. These may be known problems, uncertainties, decisions you want independently checked, feedback you have received from someone else, or simply areas where you are not confident moving forward.
You do not need to diagnose the problem yourself or describe it using engineering terminology. Explain what you are seeing, what you are unsure about, or what prompted you to seek another set of eyes. These concerns provide useful context and help Tier-1 Engineer understand what matters most to you and the project. Provide as much detail as you are able, but simple statements are often enough to direct the focus of the review, such as:
-
“I am concerned this bracket may not be strong enough.”
-
“These two parts are difficult to assemble.”
-
“I am not sure if there is enough clearance between these components.”
-
“The prototype keeps failing in this area.”
-
“I want to confirm that the material I selected makes sense.”
-
“I am concerned about how these parts will fit together.”
-
“I want to make sure the design is not unnecessarily complicated.”
-
“I am preparing to order prototypes and want the design checked first.”
-
“I am preparing to send the design to suppliers for quoting.”
-
“The design works, but I want to know what I may be overlooking.”
-
“I do not have a specific concern. I want an experienced independent review of the overall design.”
NOT SURE WHAT TO ASK?
That is completely acceptable. A Design Review does not require you to already know where the problems are. If your goal is simply to have the design independently evaluated before committing additional time or money, state that in the submission. The review is intended to help identify concerns you may not know to look for.
-
Design documentation is the collection of information used to communicate the product, its geometry, requirements, interfaces, and current state of development. It may range from a complete CAD and drawing package to a few sketches, prototype photos, or written notes.
You do not need every type of documentation listed below. Submit the most current and relevant information you have. Providing multiple forms of documentation can help clarify details that may not be obvious from a single CAD model or drawing.
USEFUL SUBMISSION MATERIALS MAY INCLUDE:
ASSEMBLY MODELS OR DRAWINGS
Documentation showing how multiple components fit together, interact, move, fasten, or locate relative to one another.
PREFERRED FILE TYPES
.STEP
.IGES
.X_T
.PDF
.PNG
SKETCHES OR CONCEPT DRAWINGS
Formal or informal drawings used to explain features, mechanisms, intended changes, or design ideas. Hand-drawn sketches are completely acceptable.
PREFERRED FILE TYPES
.PDF
.PNG
.JPEG
PROTOTYPE OR PRODUCT PHOTOS
Images showing the current physical design, assembly condition, installation, failure area, or other real-world information that may help explain the project.
PREFERRED FILE TYPES
.PPTX
.PNG
.JPEG
DESIGN REQUIREMENTS
Written requirements describing dimensional, functional, performance, material, cosmetic, customer, or other project expectations.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
SUPPLIER FEEDBACK
DFM comments, markups, emails, quotations, or technical questions received from manufacturers or suppliers.
PREFERRED FILE TYPES
.PDF
.PNG
.MSG
RFQ OR QUOTING DOCUMENTS
Information previously prepared for supplier quoting that may define expected volume, material, process, tooling, or other production assumptions.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
TEST OR INSPECTION REPORTS
Dimensional reports, prototype testing, failure information, fit checks, inspection data, or other results that provide additional context about how the current design performs.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
REFERENCE DOCUMENTS OR NOTES
Any additional information that helps explain the design, its history, known problems, previous decisions, or requirements that should be considered during the review.
PREFERRED FILE TYPES
.MSG
.DOCX
.PNG
.PDF
.JPEG
WHAT SHOULD I SUBMIT?
Start with the information that best represents the current version of the design. Avoid including obsolete files unless they provide useful background, and clearly identify any older documentation that is being submitted for reference only.
If you are unsure whether a particular file is useful, include it or describe it in the submission. The initial assessment is used to determine whether the available documentation is sufficient and identify anything additional that may be needed before the Design Review begins.
You do not need a complete professional engineering package to submit. A well-defined CAD model, a prototype, photographs, sketches, or other supporting information may be enough to begin depending on the project.
2D ENGINEERING DRAWINGS
Drawings showing dimensions, tolerances, material callouts, notes, finishes, and other requirements that may not be defined by the CAD model alone.
PREFERRED FILE TYPES
.PDF
.PNG
.JPEG
3D CAD MODELS
Digital models showing the geometry of individual parts or complete assemblies. STEP and Parasolid files are preferred when available.
PREFERRED FILE TYPES
.IGES
.X_T
.STEP
.STP
.IGES
.IGS
.X_T
2D ENGINEERING DRAWINGS
Drawings showing dimensions, tolerances, material callouts, notes, finishes, and other requirements not defined by the CAD model alone.
PREFERRED FILE TYPES
.IGES
.X_T
.PDF
.PNG
.JPEG
ASSEMBLY MODELS/DRAWINGS
Documentation showing how multiple components fit together, interact, move, fasten, or locate relative to one another.
PREFERRED FILE TYPES
.IGES
.X_T
.STEP
.IGES
.X_T
.PDF
.PNG
SKETCHES/CONCEPT DRAWINGS
Formal or informal drawings used to explain features, mechanisms, intended changes, or design ideas. Hand-drawn sketches are acceptable.
PREFERRED FILE TYPES
.IGES
.X_T
.PDF
.PNG
.JPEG
PROTOTYPE/PRODUCT PHOTOS
Images showing the current physical design, assembly condition, installation, failure area, or other real-world information.
PREFERRED FILE TYPES
.IGES
.X_T
.PPTX
.PNG
.JPEG
DESIGN REQUIREMENTS
Written requirements describing dimensional, functional, performance, material, cosmetic, customer, or other project expectations.
PREFERRED FILE TYPES
.IGES
.X_T
.MSG
.PNG
.JPEG
.DOCX
.PDF
SUPPLIER FEEDBACK
DFM comments, markups, emails, quotations, or technical questions received from manufacturers or suppliers.
PREFERRED FILE TYPES
.IGES
.X_T
.PDF
.PNG
.MSG
RFQ/QUOTING DOCUMENTS
Information previously prepared for supplier quoting that may define expected volume, material, process, tooling, or other production assumptions.
PREFERRED FILE TYPES
.IGES
.X_T
.MSG
.PNG
.JPEG
.DOCX
.PDF
TEST/INSPECTION REPORTS
Dimensional reports, prototype testing, failure information, fit checks, inspection data, or other results that provide additional context.
PREFERRED FILE TYPES
.IGES
.X_T
.MSG
.PNG
.JPEG
.DOCX
.PDF
REFERENCE DOCUMENTATION
Any additional information that helps explain the design, its history, known problems, or previous decisions that should be considered during the review.
PREFERRED FILE TYPES
.IGES
.X_T
.MSG
.PNG
.JPEG
.DOCX
.PDF
Project submission is the starting point for the Tier-1 Design Review process. You will complete the Design Review submission form, provide the project information outlined in the previous steps, and upload the most relevant design documentation currently available.
Submission does not begin the paid Design Review. It gives Tier-1 Engineer the information needed to understand the project, confirm that it is a good fit for the service, and determine the amount of engineering effort expected to complete the review properly.
DURING INITIAL ASSESSMENT, TIER-1 ENGINEER WILL:
Confirm that the project falls within the Design Review scope
Review the submitted project information and documentation
Evaluate the current maturity and complexity of the design
Identify missing or unclear information that may be needed
Determine the appropriate Review Level
Prepare the Initial Design Assessment Report (IDAR)
WHAT HAPPENS NEXT?
If the project is accepted, you will receive the IDAR documenting the initial assessment, assigned Review Level, price, estimated lead time, and any additional information required before the technical review begins.
You can review the IDAR before deciding whether to proceed. No paid technical review begins until the IDAR is approved and payment is received.
If the project is not yet ready for a Design Review, additional information may be requested or a more appropriate review path may be recommended.
SUBMISSION AND REVIEW BOUNDARIES
Tier-1 Design Readiness services are focused on practical mechanical design, physical product development, manufacturability, and production-readiness.
Not every project is a fit for review. Submitted projects are screened before paid technical work begins to confirm service fit, documentation completeness, review scope, and whether the project falls within Tier-1 Engineer’s intended review boundaries.
If a project is not a fit, Tier-1 Engineer may decline the submission, request clarification, or recommend a different review path.
ACCEPTABLE PROJECTS
MECHANICAL PARTS
PHYSICAL PRODUCT DESIGNS
PLASTIC PARTS
METAL PARTS
MOLDED COMPONENTS
CAST COMPONENTS
MACHINED COMPONENTS
SHEET METAL PARTS
FORMED PARTS
3D PRINTED PARTS
PRODUCT ENCLOSURES
BRACKETS / MOUNTS
MECHANICAL ASSEMBLIES
PROTOTYPE DESIGNS
SUPPLIER-READY PACKAGES
*LIST NOT EXHAUSTIVE
MAY REQUIRE CLARIFICATION
INCOMPLETE CAD
MISSING DRAWINGS
PROTOTYPE PHOTOS ONLY
UNCLEAR FUNCTION
UNKNOWN MATERIAL
UNKNOWN PROCESS
UNKNOWN DESIGN INTENT
SAFETY-CRITICAL ITEMS
REGULATED PRODUCTS
LARGE ASSEMBLIES
MULTIPLE PRODUCT VARIANTS
LOW-DETAIL PROJECT INFO
*LIST NOT EXHAUSTIVE
OUTSIDE OF REVIEW SCOPE
ELECTRICAL DESIGN
PCB DESIGN
CIRCUIT DESIGN
WIRING SCHEMATICS
FIRMWARE / SOFTWARE
APP DEVELOPMENT
EMBEDDED SYSTEM DESIGN
RF / ANTENNA DESIGN
BATTERY MANAGEMENT DESIGN
SAFETY CERTIFICATIONS
LEGAL DETERMINATIONS
STRUCTURAL PE CERTS
ARCHITECTURAL REVIEW
MEDICAL DEVICE APPROVAL
FIREARM SAFETY APPROVAL
LIVE-FIRE TEST VALIDATION
PROTOTYPE FABRICATION
FULL NPI CYCLES
SUPPLIER MANAGEMENT
PRODUCTION GUARANTEES
*LIST NOT EXHAUSTIVE
CONFIDENTIALITY AND FAQ
INFORMATION SECURITY
A meaningful Design Review requires an open look at the design, and that often means sharing information that is not public and should not become public. CAD models, engineering drawings, prototype images, specifications, assembly details, design concepts, and supporting documentation may represent months or years of development and significant investment.
That information is treated accordingly. Materials submitted to Tier-1 Engineer are used for the purpose of understanding your project, establishing the review scope, and performing the engineering work you requested. Ownership of your design and intellectual property remains with you.
Project information is not published, shared, repurposed for marketing, or used as portfolio material without your permission. When additional confidentiality requirements exist, NDA requests can also be furnished before sensitive project information is submitted.
The objective is to create an environment where you can provide the technical information necessary for a thorough, useful review without having to wonder how your design, documentation, or project details will be handled afterward.
IP SECURITY OVERVIEW
Ownership of your design stays with you
Files are used only for the requested project
Project information is treated as confidential
Nothing is published without your permission
Access is limited to what the review requires
NDA requests can be addressed before submission
CONFIDENTIALITY IS BUILT INTO EVERY REVIEW
FREQUENTLY ASKED QUESTIONS
Absolutely. The Design Review is available to anyone developing a physical product or mechanical design, regardless of title, education, company size, or professional background. Clients may be experienced engineers, product designers, inventors, startups, makers, or someone developing their first serious product. What matters is that there is enough of a defined design to perform a meaningful review. The findings are communicated in practical terms, with the reasoning and recommended actions explained clearly rather than assuming a particular level of formal training. In fact, every deliverable has an appendix of "Key Terminology" that provides practical definitions to any technical language found in the report.
No. Initial submission and project assessment occur before paid technical review begins. If the project is accepted, the IDAR defines the review scope, assigned Review Level, price, estimated lead time, and any additional information needed before proceeding.
No. The Review Level is assigned during the initial assessment based on the design, documentation, complexity, and expected review effort. This keeps the scope aligned with the actual project rather than requiring you to guess which level you need.
Provide the most complete representation of the current design available. This may include 3D CAD, engineering drawings, PDFs, images, specifications, assembly information, prototypes, and supporting project documentation.
The DRR provides findings and recommended design actions based on the submitted and approved review package. Re-review of revised CAD, new documentation, or substantially changed designs is outside the original review unless specifically included in the approved scope.
The Design Review identifies concerns and provides recommended design actions, but it is not a CAD redesign service unless additional engineering work is specifically scoped. The objective is to show what should change, why it matters, and where attention should be focused. Redesign of the part is not included in the scope of the Design Review, but may be added for an additional fee.
In most cases, yes. You can officially request an NDA in the Project Submission Form, before any documentation is uploaded. Any NDA must be reviewed and accepted before it is considered applicable to the project.
Usually. A design does not have to be production-ready to benefit from a Design Review. However, there must be enough defined geometry, documentation, and design intent to perform a meaningful assessment. Projects that are too early may be better suited for a Concept Review.
Yes. A Design Review can be based on CAD, drawings, prototype information, or an existing physical design when sufficient documentation is available to understand the geometry, function, and design intent.
That's okay. If a process has already been selected, it can be considered during the review. If not, obvious process-direction concerns can still be identified. Selecting or validating the final manufacturing process in depth may require a Concept Review or DFM Audit depending on the maturity of the design.
If the submitted project falls outside the intended scope of the Design Review, you will be informed during the initial assessment before paid technical work begins. Where appropriate, a different Tier-1 Engineer review path may be recommended.
The estimated lead time window is communicated in the IDAR before payment. Actual timing depends on the assigned Review Level, project complexity, documentation completeness, current workload, and client responsiveness when additional information is needed.
Yes. Reasonable clarification of findings is part of project closeout. Additional engineering work, new design evaluation, revised-file review, or expanded analysis may require a separate review or additional scope.
A Concept Review is intended for earlier-stage ideas where the product architecture, geometry, or development direction may still be taking shape. A Design Review is for a more defined design and focuses on whether the design itself makes sense, including geometry, fit, function, interfaces, assembly logic, and obvious design risks. A DFM Audit goes deeper into process-specific manufacturing readiness, including manufacturability, tolerancing, defect risk, tooling complexity, and production concerns.
Drawings are helpful but are not always required. Depending on the project, 3D CAD, images, specifications, prototype information, sketches, or other supporting documentation may provide enough information to begin. Any missing information needed for the full review is identified during the initial assessment.
The initial assessment and IDAR are intended to identify project complexity before the paid review begins. If the submitted project falls significantly outside the expected scope, that is addressed before proceeding. If substantially new conditions emerge later because the project or documentation changes, additional scope may be required.
Not necessarily. A Design Review evaluates the design itself and may identify whether it is ready to advance, but it does not replace detailed process-specific DFM, supplier validation, testing, certification, or production approval. Designs approaching manufacturing release may benefit from a Tier-1 DFM Audit afterward.
WHY TIER-1 ENGINEER
A proper design review takes more than knowing what looks correct in CAD. It takes experience seeing how design decisions affect fit, function, assembly, tooling, suppliers, manufacturing, and the problems that show up once a product moves from active design to reality. Tier-1 Engineer brings that production perspective into every review.
Tier-1 Engineer is built on a foundation of extensive practical design and manufacturing experience developed across Tier-1 automotive and defense environments, with heavy experience in a broad range of manufacturing processes, materials, component types, assemblies, suppliers, and product-development challenges. Every Design Review applies that experience directly to the submitted design, bringing together design intent, manufacturing context, and the downstream realities that often get missed when a part is evaluated only on-screen.
A useful engineering review should do more than hand back a list of problems. Tier-1 Engineer puts equal value on explaining the issue, the reasoning behind it, and the impact it can have downstream. The goal is to give you clear direction while also helping you understand the engineering behind the recommendation. You leave with more than a corrected design. You leave better equipped to make the next design decision yourself.
WHAT THAT MEANS FOR YOUR DESIGN REVIEW
Design decisions are evaluated from a full product lifecycle context
you get Practical engineering judgment and explanations, not simply a checklist
application of Experience across multiple manufacturing processes
Experienced Attention to fit, function, assembly, and downstream impact
Findings ARE prioritized by what matters MOST
Clear reasoning behind recommended design actions
No unnecessary complexity or academic, THEORY-CENTRIC LANGUAGE
START YOUR DESIGN REVIEW
HOW TO GET STARTED
1. Prepare your project information
Gather what is known about the design intent, requirements, use conditions, material, process, production volume, and your concerns.
2. Complete the Project Submission Form
Provide the project details and explain what you want reviewed. Unknown or undecided information can be identified as such.
3. UPLOAD YOUR DESIGN DOCUMENTATION
Submit the CAD, drawings, photos, sketches, notes, specifications, or other files that best represent the current design.
4. Tier-1 Engineer performs initial assessment
The submission is reviewed for project fit, design maturity, documentation completeness, complexity, and expected REVIEW effort.
5. Receive your IDAR
The Initial Design Assessment Report establishes the assigned Review Level, price, estimated lead time, missing information, and next steps.
6. Decide whether to proceed
Review the IDAR and move forward only if the proposed scope and terms make sense for your project.
A Design Review begins with a simple project submission. You provide the current design information and available documentation, Tier-1 Engineer evaluates the project, and you receive a clear review plan before any paid technical work begins.
No payment is required to submit.
Paid technical review begins only after the IDAR is approved and payment is received.
DR