AuditSahi
Create a free account

How it works

A year with AuditSahi.

It begins with a few plain questions about your organisation. From the answers, AuditSahi works out which rulebooks apply and what each one asks. Then the year runs in five parts, and a person in your company approves each one.

  1. 1

    It writes your policies.

    Eleven kinds of policy come up again and again across Indian rulebooks. AuditSahi drafts each one your rulebooks ask for from the obligations that apply to you, so every paragraph cites the clause it answers and the frequencies you chose are written into the text. You start the year with the policies written, not with a blank page.

    Where a draft needs a fact nobody has given it, such as the name of the director who chairs a committee or how long backups are kept, it leaves a marked blank. The draft is a starting point for your own people or your adviser.

    The eleven kinds of policy

    • Information security policy
    • Cybersecurity policy
    • IT policy and governance framework
    • Risk management policy
    • Access control policy
    • Change and release management policy
    • Incident response policy and procedure
    • Cyber Crisis Management Plan
    • Business continuity, disaster recovery and backup policy
    • Outsourcing and vendor management policy
    • Data protection and privacy policy

    What a draft contains

    • Each paragraph cites its clausepara 22, Directions 2026
    • Frequencies you set, written inquarterly, annual
    • Marked blanks for missing facts[[NEEDS: retention period]]
    • A check of the text before you see itnumbers and clauses traced
  2. 2

    You approve them.

    The Board, or the person your rulebook names, approves each policy. AuditSahi records who approved it, the date and the meeting reference, and the approved text is kept as a version so an auditor can see exactly what was in force and when.

    Approval satisfies the clauses that ask for a policy to exist. It does not satisfy the clauses that ask for something to have happened, such as a drill or a test. AuditSahi shows you both lists before you approve, so nothing is marked done by accident.

    What is recorded

    • Who approved itthe approvers named
    • When, and at which meetingdate and reference
    • The exact text approvedkept as a version
    • Which obligations it settlesexistence, not practice
  3. 3

    Every duty that recurs has a date and an owner.

    Quarterly reviews, annual tests, half-yearly committee meetings and incident reporting windows sit on one calendar. Where the regulator fixes the frequency, that frequency applies and nobody can soften it. Where it does not, you choose one and it is written into your policy.

    Each duty has an owner: the person named on the duty, else the one person your organisation named for everything, else the account holder. When a duty is done, the date it was done is recorded and the next date is counted from there. A duty nobody has recorded yet shows as not started, never as overdue.

    For each recurring duty

    • Frequencyfrom the clause, or chosen
    • Ownerduty, organisation, account holder
    • Last done and next duefrom the recorded date
    • Historyevery completion kept
  4. 4

    Each obligation is checked against the evidence.

    Upload a policy, a set of minutes, a test report or a vendor agreement. Each obligation is broken into the specific things it requires, and each is checked independently against the document. The result marks the obligation covered, partly covered or not addressed, quoting the line in your document that decided it. A verdict without a quote is not counted.

    Where the checks agree, the verdict stands. Where they disagree, the item is set aside for a person in your company to decide, and that decision stands.

  5. 5

    The audit pack is ready when anyone asks.

    The pack is the record of the year: which rulebooks apply and why, every obligation with its status, the document and the line behind each answer, the approvals with their dates, and the open items in order of severity. It prints the day the auditor, the Board or the regulator asks for it.

    Beside the obligations, the pack and the What applies page list the voluntary standards worth adopting for your organisation, such as ISO 27001, with the reason for each. They are not counted as obligations, but they show where the work done for the regulator also helps you win larger customers.

    In the pack

    • What applies, with the clause that says soper rulebook and tier
    • Coverage, obligation by obligationwith the quote
    • Approvals and completionswho, when
    • Open itemsmost serious first

See it on a sample organisation first.

The demo opens on a fictional NBFC with two documents already read, so you can see each of the five parts before you upload anything of your own. No account needed.