> For the complete documentation index, see [llms.txt](https://docs.prove.ly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prove.ly/readme.md). # Welcome to Provely Provely is a **Continuous Compliance Assurance** layer: policy control, campaign delivery, and audit-ready evidence, in one cycle. It keeps your policies current, delivers only what changed to only the people it affects, and makes their understanding provable on demand. The division of labor is the point: > **Provely does the work — Compliance makes the decisions.** Your team already does everything right, and the gaps happen anyway — because search, compare, coordinate, send, chase, document is a manual loop that never closes. Provely closes it, and keeps it closed. ## It starts with the map Tell Provely your company type, your countries, and your policy areas, and it renders your **obligation map**: every applicable country and category, and whether a current, provable policy stands behind it. Every red cell is a gap you can name — and a one-click path to closing it. Before Provely does anything for you, it shows you where you stand. See [Mapping your obligations](https://docs.prove.ly/compliance-users/organizational-mapping). ## One cycle, from policy change to verified understanding 1. **Map** — obligations per entity and country, and what stands behind each. 2. **Upload a policy** into the gap it closes. New versions are detected or uploaded as they happen. 3. **AI drafts** what the change means for people: readable sections, a plain-language glossary, comprehension questions, an attestation clause. Every draft is **source-linked, explainable, and approval-controlled**. 4. **A human approves.** Compliance is involved at Approve — and at exceptions. Nothing reaches an employee unreviewed, and the approval itself is recorded, versioned, and hashed into the evidence. 5. **The right people get it** — only what changed, only who it affects — read, answer, attest, usually on their phone. 6. **Evidence accumulates** in an append-only record, automatically. 7. **Audit readiness is calculated** from that evidence — never ticked off by hand. 8. **Export the proof** whenever you need it — or have it delivered on schedule. On Continuous plans, the cycle reopens itself: a new policy version, a new joiner, or a lapsing refresh triggers the next round under rules you configured — see [Staying current](https://docs.prove.ly/compliance-users/campaigns). ## Management by exception The whole program condenses into three calculated states: **Current** (approved policy, delivered, understanding verified — nothing to do), **In progress** (drafts, approvals, campaigns, reminders — Provely is chasing, not you), and **Action required** (the short list that genuinely needs a human: material changes, uncertain mappings, exceptions). States are derived from the evidence records — never typed in, never stale, never optimistic. ## Evidence, not a distribution log Your current tools track activity; Provely proves outcomes. The evidence stands on its own: append-only records, an independently recomputable SHA-256 integrity hash over the evidence itself, the full approval chain, and [privacy as a data boundary](https://docs.prove.ly/data-protection-and-security/data-protection). When the regulator asks how you ensure your people understand a policy, you hand them evidence — not a distribution log. Provely **sits on top of** your existing policy, HR, and learning systems — no replacement, no migration. Unlimited policies, frameworks, and campaigns on every plan; you [pay for people assured, nothing else](https://docs.prove.ly/plans/plans-and-billing). ## Who uses Provely **Administrators and compliance officers** map obligations, approve content, launch campaigns, monitor readiness, and export evidence. They sign in with an account. **Recipients** are your employees. They receive an email, follow a personal link, and complete a short flow — usually on their phone. They don't need a Provely account: their identity is proven through your organization's own Google Workspace sign-in. ## Where to start If you're evaluating Provely or explaining it to an auditor, start with [Core concepts](https://docs.prove.ly/core-concepts/core-concepts) — five ideas that make the rest of the product self-explanatory. If you want to see your own map, the free pilot does it in one session: map your obligations, then prove one — see [Plans and billing](https://docs.prove.ly/plans/plans-and-billing). If you're ready to run your first campaign, jump to [Creating a campaign](https://docs.prove.ly/compliance-users/campaigns). If you've just received an invitation email, see [You've received an invitation](https://docs.prove.ly/for-recipients/receiving-an-invitation). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prove.ly/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.