# How to Find What a Policy Actually Requires of You

> Policies are written to cover the organisation, not to be read. Find your obligations.

Published 2026-07-28

Policy documents are written to protect the organisation that issued them, which is a different goal from being understood. The parts that create actual obligations, deadlines, and consequences are scattered through pages of scope statements and definitions. Finding them is what turns a document you signed for into one you have read.

The obligations can be located. Whether a policy is enforceable, or what it means in a dispute, is a question for a qualified professional.

## Why are they so hard to use?

Because they are drafted defensively. A policy has to cover every case the organisation can anticipate, satisfy whatever regulation applies, and survive review by people whose job is to close gaps. Readability is not among the goals, and there is rarely anyone whose role is to advocate for it.

The practical effect is that the sentence affecting you sits between two paragraphs of scope definition, expressed conditionally, cross-referenced to an appendix. People sign acknowledgements for documents they have not read, which is the outcome the format produces.

## What should I actually look for?

Five things carry nearly all the consequence:

- **Obligations on you.** Look for shall, must, and required. These are the mandatory parts, and they are what a breach is measured against.
- **Deadlines and timeframes.** Reporting windows, notice periods, and response times.
- **Consequences.** What happens if something is not done, and who decides.
- **Exceptions and approvals.** Which situations are exempt, and who can grant an exception.
- **Scope.** Whether the policy applies to you at all, which is often narrower than it first appears.

The modal verbs are the fastest route in. Scanning for must and shall finds the operative sentences considerably faster than reading front to back.

## How do I use it?

1. Open the [Policy Document Summarizer](/ai/agents/policy-document-summarizer).
2. Upload the policy.
3. Review the obligations and deadlines it identifies.
4. Read those sections in full before relying on them.

Free includes an overview and one AI answer per document, with files up to 15MB and 50 pages.

The summary points you at the paragraphs. For anything you are acting on, read the actual text, because the wording of an obligation is what matters and a summary necessarily compresses it.

## What kinds of documents does this suit?

| Document | Why it helps |
| --- | --- |
| Employee handbooks | Long, rarely read, full of obligations |
| IT and security policies | Specific requirements with real consequences |
| Expense and travel policies | Deadlines and approval thresholds |
| Codes of conduct | Reporting duties people miss |
| Data protection policies | Obligations that vary by role |
| Vendor and supplier policies | Contractual requirements passed down |

The recurring pattern is a document issued once, acknowledged immediately, and consulted only after something has gone wrong.

## Where does this stop being enough?

Summarising tells you what a document says. It cannot tell you whether a provision is lawful in your jurisdiction, whether it conflicts with your employment contract, or what would happen if it were tested.

Those questions matter when a policy is being used against you, when it conflicts with something else you have signed, or when the consequences are serious. At that point the people to ask are your union representative, an employment lawyer, or the relevant regulator, depending on the situation. A summary is a starting point for that conversation rather than a substitute for it.

## What if the policy is a scan?

Older handbooks and policies frequently exist only as scans, [containing images rather than text](/blog/cant-search-or-copy-text-in-a-scanned-pdf). Nothing can be read until a text layer exists, so run [OCR](/tools/ocr-pdf) first.

Check recognised text carefully where numbers are involved. A misread notice period or threshold changes the obligation entirely.

## Common questions

### Can it tell me if a policy is fair?

No. Fairness depends on context, law, and what else you have agreed to. It can tell you what the document requires, which is the necessary first step to forming any view.

### What if two policies contradict each other?

Upload both and compare what each requires. Where they genuinely conflict, that is a question for whoever issued them, and it is worth raising in writing.

### Can I ask questions about a specific section?

[Chat with Doc](/ai/chat-with-pdf) lets you query a document directly and cite the page, which suits targeted questions better than a full summary.

### Is my document stored?

Files transfer over encrypted connections and are permanently deleted within 15 minutes of processing unless you save them to your library.

## Read your policy properly

Upload it to the [Policy Document Summarizer](/ai/agents/policy-document-summarizer), find the obligations, then read those sections in the original.

---

Open this page in a browser: https://fynepdf.com/blog/find-what-a-policy-actually-requires-of-you

More: [All tools](https://fynepdf.com/tools) · [AI agents](https://fynepdf.com/ai/agents) · [llms.txt](https://fynepdf.com/llms.txt) · [Sitemap](https://fynepdf.com/sitemap.xml)