Table mode

Table mode lays the entire audit out as a single scrolling page: every requirement in framework order, each with its own editable block. Nothing is hidden behind a click-through, so it is the right surface for a working session where you answer many requirements in a row, and for a reviewer who wants to read the audit end to end without opening a hundred pages.

Where to find it

Open an audit and click Table mode in the Power-ups panel, under Modes. The button is hidden while the audit is locked. Unlike flash mode, table mode is available to third-party respondents as well as internal users — it is the surface a vendor typically fills a questionnaire in.

Reading the page

A sticky header stays at the top with a Go back to the audit link carrying the audit’s name, so you never lose your place. On wide screens a table of contents sits on the right, listing every requirement title; clicking an entry scrolls straight to it.

Requirements are separated by their title rendered as a divider, with the requirement’s weight shown as a badge when the framework gives it anything other than the default. Splash screens defined by the framework render full width between requirements, as explanatory cards with no fields.

Where the framework supplies them, each block also shows the requirement’s description, its annotation, its Typical evidence hint and any mapping suggestions inferred from other frameworks.

Answering

Each requirement block exposes the fields the audit makes visible to you — which fields those are depends on the audit’s field-visibility settings and on whether you are working as an auditor or as a respondent:

• Status — To do, In progress, In review, Done.
• Result — Compliant, Partially compliant, Non-compliant, Not applicable. When the framework computes the result from questionnaire answers, the result appears as a read-only badge and follows the answers.
• Respondent alignment — the Are you aligned with this requirement? question, answered Yes, No, In progress or Not applicable.
• Score and Documentation score — sliders on the audit’s scale, shown only when scoring is enabled.
• Observation — free-text notes.
• Applied controls — link existing controls, or create one inline without leaving the page.
• Evidences — attach existing evidence, or create a new one inline.

Question-driven frameworks render their questionnaire inline in the same block. Third-party respondents land in questionnaire mode by default, so they see the questions rather than the auditor’s assessment fields.

Everything saves by itself. Changing a status, a result or an answer writes immediately; scores wait until you have stopped dragging for about half a second, so a slider sweep produces one save instead of twenty. There is no save button.

Tip

Because table mode renders every requirement at once, a large framework makes a long page. Use the table of contents to move, and your browser’s find-in-page to jump to a specific requirement reference — both are faster than scrolling.

When the audit is read-only

If the audit is Locked, or its status is In review, the page opens with a banner explaining which of the two applies and every field is disabled. The content stays fully readable, which makes a locked audit in table mode a decent read-only report for a reviewer.

Choosing between the modes

Surface	Best for
Requirement tree	Navigating a big framework, filtering, seeing roll-ups per section
Flash mode	A fast first pass — result and observation only, one card at a time
Table mode	Deep work — scores, controls and evidence on many requirements in one sitting

Related

• Audits — the audit page and its requirement tree.
• Evidences — what you can attach from a requirement block.
• Applied controls — the controls you link from each requirement.