Flash mode

Flash mode deals an audit out as flashcards: one requirement fills the screen, you set the result, type an observation if you have one, and move on. It is the fastest way to establish a first security posture across a whole framework, and the least distracting way to close the gaps left after a first pass — no tree, no filters, no scrolling past requirements you have already settled.

Where to find it

Open an audit and click Flash mode in the Power-ups panel, under Modes. The button is hidden while the audit is locked, and flash mode is an internal-user surface — third-party respondents do not see it.

What a card shows

The header carries a Go back to the audit link, a running count of how many assessable requirements have been assessed, and a position counter showing where you are in the deck. Under it, a progress bar fills as requirements get assessed, with a cursor marking your current position.

The body of the card shows the requirement’s title, its description, its annotation when the framework supplies one, and its weight when that weight is not the default. If the framework defines questions, the questionnaire is rendered inline on the card. Frameworks can also include splash screens — full-page explanatory sections that appear in the deck between requirements and carry no answer.

A coloured accent bar down the side of the card mirrors the current result, so the state of the requirement is readable at a glance: grey for not assessed, amber for partially compliant, red for non-compliant, green for compliant, dark for not applicable.

Answering

Under the card sit the controls:

• Result — a row of buttons for Compliant, Partially compliant, Non-compliant and Not applicable. Clicking the result that is already set clears it back to Not assessed, which is how you undo a mis-click. When the framework computes the result from questionnaire answers, the result is shown as a read-only badge instead and follows the answers.
• Observation — a free-text box, saved automatically about half a second after you stop typing.
• Previous and Next — move through the deck.

Everything saves as you go; there is no save button and no form to submit. Answering a question updates the computed result immediately, then reconciles with whatever the server actually stored.

Keyboard shortcuts

Flash mode is built to be driven without the mouse. The shortcuts are ignored while the cursor is inside a text field, so typing an observation never triggers navigation.

Key	Action
N or L	Next requirement
P or H	Previous requirement
G	Open the jump box
Esc	Close the jump box

The jump box takes a position number and sends you straight there — useful when you know you left requirement 47 half-finished. Press Enter to jump.

When the audit is read-only

If the audit is Locked, or its status is In review, flash mode opens with a banner explaining why and every control is disabled. You can still page through the deck to read the assessment; you just cannot change it. Unlock the audit, or move it out of review, to resume.

Tip

Flash mode covers only the requirement’s result and observation. Scores, applied controls and evidence are set on the requirement’s own page or in Table mode — so a common rhythm is a fast flash pass to get every requirement off Not assessed, then a second pass in table mode to attach the proof.

Related

• Table mode — the same requirements as one long, editable page.
• Audits — the requirement tree and everything else an audit holds.
• Evidences — attaching the proof behind an answer.