Inconsistent Site Documentation

Inconsistent Site Documentation in Adobe Acrobat — with a ready prompt for the moment it comes up. 1 real situation leads here.

1prompt height
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.

My site documentation often becomes useless because it isn't organized consistently.

1 ready prompt

Written for the moment this actually comes up.

Become — change the pattern

+
Across my last [N=18] site visits, teams wasted time because photos were unlabeled and measurements…
Across my last [N=18] site visits, teams wasted time because photos were unlabeled and measurements lacked context. Identify the pattern in how I currently record and store site data, recommend a single standard file structure and naming convention for photos and notes, and suggest one routine I can adopt on site that will make post-visit assembly painless.

Who does this, and with what

The same task is different work inside a different job.

Landscape ArchitectAdobe Acrobat

Next to this one

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