Running a readiness

  • 3:30
  • How-to
  • Narrated by Sekura
  • English
  • Updated Oct 2026

TranscriptClick a line to jump there

What Sekura says

0:00In this lesson you'll learn how to run a readiness: what the agents read, what they do, how to launch a run step by step, and what you get when it finishes.0:10A readiness tracks how much work a company has left before it can get certified, requirement by requirement. Running it means asking Sekit's agents to do the first pass: they propose a status for every requirement, and you review them afterwards.0:26What do the agents work from? What Sekit already knows about the company: its profile, its Knowledge base, the evidence already linked, and its asset inventory. For each requirement they also read what it asks for and what an auditor expects to see. A document counts once you evaluate it for the readiness, before or after the run.0:49Let's create one. Open the company, go to Gap Analysis and click New analysis.0:56For Framework, pick ISO 27001's management system, clauses 4 to 10. Under Evaluation type, choose Readiness.1:07The type can't be changed later, so choose carefully. Write a short Reason / context, such as "ISO 27001 certification", and click Start analysis.1:20The new readiness opens with every requirement still to be evaluated: the agents haven't started yet. To launch them, open More actions, the three dots in the page bar, and click Run analysis.1:34The Run this analysis? dialog tells you what will happen. Existing evaluations are kept. The run uses your AI credits and works in the background, so you can leave the page. Click Start analysis.1:47Here's what happens while it runs. The agents evaluate each requirement against the company's context. Then Sekura reviews all the verdicts together, and sends back any that look wrong for a second evaluation. Only then are they written to the readiness.2:04The page bar shows the last run as Running, and changes to Completed when it's done, so you can check on it whenever you come back.2:12When it finishes, every requirement has a status: Completed, In progress or Not started.2:19Open any row to read the Agent proposal, the agents' reasoning for that status. If you disagree, change it.2:27Here's an ISO 27001 readiness after its run. Twenty-five requirements evaluated: six Completed, nine In progress and ten Not started.2:39Take 9.2, the internal audit. The agents marked it Not started.2:45Its agent proposal says why: nothing the company has shared contains an audit programme, a plan or a report.2:53Tip. A tip: you can run it again at any time. A run only fills the requirements nobody has evaluated yet, so nothing you've already set is overwritten.3:04To recap. A run is the agents' first pass over a readiness. They work from what Sekit knows about the company. You create the readiness, then launch the run from More actions. And every status comes with the agents' reasoning, which you can check and change.3:21Thanks for watching! For more GRC lessons, visit our Learning Center at sekit.ai/learn-center.

Chapters

You'll learn

  • What running a readiness means
  • What the agents read, and what they do
  • Create and run a readiness, step by step
  • What you get when the run finishes

Try it

Do it yourself, in 3 minutes

Start a free trial. Sample data is already loaded, and the tour opens on this exact screen.

Start free trialAlready a customer? Open in Sekit

Key terms

Readiness
An assessment that tracks the work left before certification.
Run
One pass of Sekit's agents over an assessment, proposing a status for each requirement.
Knowledge base
The company's living notes in Sekit. The agents read it on every run.

NextAssessments

Keep going

Types of assessmentConcept · 4:07What a framework is, and when to run a readiness or a gap analysis.Review what Sekura wroteHow-to · 2:43Where Sekura's changes wait for you, how to read their reasoning, and how to settle them.The readiness planHow-to · 3:39Generate the readiness plan from a readiness, read each section, then edit it and share it.