Capture Technical Evidence

Capture Technical Evidence in Adobe Acrobat — with two ready prompts: the immediate one, and the one that makes it stick. 1 real situation leads here.

2prompt heights
1situation
1role does it
Open it in the interactive atlas →

The moments that lead here

If one of these is your afternoon, you are in the right place.

Interview applicants or technical staff to clarify facts that affect licensing outcomes.

2 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
Interview the applicant's chief engineer on [day=Tuesday] to clarify the technical variance —…
Interview the applicant's chief engineer on [day=Tuesday] to clarify the technical variance — prepare a PDF with interview questions, add a comments field to record answers, and attach the signed interview notes to the file.

Improve — make it easier to accept

+
Make the [day=Tuesday] interview with the chief engineer yield clear factual conclusions — prepare…
Make the [day=Tuesday] interview with the chief engineer yield clear factual conclusions — prepare a PDF interview guide with targeted technical questions, add fillable fields for verbatim answers and follow‑up actions, instruct the interviewer to initial key factual claims, and attach any supporting documents as comments to the file.

Who does this, and with what

The same task is different work inside a different job.

Government Program OfficerAdobe Acrobat ProMicrosoft Wordalso: Interview To Clarify Licensingalso: Record Applicant Statements

Next to this one

Other analyse work people do in Adobe Acrobat.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.