◆ Acrobat · edit

Capture Technical Evidence

Interview the applicant's chief engineer on [day=Tuesday] to clarify the technical variance — prepare a PDF with inter…

2heights
2tasks
1roles do it
See the prompt↓More edit workflows

The same job, four heights

do it · improve it · decide · become
AExecute — “help me do it”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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.
BImprove — “do it better”Make the [day=Tuesday] interview with the chief engineer yield clear factual conclusions —…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.

The real tasks

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

Who does this

1 roles
Government Program Officer

Questions people ask

honest answers

Because you rarely think 'I want the redaction tool'. You think 'I have to share this without leaking the client's details'. Start from the need, and the feature finds you.

Real. Every job here was drawn from what people in real roles were actually seen doing in Acrobat — not a feature checklist.

No. Each page gives you a ready prompt you can paste into an AI assistant, plus the plain steps to do it yourself. Start with either — the goal is the finished job, not the tool.