Write work-related reports

Write work-related reports — real work, not an imagined feature: named inside 21 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.

21career 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 have a 10‑page quarterly report for the county ag office that must go to the director and the…
I have a 10‑page quarterly report for the county ag office that must go to the director and the board on Friday. Send the attached draft to Julie in governance and then to Martin the director for e‑signature, in that order, with a Friday deadline. Before sending, check the executive summary shows the three headline metrics, the budget variance, and the single recommendation; return it only if all are present.

Improve — make it easier to accept

+
Before I send this quarterly report to the board, make the argument easy to scan: put the three…
Before I send this quarterly report to the board, make the argument easy to scan: put the three headline metrics and the budget variance at the top, bold the one recommendation, mark any figures that changed >10% since last quarter, and flag any data that lacks a named source or owner so a reviewer can clear it quickly.

Decide — diagnose the stuck moment

+
I sent the draft report to Paula in audit and she replied only: 'Need source files.' I can't tell…

I just got a terse reply from the auditor asking for source files.

I sent the draft report to Paula in audit and she replied only: 'Need source files.' I can't tell if she means raw data, the spreadsheets, or QA notes. Paula expects full traceability and will delay sign‑off if anything is missing. What is the quickest, defensible package to send right now that keeps us on the Friday board deadline and limits rework?

Become — change the pattern

+
Every quarter I lose credibility because the board says our executive summary buries the numbers.…

We repeatedly miss the preferred executive summary format.

Every quarter I lose credibility because the board says our executive summary buries the numbers. Over three reports we reorganize at the last minute and end up firefighting data pulls. Which habit should I change so the summary is correct first time: a checklist for each metric, a required data‑owner signoff before drafting, or a one‑page template that enforces the summary layout? Explain the tradeoffs and recommend the fastest cultural fix.

Where the evidence lives

Who was seen doing this, and what people really ask.

Agriculture ConsultantAgronomistCrop ScientistPark Ranger AidePrecision Agriculture SpecialistSeed Production Specialistalso: Write research reports and articlesalso: Write technical reportsalso: Write reports for colleagues or clients
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.