Analyze chemical substances

Analyze chemical substances — real work, not an imagined feature: named inside 3 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.

3career 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 lab report and reference spectra for a new fertilizer compound that need formal write-up…
I have a lab report and reference spectra for a new fertilizer compound that need formal write-up and signature. Merge the spectra images into the methods section, insert the IUPAC name in the title page, run spellcheck and the chemistry-specific glossary, update the table of contents, export as a locked PDF, then send the PDF to Dr. Ramos in quality assurance and to the department head, Maria Ortega, for signature by Friday at 5 p.m. — confirm the PDF shows page numbers and that the spectra images are legible before sending.

Improve — make it easier to accept

+
Before I send this analysis to procurement and the registrar, make the chemical identification easy…
Before I send this analysis to procurement and the registrar, make the chemical identification easy to verify: put the main substance name and CAS number on the first page, show the purity percentage and method of detection up top, put the spectra thumbnails next to the result so a reviewer can eyeball a match, and flag any missing references or units that would make a lab manager hesitate to sign off.

Decide — diagnose the stuck moment

+
I merged the GC-MS spectra into the methods section and the document now goes to Dr. Ramos and…

I merged the spectra but one peak didn't match the reference

I merged the GC-MS spectra into the methods section and the document now goes to Dr. Ramos and Maria Ortega. One peak in the sample doesn't match the supplier reference and I don't know if it's contamination, instrument error, or a different isomer. I'm worried QA will stop the signature process and delay shipment. What is the most likely cause and what exact three steps should I take now to resolve or clearly communicate the uncertainty to QA and the department head?

Become — change the pattern

+
Every month a report stalls in QA because reviewers ask for raw spectra or chain-of-custody details…

repeatedly getting delayed approvals over small data discrepancies

Every month a report stalls in QA because reviewers ask for raw spectra or chain-of-custody details I didn't include. I lose two days per report on back-and-forths. Which single habit change will prevent those stalls, what five checklist items should I always include in the document header, and how should I phrase one line that preempts the most common reviewer question?

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.