Are you sure?
For longer feedback or things you want logged inside the app, use the .
The basics. These fields land on the cover page of the briefing pack and at the top of the notice letter.
The site you're going to. For multi-site audits, pick the lead site here and list the others under Scope.
For external audits, the certification body or customer. For internal audits, the auditing department.
Other auditors, technical experts, and observers (trainees, witnessing-body inspectors). They'll appear on the cover page and the notice letter.
Times drive the calendar invite. Logistics flags travel onto the notice letter so the auditee can prepare access, badges, parking and any safety induction in advance.
Pick the standards in scope and the scope statement. Sub-clauses come next.
Auto-built from your clauses. Edit times, merge slots, add breaks, change attendees. Goes into the calendar invite as the body text.
Who needs to be available, their function, and which clauses they cover. The auditing body needs this in writing — last-minute substitutes break the audit.
Generated from your clauses. Pre-audit submission deadline defaults to two weeks before the audit so you have time to read.
A quick gate-check before you send. Fix the red items if you can — they're the things that most often derail audits.
Two outputs leave this screen: the briefing PDF (formal pack for the auditee), and the calendar invite for the audit team and auditees.
Cover page, formal notice letter, scope & clauses sheet, document request list, and draft agenda. Send this to the auditee management contact.
Per-day events covering each agenda slot. Drop into Outlook, Google Calendar, or any calendar app. Forwardable to all attendees.
Round-trippable plan. Re-open later in this tool to amend, or hand it to the next auditor for the next surveillance cycle.
Just the cover page — useful as a one-pager to circulate internally before the full briefing pack goes out.
Are you sure?