ProductIP helps you organise, manage and share product compliance information in one central platform. This path shows you how to create your first Technical File, collect compliance evidence, collaborate with suppliers and monitor progress across your products. By following these steps, you can build a structured compliance process and maintain complete Technical Files over time.
When to use this
Use this path if:
- you are a first-time ProductIP user
- you are responsible for managing product compliance documentation
- you want to onboard new colleagues
- you want to create a structured process for collecting and maintaining compliance evidence
- you want to involve suppliers in your compliance process
Steps in ProductIP
1. Get started with ProductIP as a customer – General
General introduction
2. Buy credits
(Applies to Essential customers only)
Credits are required to create Technical Files and order additional services in ProductIP.
3. Create a technical file
A Technical File is the foundation of your compliance process. It stores all documentation, requirements, communication and evidence related to one or more products.
Start by creating a Technical File yourself or ask a supplier to create one on your behalf further along the path.
4. Navigate the requirements list
The requirement list is the foundation of your Technical File. It shows which compliance requirements apply to your product and helps you track whether supporting evidence has been provided for each requirement.
Use the requirement list to identify gaps, monitor progress, and keep compliance activities organised.
5. Upload your documents
(Applies to Professional and Enterprise customers only)
Build your Technical File by uploading declarations, test reports, certificates, specifications, and other compliance evidence.
6. Send a document request
If suppliers own the required documentation, request it directly through ProductIP and ask them to upload documentation in the platform.
Let suppliers create and maintain Technical Files for you.
7. Review the received documents
Uploading documents is only the first step. To build a complete Technical File, you must verify whether documents are valid. Review incoming documents carefully.
8. Use metadata to link a document to the correct requirement
Link incoming documents to the correct requirements so your compliance status accurately reflects the available evidence.
9. Manage your workflow status
(Applies to Professional and Enterprise customers only)
Workflows help you organise activities, track progress, and collaborate with colleagues. They also create a clear history of decisions and actions within your Technical Files.
10. Navigate your technical files
Monitor progress, ensure document completeness, and manage supplier data efficiently.
Tips and best practices
- Define clear internal standards for technical files, required documents, and acceptance criteria before you start collecting information.
- Start by collecting existing documentation, then perform a risk-based gap analysis to identify missing evidence.
- Focus on the highest-risk requirements first. As you upload and link documents, the number of open requirements will gradually decrease.
- Schedule regular time each week to review Technical Files and follow up on missing information.
- Use Technical File requests and document requests to involve suppliers and reduce manual work.
- Use the Help for this page button throughout ProductIP to learn about features you are not familiar with.
Learn more
Looking for guidance on implementing ProductIP? Continue with Get started with ProductIP implementation.
