Findings & RFI Register

Centralised register for managing findings, corrective action requests, and information requests across all audits, reports, and management of change items.

The Findings & RFI Register provides investigators, auditors, and quality managers with a comprehensive view of all findings and information requests they have created or are responsible for reviewing. Use this page to create standalone requests, review submissions from responsible persons, approve or reject corrective actions, manage extension requests, and track the lifecycle of all quality, safety, and security findings.

1 What's on this page

The Findings & RFI Register displays a comprehensive table of all corrective action requests and information requests that you have created as an investigator, auditor, or quality manager. The page organises requests into three tabs (Active, Closed, Cancelled) and provides tools for creating standalone requests, reviewing submissions, managing extensions, and communicating with responsible persons.

What you see here
  • Tabbed register: Three tabs (Active, Closed, Cancelled) organise findings and requests by status
  • Request table: Comprehensive table showing all findings and information requests with submission status
  • Search and filters: Quick search and advanced filtering by compliance type, date range, responsible person, and more
  • Add standalone requests: Create corrective action requests or information requests independent of audits or reports
  • Review buttons: Approve or reject corrective action submissions and information responses
  • Edit capabilities: Modify draft findings and requests before responsible persons submit responses
  • Messaging system: Two-way communication with responsible persons for each request
  • Export options: Generate PDF reports for findings and information requests
Who uses this page
  • Investigators: Safety investigators managing findings from incident reports
  • Auditors: Quality auditors reviewing corrective actions from audit findings
  • Quality managers: QSS managers overseeing the findings and corrective action process
  • Management of change coordinators: Staff managing findings from MoC hazard reviews
  • Full access required: Users must have full investigator or auditor access to create and review findings

2 Understanding the three tabs

The register organises all findings and information requests into three tabs based on their current lifecycle status. Each tab displays different information and actions relevant to that status.

Active tab

What's shown: All open findings and requests that are due for submission or pending your review.

  • Due items: Corrective actions or information requests awaiting submission from responsible persons
  • Pending review: Submissions you need to approve or reject
  • Extension requests: Deadline extension requests awaiting your approval
  • Draft findings: Draft findings you can still edit before responsible persons begin work

This is your primary work area for managing active requests and reviewing submissions.

Closed tab

What's shown: All findings and requests that have been completed and approved.

  • Approved actions: Corrective actions you reviewed and approved
  • Approved information: Information responses you accepted
  • Submission codes: Each item shows its submission code for reference
  • Historical record: Maintains compliance audit trail

Useful for reviewing past decisions and maintaining compliance records.

Cancelled tab

What's shown: All findings and requests that were cancelled or withdrawn.

  • Cancelled requests: Items you cancelled before completion
  • Cancellation reason: Shows why each request was cancelled
  • Source status: Indicates if the parent audit or report was also cancelled
  • Reactivation option: You can restore cancelled requests if needed

Maintains a record of cancelled requests with the ability to restore them.

3 Search and filter the register

The register includes powerful search and filtering capabilities to help you quickly locate specific findings or groups of requests based on various criteria.

Quick search
Search by text

Use the search box at the top of the table to search findings and requests by:

  • Finding or request name/subject
  • Finding or request code
  • Source code: Audit code, report code, or MoC identifier
  • Responsible person name
  • Submission codes: Corrective action or respondent information codes

The search waits briefly after you stop typing to improve performance. Results update automatically as you search.

Advanced filters

Click to expand the filter section to access comprehensive filtering options:

Date range filter

Date Requested: Filter findings and requests by the date they were created. Use preset ranges (This Week, This Month, Last 7 Days) or select a custom date range.

Useful for reviewing recent findings or preparing period reports.

Compliance type filter

Filter by compliance category: Select one or more compliance types (Quality, Safety, Security, Dangerous Goods) to show only findings in those categories.

Different compliance types may have different submission and review requirements.

Responsible person filter

Filter by assignee: Select specific staff members to see only findings and requests assigned to those individuals.

Useful for checking workload distribution or following up on specific people's submissions.

Source filter

Filter by source: Select specific audits, reports, or management of change items to see only findings from those sources.

Helps you focus on findings from a particular audit or incident investigation.

Clear filters

To reset all filters and search, click the "Clear filters" button in the filter section. The table will reload showing all findings and requests.

4 Create standalone findings and requests

In addition to findings created within audits, reports, or management of change processes, you can create standalone corrective action requests or information requests directly from this register. These are useful for addressing issues identified outside formal processes.

