Background
Cordaid Iraq supports local civil society organisations in Baghdad, Basra, Erbil and Ninewa to strengthen how they are governed, how they plan and how they advocate. This training responds to the priorities identified in a recent organisational assessment of participating organisations.
Why this training
A recent organisational assessment found that most participating organisations collect data to report to their funders, not to make their own decisions. Many have no monitoring plan, few can point to a decision that changed because of their data, and complaints channels exist on paper more often than in use. The need is greatest in Basra and Ninewa.
This training does not teach monitoring theory. Each organisation sets up a simple routine on an activity it is already running, uses it for at least one month, and shows one decision that came out of it.
Training days, locations and language
Days differ by governorate because the assessment found different levels of need. In Baghdad, Basra and Mosul the days are split: an opening workshop, then a follow-up day six to eight weeks later, when organisations bring their first monthly records. The allocation is fixed at contract and can be adjusted by mutual agreement within the total.
|
Governorate |
Opening workshop |
Follow-up day |
Total days |
Language |
|
Baghdad |
1 |
1 |
2 |
Arabic |
|
Basra |
2 |
1 |
3 |
Arabic |
|
Erbil |
1 |
0 |
1 |
Arabic and Kurdish |
|
Mosul (Ninewa) |
2 |
1 |
3 |
Arabic |
|
Total |
6 |
3 |
9 |
|
Training in Baghdad, Basra and Mosul is delivered in Arabic only. Training in Erbil is delivered in Arabic and Kurdish (Sorani), mixed according to the participants in the room, so the Erbil trainer must be able to work comfortably in both.
What must be covered
The training is built around one real activity per organisation. Participants bring the activity's plan, its participant list format and any reports they already send. Every exercise uses that activity.
Module 1. Choosing what to measure
Participants pick one activity they are running now and decide what is worth knowing about it.
- Choosing the activity: one that runs for at least the next three months and that the team cares about
- The difference between counting what was done (sessions held, people reached) and knowing whether it worked
- Three to five indicators per activity, including at least one about quality or change, not only numbers
- Writing each indicator so anyone in the team would count it the same way: what is counted, from which source, how often
- Baselines: what the situation is now, before the next month of work
Result: a one-page indicator sheet for the chosen activity.
Module 2. Collecting and keeping data safely
Participants set up the simplest way to collect the data without adding work or risk.
- Using records the team already keeps (attendance sheets, activity notes, photos) before creating new forms
- Short tools that work in the field: a paper form, a phone form, a WhatsApp check-in, with their limits
- Collecting only the personal information that is needed, consent, and when not to collect names
- Where data is stored, who can see it, and why participant lists should not sit on personal phones
- Who in the team collects, who checks and who enters the data each month
Result: a data collection plan on one page, with names against each task.
Module 3. The monthly review
Participants learn to run a short monthly meeting that turns data into a decision.
- A monthly review the team can hold in under an hour: what the numbers say, what surprised us, what we change
- Reading simple data without software: totals, trends over three months, differences between groups (women and men, age, location)
- Recording a decision: what was decided, by whom, by when, and how it will be checked next month
- When a finding should go to the director or the board
- Using the same review to prepare reports to funders, instead of writing reports separately
Result: a monthly review template ready for the first meeting.
Module 4. Hearing from the community
Participants set up a feedback and complaints channel that people actually use.
- Choosing channels that suit the community: a phone number, a box, a short survey at the end of sessions, a community meeting
- Who receives feedback, how it is logged, and the time within which the organisation replies
- Sensitive complaints, including any about staff or volunteers, and how they go to the safeguarding focal point and not into the general log
- Closing the loop: telling the community what changed because of what they said
- A short community scorecard once per activity cycle: three questions, scored together with participants
Result: a feedback and complaints log in use, with a named person responsible.
Module 5. Follow-up day: from data to a decision and a lesson
Six to eight weeks later, each organisation reviews its own first month of data.
- Each organisation presents its first month of data and the issues it found in collecting it
- Agreeing one decision based on the data, and recording it in the review template
- Adjusting the indicator sheet where an indicator did not work
- Writing one lesson learned, in two or three sentences, and where it will be used in the design of the next activity
Result: one recorded decision and one written lesson per organisation.
Suggested sequence by governorate
|
Governorate |
Opening workshop |
Follow-up day |
Emphasis |
|
Baghdad |
Day 1: Modules 1 to 4, short form |
Day 2: Module 5 |
Using data for decisions; most organisations already measure something |
|
Basra |
Day 1: Modules 1 and 2. Day 2: Modules 3 and 4 |
Day 3: Module 5 |
Starting from scratch; many organisations have no monitoring plan |
|
Erbil |
Day 1: Modules 3 to 5, built on the tools organisations already have |
None |
Closing the loop with communities and recording lessons |
|
Mosul (Ninewa) |
Day 1: Modules 1 and 2. Day 2: Modules 3 and 4 |
Day 3: Module 5 |
Simple paper-based tools for young organisations with few staff |
Who attends: the person who runs the chosen activity and the person who will keep the monthly review, in each organisation.
What each organisation must hold at the end
The training is practical. Each organisation leaves with the following, produced by its own people:
- A one-page indicator sheet for one live activity
- A one-page data collection plan with names against each task
- A monthly review template, with the first month's data filled in by the follow-up day
- A feedback and complaints log in use, with a named person responsible
- One recorded decision based on the data and one written lesson (Baghdad, Basra and Mosul, by the follow-up day)
The trainer also submits a short completion note per governorate (one to two pages, template provided by Cordaid) listing which organisations produced each document, and which did not and why.
Fee and payment
Quote a daily rate in USD per training day delivered.
Cordaid pays only for training days actually delivered. Preparation days, materials development, reporting, travel, accommodation and meals are not paid and must not appear in your offer. Price your daily rate with this in mind.
Cordaid arranges the venue, participant invitations and refreshments through its hub facilitator in each governorate.
Payment is made after each governorate's training is completed, on the basis of signed attendance sheets and an accepted completion note.
Fees are subject to tax deductions under Iraqi law.
Cordaid may extend the contract, at the same daily rates and by written order, to additional groups of organisations until February 2028.
Timing
Opening workshops between 15 December 2026 and 31 January 2027; follow-up days six to eight weeks after each workshop, and no later than 31 March 2027, on dates agreed with the Cordaid hub facilitator in each governorate.
Trainer profile
- Monitoring, evaluation, accountability and learning specialist with at least seven years of work with civil society organisations or international NGOs in Iraq
- Demonstrated experience setting up simple monitoring routines in small organisations with no dedicated monitoring staff
- Experience setting up community feedback and complaints mechanisms, and working knowledge of personal data protection
- Arabic required for all governorates. Arabic and Kurdish (Sorani) required for Erbil.
Individual trainers, teams and firms can apply. Individuals are contracted as consultants and do not need to be registered as a company.
How you can bid
You can apply for:
- one governorate only (for example, Basra);
- several governorates of your choice; or
- all four governorates
Joint proposals are welcome. Two trainers can team up and submit one proposal for the same services, for example to combine technical and facilitation skills or Arabic and Kurdish. The proposal names a lead trainer who signs the contract and receives payment, shows which trainer delivers which days, and quotes one daily rate per governorate. Each trainer submits a CV and a signed declaration.
Cordaid may award each governorate to a different trainer, or all governorates to one trainer, depending on what gives the best result. If you bid for more than one governorate, quote a daily rate for each one, and if you wish, a combined daily rate that applies only if you are awarded all of them.
please apply online through this form: Application Form