Supervising fieldwork
You keep fieldwork moving and its quality visible: who is assigned to what, which double entries disagree, and which flagged responses need a decision. You supervise collection; you do not read the dataset as an analyst does.
What you are responsible for
Field assignments, double-entry adjudication and the quality decision on responses flagged for review. You are not responsible for analysis, exports, consent records, survey design or user administration, and the platform refuses each of those to this role.
Where you start
Signing in takes you to Field Operations, the field assignments view. It lists who is assigned to which project and what is outstanding. Your navigation also carries Operations Queue and Data Quality, and nothing else: every entry is a page whose server routes accept this role.
Assigning and verifying field work
- Assigning enumerators and double-entry work uses the collection.manage permission, which this role holds.
- Adjudicating a double-entry disagreement uses collection.verify, which this role also holds.
Quality decisions
Data Quality shows responses flagged for review in your organization. You can approve or reject a flagged response; every decision is recorded with who made it and when, and a reversal is recorded as a reversal.
Your task queue
Operations Queue shows human tasks whose gate needs a permission you hold (here, quality review) and the open data-quality issues. The agent-plan and usage panels on the same page need permissions this role does not hold, and say so rather than showing data.
When something goes wrong
| What you see | What to do |
|---|---|
| A panel says a permission is required | That panel calls a route outside this role. It is the boundary working, not a fault; ask an Organization Admin if your work needs it. |
| Field Operations is empty | No assignments exist for your organization yet, or the project filter excludes them. |
| A flagged response cannot be found | It belongs to another organization or was removed. Decisions are always scoped to your own organization. |
Limits worth knowing before you plan around them
What this role cannot do, and what the platform does not offer
- This role cannot read or export the dataset (no data.read, no data.export) and cannot run or read analyses.
- It cannot read or record consent, edit a survey, invite users or configure integrations.
- On Field Operations, the readiness, finalization-queue and review-queue panels refuse this role: their routes carry role lists that do not name it. Assignments, sync health and quality assessment work.
- There is no per-enumerator quality score and no live enumerator map. The platform does not compute either.