Planning
Planning is the starting point of the audit lifecycle. Here you decide what to audit, when, with which resources, and with what risk approach. The module is organized in four sections: Resources, Periods, Risk assessments, and Work plans.
Resources (optional)
Material resources (mobility, per diems, supplies) are loaded in units and can later be assigned to the plan and to the workflow. Human resources are not created here: they are the system users themselves; they are assigned by estimated hours to the plan.
Assigning resources is optional, but it lets you compare what was planned against what was actually executed.
To load them: Planning → Resources → New.
Periods
Periods are the time windows on which work is planned. Mawidabp does not enforce a format: they can be yearly, semiannual, quarterly, or whatever length the organization needs. All later planning hangs off a period.
Create a period
- Planning → Periods → New.
- Define name, start date, and end date.
- Save.
Risk assessment (optional)
A useful step before the plan to prioritize based on the risk of each unit or process. Requires having a risk assessment template ready in Administration (with attributes and the calculation formula).
Create a risk assessment
- Planning → Risk assessments → New risk assessment.
- Fill in:
- Name and description (free text).
- Period: the one created in Periods.
- Risk assessment template: the one created in Administration.
- Create risk assessment.
Load items and calculate
The items to assess can be:
- Business units (defined in Administration → Organization).
- Processes of best practices (defined in Administration → Best practices).
For each item, open the blue arrow on the left, fill in the template attributes, and the system applies the formula automatically.
When you finish:
- The matrix and heatmap become visible.
- You can mark the assessment as Final.
- In Actions, you can generate a work plan directly from the assessment, with processes ordered by descending risk.
Work plans
The plan contains the projects that will be executed in the period. Each project is tied to a business unit and may include resources and tags.
Create a plan
- Planning → Work plans → New.
- Select the period.
- Save.
Add projects
- Inside the plan, enter an organizational unit.
- Add project.
- Fill in:
- Project name.
- Associated business unit.
- Estimated start date and end date (must fall inside the period).
- Optionally: material resources, human resources (with estimated hours), tags, auxiliary organizational unit.
Automatic plan tracking
The plan is visualized in two ways:
- Schedule: the dates of every project on a timeline.
- Progress: aggregated metrics by unit.
Available metrics:
| Metric | What it measures |
|---|---|
| Total | Total planned projects. |
| Planned | Projects planned as of the selected date. |
| Executed | Projects with at least one review in execution. |
| On time | Projects executing within the planned timeframe. |
| Total progress | Executed / Total (%). |
| Compliance | On time / Total (%). |
Individual project status
Each project displays a color:
- 🟢 Green: concluded (with final audit report).
- ⚪ Gray: in execution within timeframe.
- 🟡 Yellow: in execution outside timeframe.
- 🔴 Red: late (no review and outside timeframe).
Downloads
From the read-only view of the plan, in the lower-left corner:
- Global audit plan (PDF): projects with estimated costs and totals, ordered by period and organizational unit.
- Detailed audit plan (PDF): same as above with additional detail.
- CSV: tabular export for external processing.
Plan versions
The plan is approved and, if it requires modification, you must add a justification when editing. This generates versions that can later be compared.
Cross-step prerequisites
Some dependencies to keep in mind:
- To create a risk assessment you need: a period and a risk-assessment template.
- To create a work plan you need: a period and an organization structure (organizational and business units).
- Projects within the plan require an existing business unit.
Next step
Once the plan is approved, the cycle continues in Execution: reviews are created for each project and findings are recorded.