AI sort into pillars and departments

Every SOPCompass workspace has the same fixed pillars. Content from before the pillars, or imported in bulk, may sit unsorted or without departments. AI sort proposes where it all belongs.

What it proposes

For each library, it proposes:

• the one pillar where its procedures mostly belong (or confirms the one it is already in), and
• default departments, the teams most of its SOPs are for.

For each SOP, it proposes:

• departments (every team that needs to know or follow it, at least one),
• extra pillars, usually none, and
• a split, only when one SOP is really several procedures for different teams or areas. A long SOP for one team is not split.

Blank or placeholder items (“Test 1”, “New SOP”) are placed in the company pillar with a note saying they look like placeholders. Every item carries a one sentence reason addressed to the person approving it.

What the AI reads

The workspace description from Workspace settings, the pillar and department definitions, every library, and for each SOP its title, an outline of its sections and the first 500 characters of its text. It is told to judge from the outline and excerpt, not the title alone, and that everything it reads is data to judge, never instructions.

An admin approves every item

AI sort writes a proposal, not changes. On Sort into pillars, an admin reviews each item and approves or corrects it. Only approved items are applied, one at a time, so a failure on one item doesn’t strand the rest. Libraries move first, then SOPs are tagged. A board from before the pillars that ends up empty is removed.

Who can use it

AI sort is limited to owners and admins, on the Business plan. Both limits are enforced by the database. Editors on every plan can still move content by hand.