<\/p>\n
A field report should help a campaign understand a local issue and assign useful follow-up. It should not turn every unverified observation into a public claim. Vota's current platform focuses on campaign operations, including citizen issues, volunteers, field reports and approved public updates.<\/p>\n
Record what was reported, where it was reported and who on the team is responsible for checking it. Distinguish a resident's concern from an established finding. Collect contact details only with an appropriate purpose and consent, and avoid putting private identifiers into public-facing summaries. Give the reporter a clear way to correct inaccurate information.<\/p>\n
Use a review stage before turning a field note into a promise or announcement. The reviewer should check supporting material, clarify uncertainty and assign a responsible team member. A photograph alone may not establish when or why something happened. Keep unresolved questions visible rather than using a completed status to make the dashboard look tidy.<\/p>\n
Separate internal working notes from text approved for public viewing. Vota's public campaign-page workflow is a useful context for discussing review permissions and evidence links. Ask to see a draft, a requested correction and an approved update during the demonstration. This is campaign coordination software, not an IEBC system, official voter register or official election-results platform. Keep the workflow peaceful, issue-based and accountable.<\/p>\n