Index of applicable requirements and sources
Record the market, product type, source, version and date accessed.
How this deliverable is checked
Applicability and exclusions can be reviewed.

Review the service and its applications. Scope, deliverables and fees are agreed following discussion.
Discuss the service →Turn applicable requirements into design checks and verification tasks.
Professional service · Acceptance against agreed deliverables
The following deliverables can be agreed. The project brief defines their depth, quantity and verification responsibilities.
Record the market, product type, source, version and date accessed.
Applicability and exclusions can be reviewed.
Turn requirements into mechanical, electrical, optical and other design checks.
Each check links to a responsible discipline and design document.
Connect verification, samples, technical documents and evidence requirements.
Requirements align with tasks, responsibilities and deliverable documents.
List tests, certification needs and external interfaces requiring further confirmation.
Unconfirmed items and external work are identified.
Fees depend on market, product, standards and the number of questions or requirements. Current revisions and applicability are checked when the engagement starts.
Target market, product category, mechanical design and functions, launch plan and priority questions.
Choose standards interpretation or product compliance planning. Scope is priced by market, product, standards topic and depth of analysis.
We confirm workload, service period and both parties' responsibilities before issuing a formal quotation. Samples, site work and third-party services are listed separately where required.
Planning deliverables are not test reports or certification certificates. Applicable regulations, revisions, laboratories and third-party fees are checked when the project begins.
We first define target markets and product boundaries, then identify requirements market by market. Additional markets or product changes require a scope review.
Sources, revisions and applicability are clear, with requirements linked to design and verification tasks.
We first assess how gaps or changes affect deliverables, timing and fees. They are included only after both parties agree; items outside the original scope are recorded separately.
Start with a summary of the product type, objectives and issues. Share detailed information after its intended use, confidentiality requirements, access scope and delivery permissions have been agreed.
Describe your current stage, main objectives and desired deliverables, then we can confirm the suitable scope and next step together.
Use the enquiry page to share a project summary. Detailed information can follow once its use and confidentiality requirements are agreed.