When to create standalone requests
Use cases for standalone requests
  • Ad-hoc findings: Issues identified during routine operations that don't relate to a specific audit or report
  • Follow-up actions: Additional corrective actions identified after closing an audit or report
  • Information gathering: Requests for information not tied to a specific investigation
  • Proactive improvements: Voluntary corrective actions for continuous improvement
  • External findings: Issues raised by external auditors, clients, or regulatory authorities
Create a standalone corrective action request
  1. Click "Add standalone action/RFI" at the top-right of the Active tab
  2. Select "Request corrective action" from the dropdown menu
  3. Complete the finding details:
    • Enter a descriptive name for the finding
    • Provide a detailed description of the issue or non-compliance
    • Select the compliance type (Quality, Safety, Security, or Dangerous Goods)
    • Identify the hazard (or mark as not applicable if no hazard is involved)
    • Perform or reference a risk assessment if required
    • Attach supporting documents if needed
  4. Assign responsible person(s):
    • Choose whether to assign internal staff or external entity users
    • Select one or more responsible persons who will develop the corrective action
    • Set the initial due date for corrective action plan submission
  5. Add team members (optional): Invite other investigators or auditors to collaborate on this finding
  6. Save as draft or publish:
    • Save as draft to continue editing later without notifying responsible persons
    • Publish to send notifications and start the corrective action process
Create a standalone information request (RFI)
  1. Click "Add standalone action/RFI" at the top-right of the Active tab
  2. Select "Request information" from the dropdown menu
  3. Complete the request details:
    • Enter a subject for the information request
    • Provide a detailed description of what information you need
    • Select the compliance type if applicable
    • Identify the related hazard if applicable
    • Define custom form fields if you need structured responses
  4. Assign respondent(s):
    • Select internal staff or external entity users to provide the information
    • Set the initial due date for information submission
  5. Add team members (optional): Invite collaborators to view responses
  6. Submit the request: The request is sent immediately with notifications to respondents

5 Review and approve submissions

When responsible persons submit corrective actions or information responses, those submissions appear in the Active tab with review buttons. Your role is to review the submissions and either approve them (closing the request) or reject them (requesting improvements).

Review a corrective action submission
  1. Identify pending submissions: Look for findings with corrective action codes in the "Submission" column
  2. Click the review button: Click the appropriate review button in the "Review" column:
    • Review plan: For short-term corrective action plans (CAP)
    • Review interim: For short-term completion and evidence (SCAI)
    • Review completion: For long-term completion and evidence (LCAI)
  3. Review the submission details:
    • Read the corrective action plan description
    • Review implementation evidence if provided
    • Check effectiveness evaluation if required
    • Review any attached documents
    • Consider the submission date and any extensions granted
  4. Make your decision:
    • Approve: If the corrective action is satisfactory and adequately addresses the finding
    • Reject: If the corrective action is inadequate, incomplete, or doesn't address the finding
  5. Provide feedback:
    • Enter detailed comments explaining your decision
    • If rejecting, clearly explain what needs to be improved
    • Attach reference documents if needed
  6. Submit your review: The responsible person receives your decision and feedback immediately
Review an information request response
  1. Click the review button: Click "Review info" in the "Review" column for information requests with submissions
  2. Review the information provided:
    • Read all narrative responses
    • Check form field responses if you defined custom fields
    • Review any documents attached by the respondent
  3. Approve or reject:
    • Approve: If the information provided is complete and adequate
    • Reject: If more information is needed or clarification is required
  4. Add comments: Provide feedback explaining your decision
  5. Submit your review: The respondent is notified of your decision

6 Review extension requests

Responsible persons can request deadline extensions for corrective actions or information requests when they need more time. Extension requests appear in the "Review" column and require your approval or rejection.

Approve or reject an extension request
  1. Click "Review ext." in the Review column for items with pending extension requests
  2. Review the extension request:
    • Read the justification provided by the responsible person
    • Check the requested new due date
    • Review any supporting documents
    • Consider the history of previous extensions if any
  3. Decide on the request:
    • Approve: If the justification is reasonable and the new date is acceptable
    • Reject: If the justification is inadequate or the extension is not warranted
    • Modify the date: You can approve with a different date than requested
  4. Add your comments: Provide feedback on your decision
  5. Submit your review: The responsible person is notified of your decision

7 Edit draft findings and requests

Findings saved as drafts can be edited before being published to responsible persons. Once published, you can still modify certain details, but changes are more limited to avoid disrupting active work.

Edit a draft finding
  1. Identify draft findings: Look for yellow "Draft" buttons in the "Edit request" column in the Active tab
  2. Click the Draft button: The finding window opens with all details editable
  3. Make your changes: Modify any field including description, compliance type, hazard, responsible persons, or due dates
  4. Save or publish:
    • Save as draft to continue editing later
    • Publish to finalise the finding and notify responsible persons
