User notifications

Mawidabp sends automatic emails to users to keep them aware of findings, comments, and due dates. This document describes which notifications exist and when they arrive, from the perspective of the user who receives them. The administrator-side configuration is in Notification settings.

Notifications about findings

New finding assigned

When an auditor moves an issue to Notify state, the assigned auditees receive an email with:

• The issue summary (title, description, origin date, risk).
• A Confirm notification link to acknowledge receipt.
• A View finding link that takes you to the issue after signing in.

The send is automatic at 8 PM the day the auditor changes the status (configurable per organization). If several issues are notified the same day to the same user, they arrive grouped in a single email.

New comment on a finding

Every time someone (auditor or auditee) adds a comment to an issue, the other participants receive an email with:

• An excerpt of the comment.
• A direct link to the finding.

The author of the comment does not get their own email.

Notifications about due dates

7 business days before the due date

For findings in Being implemented, Implemented, or Rescheduled state: an email is sent to auditors and auditees 7 business days before the committed implementation date.

1 business day before the due date

A second alert, one business day before the date. Designed to give time to load a response or commit a new date before the finding is marked overdue.

On the due date

On the actual day, auditors and auditees receive another alert.

Reminders after the due date

On Mondays at 8 PM (configurable), Mawidabp sends a summary of pending findings to the responsible parties with all issues whose implementation date expired and that remain open.

The frequency is set with the "Pending findings summary in weeks" parameter:

• 1: every week.
• 2: every two weeks.
• And so on.

Reminders keep arriving until the finding changes status.

Escalation to higher levels

If the organization enables automatic escalation, overdue issues without a response are notified to higher hierarchical levels every week:

1. First notification to auditee and auditor.
2. Following week: to the immediate superior.
3. Following week: to the superior's superior, and so on until exhausting the hierarchy.

Every time the implementation date is updated (with a reschedule or a new agreed date), the escalation clock resets to zero.

This functionality is configured at the instance level and, once enabled, applies to all organizations on that installation.

Notifications about reports

Report close to its closing date

Seven business days before the closing date of a final audit report, auditors and supervisors receive a single email with the list of all reports whose closing date is approaching.

This alert does not reach the auditee or the audit manager. The goal is to remind the execution team that, once the date passes, they will not be able to keep uploading working papers.

Summary by recipient

Notification	Auditor	Supervisor	Auditee	Manager	Hierarchical
New finding assigned			✓
New comment	✓	✓	✓
7 days before due date	✓		✓
1 day before due date	✓		✓
Due date	✓		✓
Weekly summary of pending	✓		✓
Escalation by overdue	✓		✓		✓
Report close to closing	✓	✓

Preferences and frequencies

Configurable parameters live in Administration. The most common:

• Send time for daily notifications (default 8 PM).
• Days of grace before considering an issue as unanswered (default 3).
• Findings summary period in weeks.
• Day of the week for periodic summaries (default Monday).

As an end user, you do not configure frequencies directly: the organization defines them. If a notification feels excessive or missing, talk to the Mawidabp administrator.