Evaluate current and historical financial data

Evaluate current and historical financial data — real work, not an imagined feature: named inside 6 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

6career tasks name it
4prompt heights

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 need the latest income statement and the last five years of monthly cash flow on one sheet so I…
I need the latest income statement and the last five years of monthly cash flow on one sheet so I can present performance to the finance director. Put current year-to-date and prior year-to-date side by side, show percent change, and highlight any quarters where operating cash turned negative. Before I send it, check formulas for hard-coded dates or rollups that would break on next month.

Improve — make it easier to accept

+
Before I hand this to the audit manager, make the trends obvious and the anomalies explainable:…
Before I hand this to the audit manager, make the trends obvious and the anomalies explainable: surface the three-year CAGR for revenue and EBITDA at the top, show rolling 12-month cash on hand, and flag months where receivables grew faster than sales. Add a one-line note next to each flagged line proposing likely causes: delayed collection, one-off write-down, or seasonality.

Decide — diagnose the stuck moment

+
I reconciled the general ledger import to my consolidated workbook and found a $1.2 million…

Downloaded updated GL and my consolidated sheet now shows a $1.2M variance for March.

I reconciled the general ledger import to my consolidated workbook and found a $1.2 million mismatch for March operating expenses. The controller, Priya, is on leave and the month is due to close tomorrow. I don’t know whether the error is a mapping problem in my import, a late journal from the field team, or a duplicated row. What should I check first to diagnose the source, who should I call now, and what’s the fastest way to prevent this from corrupting the rest of the year’s rolling totals?

Become — change the pattern

+
Every month we lose a morning reconciling the GL import: column mappings shift, new nominal codes…

Spreadsheets keep breaking when we import monthly GLs.

Every month we lose a morning reconciling the GL import: column mappings shift, new nominal codes appear, and someone overwrites the prior month’s sheet. It costs credibility with the business and delays forecasts. Help me design one repeatable habit that stops those daily fires: what three rules should I enforce for the import and one change to the workbook structure that prevents accidental overwrites?

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.