Operations Journey
The Operations area turns a client workspace into a working implementation environment. It is where teams define project structure, assign field work, gather evidence, track risks, communicate progress, and escalate issues.Operations Sections
Operations is divided into four sections:- Setup
- Evidence
- Reporting
- Services
Setup Section
The Setup section creates the structure that all later activity depends on.Client Projects
A client project is the main body of work being managed in a workspace. Examples:- Nutrition baseline study
- District service quality assessment
- Climate resilience field monitoring
- Public health implementation tracking
| Field | Meaning |
|---|---|
| Name | The clear project name users will recognize |
| Code | A short internal code |
| Donor or stakeholder | The funder, partner, or stakeholder linked to the project |
Workstreams
A workstream is a major area of activity inside a project. Examples:- Household survey
- Facility assessment
- Focus group facilitation
- Training follow-up
- Data quality review
Locations
A location is a field site, district, region, office, facility, or implementation area. Locations help teams understand where field work is happening.Activities
An activity is a specific piece of work that field teams or managers can act on. Examples:- Complete 40 household interviews
- Upload signed attendance register
- Validate district facility records
- Confirm enumerator training completion
Good Activity Design
A useful activity includes:- A direct action
- A clear scope
- A field site or workstream where possible
- A description of expected evidence
What Happens After Setup
Once projects, workstreams, locations, and activities exist:- Field users submit evidence against activities.
- Managers and MEL leads review submissions.
- Approved evidence supports reporting records.
- Risks and blockers are tracked as the work progresses.
- Service cases are opened when the ProjectDesk team needs to help.