Loading…
Stage 2 · Evidence
Ask the auditee for what a control needs, and have it come back filed against that control — not buried in a thread.
Requests sit against the control they belong to — the reply files itself there.
The problem
You ask for a document. It arrives in an email, or on a shared drive, or not at all, so you ask again. When it does come you still have to work out which control it belongs to and which version you were sent — and that same conversation is running in parallel across dozens of requests.
What Kimova does
You ask for what a control needs. Kimova handles everything between asking and having it on file.
You bringA request raised against the control that needs it
The document filed there on arrival, with the exchange attached
You bringOne auditee, invited once
A view holding their requests — and nothing else of the engagement
You bringA question in plain language
An answer with a citation you can open, or an honest "not in your evidence"
What it changes
Request, reply and file are one record, so you never scroll a thread to work out which version you were sent.
An auditee sees the requests meant for them and nothing else, so collaboration doesn't mean exposure.
Interrogating hundreds of pages in plain language replaces the afternoon you'd spend opening documents.
Send us a policy set and we'll show you the questions it can already answer — with citations you can check.
Book a 30-minute walkthroughThe audit, end to end