Advice sized to your organisation
ISMS Copilot sizes its recommendations, controls and documents to your organisation, keeps what a requirement or your risks call for, and names what you can remove when it reviews your plan.
What it does
In Fast and Think answers, ISMS Copilot sizes its recommendations, controls and documents to your organisation: your headcount, the data you handle and how sensitive it is, your sector and legal obligations, and your stage. It works from your company profile, your workspace's project instructions and what you said in the conversation.
- When your size is unknown and it matters, it states the size it assumed in one line, so you can correct it.
- When your sector or data suggests regulation, it leans to the fuller control.
- It prefers the smallest adequate control: one that meets the requirement, treats the risk, and that you will actually run.
- It adds nothing that neither a requirement nor a risk calls for: no extra process, tooling, roles, documents, approvals or review cycles, unless you ask for the fuller version.
- When it is not sure a requirement applies, it keeps it and says why.
- It applies a size exemption only where the framework or law provides one, and names the basis.
- The depth stays. Sizing changes what it recommends, not how thoroughly it explains: you still get the reasoning, the requirement behind each point and the steps.
When it reviews your plan or document
When you give it a plan, a design or a document to review, ISMS Copilot looks for what is more than your organisation needs as hard as for what is missing. It names what can be removed or simplified and says why each item can go. It adds a new item only when a requirement or an identified risk calls for it.
How to get the most from it
- Tell it who you are. Fill in your company profile (open Company context in the sidebar) with your size, sector, country and the data you handle. For client or project work, put the same facts in the workspace's project instructions. What to include: Provide organizational context.
- Ask for a review before you finalise. For example: "Please review this before I finalize it."
- Ask for the fuller version when you want it. If you prefer the more extensive set of controls or documents, say so.
- From Claude x ISMS Copilot or ChatGPT x ISMS Copilot, the same applies. Answers your AI gets from ISMS Copilot over the connection follow the same approach. See ISMS Copilot in Claude and ChatGPT and Run your ISMS with Claude and ISMS Copilot.
An example
A made-up 12-person SaaS company shares its security plan: a full-time CISO, a 24/7 security operations centre (SOC), 38 policies reviewed every quarter, and a weekly board meeting that approves every deployment.
ISMS Copilot suggests:
- a part-time security lead instead of a full-time CISO;
- centralised logging with alerting, and an incident response plan, instead of a 24/7 SOC;
- 8 to 12 core policies, reviewed once a year;
- a change record and a second reviewer for deployments, instead of board approval.
It keeps MFA, encryption and tested backups. It adds what the plan was missing: a risk assessment and an asset inventory.
Scope
This applies to Fast and Think answers in the web app and in Slack, and to answers given to connected AIs over MCP and the account API. Beyond mode follows later. The answer is a recommendation: you decide what stays.