Document survey operations

I need the survey operations document finalized and shared with the field team by Tuesday. Convert the draft notes into a clear procedures section that lists daily tasks, who does them, and the acceptable time windows; add a short checklist for the lead and a one-paragraph escalation path for delays. Save as Survey_Ops_V2.docx and attach to the email to Maria in Field Operations and Raj in Compliance, signing off myself first.

Before I send this to the field team, make the operations doc easy to follow under pressure — surface the daily critical tasks at the top, turn long paragraphs into numbered steps, bold who owns each step, and flag any dependencies that would make a supervisor hesitate to deploy a crew.

We just finished a pilot week and the field supervisor says crews missed several time windows but won’t say why in the meeting. I’m worried the schedule is unrealistic or the checklist is unclear, and I can’t tell if crews lack capacity, transport, or clarity. What’s the most likely diagnosis and the best next move to test it without delaying rollout?

Across three projects we keep getting late starts and incomplete daily logs from the crews, which costs two days of follow-up per week. Where are we losing time or clarity in how we write procedures and checklists, and what single habit should we change to make field teams meet windows and complete logs consistently?