Policy Reviews Across Dense Documents

Electron App · Deep Research

Turn Dense Policy Packs Into Clear, Cited Review Work

Use Deep Research to read dense policy material, pull out obligations, compare revisions, and keep the review trail easy to revisit.

Research Question

Extract obligations, compare versions, identify ambiguities, and preserve the review context so later policy updates are faster and more traceable.

Kendr Electron app Deep Research workspace for policy review

Output package

Cited policy summary, material-changes log, obligation list

The review should stay readable and fully traceable.

Decision motion

Move from dense policy packs to clear operational review

The point is fast understanding without losing the evidence trail.

Reusable memory

Policy memory for the next update cycle

Keep the prior review alive so future updates start ahead.

Focus

Obligations, version diff, ambiguity, risk

Show what changed and what still needs human judgment.

Source families

Policy docs, memos, external references

Bring internal guidance and external authority together.

Output package

Summary, change log, obligation list

Keep the deliverable useful for legal, policy, and operations teams.

Knowledge retention

Policy memory + update cycle

The next policy review should inherit this one.

Primary workflow

Deep Research

Compare obligations, effective dates, and conflicts across large document sets.

Secondary value

Knowledge Base

Preserve prior review context so future updates can be handled faster.

Why Kendr

Dense input, clear trace

Long-form review stays readable because the output comes back cited, structured, and easy to revisit.

Launch workflow

Use these prompts with real policy packs or regulations. Later, replace the placeholders with actual summary outputs, change logs, and tracked obligations from Kendr.

What The Team Needs

A legal or policy team needs fast extraction of obligations, differences between versions, and a map of what still needs human interpretation.

What Kendr Should Produce

A cited review summary, a redline-style comparison of major changes, an obligation list, and a searchable session for the next review cycle.

Prompt Samples

Run These In Kendr

Prompt 01 · Review Summary

Review the attached policy and source documents for [topic].

Identify:
- major obligations or requirements
- effective dates and time-sensitive provisions
- sections that appear ambiguous, conflicting, or operationally risky
- where a human reviewer should pay special attention

Separate clear extraction from interpretation and cite the source section for every major point.

Prompt 02 · Version Comparison

Compare version A and version B of this policy set.

Produce:
- the most material changes
- obligations added, removed, or tightened
- operational impact of each meaningful change
- a short section called "questions for counsel or policy owner"

Keep the output concise but fully cited.

Prompt 03 · Policy Memory

Create or update a KB session named policy-review-[topic]-[date].

Store the reviewed documents, comparison notes, extracted obligations, and final summary artifacts.

Then provide:
- what this KB now covers
- the key unresolved interpretation areas
- what should be monitored in the next policy update cycle

Example Deliverables

What The Team Gets Back

Policy summary

Insert the cited review summary from Prompt 01.

Material changes log

Add the top changes and operational impact from Prompt 02.

Open interpretation questions

List where human review still matters.

Policy KB session

Show the saved session and what later reviewers inherit.

Join Early Access