What should the product do?
Describe the intended user, use case, inputs, outputs and operating environment in plain language.
PROJECT PREPARATION GUIDE
Prepare your project brief
The information needed to scope engineering work, review dependencies and define deliverables.
Six things to tell us.
Where are you now?
Is this an idea, an existing schematic, a development board, a working prototype or a design that needs revision?
What needs engineering support?
Identify the parts of the project you want help with and any work your own team is completing.
What are the important constraints?
Include dimensions, power, interfaces, component preferences, fabrication limits or other non-negotiable requirements.
What does the next milestone look like?
State the outputs or behaviour you want to review. Separate a demonstration milestone from production or certification requirements.
What schedule are you working towards?
Share your target dates and dependencies, such as prototype availability or another team’s release. Feasibility is discussed after scope review.
DOCUMENT PREPARATION
Make the current design understandable.
- Identify the latest version of each file and label older references clearly.
- Include readable exports alongside native design files where possible.
- List known issues, assumptions and any missing documentation.
- Note the development tools, versions and access requirements.
- Discuss confidentiality before sending source code or proprietary design files.
MILESTONE PLANNING
Be specific about “ready”.
Concept review
Is the proposed architecture or design approach suitable for further development? Outputs may be diagrams, models or a requirements review.
Prototype demonstration
Can the agreed functions be shown under defined conditions? Record limitations and what remains outside the demonstration.
Design handover
Are the agreed source files, outputs and documentation complete and accessible? Manufacturing, reliability or certification work may still be separate milestones.
COMMON QUESTIONS
A few practical answers.
Do I need to know the exact technical solution?
No. Start with the intended function and constraints. Architecture or feasibility discussion can form part of the initial scope.
Should I send all my design files with the first enquiry?
Start with a non-confidential summary. Agree confidentiality and sharing arrangements before sending sensitive source files.
Can I request a fixed delivery date immediately?
Share the target date, but the schedule depends on the scope, technical uncertainties, dependencies and access to required hardware.
Can this guide be used for an internal brief?
Yes. Download the text template, add your project information and use it to structure an internal discussion or initial enquiry.