Standardize Field Submissions

Standardize Field Submissions 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.

Create a fillable change request form so field engineers can submit scope or schedule changes consistently.

2 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
Create a fillable change request form for field engineers including requester, location,…
Create a fillable change request form for field engineers including requester, location, description, impact, and approvals, and publish the form to the team folder so engineers can submit consistently starting [deadline=Monday].

Improve — make it easier to accept

+
Before publishing the change request form, prefill project codes, make impact fields required, add…
Before publishing the change request form, prefill project codes, make impact fields required, add dropdowns for common categories, and include a one‑line help tip for engineers so submissions are complete and reviewable without clarification calls.

Who does this, and with what

The same task is different work inside a different job.

Project ManagerAdobe Acrobat ProMicrosoft Formsalso: Create Fillable Change Formalso: Enable Consistent Change Requests

Next to this one

Other send 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.