Edit a published finding or request
  1. Click the edit button: Blue edit button in the "Edit request" column for published items
  2. Make limited edits: You can modify:
    • Finding or request description
    • Responsible persons (add or remove)
    • Due dates
    • Attached documents
    • Team members
  3. Save your changes: Responsible persons are notified of significant changes

8 Submit on behalf of responsible persons

If you have full access to a finding or information request, you can submit corrective actions or information on behalf of responsible persons. This is useful when a responsible person needs assistance or is unavailable.

Submit a corrective action on behalf
  1. Click the submit button: In the "Submit on behalf" column, click the relevant button (Plan, Interim, or Completion)
  2. Complete the submission: Fill in all required fields as if you were the responsible person
  3. Submit: The submission is recorded under the responsible person's name but shows you as the submitter
  4. Review (if required): Another investigator or auditor with full access must review and approve the submission
Submit information on behalf
  1. Click "Submit info" in the "Submit on behalf" column for information requests
  2. Provide the information: Complete all response fields and attach documents
  3. Submit: The information is recorded under the respondent's name
  4. Review: Another team member must review and approve if required

9 Communicate with responsible persons

The messaging system allows you to communicate directly with responsible persons about specific findings or information requests. Messages are attached to each request and visible to all team members and responsible persons.

Send a message
  1. Click the messages button: In the "Messages" column, click the message icon with the unread count badge
  2. View message history: All previous messages in the conversation are displayed
  3. Type your message: Enter your message in the text box
  4. Attach documents (optional): Add supporting files if needed
  5. Send: The message is sent immediately to all responsible persons and team members
Message notifications
Unread message indicators
  • Red badge: Indicates unread messages from responsible persons or team members
  • Green badge with 0: All messages have been read
  • Message count: Shows the number of messages you haven't read yet
When to use messaging
Effective messaging use cases
  • Clarification requests: Ask for more details about a submission before reviewing
  • Guidance: Provide hints or direction to help responsible persons develop better corrective actions
  • Updates: Inform responsible persons of changes to requirements or deadlines
  • Follow-up: Check on progress for overdue submissions
  • Collaboration: Coordinate with team members on complex findings

10 Cancel and reactivate requests

You can cancel findings or information requests that are no longer needed, and you can reactivate cancelled requests if circumstances change.

Cancel a finding or request
  1. Click the cancel button: Red cancel button in the rightmost column of the Active tab
  2. Enter a cancellation reason: Provide a clear explanation for why you're cancelling the request
  3. Confirm: The finding or request moves to the Cancelled tab
  4. Notifications sent: Responsible persons are notified that the request has been cancelled
Reactivate a cancelled request
  1. Go to the Cancelled tab
  2. Find the request to reactivate
  3. Click the restore button: Grey restore button in the "Activate" column
  4. Confirm: The request moves back to the Active tab
  5. Notifications sent: Responsible persons are notified that the request is active again

11 Export findings and requests

Generate PDF reports for individual findings or information requests, or export the entire register to Excel for analysis.

Export individual items
Generate PDF reports

In the "Export" column, click the PDF icon to generate a comprehensive PDF report for a single finding or information request. The report includes:

  • Finding or request details: Description, compliance type, hazard, risk assessment
  • Submission history: All corrective action submissions and reviews
  • Extension requests: Any deadline extensions granted
  • Messages: Complete message thread
  • Documents: Links to attached evidence
Export the register to Excel
  1. Apply filters (optional): Use search and filters to show only the items you want to export
  2. Click the Excel button: At the top-right of the table, click the Excel export button
  3. Download the file: The Excel file downloads with all visible findings and requests
  4. Analyse in Excel: Use pivot tables, charts, and formulas for reporting and analysis

12 Understanding the register columns

The register table displays different columns depending on which tab you're viewing. Here's what each column means and how to use it.

