Sentinel Assure
Governance, risk, compliance and local data analysis for audit and assurance teams.
Audit, risk, compliance and revenue-assurance teams
A traceable view of risks, controls, findings and follow-up actions.
An audit finding is useful when the right person can understand the evidence, take responsibility and follow it through. Sentinel Assure brings that work into permission-controlled workspaces, alongside the data and document tools an analyst needs to investigate an exception.
See review workload, registered risks and items requiring attention in the same workspace.
Track owners, status, priority, deadlines and evidence references for risks, audits, controls, compliance obligations and remediation. Revenue-assurance fields support the configured deployment.
Owners share each workspace with the appropriate Viewer or Editor access. Staff administration does not bypass this business-record boundary.
The studio extracts supported spreadsheets, text, Office files, PDFs and common images. Image OCR uses local Tesseract resources.
Permitted staff can browse a bounded source schema and prepare a question using the configured database adapters.
Configured local Ollama models support query planning and draft observations. The resource manager supports approved model downloads.
Reports show findings, coverage, workload, deadlines and underlying record references. Supported exports include PDF, HTML and CSV.
Application screenshots use fictional records in the existing revenue-assurance edition. The organisation branding visible in this edition is not a customer testimonial or endorsement.
See review workload, registered risks and items requiring attention in the same workspace.
Review the reporting scope and filters before exporting findings for management.
Start an authorised source connection or prepare a supported document for analysis.
A reviewer opens the workspace to understand which assessments, reconciliation items and cases are still open. The risk landscape provides a second view of registered exposure; owners and due dates give the team a practical way to decide what to review next.
Keep the finding, its evidence reference and the responsible owner together. A change in status should reflect the review that actually happened. A completed item is a recorded workflow state; independent assurance still depends on the organisation’s evidence and review process.
Application preview with demonstration data.
A reconciliation question may begin in a spreadsheet, an image of a document or an authorised database. The studio gives analysts a place to prepare supported inputs and explore the intended source scope. Where local AI is configured, draft analysis can assist the reviewer.
The analyst remains responsible for checking extracted text, table relationships, query scope and the returned rows. Read-only database permissions are an essential deployment boundary. Local models, OCR resources and connector dependencies must be installed and validated for the actual inputs.
Application preview with demonstration data.
A report should help a manager understand what was reviewed and what still needs action. Sentinel Assure reporting draws on workspace records and selected filters, so the reviewer can connect the summary to the work behind it.
Use the supported PDF, HTML and CSV outputs for the intended audience. Review the scope, dates, statuses and ownership before sharing. Protect exported files under the organisation’s information-handling policy; an export does not automatically retain the application’s access restrictions.
Application preview with demonstration data.
Create staff accounts and grant workspace-creation or external-analysis permissions. Business-record access still requires ownership or sharing.
Manage membership, assign accountability and review assurance records.
Maintain records and follow-up actions in the shared workspace.
Read and export authorised reports without changing records.
An assurance team records a control weakness and supporting references.
Practical value: The review follows the issue to its responsible officer and recorded response.
Requirements: Staff must maintain source evidence and current record status.
An analyst reviews an authorised finance or revenue source.
Practical value: The query result supports an accountable investigation.
Requirements: Read-only grants, correct relationships and a supported dialect are required.
An owner invites an independent staff reviewer.
Practical value: Read and edit permissions remain explicit.
Requirements: The reviewer needs an active account and the appropriate membership.
A team receives a supported spreadsheet or scanned page.
Practical value: Findings remain tied to supplied evidence.
Requirements: OCR quality, supported formats and processing limits apply.
These scenarios explain workflows using fictional examples.
Authentication and explicit workspace selection.
Workspace permission checks, validation and reporting.
Application accounts, records and workspace membership.
Approved source accounts, local OCR and configured Ollama models.
Read-only source account and permitted catalog access.
Validate server version, schema scope and relationships.
Configured connection and read-only grants.
Review schema and query intent before execution.
Supported driver and scoped source account.
Source permissions and actual dialect testing remain essential.
Approved collections or SQLite files within the source root.
External MongoDB cannot target the application database.
Local runtime, approved model weights and OCR resources.
Initial provisioning may need internet; choose suitable host resources.
Review the selected scope, source records and intended audience. Confirm which staff may export or retain the output and protect downloaded files under your organisation’s policy.
Explore information handling and access →Confirm users, workflows, inputs and the outcome your team needs.
Set up accounts, sources, devices and the agreed integration scope.
Exercise normal and failure cases with representative inputs.
Train the responsible staff and agree recovery, maintenance and support.
No. Sentinel Assure handles assurance workspaces and data analysis. Camera and building access belong to Sentinel SiteGuard.
No. Staff review generated plans, source rows and draft observations.
No. Ownership or explicit sharing is required for business-record access.
Documented adapters still need validation against actual server versions and permitted schemas.
Only documented formats and processing limits are supported. OCR output requires review.
A separate quote covers users, hosting, sources, model resources, deployment, training and support.
Sentinel Assure is a governance and analysis application. It does not provide camera monitoring, biometric identification or drone control.
Tell us who will use the product, which inputs or devices you need to connect and how you want to deploy it. We can then define a demonstration and a separate product-specific quotation.
Capabilities, practical examples and deployment requirements for this product.
Review the implemented capabilities and their operating conditions.
Explore features →Follow illustrative workflows and the records needed for review.
Explore use cases →Understand supported connections and the work needed to commission them.
Explore integrations →Review access boundaries and operational responsibilities.
Explore security →Plan a pilot, acceptance tests, training and support.
Explore deployment →Read the full proposal and use the editable presentation.
Explore proposal & slides →