No account needed. Answer the questions, pay securely, and receive your deliverable.
Name shown on the deliverable
Shown on the deliverable.
Keep this field from the AI: its content is replaced before the AI provider receives it, then restored in your deliverable.
Deliverable
You set its title, author and structure.
As it will appear on the result.
Shown as the author of the deliverable; never filled in by the AI.
Purpose of the scope
What this scope is for, and who answers for it.
It decides the vocabulary of the document.
What the certificate or programme has to prove, and to whom.
Function of the person who keeps it up to date.
What the scope takes into account
Clause 4.3 asks you to consider your issues and the requirements of interested parties.
What in your market, your rules and your structure affects this scope.
One row per entry, e.g. “Bank partners; ISO/IEC 27001 certificate covering the gateway; Partner contracts”
What is in scope
Name what is covered; anything not named is outside.
Offices, warehouses, data centres, cloud regions.
E.g. “Merchant onboarding”.
E.g. “Payment gateway”, “Microsoft 365”.
Categories only, never the data itself.
Interfaces and exclusions
Where the scope stops, and what it still depends on.
One row per entry, e.g. “Hosting provider; Hosts the platform; Provider for infrastructure, we for configuration; Contract, SOC 2 report”
One row per entry, e.g. “Payroll; Outsourced and unrelated to the platform; HR data stays with the provider”
Anything the service should take into account.
What the AI provider receives
Your answers, to write this deliverable.
Replaced first, then put back in your deliverable: Email addresses, People's names, Company names.
