Functional architecture
Mawidabp is organized into modules that match the stages of the audit lifecycle. Each module consumes data from the previous one and enriches it, so work moves in a single direction with full traceability.
Processing flow
Organization → Period → Plan → Review → Execution → Conclusion → Follow-up
Stages
| # | Stage | Description |
|---|---|---|
| 1 | Organization | Top-level entity that groups everything. Business units, users, profiles, and general parameters are configured here. |
| 2 | Period | Time window (monthly, quarterly, yearly…) in which work is planned. |
| 3 | Plan | Set of projects to execute in the period, optionally derived from a previous risk assessment. |
| 4 | Review | Concrete review of a project from the plan. Includes scope, workflow, assigned users, and working papers. |
| 5 | Execution | Scoring of control objectives, detection and documentation of findings (issues and improvement opportunities). |
| 6 | Conclusion | Consolidation into a draft audit report (iterative) and then a final audit report (frozen). |
| 7 | Follow-up | Management of pending findings until they are solved, with auditor-auditee dialogue and automated notifications. |
The five application modules
At the menu level, Mawidabp exposes the flow above as five modules:
- Administration: parameters, organization, users, profiles, best practices, templates, questionnaires.
- Planning: resources, periods, risk assessments, work plans.
- Execution: reviews, workflows, working papers, findings, interviews.
- Conclusion: draft and final audit reports.
- Follow-up: pending findings, solved, repeated, notifications, and reports.
Key relationships
- An organization can have several organizational units and business units.
- A period contains zero or more risk assessments and one or more work plans.
- A plan contains projects; each project is tied to a business unit.
- A review references a project from the plan and defines its own workflow.
- A control objective lives inside a review and may generate several findings.
- A finding (issue or opportunity) goes through statuses until it is closed in follow-up.
Flow dependencies
:::warning Important
- A plan cannot be created without a period.
- A review cannot be created without a project from the plan.
- A final audit report can only derive from an approved draft audit report.
- Findings are born during the execution of a review and are closed in follow-up; their full history stays in the system log.
- All information is multi-tenant: data from one organization is isolated from the rest. :::
Automatic coding
Mawidabp codes work elements uniquely and sequentially:
- Working papers of control objectives:
PTOC 001,PTOC 002, … - Issues:
O 001,O 002, … - Working papers of issues:
PTO 001,PTO 002, …
If an element is cancelled or deleted, you can recode to keep the range contiguous.