​

Operating Model

ProjectDesk is built around a results-based field operations model. This means each workspace should connect project intent, field work, evidence, MEL records, reporting, and learning decisions in one continuous journey.

​

The ProjectDesk Work Cycle

The normal work cycle is:

1. Define the project and its results framework.
2. Document the MEL plan.
3. Create workstreams, locations, and activities.
4. Define evidence requirements.
5. Assign and complete field work.
6. Submit evidence against the requirement.
7. Review evidence and request corrections where needed.
8. Update indicators, risks, reports, and stakeholder updates.
9. Record learning or adaptation decisions.
10. Share approved information with stakeholders or auditors.

​

Results Framework

The results framework explains why the project exists and what change it is meant to create. It can include: Managers and MEL leads use the results framework to keep field work connected to project purpose.

​

MEL Plan

The MEL plan explains how the project will monitor progress, evaluate results, and learn from implementation. It can include:

• Theory of change
• Learning questions
• Data sources
• Collection frequency
• Responsible role
• Reporting use
• Data quality approach
• Evaluation plan

Use the MEL plan before creating indicators or reports. It gives the team a shared understanding of what should be measured, why it matters, and how the data will be used.

​

Evidence Requirements

Evidence requirements define the standard field teams must satisfy when submitting proof of work. An evidence requirement can describe:

• The activity it supports
• The expected proof
• The required format
• The verification standard
• The data quality checks reviewers should apply

Field users should read the requirement before submitting evidence. Reviewers should use the requirement when deciding whether to approve, request correction, or reject a submission.

​

Indicators

Indicators track progress against a target. In ProjectDesk, an indicator should also explain how the data is collected and used. Useful indicator metadata includes:

• Baseline
• Target
• Actual value
• Data source
• Collection frequency
• Responsible role
• Reporting use
• Quality notes

This prevents indicators from becoming disconnected numbers with no clear source or reporting purpose.

​

Learning and Adaptation Decisions

Learning decisions record what the team changed because of evidence, risk, field feedback, or stakeholder review. A good decision record states:

• What evidence or issue triggered the decision
• What decision was made
• What next step follows
• Whether the decision is still open, in progress, or closed

Use this area when a field reality changes the implementation plan. It helps managers, donors, and auditors understand not just what happened, but how the project responded.