Collect samples and measurements

Collect samples and measurements — real work, not an imagined feature: named inside 7 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.

7career 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 an organized worksheet to collect samples and measurements from the plant tomorrow: list…
I need an organized worksheet to collect samples and measurements from the plant tomorrow: list fields for sample ID, operator, line number, time, temperature, pH, water activity, weight, visual notes, preservation batch number, and chain-of-custody signer. Make the order optimized so a line tech can write while holding a clipboard and a QA analyst can sort later.

Improve — make it easier to accept

+
Before I hand this form to QA, make it easy to use on the line: put time, line number, and sample…
Before I hand this form to QA, make it easy to use on the line: put time, line number, and sample ID at the top, make temperature and pH adjacent, remove any unnecessary free-text boxes, flag fields that must be filled before samples leave the line, and highlight the chain-of-custody signer field.

Decide — diagnose the stuck moment

+
We collected 48 samples this morning but roughly half lack recorded times and two have no operator…

We collected samples but half the times are missing

We collected 48 samples this morning but roughly half lack recorded times and two have no operator name. The shift supervisor says the clipboard was handed off during a rush. I’m worried the missing timestamps will invalidate trend analysis. What is the most likely reason for these gaps and the next three corrective actions to salvage the dataset before reporting to QA?

Become — change the pattern

+
Over the last six audits our sample logs repeatedly miss timestamps and operator IDs, costing us…

Sample sheets routinely arrive with incomplete critical fields

Over the last six audits our sample logs repeatedly miss timestamps and operator IDs, costing us retests and delaying reports. Suggest one change to the form, one training habit for operators at shift handover, and one enforcement step for supervisors that will stop this bleed.

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.