Tuesday, 11:20 · One comment on one policy
It starts with six words in a comment.
“Is this still what we do?” A colleague leaves it on the access control policy. It is a small comment with a long tail: three other documents quote that rule, and two customer answers were built on it last quarter.
First, see what depends on it.
Lea opens the policy and follows its links. The rule appears in the onboarding standard, the supplier answer set and a register entry with a different owner. Before she changes a word, she can see everything the change will touch, which is the part that normally gets discovered too late.
- Linked policies, standards and registers
- Owner, version, status and review date on every document
- Version history with the reason for each change
Follow that comment yourself
Open the linked policy, ask the question, then build a controlled pack. Sample data.
POL-01
Information security policy
- Owner:
- Head of Security
- Version:
- 3.2
- Status:
- Published
This policy sets how information is classified, handled and protected. It applies to all staff, contractors and systems.
Roles and approval authority are held in the role register and referenced here, not repeated. See .
Access is granted on least privilege and reviewed quarterly. The review procedure is defined in .
Retention periods are defined per data category in and are binding for all systems.
Linked sources:
The comment becomes a reviewed change.
The wording is proposed, checked against the source and approved by a person. The assistant can draft and cite, but it cannot quietly rewrite a policy. Once the change is approved, every answer that leans on that rule is drawing from the corrected version.
- Comments become proposed changes
- A human approves before the document changes
- Dependent answers follow the approved wording
The shortcut everyone takes
A general AI will answer anything. It just does not know your company.
Asked in a general chatbot
The reply reads well and sounds certain. It describes how a company like yours usually handles access reviews. It does not know your rule, your version, your owner or what you already told this customer last year. Someone still has to verify every line before it can be sent.
Asked inside your own documents
The same question is answered from the policies your company actually maintains, and the answer names the documents it used. Lea opens the wording, sees who owns it and when it was last reviewed, and forwards it. The verification is the answer, not a second job.
And the question does not come back.
When the same question arrives in the next questionnaire, the answer is there with its source attached, and the reviewer can inspect it without a call. Lea keeps her attention for the questions that are genuinely new. That is the quiet part of this that matters most.
- Full-text search and tag filters
- Cited, read-only assistant
- Scoped access for external reviewers
How the knowledge base works
Document control
- Owners, versions, status and tags
- Linked policies, standards and registers
- Version history, differences and change reasons
Review and retrieval
- Full-text search and tag filters
- Action owners and due dates
- Cited, read-only assistant
Controlled sharing
- Selectable PDF and Markdown packs
- Branded contents and page numbering
- Restricted notes excluded from exports
Access
- Role-based access
- External reviewer access
- Mobile-friendly vault and export
The work around the documents stays visible
Policy work is never one person. Reviews, evidence and open actions can be tracked directly in iquerion, or in the tool your organisation already runs, so nobody has to chase status in a chat thread.
Track it in iquerion
Actions, owners, due dates and review status sit next to the document they belong to.
Track it in Jira
Work items can be created and kept in sync with your existing Jira projects and workflows.
'/%3e%3cpath%20d='M30.4189%2019.0625C30.4189%2021.2234%2028.6676%2022.9747%2026.5067%2022.9747C24.3458%2022.9747%2022.5946%2021.2234%2022.5946%2019.0625C22.5946%2016.9016%2024.3458%2015.1504%2026.5067%2015.1504C28.6676%2015.1504%2030.4189%2016.9016%2030.4189%2019.0625ZM14.1889%2021.8853C15.0476%2023.3432%2017.1584%2023.336%2018.008%2021.8728L21.0562%2016.6279C22.6447%2014.0359%2024.4406%2012.6496%2026.6856%2012.3437C27.2294%2012.2704%2027.7625%2012.1452%2027.9074%2011.3259L28.741%206.65169C28.8823%205.97194%2028.3635%205.33154%2027.6677%205.33154C23.5766%205.33154%2018.8184%206.954%2015.1066%2013.0396L12.062%2018.2772L14.1889%2021.8853Z'%20fill='url(%23paint1_linear_40000205_3911)'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_40000205_3911'%20x1='1.66667'%20y1='7.99984'%20x2='14.5556'%20y2='26.6665'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%23AB40FF'/%3e%3cstop%20offset='1'%20stop-color='%235D2BFF'/%3e%3c/linearGradient%3e%3clinearGradient%20id='paint1_linear_40000205_3911'%20x1='24.7776'%20y1='7.11107'%20x2='15.3428'%20y2='21.0749'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%23AB40FF'/%3e%3cstop%20offset='1'%20stop-color='%2327039D'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
Track it in Productive
Tasks and delivery work can run in Productive, with the document as the reference point.
Integrations are configured during setup for the tools you use. The document stays the single source; the task tool stays where your teams already work.
Where we stop
- No self-service signup or public customer vault.
- The assistant proposes answers. It does not silently change policy.
- Endpoint security and security operations remain outside the product.
Which request is holding up your next decision?
Bring the assessment, the audit request or the IT question. We will map the evidence and the next hand-off with you.