The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I finished reconciling the month-end ledger and attached the trial balance. Send the reconciliation…
Execute — do the immediate task
+I finished reconciling the month-end ledger and attached the trial balance. Send the reconciliation report to Lidia in accounting and then to Marco in finance for e-signature, in that order, with a Friday deadline. Before sending, confirm every account on the attached trial balance matches the general ledger totals and that the variance column is explained. If anything is off, flag the account and an estimated impact in the body of the email.
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 this reconciliation to accounting, make it easy for Lidia to sign off — surface the…
Improve — make it easier to accept
+Before I send this reconciliation to accounting, make it easy for Lidia to sign off — surface the unexplained variances at the top, put supporting source entries next to each variance, and highlight any negative ending balances. Also create a one-line summary that says what I changed this month and why a reviewer might hesitate so she can approve quickly.
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 reconciled the bank and GL and found a $14,752 unexplained variance on account 4100. The ledger…
Decide — diagnose the stuck moment
+I discovered a $14,752 unexplained variance on account 4100 during reconciliation.
I reconciled the bank and GL and found a $14,752 unexplained variance on account 4100. The ledger entries for June are posted, Lidia is the accounting reviewer, Marco signs for finance, and the month closes Friday. I’m worried this is either a missed journal or a misposted deposit, and I can’t tell which ledger rows to trust without more time. What’s the most efficient next move to isolate whether this is a posting error, a timing issue, or fraud, and how do I present the finding to Lidia so she can act before close?
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 finding small material variances like $5k–$25k during the last two days of the month; it…
Become — change the pattern
+Repeated late discoveries of small but material variances at month close.
We keep finding small material variances like $5k–$25k during the last two days of the month; it forces rushed journals and missed explanations. Lidia and I trade incomplete notes and Marco rejects entries for lack of backup. What habit should I adopt in the monthly close to catch these earlier and reduce rework — daily cutoffs, a short variance dashboard, different inbox rules — and how would I implement it so the team adopts it starting next month?
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 AssistantAccountantAuditorBilling SpecialistBookkeeperChartered Accountantalso: Prepare financial recordsalso: Check accounting records
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.