TIER-1 ENGINEER
ENGINEERING AND MANUFACTURING
SIMPLIFIED
WHAT IS A TIER-1 CONCEPT REVIEW?
A Tier-1 Concept Review is a practical, structured engineering review focused on evaluating an early-stage product idea before significant time and money are committed to detailed design, prototypes, or supplier involvement.
The review looks at the concept from a real-world engineering perspective, including intended function, basic feasibility, operating conditions, early design assumptions, preliminary manufacturing direction, and other unknowns.
The goal is to identify weak assumptions, missing requirements, and early design risks, then provide clear direction on what should be defined, tested, changed, or proven before the concept moves deeper into development.
No payment is required to submit. Project fit, scope, price, and lead time are confirmed first.
CR
WHY USE A TIER-1 CONCEPT REVIEW
CONFIRM EARLY ASSUMPTIONS BEFORE THEY SHAPE THE DESIGN
GET EXPERIENCED INPUT BEFORE INVESTING IN DETAILED CAD
IDENTIFY MAJOR UNKNOWNS THAT NEED TO BE RESOLVED
CHECK WHETHER THE CONCEPT APPEARS PRACTICALLY FEASIBLE
DEFINE WHAT SHOULD BE PROTOTYPED, TESTED, OR REFINED NEXT
MOVE INTO DESIGN DEVELOPMENT WITH CLEARER TECHNICAL DIRECTION
CORE OBJECTIVES
COMMON APPLICATIONS
INDEPENDENT INVENTORS
Clarify an early idea before investing heavily in design or prototypes.
GARAGE PROTOTYPERS
Check whether the concept makes practical sense before the next build.
SERIOUS MAKERS
Identify weak assumptions, unknowns, and development risks early.
PRODUCT STARTUPS
Reduce uncertainty before committing resources to detailed product development.
MECHANICAL ENGINEERS
Get external EYES on feasibility, function, and early design direction.
PRODUCT DESIGNERS
test the concept before committing to detailed geometry and refinement.
OEM ENGINEERING TEAMS
Review early concepts before prototype, internal release, or supplier involvement.
SMALL BUSINESSES
Get practical engineering direction without dedicated internal resources.
WHAT YOU GET
INITIAL CONCEPT ASSESSMENT REPORT
The Initial Concept Assessment Report (ICAR) establishes the starting point for a Tier-1 Concept Review before paid review begins.
It organizes the submitted concept, intended purpose, available supporting information, current development condition, known requirements, major unknowns, and any information still needed to perform a useful Concept Review.
The ICAR gives the client a clear picture of how Tier-1 Engineer understands the idea before deeper evaluation begins. It confirms whether the concept is ready for review, defines what will be evaluated, establishes the review scope, price, and estimated lead time, and identifies anything that should be clarified before moving forward.
THE ICAR ESTABLISHES:
THE CURRENT CONDITION AND DEFINITION OF THE SUBMITTED CONCEPT
THE STATED PURPOSE, FUNCTION, AND INTENDED USE
AN ORGANIZED SUMMARY OF THE AVAILABLE CONCEPT INFORMATION
KNOWN REQUIREMENTS, ASSUMPTIONS, AND MAJOR UNKNOWNS
WHETHER THE CONCEPT IS READY FOR MEANINGFUL REVIEW
A CLEARLY DEFINED SCOPE FOR THE CONCEPT REVIEW
THE PRICE AND ESTIMATED LEAD TIME BEFORE WORK BEGINS
ANY MISSING INFORMATION NEEDED TO SUPPORT THE REVIEW
A CLEAR PATH TO INITIATE THE PAID CONCEPT REVIEW
The ICAR gives both parties a shared understanding of the concept, identifies what is known and still uncertain, and establishes the scope, timing, cost, and next steps before the Concept Review begins.
CONCEPT REVIEW REPORT
The Concept Review Report (CRR) is the final deliverable of a Tier-1 Concept Review and contains the detailed engineering evaluation developed from the approved concept scope.
It evaluates concept alignment, practical feasibility, prototype readiness, early design concerns, and concept-level manufacturability risks while identifying the assumptions, requirements, and unknowns that should be addressed before deeper development.
The CRR is intended to turn an early idea into a clearer development path. It identifies what appears workable, what needs attention, what should be proven through prototyping or testing, and which actions should come next before committing additional time and resources to detailed design. The CRR goes beyond generic concept feedback by combining feasibility, prototype-readiness, design and manufacturability findings, and a staged prototype/testing plan.
THE CRR PROVIDES:
A CLEAR ASSESSMENT OF OVERALL CONCEPT FEASIBILITY
EVALUATION OF CONCEPT ALIGNMENT AND INTENDED FUNCTION
IDENTIFICATION OF EARLY DESIGN CONCERNS AND WEAK ASSUMPTIONS
CONCEPT-LEVEL MANUFACTURABILITY OBSERVATIONS
A DETERMINATION OF PROTOTYPE READINESS
PRIORITIZED CONCEPT FINDINGS AND RISK AREAS
PRACTICAL RECOMMENDATIONS FOR CONCEPT REFINEMENT
PROTOTYPE METHODS, TESTING DIRECTION, AND LEARNING GOALS
A CLEAR DEVELOPMENT PATH AND RECOMMENDED NEXT STEPS
The CRR gives the client a structured evaluation of the concept itself, showing what appears viable, what still needs to be resolved, and what should be learned or changed before moving into detailed design.
REVIEW SCOPE AND PRICING
WHAT DOES A CONCEPT REVIEW COVER?
A Tier-1 Concept Review uses one defined review scope rather than multiple Review Levels. The service is intended for early-stage concepts where the primary need is to evaluate feasibility, function, development direction, major unknowns, and what should be proven before detailed design begins.
The same core Concept Review process and deliverables apply to every accepted project. The ICAR establishes the approved review scope before paid work begins, and the CRR documents the completed concept evaluation and recommended next steps.
If a submission is too broad, too mature, or requires analysis beyond the intended Concept Review scope, Tier-1 Engineer may narrow the review, request clarification, or recommend a Design Review or DFM Audit instead.
If the submitted project requires substantially more detailed design or manufacturing analysis, Tier-1 Engineer will identify that during the initial assessment before paid review begins.
CONCEPT REVIEW SCOPE DRIVERS
CONCEPT DEFINITION
NUMBER OF COMPONENTS OR FUNCTIONS
CLARITY OF DESIGN INTENT
NUMBER OF MAJOR UNKNOWNS
AVAILABLE SUPPORTING INFORMATION
FUNCTIONAL COMPLEXITY
PROTOTYPE / TESTING QUESTIONS
OVERALL CONCEPT REVIEW EFFORT
THE CONCEPT REVIEW IS INTENDED TO PROVIDE A CLEAR, ACCESSIBLE ENGINEERING CHECKPOINT WITHOUT REQUIRING THE CLIENT TO SELECT FROM MULTIPLE SERVICE TIERS.
Concept Reviews use a starting price rather than fixed Review Levels. The listed price applies to typical early-stage concepts with a manageable scope, limited complexity, and enough information to support a focused engineering review.
Larger assemblies, broader concepts, extensive documentation, or projects requiring substantially more engineering effort may be priced above the starting rate. Final scope, price, and lead time are established during the initial concept assessment and presented in the ICAR before any paid review begins.
Initial concept assessment (ICAR)
FULL Concept Review REPORT (CRR)
Findings and explanations
FUNCTIONALITY ASSESSMENT
RECOMMENDED TESTING OUTLINE
RECOMMENDED PROTOTYPE METHOD
Recommended next steps
HOW CONCEPT REVIEW PRICING WORKS
WHAT'S INCLUDED
CONCEPT REVIEW
TYPICAL PROJECT CHARACTERISTICS
ROUGH CONCEPTS
EARLY CAD
SKETCHES
PROTOTYPES
REVIEW SCOPE FACTORS
COMPLEXITY
ASSEMBLY SIZE
INFORMATION CLARITY
DESIGN INTENT CLARITY
TYPICAL LEAD TIME
3-5
BUSINESS DAYS
STARTING AT:
$199
Product ideas
Hand sketches
Early CAD
Rough prototypes
Early development questions
Existing-product concepts
Concepts needing direction
TYPICAL PROJECTS
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
Concept Reviews use a starting price rather than fixed Review Levels. The listed price applies to typical early-stage concepts with a manageable scope, limited complexity, and enough information to support a focused engineering review.
Larger assemblies, broader concepts, extensive documentation, or projects requiring substantially more engineering effort may be priced above the starting rate. Final price and lead time are established during the initial assessment and presented in the ICAR before any paid review begins.
Initial concept assessment (ICAR)
Full Concept Review REPORT (CRR)
Findings and explanations
FUNCIONALITY ASSESSMENT
RECOMMENDED TESTING OUTLINE
RECOMMENDED PROTOTYPE METHODS
RECOMMENDED NEXT STEPS
HOW CONCEPT REVIEW PRICING WORKS
WHAT'S
INCLUDED
CONCEPT REVIEW
TYPICAL PROJECT CHARACTERISTICS
ROUGH CONCEPTS
EARLY CAD
SKETCHES
PROTOTYPES
REVIEW SCOPE FACTORS
COMPLEXITY
ASSEMBLY SIZE
INFORMATION CLARITY
DESIGN INTENT CLARITY
TYPICAL LEAD TIME
3-5
BUSINESS DAYS
$199
STARTING AT:
Product ideas
Hand sketches
Early CAD
Rough prototypes
Early development questions
Existing-product concepts
Concepts needing direction
TYPICAL PROJECTS
HOW IT WORKS
THE FOUR-PHASE SYSTEM
The Tier-1 Concept Review process uses a structured four-phase system to keep the review clear, predictable, and controlled from initial concept submission through final report delivery.
Before paid review begins, the submitted concept is screened for project fit, available information, concept definition, and overall review scope. This helps identify missing context, clarify expectations, and establish the price and lead time before the review starts.
Each phase has a defined purpose and gives the client a clear checkpoint before committing to the full Concept Review. It also keeps the review focused on the submitted concept, stated goals, known requirements, and approved review scope.
The result is a straightforward concept evaluation process with clear boundaries, useful engineering feedback, and practical development direction delivered through the CRR.
PHASE SYSTEM ADVANTAGES
STRUCTURE PROVIDES CLARITY AND CLEAR RESPONISBILITIES
PROJECT FIT IS CONFIRMED BEFORE PAYMENT
PRICE AND LEAD TIME ARE DEFINED UP FRONT
MISSING OR UNCLEAR INFORMATION IS IDENTIFIED EARLY
CLEAR DELIVERABLES AND NEXT STEPS ARE ESTABLISHED
PAID REVIEW BEGINS ONLY AFTER CLIENT APPROVAL OF ICAR
PROVIDES A STREAMLINED, LOW STRESS CLIENT EXPERIENCE
CONCEPT REVIEW PHASES
WHAT YOU DO:
Gather the available concept information, complete the Concept Review Project Submission Form, upload supporting material, and submit the project.
WHAT YOU DO:
Wait for confirmation of project fit and ICAR delivery. Review the proposed price and lead time, then approve and pay to begin the Concept Review.
WHAT YOU DO:
Wait for Tier-1 Engineer to complete the Review of the approved submission and develop the findings, ACTIONS, and next-step guidance in the CRR.
WHAT YOU DO:
You receive the CRR with concept findings, prototype & testing direction, and recommended ACTIONS. The review closes.
WHAT YOU DO:
Gather the available concept information, complete the Concept Review Project Submission Form, upload supporting material, and submit the project.
WHAT YOU DO:
Wait for confirmation of project fit and ICAR delivery. Review the proposed scope, price, and lead time, then approve and pay to begin the Concept Review.
WHAT YOU DO:
Wait for Tier-1 Engineer to complete the structured Concept Review of the approved submission and develop the findings, recommendations, and next-step guidance in the CRR.
WHAT YOU DO:
You receive the CRR with concept findings, engineering explanations, prototype or testing direction, and recommended next steps. The review closes.
HOW TO BEGIN
GUIDED SUBMISSION METHOD
Starting a Concept Review does not require a finished design, formal engineering package, or every technical decision already defined. The goal is to provide enough information to understand what the concept is intended to accomplish, who or what it is for, how you currently expect it to work, and what questions or uncertainties still need to be resolved.
The steps below are designed to help organize that information before submission. Each section explains what is useful to provide, what the terminology means, and the level of detail that can help the review. If something is unknown, undecided, or only a rough assumption, that is completely acceptable. Simply provide what is currently known.
A well-prepared submission helps Tier-1 Engineer understand the concept faster, identify important unknowns early, and establish an appropriate review scope before paid work begins.
THE PROJECT SUBMISSION FORM
The Concept Review Project Submission Form provides the context needed to understand the idea before the review begins. Sketches, CAD, photos, or prototypes can show what currently exists, but they do not always explain the problem being solved, intended function, user needs, known constraints, or other questions.
Providing as much relevant detail as possible helps reduce assumptions, identify missing information early, clarify what you want evaluated, and establish an accurate review.
You do not need to have every answer. If something is unknown, undecided, or still being explored, simply say so. A clear and honest submission gives the Concept Review the best possible starting point.
EXPLORE THE STEPS BELOW TO PREPARE FOR A TIER-1 CONCEPT REVIEW SUBMISSION
This establishes why the concept exists and what it must accomplish. It includes the problem being solved, the primary function of the proposed product, and the practical performance requirements that define what a successful concept needs to do.
PROBLEM BEING SOLVED
WHAT PROBLEM OR NEED IS THE CONCEPT INTENDED TO ADDRESS?
The problem being solved describes the real-world need that led to the concept in the first place. It explains what condition, inconvenience, limitation, or opportunity the product is intended to improve. Defining the problem helps keep the Concept Review focused on whether the proposed idea actually addresses the reason it exists.
EXAMPLES
-
Keep an object securely positioned
-
Reduce unwanted movement
-
Protect a component from damage
-
Improve access or usability
-
Simplify an existing task
-
Replace a complicated existing solution
A clear problem statement helps prevent the concept from becoming a solution in search of a problem.
PRIMARY FUNCTION
WHAT IS THE MAIN JOB THE CONCEPT MUST PERFORM?
The primary function is the most important action or result the product must provide to solve the stated problem. It describes what the concept actually needs to do when used as intended. A product may eventually perform several functions, but identifying the primary one helps establish what must work before secondary features or refinements are considered.
EXAMPLES
-
Retain or support an object
-
Connect two components
-
Guide or control movement
-
Protect an internal assembly
-
Position something accurately
-
Allow controlled opening or release
-
Provide adjustment or retention
If the concept cannot reliably perform its primary function, secondary features have limited value.
PERFORMANCE REQUIREMENTS
WHAT MUST THE CONCEPT WITHSTAND OR ACHIEVE?
Performance requirements describe the conditions the concept must satisfy while performing its intended function. These may involve loads, forces, movement, fit, durability, operating life, or other measurable expectations. They help turn a general idea into requirements that can eventually be evaluated through design and prototype testing.
EXAMPLES
-
Expected loads or forces
-
Required holding or release force
-
Fit range
-
Movement or travel
-
Required stiffness or flexibility
-
Expected operating cycles
-
Impact or rough-use resistance
-
Required accuracy or positioning
-
Noise limitations
-
Durability expectations
Exact values are helpful when known, but early estimates or desired behavior are completely acceptable.
-
This establishes the real-world application of the concept. It includes the use environment, how the user will interact with the product, and what people, objects, equipment, or surfaces the concept must fit or interface with during normal use.
USE ENVIRONMENT
UNDER WHAT CONDITIONS WILL THE PRODUCT BE USED?
The use environment is the physical setting and operating conditions the concept is expected to encounter during normal use, storage, transportation, or field activity. This may include temperature, moisture, dirt, abrasion, sunlight, vibration, impact, chemicals, or other environmental conditions that could affect function, durability, comfort, or material direction.
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 chemicals
-
Salt or corrosive environments
-
Continuous vibration
-
Shock or impact
-
Rough field use
A simple description is acceptable. For example: “Used outdoors during hiking, rain, dirt, and rough handling.”
USER INTERACTION
HOW WILL THE USER OPERATE, ADJUST, OR HANDLE THE PRODUCT?
User interaction describes how a person is expected to physically engage with the concept during normal use. This may include holding, wearing, inserting, removing, adjusting, carrying, opening, releasing, or repositioning the product. Understanding these interactions helps identify usability concerns, awkward motions, access issues, and conditions that should be evaluated during prototyping.
EXAMPLES
-
Held or carried by hand
-
Worn on the body
-
Inserted or removed repeatedly
-
Opened or closed during use
-
Adjusted by the user
-
Operated while wearing gloves
-
Used with one hand
-
Accessed while moving
-
Serviced or repositioned
-
Exposed to repeated handling
Describe how the product will actually be used, even if the interaction is still only an early assumption.
FIT & INTERFACE REQUIREMENTS
WHAT DOES THE CONCEPT NEED TO FIT, CONTACT, OR INTERACT WITH?
Fit and interface requirements describe the people, components, equipment, surfaces, or objects the concept must physically work with. This includes size ranges, contact areas, mating conditions, clearances, attachment points, and other relationships that may determine whether the concept can function successfully across its intended use range.
EXAMPLES
-
Existing mating components
-
User size or body-fit range
-
Equipment size variations
-
Mounting locations
-
Contact surfaces
-
Required clearances
-
Retained objects
-
Attachment points
-
Moving interfaces
-
Alignment requirements
-
Multiple product sizes or variants
If the concept must work across a range of users, parts, or equipment sizes, identify that range as clearly as possible.
-
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.
EXPECTED PROCESS
HOW DO YOU CURRENTLY EXPECT THE PRODUCT MAY BE MADE?
The expected process is the manufacturing method currently being considered for the product or its major components. At the concept stage, this may be little more than an early assumption. Understanding the likely process helps identify obvious conflicts between the concept and the way the product may eventually need to be produced.
EXAMPLES
-
Injection molding
-
CNC machining
-
Die casting
-
Sheet metal forming
-
Extrusion
-
Additive manufacturing
-
Fabrication and welding
-
Casting
-
Off-the-shelf components
-
Combination of processes
If no process has been considered yet, simply identify it as not yet determined.
MATERIAL DIRECTION
WHAT MATERIALS ARE CURRENTLY BEING CONSIDERED?
Material direction describes any material, material family, or general material characteristics currently being considered for the concept. A specific grade is not required. Even broad assumptions such as plastic, aluminum, steel, rubber, or flexible polymer can provide useful context when evaluating feasibility and early design direction.
EXAMPLES
-
Aluminum
-
Carbon steel
-
Stainless steel
-
ABS
-
Nylon
-
Polycarbonate
-
Polypropylene
-
Rubber or elastomer
-
Reinforced plastic
-
Composite material
-
Material not yet selected
If several materials are being considered, include the options and any reason one may be preferred.
EST. PRODUCTION VOLUME
Approximately how many parts do you expect to PRODUCE?
Estimated production volume is the rough quantity the concept may eventually need to support if development is successful. At this stage, an exact forecast is not expected. A general range helps provide context for prototype strategy, manufacturing direction, design complexity, and whether the concept could reasonably scale beyond early development.
EXAMPLES
-
One proof-of-concept prototype
-
A handful of development units
-
Fewer than 100 units
-
Hundreds per year
-
Thousands per year
-
Tens of thousands per year
-
High-volume production
-
Volume not yet known
A rough estimate is enough. If future demand is completely unknown, simply state that production volume has not yet been established.
-
WHAT WOULD YOU LIKE THE CONCEPT REVIEW TO HELP YOU UNDERSTAND, CHALLENGE, OR CLARIFY?
Your questions and concerns identify the areas of the concept where you want additional engineering attention. These may be uncertainties, assumptions you want challenged, functions you are unsure about, decisions that have not yet been made, or simply areas where you do not know what the next step should be.
You do not need to diagnose the issue yourself or describe it using engineering terminology. Explain what you are trying to accomplish, what you are unsure about, or what has been difficult to work through so far. These concerns provide useful context and help Tier-1 Engineer understand where the Concept Review can provide the most value, such as:
-
“I am not sure whether this idea will work the way I expect.”
-
“I do not know the best way to make this mechanism function.”
-
“I am unsure whether this concept is too complicated.”
-
“I want to know what I should prototype first.”
-
“I am not sure what material or process makes sense yet.”
-
“I want to identify the biggest weaknesses before I spend more money.”
-
“I do not know whether this feature is actually necessary.”
-
“I am unsure how the product should attach, move, or adjust.”
-
“I have several possible directions and do not know which one to pursue.”
-
“I want to know what assumptions need to be proven before detailed design.”
-
“I do not have a specific concern. I want an experienced engineering review of the overall concept.”
NOT SURE WHAT TO ASK?
That is completely acceptable. A Concept Review does not require you to already know what the important engineering questions are. If your goal is simply to have the idea evaluated before committing more time, money, or design effort, state that in the submission. The review is intended to help identify the questions, risks, and unknowns that should be addressed next.
-
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 Concept Review begins.
You do not need a complete professional engineering package to submit. A rough CAD model, a prototype, photographs, sketches, or other supporting information may be enough to begin depending on the project.
Concept submission is the starting point for the Tier-1 Concept Review process. You will complete the Concept Review submission form, provide the information outlined in the previous steps, and upload the most relevant concept materials currently available.
Submission does not begin the paid Concept Review. It gives Tier-1 Engineer the information needed to understand the idea, confirm that it is a good fit for the service, and establish the scope and engineering effort expected to complete the review properly.
DURING INITIAL ASSESSMENT, TIER-1 ENGINEER WILL:
CONFIRM THAT THE PROJECT FALLS WITHIN THE CONCEPT REVIEW SCOPE
REVIEW THE SUBMITTED CONCEPT INFORMATION AND SUPPORTING MATERIAL
EVALUATE THE CURRENT DEFINITION AND COMPLEXITY OF THE CONCEPT
IDENTIFY MISSING OR UNCLEAR INFORMATION THAT MAY BE NEEDED
ESTABLISH THE REVIEW SCOPE, PRICE, AND ESTIMATED LEAD TIME
PREPARE THE INITIAL CONCEPT ASSESSMENT REPORT (ICAR)
WHAT HAPPENS NEXT?
If the project is accepted, you will receive the ICAR documenting the initial assessment, review scope, price, estimated lead time, and any additional information required before the technical Concept Review begins.
You can review the ICAR before deciding whether to proceed. No paid Concept Review work begins until the ICAR is approved and payment is received.
If the concept is not yet ready for review, additional information may be requested or a more appropriate Tier-1 Design Readiness service may be recommended.
HOW TO BEGIN
GUIDED SUBMISSION METHOD
Starting a Concept Review does not require a finished design, formal engineering package, or every technical decision already defined. The goal is to provide enough information to understand what the concept is intended to accomplish, who or what it is for, how you currently expect it to work, and what questions still need to be resolved.
The steps below are designed to help organize that information before submission. Each section explains what is useful to provide, what the terminology means, and the level of detail that can help the review. If something is unknown, undecided, or only a rough assumption, that is completely acceptable. Simply provide what is currently known.
A well-prepared submission helps Tier-1 Engineer understand the concept faster, identify important unknowns, and establish an understanding before work begins.
THE PROJECT SUBMISSION FORM
The Concept Review Project Submission Form provides the context needed to understand the idea before the technical review begins. Sketches, CAD, photos, or prototypes can show what currently exists, but they do not always explain the problem being solved, intended function, user needs, known constraints, or questions behind the concept.
Providing as much relevant detail as possible helps reduce assumptions, identify missing information early, clarify what you want evaluated, and establish an accurate review scope.
You do not need to have every answer. If something is unknown, undecided, or still being explored, simply say so. A clear and honest submission gives the Concept Review the best possible starting point.
EXPLORE THE STEPS BELOW TO PREPARE FOR A TIER-1 CONCEPT REVIEW SUBMISSION
This establishes why the concept exists and what it must accomplish. It includes the problem being solved, the primary function of the proposed product, and the practical performance requirements that define what a successful concept needs to do.
PROBLEM BEING SOLVED
WHAT PROBLEM OR NEED IS THE CONCEPT INTENDED TO ADDRESS?
The problem being solved describes the real-world need that led to the concept in the first place. It explains what condition, inconvenience, limitation, or opportunity the product is intended to improve. Defining the problem helps keep the Concept Review focused on whether the proposed idea actually addresses the reason it exists.
EXAMPLES
-
Keep an object securely positioned
-
Reduce unwanted movement
-
Protect a component from damage
-
Improve access or usability
-
Simplify an existing task
-
Replace a complicated existing solution
A clear problem statement helps prevent the concept from becoming a solution in search of a problem.
PRIMARY FUNCTION
WHAT IS THE MAIN JOB THE CONCEPT MUST PERFORM?
The primary function is the most important action or result the product must provide to solve the stated problem. It describes what the concept actually needs to do when used as intended. A product may eventually perform several functions, but identifying the primary one helps establish what must work before secondary features or refinements are considered.
EXAMPLES
-
Retain or support an object
-
Connect two components
-
Guide or control movement
-
Protect an internal assembly
-
Position something accurately
-
Allow controlled opening or release
-
Provide adjustment or retention
If the concept cannot reliably perform its primary function, secondary features have limited value.
PERFORMANCE REQUIREMENTS
WHAT MUST THE CONCEPT WITHSTAND OR ACHIEVE?
Performance requirements describe the practical conditions the concept must satisfy while performing its intended function. These may involve loads, forces, movement, fit, durability, operating life, or other measurable expectations. They help turn a general idea into requirements that can eventually be evaluated through design and prototype testing.
EXAMPLES
-
Expected loads or forces
-
Required holding or release force
-
Fit range
-
Movement or travel
-
Required stiffness or flexibility
-
Expected operating cycles
-
Impact or rough-use resistance
-
Required accuracy or positioning
-
Noise limitations
-
Durability expectations
Exact values are helpful when known, but early estimates or desired behavior are completely acceptable.
-
This establishes the real-world application of the concept. It includes the use environment, how the user will interact with the product, and what people, objects, equipment, or surfaces the concept must fit or interface with during normal 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.
FIT & INTERFACE REQUIREMENTS
WHAT DOES THE CONCEPT NEED TO FIT, CONTACT, OR INTERACT WITH?
Fit and interface requirements describe the people, components, equipment, surfaces, or objects the concept must physically work with. This includes size ranges, contact areas, mating conditions, clearances, attachment points, and other relationships that may determine whether the concept can function successfully across its intended use range.
EXAMPLES
-
Existing mating components
-
User size or body-fit range
-
Mounting locations
-
Contact surfaces
-
Required clearances
-
Attachment points
-
Moving interfaces
-
Alignment requirements
-
Multiple product sizes or variants
If the concept must work across a range of users, parts, or equipment sizes, identify that range as clearly as possible.
USER INTERACTION
HOW WILL THE USER HOLD OR OPERATE THE PRODUCT?
User interaction describes how a person is expected to physically engage with the concept during normal use. This may include holding, wearing, inserting, removing, adjusting, carrying, opening, releasing, or repositioning the product. Understanding these interactions helps identify usability concerns, awkward motions, access issues, and conditions that should be evaluated during prototyping.
EXAMPLES
-
Held or carried by hand
-
Worn on the body
-
Inserted or removed repeatedly
-
Opened or closed during use
-
Adjusted by the user
-
Operated while wearing gloves
-
Used with one hand
-
Accessed while moving
-
Serviced or repositioned
-
Exposed to repeated handling
Describe how the product will actually be used, even if the interaction is still only an early assumption.
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 chemicals
-
Salt or corrosive environments
-
Continuous vibration
-
Shock or impact
-
Rough field use
A simple description is acceptable. For example: “Used outdoors during hiking, rain, dirt, and rough handling.”
-
A Concept Review does not require the manufacturing process, material, or production volume to already be finalized. However, any current assumptions about how the product may eventually be produced are useful for evaluating feasibility, early manufacturability, prototype direction, and whether the concept is developing toward a practical production path.
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.”
EXPECTED PROCESS
HOW DO YOU CURRENTLY EXPECT THE PRODUCT MAY BE MADE?
The expected process is the manufacturing method currently being considered for the product or its major components. At the concept stage, this may be little more than an early assumption. Understanding the likely process helps identify obvious conflicts between the concept and the way the product may eventually need to be produced.
EXAMPLES
-
Injection molding
-
CNC machining
-
Die casting
-
Sheet metal forming
-
Extrusion
-
Additive manufacturing
-
Fabrication and welding
-
Casting
-
Off-the-shelf components
-
Combination of processes
If no process has been considered yet, simply identify it as not yet determined.
MATERIAL DIRECTION
WHAT MATERIALS ARE CURRENTLY BEING CONSIDERED?
Material direction describes any material, material family, or general material characteristics currently being considered for the concept. A specific grade is not required. Even broad assumptions such as plastic, aluminum, steel, rubber, or flexible polymer can provide useful context when evaluating feasibility and early design direction.
EXAMPLES
-
Aluminum
-
Carbon steel
-
Stainless steel
-
ABS
-
Nylon
-
Polycarbonate
-
Polypropylene
-
Rubber or elastomer
-
Reinforced plastic
-
Composite material
-
Material not yet selected
If several materials are being considered, include the options and any reason one may be preferred.
EST. PRODUCTION VOLUME
APPROXIMATELY HOW MANY PRODUCTS MIGHT EVENTUALLY BE NEEDED?
Expected production volume is the rough quantity the concept may eventually need to support if development is successful. At this stage, an exact forecast is not expected. A general range helps provide context for prototype strategy, manufacturing direction, design complexity, and whether the concept could reasonably scale beyond early development.
EXAMPLES
-
One proof-of-concept prototype
-
A handful of development units
-
Fewer than 100 units
-
Hundreds per year
-
Thousands per year
-
Tens of thousands per year
-
High-volume production
-
Volume not yet known
A rough estimate is enough. If future demand is completely unknown, simply state that production volume has not yet been established.
-
WHAT WOULD YOU LIKE THE CONCEPT REVIEW TO HELP YOU UNDERSTAND, CHALLENGE, OR CLARIFY?
Your questions and concerns identify the areas of the concept where you want additional engineering attention. These may be uncertainties, assumptions you want challenged, functions you are unsure about, decisions that have not yet been made, or simply areas where you do not know what the next step should be.
You do not need to diagnose the issue yourself or describe it using engineering terminology. Explain what you are trying to accomplish, what you are unsure about, or what has been difficult to work through so far. These concerns provide useful context and help Tier-1 Engineer understand where the Concept Review can provide the most value, such as:
-
“I am not sure whether this idea will work the way I expect.”
-
“I do not know the best way to make this mechanism function.”
-
“I am unsure whether this concept is too complicated.”
-
“I want to know what I should prototype first.”
-
“I am not sure what material or process makes sense yet.”
-
“I want to identify the biggest weaknesses before I spend more money.”
-
“I do not know whether this feature is actually necessary.”
-
“I am unsure how the product should attach, move, or adjust.”
-
“I have several possible directions and do not know which one to pursue.”
-
“I want to know what assumptions need to be proven before detailed design.”
-
“I do not have a specific concern. I want an experienced engineering review of the overall concept.”
NOT SURE WHAT TO ASK?
That is completely acceptable. A Concept Review does not require you to already know what the important engineering questions are. If your goal is simply to have the idea evaluated before committing more time, money, or design effort, state that in the submission. The review is intended to help identify the questions, risks, and unknowns that should be addressed next.
-
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 Concept Review begins.
You do not need a complete professional engineering package to submit. A rough 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
Concept submission is the starting point for the Tier-1 Concept Review process. You will complete the Concept Review submission form, provide the information outlined in the previous steps, and upload the most relevant concept materials currently available.
Submission does not begin the paid Concept Review. It gives Tier-1 Engineer the information needed to understand the idea, confirm that it is a good fit for the service, and establish the scope and engineering effort expected to complete the review properly.
DURING INITIAL ASSESSMENT, TIER-1 ENGINEER WILL:
CONFIRM THAT THE PROJECT FALLS WITHIN THE CONCEPT REVIEW SCOPE
REVIEW THE SUBMITTED CONCEPT INFORMATION AND SUPPORTING MATERIAL
EVALUATE THE CURRENT DEFINITION AND COMPLEXITY OF THE CONCEPT
Identify missing or unclear information that may be needed
ESTABLISH THE REVIEW SCOPE, PRICE, AND ESTIMATED LEAD TIME
PREPARE THE INITIAL CONCEPT ASSESSMENT REPORT (ICAR)
If the project is accepted, you will receive the ICAR documenting the initial assessment, review scope, price, estimated lead time, and any additional information required before the technical Concept Review begins.
You can review the ICAR before deciding whether to proceed. No paid Concept Review work begins until the ICAR is approved and payment is received.
If the concept is not yet ready for review, additional information may be requested or a more appropriate Tier-1 Design Readiness service may be recommended.
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.
CONCEPT REVIEW
STRUCTURED ENGINEERING GUIDANCE FOR EARLY PRODUCT CONCEPTS
-EVALUATE YOUR IDEA BEFORE DETAILED DESIGN-
TIER-1
SUBMISSION AND REVIEW BOUNDARIES
Tier-1 Concept Reviews are focused on early-stage physical product ideas, mechanical concepts, and developing product designs that need practical engineering direction before detailed design, prototyping, or manufacturing commitment.
A concept does not need to be fully defined to be reviewable. Submitted projects are screened before paid work begins to confirm that there is enough information to understand the intended purpose, basic function, current development direction, and the questions the client wants help resolving.
Projects that are extremely broad, highly regulated, safety-critical, or outside the intended mechanical product-development scope may require clarification, a narrower review scope, or a different review path before proceeding.
ACCEPTABLE PROJECTS
PRODUCT IDEAS
ROUGH CONCEPTS
HAND SKETCHES
EARLY CAD
EARLY PROTOTYPES
MECHANICAL PART CONCEPTS
MECHANISM CONCEPTS
PRODUCT ENCLOSURES
BRACKETS / MOUNTS
SIMPLE ASSEMBLIES
PRODUCT IMPROVEMENT IDEAS
EARLY PRODUCT REDESIGNS
PROTOTYPE CONCEPTS
*LIST NOT EXHAUSTIVE
MAY REQUIRE CLARIFICATION
LIMITED PROJECT INFO
NO DEFINED DESIGN INTENT
LARGE/COMPLEX ASSEMBLIES
UNKNOWN REQUIREMENTS
SAFETY-CRITICAL CONCEPTS
REGULATED PRODUCTS
UNPROVEN TECHNOLOGY
MULTIPLE PRODUCT VARIANTS
CONFLICTING REQUIREMENTS
*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 Concept 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
Yes. Concept Review is specifically intended to be accessible to inventors, makers, startups, product developers, engineers, and anyone working through a physical product idea. You do not need an engineering degree, professional title, or experience with formal product development.
No. Submission and initial assessment occur before paid review begins. If the concept is accepted, the ICAR establishes the approved scope, final price, estimated lead time, and any additional information needed before you decide whether to proceed.
Concept Reviews begin at the listed starting price for projects that fall within a typical review scope. Larger assemblies, broader concepts, extensive documentation, or projects requiring substantially greater engineering effort may cost more. Final pricing and lead time are established in the ICAR before payment.
Submit whatever best communicates the idea in its current state. This may include sketches, written descriptions, rough CAD, complete CAD, photos, prototype images, requirements, reference material, existing products, notes, or other information that helps explain what you are trying to accomplish.
The CRR provides findings, recommendations, and development direction based on the concept submitted for review. Review of substantially revised concepts, new configurations, additional concepts, or later design iterations is not automatically included and may require a separate review.
No. Concept Review is an engineering evaluation and guidance service, not a full product-development or CAD-design service. The review helps identify what should be clarified, changed, tested, or developed next, but Tier-1 Engineer does not take ownership of completing the design for you.
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.
Very early. A finished CAD model or prototype is not required. A concept may be reviewable from sketches, written descriptions, reference images, rough models, or other early development information, provided there is enough detail to understand the problem, intended function, and general concept direction.
Yes. Concept Review can also be used to evaluate an early prototype, explore a new direction for an existing product, or reconsider a product concept before additional design work is performed.
That is completely acceptable. Concept Review occurs early enough that these decisions may still be open. Current assumptions can be provided when available, and obvious material or manufacturing-direction considerations may be identified as part of the review.
You will be informed during the initial assessment before paid work begins. Tier-1 Engineer may request clarification, narrow the proposed review scope, recommend a Design Review or DFM Audit, or decline projects that fall outside the intended Concept Review boundaries.
Typical Concept Reviews are expected to fall within the published lead-time range. Larger or unusually complex projects may require additional time. The actual estimated lead time is established in the ICAR before payment.
Yes. Reasonable clarification of findings and recommendations is part of review closeout. New concept evaluation, revised designs, additional analysis, or expanded development questions may require additional scope.
A Concept Review evaluates the idea, feasibility, major assumptions, early risks, and development direction. A Design Review evaluates a more defined design, including geometry, fit, function, interfaces, and assembly. A DFM Audit evaluates the design against the realities of the intended manufacturing process.
Put simply: Concept Review evaluates the product direction. Design Review evaluates the design. DFM Audit evaluates the manufacturability of the design.
No. Sketches, descriptions, photographs, rough models, or prototypes may be enough for a Concept Review. CAD and drawings are useful when available, but requiring them would defeat the purpose of an early-stage engineering review.
The initial assessment is intended to identify this before paid review begins. If the concept includes a large assembly, several interacting systems, multiple product variants, or substantially more engineering effort than a typical Concept Review, the scope, price, and lead time may be adjusted in the ICAR.
Not automatically. The purpose of the Concept Review is to determine what appears viable, identify unresolved risks and assumptions, and establish what should happen next. The CRR may recommend proceeding, refining the concept, proving specific functions through testing, developing an early prototype, or resolving additional questions before detailed design begins.
I especially like #8 and #15 for this page. Those two make it immediately clear that Concept Review is the service where someone can show up with an idea that is still rough, rather than feeling like they need to engineer half the product before they're qualified to ask for help.
WHY TIER-1 ENGINEER
Early product development is often less about having every answer and more about knowing which questions need to be asked. A useful Concept Review takes experience recognizing weak assumptions, conflicting requirements, unnecessary complexity, and development paths that may create problems long before the design is mature enough for detailed engineering.
Tier-1 Engineer brings broad practical experience across design, manufacturing, product development, suppliers, and production environments into the earliest stages of a project. That perspective helps evaluate a concept beyond how it looks on paper, considering function, feasibility, usability, manufacturability, development risk, and what will eventually be required to turn the idea into a real product.
Tier-1 Concept Reviews don't simply hand you a list of good / no good items. Tier-1 Engineer places value on explaining the reasoning behind each finding, identifying what remains uncertain, and defining what should be proven next. The goal is to leave you with a clearer concept, better questions, and a practical path into the next stage of development.
WHAT THAT MEANS FOR YOUR CONCEPT REVIEW
EARLY ASSUMPTIONS ARE CHALLENGED BEFORE THEY BECOME DESIGN COMMITMENTS
THE CONCEPT IS EVALUATED FROM BOTH DESIGN AND MANUFACTURING PERSPECTIVES
PRACTICAL ENGINEERING JUDGMENT IS APPLIED WITHOUT REQUIRING A FINISHED DESIGN
FUNCTION, FEASIBILITY, USER NEEDS, AND DEVELOPMENT RISKS ARE CONSIDERED TOGETHER
FINDINGS FOCUS ON THE QUESTIONS THAT MATTER MOST AT THE CURRENT STAGE
RECOMMENDATIONS INCLUDE THE REASONING BEHIND THE NEXT STEP
No unnecessary complexity or academic, THEORY-CENTRIC LANGUAGE
START YOUR CONCEPT REVIEW
HOW TO GET STARTED
1. Prepare your CONCEPT information
GATHER WHAT IS KNOWN ABOUT THE IDEA, INTENDED FUNCTION, USE CONDITIONS, REQUIREMENTS, CURRENT DIRECTION, AND ANY MAJOR UNKNOWNS.
2. Complete the Project Submission Form
DESCRIBE THE CONCEPT, WHAT YOU ARE TRYING TO ACCOMPLISH, WHAT CURRENTLY EXISTS, AND WHAT YOU WANT HELP UNDERSTANDING OR EVALUATING.
3. UPLOAD YOUR SUPPORTING MATERIAL
SUBMIT SKETCHES, PHOTOS, NOTES, EARLY CAD, PROTOTYPE IMAGES, REFERENCE MATERIAL, OR OTHER INFORMATION THAT HELPS EXPLAIN THE CONCEPT.
4. Tier-1 Engineer performs initial assessment
THE SUBMISSION IS REVIEWED FOR PROJECT FIT, CONCEPT DEFINITION, AVAILABLE INFORMATION, OVERALL COMPLEXITY, AND EXPECTED REVIEW EFFORT.
5. Receive your ICAR
THE INITIAL CONCEPT ASSESSMENT REPORT ESTABLISHES THE REVIEW SCOPE, PRICE, ESTIMATED LEAD TIME, MISSING INFORMATION, AND NEXT STEPS.
6. Decide whether to proceed
REVIEW THE ICAR AND MOVE FORWARD ONLY IF THE PROPOSED SCOPE, PRICE, AND TERMS MAKE SENSE FOR YOUR PROJECT.
A Concept Review begins with a simple project submission. You provide what is currently known about the idea and any supporting material, Tier-1 Engineer evaluates the concept, and you receive a defined review plan before any paid technical work begins.
No payment is required to submit.
Paid technical review begins only after the ICAR is approved and payment is received.
CR