Compliance Evidence Collector
See which of your controls have fresh evidence and who must collect the rest.
What installing it brings
- 1 workflow20 steps in what runs behind it.
- 1 screenThe pages of its application.
- 1 tableThe data tables it works with.
About this application
See which of your controls have fresh evidence and who must collect the rest. Paste your control list (control id, requirement, evidence expected, owner, frequency) from your SOC 2, ISO 27001 or internal spreadsheet, and the list of evidence files you hold (file name, date, owner, short description, link as text). Code matches each file to a control by the control id in its name or by the words they share, then counts from the control's own frequency, plus the days of grace you set, whether the newest file is still recent enough. Every control becomes a card on your Evidence board: Covered (a file matches and is within its period, not reviewed yet), Stale, Missing or Needs a person, and you move a card to Accepted once you have checked it. For the controls the rules could not match, an AI step may propose one file with a quote of the control and a quote of the file, and code checks both quotes word for word before the proposal is shown. A file you refuse is never proposed again. Copy the gap list, grouped by owner, or as CSV. Settings: framework name, run date, days of grace, renewal warning, date order, match by words, AI proposals and how many controls the AI examines, language, and preview only. Needs no account. Nothing is uploaded, fetched or sent, a Drata or Vanta read comes later, and Covered never means compliant: this is not an audit opinion. When someone leaves, see Offboarding Access Sweep.
The published app, exactly as it runs.
This preview is not interactive.
The workflow
What runs behind it: 20 steps, 1 screen.
Published by
livecontext
@livecontext