The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The lab manager needs the calibration record updated and the technician's sign-off appended. Send…
Execute — do the immediate task
+The lab manager needs the calibration record updated and the technician's sign-off appended. Send the attached calibration spreadsheet to Carlos in maintenance and then to Mei in quality for their e-signatures, in that order, with a Friday close — verify every instrument serial number matches the equipment list first.
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 give this to maintenance, surface the most recent failed calibration at the top, highlight…
Improve — make it easier to accept
+Before I give this to maintenance, surface the most recent failed calibration at the top, highlight any drift beyond tolerance in red, and make the corrective action column short and prescriptive so a technician can act without hunting through notes.
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
+We ran the standard on Pump 4, the reading was 3.4% high, and the technician wrote 'can't…
Decide — diagnose the stuck moment
+A calibration failed and the tech left a note saying 'can't reproduce'.
We ran the standard on Pump 4, the reading was 3.4% high, and the technician wrote 'can't reproduce' in the comments and left at 4pm. I'm Carlos, responsible for equipment uptime. I'm worried the pump is drifting overnight and we'll miss batch specs; I can't tell if the note hides an incomplete check or a transient fault. Do I schedule an immediate re-check tonight, escalate to quality, or log it as intermittent and monitor? Which gives the fastest safe outcome?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last quarter we lose an hour per instrument chasing vague comments, and we repeatedly…
Become — change the pattern
+Calibration records routinely come back with vague technician notes and late sign-offs.
Over the last quarter we lose an hour per instrument chasing vague comments, and we repeatedly recheck the same units. I own calibration accuracy. Which habit change would cut repeated checks and late sign-offs: require a two-line standard comment template, enforce time-stamped photos of the test readout, or mandate scheduled calibration windows with assigned techs? Recommend the single best change and how to enforce it this 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.
Environmental Health OfficerLab Technician ChemistryPcr Molecular Lab TechnicianSoil Testing TechnicianWater Quality TechnicianCoatings Inspectoralso: Calibrate testing instruments against standardsalso: Calibrate and maintain laboratory equipment
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.