When you ask whether something is required

Half the questions people ask while tailoring a document are the same question wearing different clothes: do we actually have to?

Do we have to keep this register. Do we have to name an owner. Is it a problem that we do not have one. It is the question that decides how much work the next month holds, so it is the one an answer has to be right about — and "right" here does not mean confident. It means traceable.

Every answer names where it came from

When the assistant tells you something is required, mandatory, optional, or fine to leave out, it names the clause that says so. Not as a flourish at the end — as the source the sentence rests on.

That is a rule the product enforces, not a habit it has. If a reply reaches that point without a clause behind it, it does not go out: the assistant reads the clause first and answers again from the text. You will occasionally notice the difference as a slightly longer pause on that kind of question. That pause is the clause being read.

A clause number on its own is not enough. The assistant also carries working guides for each part of a management system, and those guides say which clauses they touch. A guide is a map of the requirement, not the requirement itself, so an answer that only repeats what a guide says, clause number included, is sent back the same way: the clause is read and the answer is written again from its text.

Where there is nothing to read — the question is about a framework that is not in your catalogue, or the text does not settle it — you get told exactly that, and no verdict. The same holds when you tell it you will skip something a standard may require: it reads the clause before it goes along with you, and tells you whether skipping leaves a gap. An honest "I cannot tell you from what I hold" is the answer the rule asks for. A confident guess is the thing it exists to prevent.

Required to do it, required to write it down

These are different, and the difference is where most of the confusion lives.

A clause can require an outcome — that you have worked something out, that you have decided it, that you know who is responsible — without requiring any particular document to show it. The outcome is not negotiable. The register, the log, the spreadsheet is the usual way people demonstrate the outcome, and usually not the mandated one.

So the answer to "is this register mandatory?" is often two answers:

• the thing the clause actually requires, which you do have to do;
• the artefact you were asking about, which is expected rather than demanded, and which you may replace with something else that shows the same thing.

The assistant is expected to give you both halves. Collapsing them into one — "yes, it is mandatory" or "no, it is not" — is how a true sentence turns into a misleading one.

When you push back

Tell the assistant it is wrong and it will not simply agree with you.

It re-reads the clause and answers from the text again. It may agree with you, disagree, or tell you that you are each right about a different half — which is the most common outcome, because the two halves above are usually what the disagreement is about. What it will not do is reverse its position because you sounded certain. A changed answer comes with a clause you can check; it does not come with an apology.

This is deliberate, and it is worth knowing about, because the alternative is worse than it looks. An assistant that folds under pressure gives you the answer you already believed — which means it has told you nothing, at exactly the moment you were checking.

If you think it has the clause wrong, quote the text at it. That is a new source, and a new source is precisely the thing that is allowed to change the answer.

What this does not do

• It does not predict what an auditor will decide. It tells you what the framework requires and where you stand against it. Two auditors can read the same evidence differently and neither of them works here.
• It is not legal advice. Where a question turns on law rather than on a framework, you get the compliance view and a line saying so.
• It cannot tell you about a framework you have not added. The catalogue is what it reads; nothing else is in scope, and it will say so rather than improvising.

See also

• AI review and assistance — how the assistant works generally, and what every AI change leaves behind.
• Documents the assistant writes — how a document is designed with you and created.
• Standards knowledge — the requirements, guidance, regulations and working methods it reads, and how it keeps the four apart. A method is never the answer to "is it required": the clause is what is required, and a method is one way to meet it, recommended only where it fits you.

When you do not know the clause

You do not have to name a clause to get an answer that names one. Ask in your own words — "do we have to write down which issues affect our management system?" — and the assistant first searches the knowledge base by meaning, then reads the requirement its best match points to, and only then tells you what is required, citing that clause. The search narrows the question to a clause; the clause is what the answer rests on. If the search is unavailable on an environment, the assistant says so and still reads any clause you can name.