The moments that lead here
If one of these is your afternoon, you are in the right place.
Set and enforce archive retention policies for teller transaction records with IT so audits always find the right versions.
2 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Coordinate archive retention with [team=IT]: assemble sample transaction PDFs, propose retention…
Execute — do the immediate task
+Coordinate archive retention with [team=IT]: assemble sample transaction PDFs, propose retention durations, create a reusable library template for teller records, and ask [team=IT] to apply access controls so audits can always find the right versions.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before finalizing retention rules with [team=IT], make the policy practical for auditors: provide…
Improve — make it easier to accept
+Before finalizing retention rules with [team=IT], make the policy practical for auditors: provide examples of required documents and retention periods, include naming conventions and versioning rules, request automated archiving to the branch archive with indexed metadata, and ask [team=IT] to produce a test retrieval by audit date.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Bank TellerAdobe Acrobat ProSharePointalso: Approve Payment Exceptionalso: Verify Transaction Integrity
Next to this one
Other record work people do in Adobe Acrobat.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.