The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+There are 18 invoices stuck in the validation queue that must go to Accounts Payable by Wednesday…
Execute — do the immediate task
+There are 18 invoices stuck in the validation queue that must go to Accounts Payable by Wednesday to meet vendor terms. Check that invoice numbers, supplier names, amounts, and remittance codes match the AP master, correct any mismatches, and mark each validated row as Approved with my initials. Then save the workbook as the payment batch and upload to the portal.
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 I send the batch to AP, make the invoice sheet easier for the approver: put the total…
Improve — make it easier to accept
+Before I send the batch to AP, make the invoice sheet easier for the approver: put the total payable at the top, highlight invoices with mismatched GL codes in amber, and create a single column that explains, in one line, why any invoice was adjusted. Also add a short note for the AP reviewer explaining that invoices over $10,000 need director sign-off.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I found three invoices flagged with GL codes that don’t match the purchase order. I’m the payments…
Decide — diagnose the stuck moment
+Three invoices flagged with wrong GL codes
I found three invoices flagged with GL codes that don’t match the purchase order. I’m the payments clerk; the vendor is due Thursday and the procurement lead is unreachable. I can’t tell if I should change the GL to get the payment out or hold and risk late fees. What is the safest immediate decision and exactly how should I document it so I don’t break audit trail?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep scrambling the day before payment runs because invoices lack correct GL codes or approvals…
Become — change the pattern
+We repeatedly scramble before payment runs
We keep scrambling the day before payment runs because invoices lack correct GL codes or approvals and AP rejects the batch. It wastes a day per run. What one change to the way we capture invoice metadata and one audit control to add would stop last-minute fixes and ensure the batch passes AP validation consistently?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Accountant AssistantAuditorBilling SpecialistBookkeeperFarm AccountantInventory Accountantalso: Process invoices and financial dataalso: Prepare customer invoices and accept payment.
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.