Most avoidable AER OneStop submission problems aren't caused by bad work in the field — they're caused by evidence and records that drift apart before anyone assembles the package. The fix isn't a bigger submission scramble at the end. It's a short, repeatable pre-check that runs upstream of OneStop, while issues are still cheap to fix.
Here's the operator-side checklist we build into field and office workflows.
1. Screen the location early
Before work is finalized, run the project location against regulatory layers, disposition boundaries, access routes, and environmental constraints. Most "surprises" at submission are visible weeks earlier on a map — if anyone looks.
2. Capture field evidence as structured data
Photos, notes, coordinates, dates, and inspection observations should be captured in a structure that's usable later — not scattered across phones, emails, and folders. The goal is evidence that's submission-ready the moment it's collected.
3. Validate dispositions against reality
Compare disposition records, internal asset records, GIS boundaries, and actual field status. Mismatches between what's on file and what's on the ground are one of the most common — and most defensible-when-caught-early — issues.
4. Track exceptions in a review queue
Missing evidence, mapping conflicts, incomplete records, and inconsistent data should land in a review queue with an owner — not get discovered the night before a deadline.
5. Assemble the package from clean inputs
When maps, photos, forms, notes, and attachments are already structured and validated, assembling a defensible submission package is the easy last step instead of the whole job.
The shift
None of this requires replacing your systems. It means moving from submission cleanup to submission readiness — embedding the checks into the work so compliance is part of the workflow, not a scramble at the end.