Operate surveying instruments

I need the instrument log and field notes from yesterday assembled into a single, signed report for the lab manager and the regional surveyor, due Friday. Combine the GPS readings, calibration checks, and observation photos into one document, confirm the instrument serial numbers and firmware versions, annotate any outlying readings, and sign at the end. Check completeness before sending.

Before I send this to the regional surveyor, make the findings easy to verify: put the mean offsets and confidence interval on the first page, show the raw GPS traces next, flag any timestamps where calibration drift exceeded tolerance, and mark the photos that correspond to those timestamps so a reviewer can audit in ten seconds.

I finished the survey and logged that the east‑station instrument read consistently high but I didn’t have a spare calibration kit on site. The regional surveyor expects precise offsets and the lab manager will want a corrected dataset. I’m worried re‑running will push deadlines and trigger extra QA. Is it better to reopen the field tomorrow to recalibrate and remeasure the suspect points, or to include an adjusted correction with full raw traces and documented uncertainty? Advise the likely risk to deliverables and the best next move.

Across projects we lose hours because GPS logs, calibration entries, and photos are saved separately and reviewers chase missing serial numbers or timestamps. I need one habit change that stops this cleanup loop: what single step during every field session will prevent incomplete reports, how to make the team adopt it, and what simple verification should trigger before any report leaves my desk?