Statement of Applicability

The Statement of Applicability (SOA) lists all ISM controls with their applicability and implementation status. IRAP assessors require it. QuantAssure supports a round-trip workflow: generate the SOA report as a CSV, send it to your assessor, then import their updates with Import SOA.

SOA Table View

Go to Compliance → Frameworks, open your ISM framework, and choose the SOA tab.

The SOA table provides a dense view of all controls with:

  • Control ID and control name
  • Applicability (Applicable / Not applicable)
  • Status
  • Evidence (a freshness marker; see Evidence Freshness)
  • Notes (implementation notes)

Inline Editing

Click any field to edit directly in the table:

  • Applicability: select from dropdown
  • Status: select from dropdown
  • Notes: click to open a text box; it saves when you click away or press Cmd+Enter (Ctrl+Enter on Windows), and Esc cancels

Filtering

  • Filter by Topic, Applicability or Status
  • Search by control ID or keywords ("Search controls...")
  • The tiles above the table show Total, Applicable, Not Applicable, Compliant, Gaps and Not Assessed
  • Viewers see the table but cannot edit it or import

Exporting for Assessor Review

The SOA tab has no export button of its own. The CSV comes from the Statement of Applicability report.

Export Process

  1. On the framework's Readiness tab, click Generate Report under Quick Actions. This opens Reports → Generate Report with the Statement of Applicability report and your framework selected. You can also start it from Reports & audit → Reports. Generating a report needs edit access.
  2. Click Generate Report on the form, and when the report is ready, click CSV on the report page
  3. The CSV includes all controls with current status and notes
  4. Send the CSV to your IRAP assessor

What the CSV Contains

  • Control ID, control name, topic
  • Applicability and reasoning
  • Current compliance status: your determination where you have made one, otherwise the AI's
  • Implementation notes
  • Columns for the assessor to fill: Assessor Determination, Assessor Notes, Evidence Description and Evidence Source

For the ISM, statuses are written in the ISM's own terms: Implemented, Partially implemented and Not implemented. Other frameworks use Compliant, Partially compliant and Non-compliant. Needs review means the AI found the evidence ambiguous and a person has to decide.

Importing Assessor Updates

The Round-Trip Workflow

  1. You generate the SOA report and download it as CSV
  2. Assessor reviews and fills in their columns
  3. You import the updated CSV back into QuantAssure
  4. System updates statuses and creates evidence records

Import Process

  1. Click Import SOA on the SOA tab
  2. Select the assessor's updated CSV file. The import starts as soon as you choose the file, with no separate confirmation step.
  3. Read the summary that appears above the table: how many controls were updated, how many evidence items were created, how many rows were skipped because nothing changed, and the first few errors, if any

Assessor Determination Values

The Assessor Determination column accepts any of the status names above, in either set of terms (for example "Partially implemented" or "partially_compliant"), and these common alternatives. Case and surrounding spaces are ignored.

You can writeImported as
Compliant, Implemented, Yes, EffectiveCompliant
Partial, Partially compliant, Partially implementedPartially compliant
Non-compliant, Not implemented, Gap, NoNon-compliant
Not assessedNot assessed
N/A, Not applicableApplicability set to Not applicable

A blank determination leaves the control's status unchanged, so rows that only add notes or evidence don't reset it. "N/A" takes precedence over the Applicability column. Needs review is not accepted: an assessor's determination is always one of the others. Rows with any other value are reported as errors, with the row number and the accepted values, and are not imported.

What Gets Updated

  • Control statuses updated to assessor's determination
  • Implementation notes merged with assessor notes
  • Evidence records created (type: assessor_review)
  • All changes logged in audit trail

Import will overwrite existing status and notes for controls included in the CSV.

After Import

  • Review your readiness dashboard for updated scores
  • Address any gaps identified by the assessor
  • Add evidence for controls the assessor flagged

Learn more about readiness tracking →