How do I complete product compliance work for a partner client?

Partners complete product compliance work inside the client workspace on a consultant seat. The product workspace guides classification, context, risk assessment, requirements, evidence, conformity documents, and monitoring. Client reviewers confirm product facts and approve the completed records.

Key takeaways

• Check the client banner and product name before each change.
• Confirm product facts and classification with the client.
• Save each panel through the save method shown on the screen.
• Review generated drafts and evidence before acceptance.
• Export approval and the product export checks are separate controls.

Last updated 5 October 2026.

Partner manuals.

Screenshots use test data captured on 4 and 5 October 2026. Click a screenshot to open the full image.

Before you start

Complete client onboarding. Confirm partner access and a plan that permits the required product work. Prepare the client product manual, architecture information, test records, and the names of client reviewers.

Agree which product and version the assessment covers. Record unknown information as an open task for the client.

Step 1. Enter the client and open Products

1. Open the Partner Console.
2. Click Clients.
3. Click Work in for the agreed client.
4. Check the client banner and your signed-in email.
5. Open Products in the client workspace.
6. Check whether the product already exists.

Figure 1. Use the existing product record when one already exists.

Step 2. Create a product when required

1. Enter the approved Product name under Create manually.
2. Enter the product function in Short description.
3. Check the name and description with the client.
4. Click Add product.
5. Wait for creation to complete.
6. Open the new product.
7. Check the client and product names.

Use Use an industry template when an appropriate template exists. Check all template facts and proposed entries after creation. A template can prepare starter records. The client still must review those records.

Use Upload a document when the client has an approved manual or datasheet. Check the detected product name and description before creating a record. Follow the document manual for review and confirmation.

Step 3. Read the product work plan

1. Read the readiness card below the product name.
2. Read the current next action.
3. Click Remaining work to inspect the open work list.
4. Assign an owner for information you must obtain from the client.
5. Open the tab for the current task.

Figure 2. Use the next action and remaining work to plan the product task.

Tab	Partner work
Assess	Classification, context, risk assessment, and document analysis.
Requirements	Requirements checklist and clause artifact records.
Evidence	Evidence records, acceptance, validity, and related files.
Conformity	Export review and conformity document preparation.
Monitoring	Review dates, review triggers, and snapshot actions.
Secure by design	Engineering playbooks and release gate review.

Step 4. Confirm classification

1. Click Assess.
2. Expand CRA classification (Annex III / IV).
3. Read any suggested category and the stated scope.
4. Check the product's main function with the client.
5. Select the approved category.
6. Record the classification basis when required.
7. Record only standards that the client can support with records.
8. Check the displayed conformity route.
9. Click Save classification.
10. Check the saved classification in the product header.

Figure 3. Read the proposed category and route before saving the classification.

Figure 3a. Check the recorded basis before you click Save classification.

A proposed category requires a decision. Read the category scope and source links in the panel. Ask the client's qualified reviewer to resolve an uncertain category. If the save control is disabled, check the category selection and required basis.

Step 5. Complete product context

1. Expand Product context (Clause 6.2) on Assess.
2. Enter the approved product context for each input.
3. Move focus out of the field when the panel states automatic saving.
4. Check the save state.
5. Edit the product description when required.
6. Click Save description for a description change.
7. Reload the product to check the saved facts.

Use a manual only with the client's approval. Review extracted context before acceptance. Check intended use, interfaces, operating environment, and user capability with the client engineering team.

Step 6. Complete and save the risk assessment

1. Expand Risk assessment.
2. Check the assets against the product architecture.
3. Add missing assets through Add asset.
4. Confirm proposed assets after client review.
5. Review the data-flow diagrams.
6. Review each threat in Threat model.
7. Confirm proposed threats only after review.
8. Record the approved treatment and remaining risk for each threat.
9. Review the applicability decisions in Essential requirements.
10. Enter the required justification for each applicability decision.
11. Click Save assessment.
12. Check the saved assessment and remaining work.

Figure 4. Review proposed assessment entries with the client before confirmation.

Use generated proposals to prepare review work. A generated proposal requires review of the actual product and source evidence. Do not accept an unknown product fact to clear a task.

Step 7. Complete requirements and artifact records

1. Click Requirements.
2. Open the applicable checklist item.
3. Assign the responsible owner.
4. Record the planned date.
5. Record the supporting evidence.
6. Record the remaining risk when required.
7. Click Save checklist after checklist changes.
8. Check the Saved message.
9. Review the item with the authorized client reviewer.
10. Use the sign-off control after the reviewer accepts the item.
11. Check the saved signatory and date.

