Evidence Intake
Upload Evidence
Add audit evidence to the repository, then analyze it to generate readiness outcome, evidence strength, mapped controls, missing evidence, corrective actions, and risk rationale.
Before UploadUse clear, audit-friendly evidence
Prefer approved, dated, version-controlled, owner-visible documents. Evidence should show what control exists and how it operated.
After UploadAnalyze from Repository
Upload stores the file and metadata. Analysis runs separately from Repository so one document uses one AI generation call.
Deployment ReadyMetadata is stored in cloud-ready fields
Framework, control area, owner, notes, and upload source are sent with the file so the same structure can later move to Supabase.
📄
Click or drag a document here
Supported: PDF, DOC, DOCX, XLS, XLSX, CSV, TXT
No file selected yet.
Suggested file naming patternISO27001_AccessControl_UserAccessReview_FY2026_v1.pdf
Rename files before upload when possible. Readiv stores the original file name, suggested name, metadata, and document content for later analysis.