Missing a file? The request is drafted
Where a sub-requirement has no file, Enpasse suggests a request for your assessor to edit and send.
Evidence
Every file the client sends,in its place
Upload once.
Every page read.
Drop in what the client sends. Enpasse reads each one and maps it to the sub-requirements it supports, with the place it shows them.
Read by Enpasse, cited by you
Each file is read, partly read or not read. Mapping runs in the background; your assessor cites each mapping or sets it aside.
One path per file
Read, mapped, cited, listed in Section 6, in the report. Everyone sees where each file stands.
Nothing in a file runs
Read in isolation. Nothing inside runs, loads or calls out; hidden text is flagged.
From the client
Drag a file into Enpasse, or press it.
Drop files to uploadAny file the client sends
Drop a file. Watch it read.
Each mapping lifts off the lines it shows. You cite it or set it aside.
Decide where
each file fits
Each mapping opens beside its source. Your assessor compares, then cites or sets it aside, one row or a few at a time, with Undo.
A few rows at a time, with Undo
Tick clean rows in one file and cite them together. Anything flagged stays out.
Find a control by what it does
Type "detected" and the 11.5.1 controls matrix lights up, with every page that holds the word. Pages, rows and lines in order. Works without AI.
Cite the
exact place
A citation is a passage, page, rows or region, never a typed note. One click opens the original, the place marked.
Point at a requirement.
Its files rise.
Each sub-requirement keeps the files that support it, open at the place they show. One with no file stands out, its request drafted.
Every file tied to the place it supports
Lines, rows, a region or a page. A gap shows before anyone has to look for it.
Never retype
an interview
An interview is a file too. Each point quotes the exact words, with role and time. Procedures cite the line, and the report lists the interview.
What you saw,
on the record
Scope and testing procedures each have an Observe step. It saves a numbered record to the files list, stamped by the person who made it.
Proc-14
Add observation
9.4.1
Seen on
Observer
What was seen
Where
ResultShownFailingNot shown
Onsite or remoteOnsiteRemote
Save observation
MRMaria Reyes3 Sep
Sub-requirement9.4.1Media physically secured
ExamineEV-041
ObserveWaitingProc-14
ResultFranchise store 141 not yet seen
ROC1.3Onsite or remote
From recordsInt-01Int-01, Proc-14
Never an upload. Never sent to AI as a file.
- One walkthrough, two records
- A sitting saves an interview record and an observation record, each a file in the files list.
- The observer is checked
- A current QSA or Associate QSA, never the QA reviewer.
- Always yours
- Never in a batch. Enpasse never records one or sets its result.
- Onsite or remote counts
- Records work out the report's line. Your lead confirms it.
Replace a file.
See what relied on it.
Before a new version replaces the old one, Enpasse shows every test, finding and draft that used it. That work goes back for review, and old citations keep their original pages.