Questions, answered

Click Get started, then use Proto to configure GRC Audit Compliance for your business. Start with one organization, business unit, assessment period and active control, then rehearse a test, finding and independent review.

Name the organization, business unit, owner, subject, period and planned tests. Agree the control scope before testing begins.

Yes. Risk records carry likelihood, impact and scale version, then link to controls with effective dates and named owners.

A test line records its assessment and control, tested date, sample size, exception count, result and evidence reference.

A failed or inconclusive result can lead to a finding with severity, description, assessment and control. Assign correction work with a due date and evidence.

An Independent Reviewer records an approve, reject or return decision against the source revision, with a date and reason.

A separate reviewer records a retest. A passing independent retest supports closure. The Independent Reviewer also decides the submitted assurance review revision, and closure completes after the resulting effects are saved. Keep the corrective action and earlier result linked to the finding.

Evidence attachments include an internal or shared visibility choice. Set access for each organization and role during implementation.

Check the operation receipt, expected revision and persisted effects before repeating the request. A failed or uncertain receipt stays visible for investigation.

Use Operations Overview for assessment, test, review decision and failed-operation context, then open the relevant record for detail.