Read results and next steps

Open the actual record #

Find the check by reference and read its current status and next-step message. A dashboard total, activity event or chat answer is not the full result record. Different stages can finish at different times.

For an organisation, review only the outcomes your role is authorised to see. For an individual, open your own check and follow any action requested of you.

Distinguish the kinds of completion #

A completed upload means evidence was received. A reviewed identity stage means its authorised review step has an outcome. A completed synthetic demo check shows how the product presents a finished example. These are not interchangeable.

A simulated result is not an official DBS certificate. Do not download or share it as proof of a real check. Public demonstrations do not establish ClearDBS approval as a Responsible Organisation or live availability of Standard or Enhanced checks.

Find outstanding work #

Read the latest stage message and any correction request. If the applicant needs to act, use the product’s supported follow-up route. If the check is in review, adding another upload without a request may not help.

Do not promise a completion date based on the demo timeline. Use current product communications for processing expectations.

Share and retain appropriately #

Use the available authorised document or result controls, and follow your organisation’s access and retention responsibilities. Avoid copying raw identity evidence into team notes, AI chat or unapproved storage.

If the outcome appears inconsistent with the check details, preserve the reference and visible message and contact Support. Do not alter the applicant’s information simply to make a status change.

Detailed walkthrough #

1. Read the result in context

Start with the status and supporting information in Application summary. A completed workflow task, an identity outcome and a DBS result are different things. Every outcome in this practice workspace is synthetic and must not be presented as an official certificate.

2. Interpret individual document outcomes

Review the recorded outcome against each document separately. One successful document check does not imply that all evidence is complete or that a DBS decision exists. Follow any outstanding action attached to the affected document.

3. Read a completed stage again

Completed stages remain useful for understanding the information behind the current summary. Open them to review what was recorded, not to restart the application. If something is incorrect, use the correction or support route appropriate to the check.

Practise this section #

Open Help & tutorials, select this guide and choose Start practice walkthrough. Read each highlighted component before continuing. Use Back to revisit an explanation and Retry if a sample has not loaded. The walkthrough uses fictional records; do not enter real applicant information.

Use Exit tutorial to leave and keep your place, then Resume walkthrough in this guide to continue. When returning from practice to a real workspace, review the actual record and your permissions before making a change. Tutorial completion does not perform the underlying task.

Before using this guide #

Open the intended check’s summary and read the recorded status and evidence information together. Demo results are fictional.

Worked example #

A document outcome can be complete while the application still awaits other work. Do not describe the document outcome as an official DBS certificate or final DBS decision.

Guided component walkthrough #

Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.

Main walkthrough

Application summary

• Application summary: Progress and outcome read together here. A workflow status in the demo is not an official DBS certificate.
• Check reference and outcome: Before interpreting a result, confirm that the summary belongs to the intended check. Keep its reference with any internal follow-up so that a similarly named applicant is not confused with this record.
• Read the result in context: Start with the status and supporting information in Application summary. A completed workflow task, an identity outcome and a DBS result are different things. Every outcome in this practice workspace is synthetic and must not be presented as an official certificate.

Recorded outcomes

• Recorded outcomes: Each document carries its own result, and those results are what the summary status is built from.
• Evidence is one part of the check: The document panel describes identity evidence outcomes. Read these alongside the application summary; an accepted evidence item is not itself an official DBS result.
• Interpret individual document outcomes: Review the recorded outcome against each document separately. One successful document check does not imply that all evidence is complete or that a DBS decision exists. Follow any outstanding action attached to the affected document.

Completed stages

• Completed stages: A finished stage stays readable. Completing the identity steps is separate from the DBS decision itself.
• Read a completed stage again: Completed stages remain useful for understanding the information behind the current summary. Open them to review what was recorded, not to restart the application. If something is incorrect, use the correction or support route appropriate to the check.

Individual walkthrough

Application summary

• Application summary: Progress and outcome read together here. A workflow status in the demo is not an official DBS certificate.
• Check reference and outcome: Before interpreting a result, confirm that the summary belongs to the intended check. Keep its reference with any internal follow-up so that a similarly named applicant is not confused with this record.
• Read the result in context: Start with the status and supporting information in Application summary. A completed workflow task, an identity outcome and a DBS result are different things. Every outcome in this practice workspace is synthetic and must not be presented as an official certificate.

Recorded outcomes

• Recorded outcomes: Each document carries its own result, and those results are what the summary status is built from.
• Evidence is one part of the check: The document panel describes identity evidence outcomes. Read these alongside the application summary; an accepted evidence item is not itself an official DBS result.
• Interpret individual document outcomes: Review the recorded outcome against each document separately. One successful document check does not imply that all evidence is complete or that a DBS decision exists. Follow any outstanding action attached to the affected document.

Completed stages

• Completed stages: A finished stage stays readable. Completing the identity steps is separate from the DBS decision itself.
• Read a completed stage again: Completed stages remain useful for understanding the information behind the current summary. Open them to review what was recorded, not to restart the application. If something is incorrect, use the correction or support route appropriate to the check.

Related guides