Documentation
A public guide that explains what each part of Atlas FieldOps is for, who uses it, what to prepare, what happens after each action, and how field data becomes trusted operational evidence.
Atlas FieldOps helps organizations plan field work, build forms, assign teams, collect data online or offline, review submissions, clean imported records, track entities, map activity, measure KPIs, and produce governed reports.
The workspace follows the real operating flow: organization settings, projects, entity categories, forms, assignments, submissions, approvals, data quality, maps, metrics, reports, and audit history.
Data becomes ready for dashboards, exports, entities, and reports after it is submitted or imported, reviewed where required, cleaned when needed, approved, and linked to the right project, form, entity, location, user, and time period.
Sector packs and custom project settings change the language and templates for agriculture, health, education, retail, inventory, logistics, audits, HR, humanitarian work, government programs, research, and custom operations.
Start here
Create a project, build a form, publish it, assign it to field officers, then let officers sync the form in the mobile app.
Open the published form data page, upload the spreadsheet, map columns, clean rows in the grid, then confirm clean rows for review or use.
Activate an entity category in the project, link a registration form to that category, map profile fields, and approve registration submissions.
Use approved submissions and clean imported data. Connect metrics or KPIs where needed, then open Reports or Dashboards with project and date filters.
Use Users & Teams, role assignments, project/location scope, form permissions, and Governance audit trails. Frontend hiding is not enough; backend permissions enforce access.
Assign forms, entities, and locations, confirm mobile rules, let officers sync once online, collect offline, then sync queued submissions when connected.
How the platform works
Atlas FieldOps is built around the way field organizations actually work: configure the context, collect evidence, review it, and turn approved data into action.
Choose a sector pack or custom setup, define projects, locations, teams, entities, KPIs, approval rules, and reporting needs.
Create forms for surveys, inspections, stock counts, registrations, delivery proof, audits, training, complaints, or custom workflows.
Send the right forms, entities, locations, boundaries, and instructions to field officers, supervisors, stores, routes, facilities, or assets.
Capture responses, GPS, timestamps, photos, signatures, files, barcodes, linked records, and draft work even when connectivity is weak.
Run approvals, corrections, duplicate checks, GPS validation, spreadsheet-style cleaning, data quality review, and audit logging.
Approved data updates entities, maps, dashboards, KPIs, reports, exports, supervisor queues, and management decisions.
Module ecosystem
The public pages now show Atlas FieldOps as one operating system: projects sit at the center, and every module contributes to collection, control, analysis, or action.
Sector setup, locations, teams, KPIs, reports, and project health.
Enterprise form builder for surveys, inspections, audits, stock counts, checklists, and mobile workflows.
Assignments, field officers, supervisors, targets, work plans, and monitoring.
Review queues, approval workflows, corrections, attachments, quality flags, and audit history.
GIS maps, boundaries, coverage, GPS validation, and spatial issue discovery.
Sector, geography, forms, teams, entities, rules, collection, and reporting stay anchored to the same project context.
KPI library, targets, baselines, calculations, trend tracking, and disaggregation.
Standard reports, custom dashboards, client outputs, scheduled delivery, and exports.
Duplicates, outliers, missing data, GPS issues, validation failures, and risk alerts.
Audit trails, policies, approvals, retention, consent, compliance, and data stewardship.
Reference data, integrations, notifications, API settings, backups, and system defaults.
Role context
Create the organization structure, invite users, assign roles, set permissions, configure reference data, and keep governance settings understandable.
Role context
Create projects, choose the sector context, define locations and entities, attach forms, assign field teams, and monitor progress.
Role context
Review submissions, approve clean data, return records that need correction, manage imports, clean spreadsheet uploads, and protect data quality.
Role context
Assign field officers, review daily work, approve field visit requests, check sync status, and follow up on returned submissions or quality issues.
Role context
Use the mobile app to download assigned work, collect data, save drafts, capture GPS/media evidence, and sync submissions when connected.
Role context
Read approved summaries, dashboards, reports, maps, and exports without changing operational records.
Beginner workflow
Most organizations should follow this order so forms, assignments, submissions, entities, maps, and reports stay connected.
Create or join the correct organization. Confirm users, teams, permissions, locations, reference data, and platform settings before operational data collection starts.
Choose the sector or custom setup, define geography, entity categories, KPIs or metrics, forms, teams, governance rules, and readiness requirements.
Create questions, validation, logic, entity links, duplicate rules, workflow, mobile controls, permissions, and review readiness before publishing a stable version.
Send published forms, locations, entities, and tasks to the right field officers or teams so the mobile app only shows authorized work.
Field officers collect on mobile or web. Data managers can upload spreadsheet data into published forms and clean rows before confirming them.
Supervisors or data managers approve, reject, return, or archive submissions. Approved records become official evidence for entities, metrics, maps, and reports.
Ready data feeds entity profiles, project dashboards, GIS maps, quality scorecards, metric tracking, exports, reports, and management decisions.
Architecture
Every record keeps its organization, project, entity, form version, user, location, review state, and audit trail so data can move safely from mobile capture to dashboards and reports.
Multi-tenant
Tenant isolation
Offline-ready
Mobile sync
Governed
Audit history
Tenant, users, roles, branding, security, plans, and audit policy.
Sector context, geography, entity categories, teams, forms, KPIs, and governance.
People, households, facilities, products, stores, assets, cases, routes, or custom records.
Mobile-ready surveys, inspections, audits, inventory checks, registrations, and follow-ups.
Every record keeps tenant, project, entity, form version, location, user, status, and audit context.
Field, web, uploaded, imported, returned, corrected, approved, or rejected records.
Validation, duplicates, GPS checks, missing data, outliers, conflicts, and reconciliation.
Maps, metrics, dashboards, reports, exports, donor/client views, and management actions.
Data use
A visitor should understand immediately: raw data is captured first, then reviewed and cleaned, then promoted into official records, dashboards, maps, KPIs, and reports.
Mobile/Web/Import
Approve/Return/Clean
Entities/KPIs/Maps
Reports/Dashboards/Exports
Final result: trusted operational intelligence
Approved submissions update entity profiles, quality dashboards, GIS layers, KPI progress, supervisor queues, reports, and governed exports.
Documentation maintenance rule
01
Users sign in to an organization workspace, see only the modules allowed by their role, and start from Dashboard for the current operating picture.
How it works: Organization, role, permissions, access scope, and audit logs control what each user can view or change.
02
Projects organize program context, donors, geography, teams, indicators, forms, submissions, reports, and governance. Surveys organize baseline, monitoring, registration, endline, and other M&E activities inside a project.
How it works: Managers create project setup, select sector guidance, define locations, attach forms, configure teams, and activate the project when ready.
03
Forms are the data collection tools. Users build questions, configure validation, entity rules, permissions, workflow, data quality controls, mobile readiness, and publishing rules.
How it works: Draft forms can be saved and edited. Published forms create stable versions for assignments and mobile sync.
04
Managers assign field officers to projects, forms, locations, entities, visits, and operational activities. Supervisors can approve movement requests and monitor field progress.
How it works: The field officer profile shows assignments, supervisor relationship, devices, permissions, submissions, performance, and activity history.
05
Field officers sign in, sync assigned work, collect data offline, save drafts, capture GPS and media evidence, queue submissions, and sync when connected.
How it works: Mobile bootstrap downloads profile, permissions, assignments, projects, forms, locations, entities, rules, and returned submissions.
06
Submitted records arrive in the web app for review. Reviewers approve, return, reject, or archive records based on quality, evidence, and governance rules.
How it works: Approved data can feed entities, indicators, reports, dashboards, maps, and audit history. Unapproved records stay visible but should not count as official results.
07
Users can upload spreadsheet data into forms, map columns, see missing fields, clean rows in an Excel-like grid, and confirm clean data for review.
How it works: Uploaded and imported records keep source labels, import batch context, row issues, and cleaning status so they are not confused with live field submissions.
08
Entities such as farmers, households, facilities, schools, groups, and other records are the long-term records connected to approved submissions.
How it works: Approved entity-linked forms can create or update entities, generate stable codes, preserve profile lineage, and send conflicts to reconciliation.
09
Data Quality helps teams investigate duplicates, missing values, outliers, invalid GPS, profile conflicts, suspicious activity, and unlinked records.
How it works: Quality issues are reviewed before records are used in reports, indicators, entity profiles, or donor outputs.
10
Mapping shows project areas, entity locations, submission points, facilities, coverage gaps, GPS quality issues, and operational movement evidence.
How it works: GPS capture stores coordinates, accuracy, source, timestamp, and quality signals where forms or activity rules require location evidence.
11
Indicators track baselines, targets, actual progress, disaggregation, and reporting periods. Reports turn approved data into dashboards, exports, and donor-ready outputs.
How it works: Reports should use approved, traceable data linked to forms, projects, entities, indicators, and quality checks.
12
Admins manage users, stacked roles, teams, permission scopes, role profiles, supervisor relationships, and organization access.
How it works: Governance records sensitive actions, approvals, policy changes, profile updates, exports, audit trails, and access decisions.
13
Administration manages reusable reference data, location hierarchy, notifications, API settings, integrations, mobile devices, version policies, backups, and system settings.
How it works: System-wide settings live in Administration, while form, project, data quality, user, and governance settings stay in their owning modules.
Atlas FieldOps