Skip to main content

Follow-up

After the final audit report, follow-up begins: findings enter the Follow-up module and are managed until they are closed. Here auditor and auditee coexist in a dialogue with full traceability, comments, attached evidence, and automatic notifications about due dates.

Each user only sees the findings they are assigned to.

Finding statuses​

Findings move through a chain of statuses. The usual flow is:

Incomplete → Notify → Being implemented → Implemented → Implemented/Audited

With alternative final statuses: Cancelled, Dismissed, Differs in criteria, Risk assumed, and No response.

Detail of each status:

StatusDescription
Incomplete (draft)The auditor is still building it. The auditee does not see it.
NotifyThe system emails the auditee at 8 PM (configurable). The issue enters Follow-up.
To regularizeAllows approving the draft and issuing the final audit report even without an implementation date. Requires corrective actions to be loaded.
Being implementedAn action plan and a committed date exist. Mawidabp tracks due dates.
ImplementedThe auditee submitted evidence; auditor review is pending.
Implemented/AuditedClosed with the supervisor's approval. Moves from "pending" to "solved".
No responseThe auditee did not respond within the deadline (3 days by default, configurable).
CancelledIssue created by mistake. Final status; not reversible.
DismissedIssue about an object that no longer exists.
Differs in criteriaAn external body considers there is an issue but internal audit differs.
Risk assumedThe organization accepts the risk of not solving it.

Typical lifecycle​

1. Creation and notification​

The issue is born in Incomplete. The auditor fills the fields and moves it to Notify when ready.

When moving to Notify:

  • An email is sent to the responsible auditee.
  • The email includes a Confirm notification link and a View finding link.
  • The issue shows up in Follow-up → Pending findings.

2. Auditee response​

The auditee enters the finding and responds:

  • Response / corrective actions: what they will do to remediate.
  • Estimated implementation date: their time commitment.

If the auditee does not respond in 3 days (configurable), the system changes the status to No response.

3. Being implemented​

The auditor reviews the response and changes the status to Being implemented. To advance to this status the following are required:

  • Response / corrective actions.
  • Implementation date.

Mawidabp tracks due dates automatically and sends reminders as the deadline approaches or passes.

4. Continuous dialogue​

From this point until closure, auditor and auditee can:

  • Add comments to the finding (each comment triggers an email to the other party).
  • Attach files as evidence.
  • Add associated tasks.

When the auditee attaches a file, the auditor can:

  • Download it directly.
  • Promote it to a working paper of the finding with one click.

5. Implemented​

When the auditee considers the work done and submits evidence, the auditor can mark the finding as Implemented. This stops automatic reminders but keeps the finding open until the supervisor's review.

6. Implemented/Audited​

The supervisor reviews the evidence and marks Implemented/Audited to close. Required fields:

  • Solution date.
  • Auditor comments.

The finding moves from Pending findings to Resolved findings.

Module views​

Pending findings​

Follow-up → Pending findings shows the list of open findings assigned to the user. Allows:

  • Searching by any black column (gray columns are excluded from the filter).
  • Downloading the listing as CSV or a PDF summary.
  • Viewing or editing each finding.

Resolved findings​

Follow-up → Resolved findings shows findings closed with status Implemented/Audited or repeated in later reviews.

Repeated findings​

Follow-up → Repeated findings lists findings that, after being closed, reappeared in later reviews. A key input to evaluate the actual effectiveness of corrective actions.

Approvals​

Follow-up → Approvals gathers findings pending the supervisor's review. Useful as a work tray for the role.

Per-finding downloads​

Inside each finding, in the lower-right corner:

  • Download follow-up: PDF with the most important data of the finding to date.
  • Download full follow-up: includes change history and comments.

Automatic notifications​

Mawidabp sends email notifications at several moments:

  • To the auditee when an issue moves to Notify.
  • To both auditor and auditee with each comment from the other.
  • Reminders N days before the due date (configurable).
  • Alerts when the finding becomes overdue.
  • Escalation when a Being implemented issue is overdue.
  • Periodic summary of pending findings.

The detailed configuration of these notifications lives in Notification settings.

Reports​

Follow-up → Reports offers two blocks:

  • Audit: view from the audit area (finding evolution, deadline compliance, effectiveness).
  • General (auditee): view from the auditee side (their pending and resolved findings).

All reports accept filters by period, unit, owner, tag, and status, and can be exported to PDF, Excel, or CSV.