PlannedDiscover
Describe the work and CoMap lists the requirements it finds, each with its source. It also says where it searched, so you know what it could have missed.

CoMap has read them. Describe the work and it will find what applies, show the exact passage, check your document against it, and warn you when the pages change.
The policy people must work from is large, scattered and often unread. It used to live in the heads of colleagues who stayed for decades. People move on sooner now, and the memory that used to catch mistakes has gone with them.
Policy also changes faster. Work goes out with something missing that should have been caught, then stays in use while the rules it rests on move.
You need the source at the point of work, then another check when either side changes.
The same source record stays with the work from the first question to the evidence pack.
Describe the work and CoMap lists the requirements it finds, each with its source. It also says where it searched, so you know what it could have missed.

Your own policy joins the same requirements picture, each requirement tied to its source paragraph.
Write with help that is grounded in current sources. You stay accountable for every line.

Any governed document is checked against an approved scope, requirement by requirement. Each one is marked Covered, Gap identified or Needs review. There is never a verdict.

Scheduled rechecks watch for change in the work or in the policy beneath it.

Close the gaps the check found. Any improvement ideas are marked as the model's own reasoning, not as a sourced finding.

The evidence pack records what was checked, against which sources and with which assumptions, and hands the next owner a current briefing.
Ask across the public policy library. Each answer points to the document, version and paragraph. Asking across the documents you are allowed to use is planned.

Every line written with AI help is either grounded in a named document, version and paragraph, or clearly flagged as ungrounded. The two never look the same.
CoMap maps coverage and identifies gaps. It does not decide whether your work complies. The map is yours to act on.
You will be able to see where content lives, who can use it and whether a hosted model is ever allowed to read it.
Your documents stay inside their workspace scope. They are never mixed into the shared public library.
Only include what your organisation's handling rules allow. For UK public-sector organisations that means nothing above OFFICIAL.
Connected documents stay in SharePoint or wherever they already live. CoMap keeps only the evidence and processing records it is allowed to keep.
CoMap does not train on your private content.
CoMap is invite-only while it is in preview. You can request an account, or sign in if you already have one.