Column Description Available in
Review Buttons to review corrective action submissions, information responses, or extension requests. Button labels indicate what type of review is pending (Plan, Interim, Completion, Info, Extension). Active, Closed
Edit request Button to edit the finding or information request. Yellow button for drafts, blue button for published items. Available only if you have full access to the source. Active
Name/Subject The name of the finding or subject of the information request as entered when it was created. All tabs
Submit on behalf Buttons to submit corrective actions or information on behalf of responsible persons. Shows which submission type is due (Plan, Interim, Completion, or Info). Only visible if you have full access. Active
Submission The code of the corrective action (e.g., CA2025070012) or respondent information submission (e.g., RIN2507.002). Shows "N/A" if no submission has been made yet. All tabs
Finding/Request The code of the finding or information request. Click to view full details including description, hazard, risk assessment, and all submission history. All tabs
Source The audit code, report code, or MoC identifier where this finding originated. Shows "Standalone" for findings created directly in this register. All tabs
Requested by The name of the investigator, auditor, or quality manager who created the finding or request. Click the column header to sort by requestor name. All tabs
Date requested The date the finding or request was initially created. Click the column header to sort by date (most recent first or oldest first). All tabs
Resp. person List of responsible persons assigned to respond. Hover over truncated names to see the full list. Multiple responsible persons are shown as bullet points. All tabs
Messages Button to open the message thread. Badge shows number of unread messages (red if unread, green if all read). Disabled for anonymous respondents. All tabs
Export Button to generate a PDF report for this individual finding or information request. All tabs
Cancel Red button to cancel this finding or request. Requires entering a cancellation reason. Only visible if you have full access. Active
Activate Grey button to restore a cancelled finding or request back to active status. Disabled if the parent audit, report, or MoC is also cancelled. Cancelled

13 Field and status reference

Understanding the key fields, statuses, and terminology used in the Findings & RFI Register.

Finding and request types
Type Description
Audit Finding A finding identified during a quality audit. Associated with a specific audit checklist item and audit code.
Report Finding A finding identified during a safety investigation of an incident report. Associated with the report code.
MoC Finding A finding identified during a management of change hazard review. Associated with the MoC identifier and identified hazard.
Standalone Finding A finding created directly in this register, not associated with any audit, report, or MoC process.
Report RFI A request for information associated with an incident report investigation.
MoC RFI A request for information associated with a management of change process.
Standalone RFI An information request created directly in this register, independent of any specific process.
Compliance types
Compliance Type Description
Quality Findings related to quality management system standards, procedures, and organisational requirements.
Safety Findings related to aviation safety, flight operations, hazards, and safety management system requirements.
Security Findings related to aviation security, access control, and security management requirements.
Dangerous Goods Findings related to dangerous goods handling, transport, and compliance with IATA regulations.
Submission statuses
Status What it means
N/A (No submission) The responsible person has not yet submitted a corrective action or information response. The submission is still due or overdue.
CAP code shown A corrective action plan has been submitted and is pending your review or has been approved/rejected.
SCAI code shown Short-term corrective action implementation evidence has been submitted and is pending review or approved.
LCAI code shown Long-term corrective action implementation evidence has been submitted and is pending review or approved.
RIN code shown Respondent information has been submitted for an RFI and is pending review or has been approved/rejected.
Review button labels
Button Label What you need to review
Review plan Review and approve or reject the corrective action plan (what the responsible person intends to do).
Review interim Review and approve or reject short-term implementation evidence (proof that short-term actions have been completed).
Review completion Review and approve or reject long-term implementation evidence (proof that long-term actions have been completed and are effective).
Review info Review and approve or reject information provided in response to an information request.
Review ext. Review and approve or reject a deadline extension request submitted by the responsible person.

14 Permissions and access control

Access to the Findings & RFI Register and its features depends on your role and permissions within the quality, safety, and security management system.

Who can view this page
View access

You can view the Findings & RFI Register if you meet any of these criteria:

  • Auditor on an audit: Listed as an auditor with full access on one or more quality audits
  • Investigator on a report: Listed as an investigator with full access on one or more safety reports
  • MoC team member: Listed as a team member with full access on one or more management of change processes
  • Creator of standalone findings: You created standalone findings or information requests
Who can create standalone requests
Create access

Creating standalone findings and information requests requires:

  • Full IQSMS management permissions: The ability to create standalone action requests and information requests
  • This permission is typically granted to quality managers, safety managers, and senior auditors/investigators
  • Contact your system administrator if you need this permission
Who can edit findings and requests
Edit access

You can edit findings and requests if:

  • You have full access to the source: Full auditor access for audit findings, full investigator access for report findings, full MoC editor access for MoC findings
  • You're a team member on standalone items: Listed as a team member with full editor access on standalone findings or RFIs
  • Edit capability is more limited after submissions begin
Who can review submissions
Review access

Reviewing and approving submissions requires:

  • Full access to the source (audit, report, or MoC) where the finding originated
  • You cannot review submissions you made yourself (even if on behalf of someone else)
  • At least one other person with full access must exist to provide independent review
Navigation
Settings

Theme


Other settings coming soon...

An unhandled error has occurred. Reload 🗙
Interactive features loading...