# Quick wins (https://systemhub.com/docs/quick-wins)

> Part of systemHUB Docs · Connect: Settings → AI Gateway in systemHUB · Auth: OAuth (scoping is workspace-level today — see Getting started) · MCP tools: 48 · Full corpus: https://systemhub.com/llms-full.txt

Copy-paste prompts to run with your connected AI (Claude, ChatGPT or any MCP-capable client) once systemHUB is connected. Every prompt on this page has been verified against the live systemHUB MCP server — each one maps to tools that exist today, so none of them will leave your AI apologising.

Not connected yet? Start with **[Getting started](/docs/getting-started)** or the step-by-step help article: [Connecting systemHUB to Claude + ChatGPT (AI Gateway / MCP)](https://kb.systemology.com/help-center/connecting-systemhub-to-claude-ai-gateway-/-mcp).

## Accountability

The reports that used to mean chasing people or exporting spreadsheets. Ten seconds each.

**1. Policy sign-off status**

> Check our [policy name] policy in systemHUB. Who still hasn't signed off on it? Draft me a friendly chase-up message for each person.

Returns the exact signed-off and pending lists with names and emails, from `get_document_agreement_status`.

**2. Training progress**

> How's the team going on the [training name] training? Show me who's done, who's mid-way and who hasn't started.

Returns per-person completion status and percentages, from `get_document_training_progress`.

**3. Ownership handover**

> [Name] is going on leave. List every system, policy and training they own so we can reassign them.

Returns everything they own across all three sections in one call, from `list_documents_by_owner`. Use the person's exact full name as it appears in systemHUB.

## Build and update

**4. Talk a process into a draft SOP**

> I'm going to talk you through how we [do a task]. Ask me questions until you've got it, then draft it as a system in systemHUB for my review.

The AI creates the document in systemHUB where your team can see and review it — not in a chat window that disappears. The full worked loop: [Draft an SOP](/docs/guides/drafting-sops).

**5. Keep a system current**

> Our [process] changed: [describe the change]. Find the system in systemHUB and update it to match, keeping the same format.

**6. Gap and contradiction scan**

> Search systemHUB for everything we have about [topic]. What's covered, what's missing and where do two documents contradict each other?

## Daily use

**7. Answer from your own systems**

> Using only our systemHUB, how do I [do the task]? Cite which system you're reading from.

**8. New-hire week one**

> We've got a new [role] starting Monday. Pull their relevant systems and trainings from systemHUB and build a week-one onboarding checklist.

**9. Share a system with an outsider**

> Get me a share link for our [system name] system that I can send to our new contractor — they don't have a systemHUB login.

Your AI calls `get_document_share_link`, then hands you the **human-readable** form — `https://{alias}.systemhub.com/systems/{uuid}/{shareCode}` — which opens the document in a browser with no login. (The raw `api.systemhub.com` version of the same code returns JSON, which is for programs, not people.) See [Sharing & links](/docs/concepts/sharing-and-links). Anyone with the URL can read it, so share deliberately.

**10. Who touched this document?**

> Who created our [system name] system, and who last edited it? Anything change recently?

Returns the creation and edit history from `get_document_activity_log`.

## What the MCP can't do yet

Stated plainly so your AI doesn't attempt it (see also [Known limits](/docs/#known-limits), [Errors & limits](/docs/concepts/errors-and-limits), and the [changelog](/docs/changelog)):

- **Workspace-wide "who viewed what" analytics.** Per-document activity (including views) is readable via the activity log, and sign-offs (a deliberate "I agree" click) are fully reportable — but for accountability, ask "who hasn't signed off", never "who hasn't read": a view proves nothing.
- **Inviting users or managing seats.** Assigning existing members and roles *to a document* works via the MCP; bringing new people into the workspace or changing licences is app UI only.
- **Deleting documents.** Blocked by design — your AI can create, edit, move and publish, but never destroy.

Next: **[Document lifecycle →](/docs/concepts/document-lifecycle)**