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 have the internal control review due Friday for the accounting team and need to send the…
Execute — do the immediate task
+I have the internal control review due Friday for the accounting team and need to send the recommended policy changes to Marcus in Internal Audit and to Jenna, the CFO, for approval, signers in that order. Check the checklist and the evidence folder first to make sure every control gap cited has supporting file names and dates, then assemble the cover email that explains residual risk and the implementation deadline of October 1.
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 present policy edits to Marcus in Internal Audit, make it easy for Jenna and the finance…
Improve — make it easier to accept
+Before I present policy edits to Marcus in Internal Audit, make it easy for Jenna and the finance directors to approve: put the high-risk gaps and proposed mitigations at the top, quantify the estimated annual error exposure in dollars, attach the exact evidence file names and dates next to each finding, and flag any change that will require headcount or system work so reviewers know whether a separate business case is needed.
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 just finished a walkthrough and found bank reconciliations are performed on different cutoff…
Decide — diagnose the stuck moment
+I reviewed controls, found inconsistent bank reconciliation timing across regions.
I just finished a walkthrough and found bank reconciliations are performed on different cutoff dates in Europe and the US, and Marcus in Internal Audit will see that as a repeat deficiency. I do not know how entrenched local practice is or whether local accountants will resist standardizing. Are we facing a documentation-only fix or will this need process training and a deadline for harmonization? Recommend the most defensible next step and a short rationale for Marcus.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every quarter we reopen the same three control exceptions and waste time re-auditing the same…
Become — change the pattern
+We keep re-opening the same control findings across quarters.
Every quarter we reopen the same three control exceptions and waste time re-auditing the same transactions. I cannot keep chasing signatures and local remediation plans. Tell me one habit to change in how we close the loop so remediation actually sticks across regions, and give a practical first-week tactic I can roll out with Marcus and local controllers.
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.
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.