Suggestions with sources.Decisions with names.
A result beside
the passages it cites
For each testing procedure, Enpasse suggests a result and cites every claim to its passage. Your lead QSA accepts, edits or enters their own, and that one act records the testing.
The finding follows the results. Enpasse never suggests a finding. It fills in from the recorded results, and one that contradicts them is refused, with the reason.
The decision records the testing. Accepting a result records the examination of the passages it cites, and the interview lines it cites. Observe stays your own entry.
Every requirement
on one wall
Testing shows all 260 sub-requirements, with counts that always add up. In Auto, Enpasse takes a first pass once the lead says all evidence is in, and brings what needs a person to the top.
Clean items, a few at a time. Accept these N takes every clean item on screen. Two random rows are read first, and anything waiting stays out, named with its reason.
Next needing me. One button opens the next item in report order: needs review first, then in progress. Worked out from records, never by AI.
One scope answer
settles what it decides
Each Scope question shows what it decides. A No drafts each Not Applicable reason, accepted on its page with the testing behind it. See Scope
Drafted by rule, accepted by a person
For a merchant, 25 questions decide 79 sub-requirements. Unsettled stays Not yet known, never guessed.
Know what
needs you next
One overview per assessment. Next is worked out from the records, never by AI, and client requests come first so replies are under way while you test.
The next step is always on screen
Each button opens the place to act. Counts from the records, never a percentage.
Follow up
with a record
A sample, an interview, a task or a gap feeds the result it bears on. Enpasse may suggest one with its passages; only the lead confirms, requests and closes it, and Enpasse sends nothing to the client.
Type any four digits and draw. The same code, list and size always give the same stores.
A reviewer can redraw your sample and get the same members
A fixed random draw picks the members, never AI, and every region gets at least one. Drawing and accepting are one act by the QSA, recorded with its draw code. Testing covered 3 stores, so the lead requested the other 2 by exact list, and one task tracks the wait.
An interview, in their own words. Each point quotes a participant with speaker and time. Testing that cites the lines records the interview.
Every open request, one text. Copy all requests gathers each open request for your own email. There is no send button, by design.
Closed by a person. A file or a result only says it may close a task or gap. The lead closes it and links the record that shows it.
The 6.2 statements,
cited
For each sample set, Enpasse suggests why the sample represents the population, each claim with its source. Your lead accepts, edits or writes their own.
Sizes are counts. Nothing rates a sample as adequate, and nothing shows a confidence.
Every three months,
on real dates
Scan reports are files, tested on 11.3.1 and 11.3.2. Each scan is counted or not, with its reason. A stretch over three months shows with its days, never as a calendar quarter.
No counted external scan from 5 Feb to 22 Jul, 167 days.
- Found in the reports, decided by your lead
- Enpasse finds each scan's facts with their page. Without AI, your lead enters them. A first assessment is flagged by rule, and your lead confirms it.
- Coverage by list, never by count
- Counts when the target list holds every in-scope target.
- Internal scans have no Pass or Fail
- High or critical found, with a count and the scan that resolves it.
- Section 5 comes from the record
- Every accepted quarterly scan lists in 5.1 and 5.3. 5.2 follows the attestations.
One named act
ends the stage
Sign off Assess opens only when nine gates hold. The lead checks the findings tally, confirms the client and approves by name, and the work freezes for drafting.