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 raw time log from last week's site sessions with start and stop timestamps and a separate…
Execute — do the immediate task
+I have a raw time log from last week's site sessions with start and stop timestamps and a separate sheet of activity codes. Calculate operative times for each activity per technician, then produce a single column of total operative minutes per technician for Friday's review. Check for overlapping intervals and for any gaps larger than 15 minutes that look like missing stops before you finalize.
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 hand this to the project leads, make the operative-time output easy to trust: surface each…
Improve — make it easier to accept
+Before I hand this to the project leads, make the operative-time output easy to trust: surface each technician's total operative minutes at the top, show the three largest activity blocks and flag any day with overlapping timestamps or gaps over 15 minutes, and make the calculation transparent by adding one-row notes that show which rows were excluded and why.
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
+I merged start/stop timestamps and summed operative minutes per technician, and now two technicians…
Decide — diagnose the stuck moment
+I ran the time-merge and totals but some technicians have operative minutes exceeding their shift length.
I merged start/stop timestamps and summed operative minutes per technician, and now two technicians show totals larger than their rostered shift. I suspect overlapping intervals or duplicated entries from device syncing, but I don't know which days or which entries to treat as duplicates without losing legitimate work. What is the most likely cause and the safest next step to resolve it before reporting totals to operations?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across several projects we keep finding overlapping intervals and then hand-editing the…
Become — change the pattern
+Recurring audits show repeated timestamp overlaps and manual corrections.
Across several projects we keep finding overlapping intervals and then hand-editing the spreadsheet, which eats time and makes audits harder. Recommend one habit change and a small enforcement rule that will reduce rework and preserve an audit trail, so we stop fixing the same timestamp errors every week.
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.
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.