Inspections & actions — guided interface tutorial

Silent annotated screenshots of real fictional-demo screens.

1. Begin with the actual workflow
Assess inspection results and verify corrective actions before closure. The path shown for this system is: Define a pass threshold, submit an inspection, assess its result and verify required corrective actions. Open the fictional demo before using live organisational data. Compare that path with your requirements and confirm which advanced sector features are included.
Check: Use the PDF workbook to list one task your organisation needs to complete.

2. Read the dashboard in context
The Inspections & actions demo contains saved fictional records. Cards count those records, included systems and authorised members. Line, bar and status charts use the same workspace data. Live refresh runs every sixty seconds while the page is visible and can be paused.
Check: A count of records is not a count of verified payments or unique customers.

3. Find the reference record
Open Inspection types. Search the visible text fields or choose a status, then apply the filter. The reference identifies the saved row in this workspace. Open a row to review its details before linking it to another operational record.
Check: Confirm the correct workspace and record reference before taking any action.

4. Create clear starting information
Choose New record and complete the marked fields. In this section they include Inspection type, Checklist code, Passing score out of 100. Optional fields may remain blank. References are restricted to your workspace, while computed fields are calculated by the server. Correct validation errors before saving the record.
Check: Use fictional information in the demo. Never enter passwords or payment PINs in notes.

5. Follow the operational record
Open Inspections, locate the relevant reference, and inspect its current status. The configured path starts draft → submitted → passed → needs correction. Use filters to separate work awaiting a decision from finished records. Refresh a changed record before editing or applying another workflow action.
Check: A processed record is protected from ordinary edits; use its valid next action.

6. Apply the rule behind the action
The record page shows the available actions, field values and workflow history. A typical first action here is submit. Assessment compares the score with the checklist threshold. A failed inspection needs corrective work. Resolution requires an evidence summary; a manager verifies it. Closure is blocked until every corrective action is verified. These are internal inspection records.
Check: Approval actions require the configured manager role. Read any validation message before continuing.

7. Trace a chart to its figures
Managers can open Visual reports and choose an ordered date range of up to one year and an entitled system. The page shows records created in that period, grouped by current status. Review the underlying figures before downloading an eligible CSV or a system-signed report PDF.
Check: Monetary field totals may include drafts, costs or estimates. They are not verified revenue.

8. Keep a useful, private record
Use Generate PDF on a record to create an immutable snapshot, then find it in Documents. The QR opens a minimal verification entry; it does not publish the private record. System signatures detect changes to stored snapshots. Personal CEO signatures require an authorised uploaded asset.
Check: Your next step: complete one fictional scenario and compare its saved result with the guide.