PlyLoom / Use cases
A new version of a document is out. What do we do?
A policy, a contract, a standard or a law has changed. You need to see what exactly changed, which processes it touches and who does what by when — and show it to management in one memo.
The example is fictional. It opens in the demo as a separate working copy; PlyLoom sends nothing anywhere.
What you end up with
- Impact memo (HTML)Changes with clause numbers, affected processes, actions with owners and due dates, open questions. Opens in a browser, prints to PDF.
- The same memo in Word (.docx)Headings in the navigation pane, a linked table of contents, page numbers and the map version in the footer; from there it is an ordinary document to edit.
- Action checklist (CSV for spreadsheets)A row per action: owner, due date, status.
- Change × process matrix (CSV)Which change touches which process; the last column counts the processes touched.
Every file above was assembled from the example map with Project → Assemble — no AI and no network. Each document names the map version it was built from.
Who it is for
Analysts, lawyers, quality and compliance specialists, heads of shops and departments — anyone who receives a new version and the question “what does this mean for us”.
Why a map rather than one document
One change touches several processes, and one process several changes. In a document this becomes cross-references that drift apart at the first edit. On the map a change is one entity: it stands on the changes sheet and next to the processes it touches, and the memo, the checklist and the matrix come from one source.
Sheets of the example
- Changes — What changed between versions 2 and 3 — one node per change, with clause numbers in both versions.
- Affected processes — Where the changes alter the shop's work. The “affects” relations come from the changes.
- What to do — Actions with an owner, a due date and a status. The rollout checklist is assembled from this sheet.
- Questions — What to ask the author of the policy. A question without an answer stays open.
- 🔒 For me — Personal notes. The sheet is private: it never goes to an AI or into a file for someone else.
How to work
Alone, no AI
- Open the example and look at the sheets: Changes, Affected processes, What to do, Questions and the private For me.
- For your own document: one node per change, with clause numbers in both versions; place the change next to every process it touches as well.
- Project → Assemble a document makes the memo; save the settings as an assembly, and from then on it is one button in the menu. Assemble a table makes the checklist and the matrix.
With a colleague
- Project → Download .plyloom → “For someone else — without private parts”; What goes out shows the file before it is saved — your own assessments on For me are not in it.
- The lawyer edits their copy and sends the file back.
- Compare with a file shows their edits item by item: you accept the ones you want, and your private parts are not offered for deletion.
With an AI
- AI → A new map from materials… → the task “A new version: what we must do”; attach both versions in the chat.
- Paste the answer into the same window: PlyLoom shows the map before it appears.
- Check every change against the clause numbers in its attributes — a draft is checked against the document, not taken on trust.
Ready-made prompts
These are tasks for the end of a prompt. In the app, the AI menu: its window holds the base of the prompt, your map and the field for the answer. Private sheets, nodes and attributes never reach the prompt.
A new version: what we must do
Compare the two attached versions of the document “[name]”. Sheets: “Changes”, “Affected processes”, “What to do”, “Questions”. Each change is a node of its own with the attributes clause_old (text: the clause in the old version, or null), clause_new (text: the clause in the new version, or null), change (select: added, removed, changed, moved) and source (text: clause and page). Our processes and roles: [list them]. Link each change to every process it affects. For each affected process, add an action on the sheet “What to do” with the attributes owner (text), due (date or null) and status (select: not started, in progress, done). A change that touches several processes is one entity on several sheets, not a copy. Mark renumbering without a change of meaning as “moved”. Everything unclear becomes a node of type question.
Answer open questions
Find nodes of type question that no relation answers points to yet. For each, add 1–3 answer nodes linked to the question with answers and carrying the attributes source and confidence (if the dictionary lacks them, define them with define: source as text, confidence as a number 0–100). If there is no reliable answer, say so in the node, with confidence 30 at most. At the end, propose up to 3 new questions (type question) that came up, each linked to the node it is about.
Change it, assemble again
An action's due date moved — change the attribute on one node and assemble again: the date changes in the memo, the checklist and everywhere the action is mentioned. Version 4 arrives — compare, accept the edits item by item and assemble again; the new memo carries the new map version in its header.
Limits
- PlyLoom does not compare document texts by itself: you, or an AI at your request, lay out the changes, and you check them.
- The example is fictional: the shop, the policy and the clauses are invented.