Manage internal audit engagements, scoped control tests, findings, remediation, retesting and revision-aware review evidence.

Assure connects the audit universe to engagements and scoped control tests. Record test evidence, a result and any finding. Failed controls remain open through remediation and need a passing retest before the engagement can move to review. A recorded sign-off applies to the current engagement revision, so subsequent changes require a fresh review before closure. The coverage dashboard summarizes scoped control results by business unit and highlights findings awaiting remediation or retest.
Built for Internal audit teams and control owners coordinating operational and technology audits.
Manage internal audit engagements, scoped control tests, findings, remediation, retesting and revision-aware review evidence.
Review scoped coverage and remediation priorities.
Plan an audit engagement and assign its accountable owner.
Scope controls, record tests, resolve findings through retest and review the engagement.
Maintain business-unit ownership, scope and planned audit effort.
Compare passing controls, open findings and untested controls across business units. Coverage counts describe the scoped work and do not claim a compliance certification.
Create an engagement, scope owned controls and record sample evidence with Pass, Fail or Not applicable results. Findings and exclusions need a rationale.
Record corrective work, a remediation owner and a retest target. Remediation-ready findings remain open until a passing test with fresh evidence is recorded.
Require complete passing tests or justified exclusions before review. Closure requires a sign-off of the current revision; material updates make prior sign-off historical.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Audit universe | 4 sample directory entries | Fictional business unit records providing ownership and planning context. |
| Audit engagements | 4 sample records | Fictional engagement records with linked work items, decisions and activity history. |
English desktop pilot, bounded to 1,000 rows per table. This is an operational audit tracker, not a compliance certification or a complete GRC platform. Evidence is recorded as text and references. No document repository, external collection, scheduled reminders or enforced independent reviewer roles. Broader audit program scheduling and regulatory frameworks require customization.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
A failing control test records its finding and severity on the scoped control. Remediation and subsequent retest remain linked to that control.
No. Recording corrective work marks it ready for retest. A new passing test with fresh evidence is still required.
A subsequent record update changes the revision. Closure requires a review of the current revision and no unresolved control results.
No. It summarizes the results of scoped control tests. Certification, regulatory mappings and assurance conclusions require the appropriate independent process.
Yes. Use the starter prompt as a starting point, or describe changes to an app in the ToolJet AI builder. Ask for your branding, a different layout or extra workflow features, then review and test the generated changes.