Figure 5. Checklist saves and sign-off actions are separate.

Sign-off records the signed-in identity. Sign-off saves immediately. Evidence, owners, planned dates, and remaining risk use Save checklist. Check both results when you complete an item.

Work through the clause artifact sections on the same tab. Read each artifact's required inputs. Draft the artifact from approved product records. Review the generated content. Save the reviewed record through the artifact controls. Follow the full product procedure for shared product work.

Step 8. Review evidence

1. Confirm document suggestions through Assess when required.
2. Click Evidence.
3. Open the relevant control row.
4. Read the evidence title, file, coverage, and current state.
5. Check that the evidence supports the control for the assessed product version.
6. Accept supported evidence through the row controls.
7. Set the approved validity period when required.
8. Reject unsuitable evidence through the row controls.
9. Check the updated evidence state.

Figure 6. Open a control row to inspect its evidence and review controls.

Evidence marked partial can require more work. Expired evidence needs review. Use the document manual for upload and draft confirmation.

Step 9. Complete engineering playbook review when agreed

1. Click Secure by design.
2. Open the playbook for the agreed engineering task.
3. Read the release gate assertions and supporting evidence.
4. Select only assertions that the client engineering records support.
5. Click Save playbooks.
6. Check the saved gates.
7. Use the playbook sign-off control when all required gates are complete.
8. Check the saved signatory.

Save the gates before sign-off. Keep unresolved assertions with the engineering task owner.

Step 10. Prepare conformity documents and export review

1. Click Conformity.
2. Check the manufacturer identity.
3. Record the approved manufacturer details when the default is unsuitable.
4. Record any required economic operator details.
5. Record the notified body details when the route requires them.
6. Click Save notified body after a change.
7. Review the displayed draft conformity documents.
8. Use Regenerate after changing source product or manufacturer details.
9. Record the agreed support period.
10. Click Save support period.
11. Regenerate and review the user information draft when required.
12. Complete Export review through the agreed reviewer process.

Figure 7. Set the review requirement and second reviewer requirement separately.

Use Require approval before export for the agreed export review gate. Use Require a second admin to review when a different administrator must decide the request. The requester cannot decide the same request when second review is required.

Use Submit for review or Request new review when the current product needs review. Check the resulting pending state. Follow the review manual for approval and rejection.

Generated conformity documents are drafts with placeholders. Obtain the required client review before use. An approval can become stale after an assessment change.

Step 11. Check export and monitoring

1. Read the export checks for the product.
2. Resolve the failed checks with the responsible client owner.
3. Check that any required export approval is current.
4. Use the technical file export link for the required format.
5. Check the exported product identity and version.
6. Click Monitoring.
7. Check the review cadence and due date.
8. Read each open review trigger.
9. Complete the review work for the selected triggers.
10. Enter a review note.
11. Select only the triggers that the review addressed.
12. Click Mark review complete.
13. Check the saved review date and trigger state.

Figure 8. Complete a review before closing its triggers.

Use Capture snapshot with the correct reason when the client has approved a frozen assessment record. Check the resulting snapshot version. A snapshot reason can record a product lifecycle event. Confirm that event with the client before capture.

Step 12. Report the result to the client

1. Record the completed product tasks.
2. List remaining product and evidence tasks.
3. Assign an owner and due date to each remaining task.
4. Record the review and export state.
5. Agree the next product review date.
6. Return to your own workspace.
7. Check the client in Review queue.

Common problems

Problem	Corrective action
Product creation is blocked by the plan.	Check billing, plan access, and the product limit.
Classification save is disabled.	Check category selection and required classification basis.
A generated record contains an unknown fact.	Get the client fact before accepting the record.
Checklist changes disappear.	Check Save checklist and the Saved message before leaving the page.
Sign-off is unavailable.	Check saved gates and the required reviewer role.
Approval is stale.	Complete the product changes and request a new review.
Export fails after approval.	Resolve the other export conformance checks.
A monitoring trigger remains open.	Check that the completed review selected and addressed that trigger.

Recommended practices

• Assess one agreed product version at a time.
• Get engineering input for architecture and risk facts.
• Review generated content against source documents.
• Save checklist changes before signing off.
• Complete changes before requesting export review.
• Keep client acceptance and open work with the handover record.

Completion checklist

• Client and product identity checked.
• Product facts and classification reviewed with the client.
• Context and risk assessment saved.
• Requirements have owners and supporting records.
• Evidence reviewed and validity checked.
• Generated drafts reviewed.
• Export review and export checks checked.
• Monitoring tasks and next review date recorded.
• Open work has named owners.

Complete the client handover checks when the engagement ends.