Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
International Livestock Research Institute (ILRI)
Job Description
for paragraphs,
for section headers, - for lists. No CSS, inline styles, ,
. Preserve ALL original content word-for-word. If no clear sections, just wrap in . Return ONLY the HTML. No markdown fences, no explanation, no preamble.
Then the user provides the actual job description text.
Wait, the user's message has two parts:
- First part: "You are a job listing editor..." with rules about removing/keeping stuff, return ONLY cleaned job text.
- Second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules.
- Then the actual job description text follows.
I need to figure out which format to output. The very last instruction says: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And the task is to format the given job description as clean semantic HTML using the specified tags.
Let re-read carefully: The user starts with "You are a job listing editor..." but then switches to "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." and gives HTML-specific rules. The final text is the job description. The output should be HTML formatted according to the rules.
I will follow the HTML formatting rules, as that's the explicit final task. I need to convert the provided plain-text job description into semantic HTML using
,
, , - ,
. No , no inline CSS, no
. Preserve all content word-for-word.
Let's examine the job description text. It's already mostly in tags with some inline styles (text-align:justify, style=...). But the rule says: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". And "Use
for introductory paragraphs and general text", "Use
for section headers", "Use - for list items", "No CSS classes, no inline styles, no s, no
tags".
So I need to strip the existing tags and formatting, but keep the text content, and wrap/reformat into the required semantic HTML. The instruction says "Preserve ALL original content word-for-word". That means I shouldn't change the wording, but I can restructure the tags as per the rules. The existing text has some formatting like ``, ``, etc. I need to remove inline styles and structural tags that aren't allowed, but keep the text. I'll need to interpret "preserve ALL original content word-for-word" as keeping the exact text strings, but I can re-tag them.
Let's parse the text and plan the HTML structure.
The text starts with:
`
POSITION ANNOUNCEMENT
`
Then `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
`
Then `REF: C/AGRA/020/2026
`
Then `AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
`
And so on.
I need to output ONLY HTML, no markdown fences. So I'll just output the HTML body.
Rules:
- Use for introductory paragraphs and general text
- Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)
- Use - for list items (duties, requirements, qualifications, skills)
- No CSS classes, no inline styles, no s, no
tags
- Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase
- If text has no clear sections, just wrap paragraphs in tags
- Return ONLY the HTML. No markdown fences, no explanation, no preamble.
Key challenge: "Preserve ALL original content word-for-word". I need to make sure every word from the original text appears exactly, but I can change the tag structure. The original has inline styles like `style="text-align:justify;"` which I must remove. It has `` which I can keep or remove? The rule says use for section headers, - for list items. It doesn't say I can't use , but it says "No CSS classes, no inline styles, no s, no
tags". So I should remove inline styles, but can I keep ? It's not explicitly forbidden, but to be safe, I might either keep it as part of text or remove it since the focus is on the structural tags. However, "Preserve ALL original content word-for-word" might mean I shouldn't omit any text, including "POSITION ANNOUNCEMENT". I'll keep the text, and use appropriate tags. I can wrap text in , and for headers use
. I might need to use for bold text if it's part of the original, but the rule says "Use for section headers (e.g. Responsibilities, Qualifications, ...)". The original has `POSITION ANNOUNCEMENT `, `Consultant - ...`, `REF: ...`, `1. GENERAL BACKGROUND`, etc. I need to decide how to handle these. Since the rule says "Use for section headers", I should probably convert section headers to , and maybe keep for other bold text, or just remove formatting and let the text flow. But "Preserve ALL original content word-for-word" suggests I shouldn't lose any words, but I can change tags. I think it's safest to keep the text exactly as is, but strip the inline styles, and re-tag with allowed tags. I'll use for paragraphs,
for what are clearly section headings, and for other bold text, I might just keep them as plain text within
, or use if allowed. The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . I'll use where the original had , and for section headers like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. But the example list of headers: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", "3. SCOPE OF WORK", "4. DURATION OF ASSIGNMENT, DUTY STATION", "5. PROVISION OF MONITORING AND PROGRESS CONTROLS", "6. FINAL PRODUCTS", "7. REVIEW TIME REQUIRED", "8. REQUIRED QUALIFICATIONS AND DOCUMENTS". These are section headers. I'll use for them.
Let's outline the structure:
- Start with the job title and ref. Maybe wrap in
or
. The original has `
POSITION ANNOUNCEMENT
`, `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
`, `REF: C/AGRA/020/2026
`. I'll keep these as with the text, maybe strip or keep it. To preserve word-for-word, I should keep the text, but I can change tags. I'll use and keep the content, perhaps without since it's not a section header per the example, but the rule says use for section headers. I'll treat "POSITION ANNOUNCEMENT" as part of the intro, maybe
. "Consultant - ..." as title, maybe
? But the example says "Use for section headers (e.g. Responsibilities, Qualifications, ...)". Job title might not be a section header. I'll put the title and ref in a
at the top.
Better approach: I'll parse the text sequentially and wrap each block appropriately.
Let's go through the text line by line (mentally) and assign tags:
1. `
POSITION ANNOUNCEMENT
` -> I'll output `POSITION ANNOUNCEMENT
` (strip but keep text; or keep ? I'll keep since it's not inline CSS/style, and the rule only forbids inline styles, classes, div, br. is a valid HTML tag. But "preserve ALL original content word-for-word" - if I keep , the content includes the tag, but the rule might mean the textual content. I think it's safer to keep the text and use as it's semantic. I'll keep where originally present, as it's part of the content's semantics.)
Actually, re-read: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely means the textual content must be exact, not that HTML tags must be preserved. I can restructure tags. I'll remove inline styles, but keep the text content exactly. I'll use ,
, , - as specified. I'll keep only if it doesn't conflict, but to be safe, I might just keep the text without , or I can use since it's allowed. The rule says "No CSS classes, no inline styles, no s, no
tags". is none of those. I'll use for bold emphasis where the original had it, but I need to be careful not to overuse. Actually, the original has a lot of ``. I'll just keep the text as is, and wrap paragraphs in , and for section headers use
. I'll replace `header` with `header
`, and for body text, use `
`. For lists, use `
- `.
Let's decide: I will convert the entire text into semantic HTML as per rules. I'll strip the `style="text-align:justify;"` inline styles. I'll keep all text content exactly. I'll use `
` for paragraphs, `
` for section headers, `- ` for list items. I'll also keep `` maybe for key terms, but to avoid violation, I'll just use normal text or if it was originally. Actually, the instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say I can't use other tags, but it emphasizes those. I'll use for the main section headers that correspond to those categories. The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. I'll map those to .
Let's plan the HTML structure:
```
POSITION ANNOUNCEMENT
Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
REF: C/AGRA/020/2026
AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
AGRA founded in 2006, is an African-led African-based organization that seeks to catalyze Agriculture Transformation in Africa. AGRA is focused on putting smallholder farmers at the center of the continent’s growing economy by transforming agriculture from a solitary struggle to survive into farming as a business that thrives. As the sector that employs the majority of Africa’s people, nearly all of them small-scale farmers, AGRA recognizes that developing smallholder agriculture into a productive, efficient, and sustainable system is essential to ensuring food security, lifting millions out of poverty, and driving equitable growth across the continent.
AGRA is rolling out a new 5-year strategy to catalyze and sustain an Inclusive Agricultural Transformation in Africa to increase incomes and improve food security for 30 million farmers. Under this strategy, AGRA will deliver through an approach that simultaneously catalyzes change at farmer level, strengthens input and output market systems and puts government at the center to enable and champion private-sector-led agricultural growth at national level.
1. GENERAL BACKGROUND
AGRA is implementing the RE-GAIN Programme, financed by the Green Climate Fund (GCF), to reduce climate-induced food losses and strengthen resilient agricultural value chains. In Ethiopia, the programme focuses on teff and wheat and supports the adoption of Food Loss-Reduction Solutions (FL-RS), including hermetic storage bags, drying tarpaulins, silos, threshers/shellers, communal storage and aflatoxin management. RE-GAIN is implemented in accordance with AGRA's Environmental and Social Management System (ESMS), relevant GCF environmental and social requirements, and applicable international good practice. The ESMS is integrated into AGRA's Programme Operations Manual (POM), including requirements related to environmental and social risk management, stakeholder engagement, gender and accountability. The environmental and social screening for RE-GAIN activities in Ethiopia has been completed. The current requirement is therefore to operationalise and strengthen implementation of the existing ESMS and related accountability and safeguarding arrangements, rather than establish parallel systems. The consultant will provide country-level technical support to AGRA Ethiopia to strengthen implementation of mitigation measures, stakeholder engagement, grievance and feedback mechanisms, safeguarding, accountability and partner assurance. Particular attention will be given to establishing an accessible Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system with appropriate hotline/SMS functionality.
2. OBJECTIVE OF THE ASSIGNMENT
Overall Objective
To support AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
Specific Objectives
The consultancy will:
- Refine and operationalize Environmental and Social Action Plans (ESAPs) for RE-GAIN interventions and partners.
- Develop and support implementation of a risk-proportionate Stakeholder Engagement Plan (SEP).
- Establish and operationalise an AGRA Ethiopia country-level Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system and appropriate hotline/SMS channels as part of FGM.
- Develop a Country Accountability, Safeguarding and Partner Assurance Framework, including minimum safeguarding standards and partner assurance tools.
- Build the capacity of AGRA staff and partner focal points to manage ESMS, accountability, safeguarding and feedback systems sustainably.
3. SCOPE OF WORK
The consultant will undertake the following key activities:
3.1. Environmental and Social Action Plans
- Review screening results, risk categorization and existing mitigation measures.
- Refine ESAPs with clear actions, responsibilities, timelines, indicators and budgets where required.
- Facilitate consultations with implementing partners, suppliers and relevant stakeholders to agreed actions.
- Establish and maintain a consolidated country ESAP tracker.
3.2. Stakeholder Engagement
- Map and analyse key stakeholders, including farmers, women, youth, persons with disabilities, advisors, cooperatives, MSMEs, suppliers, financial institutions, government institutions and relevant community organisations. Assess their interests, influence, exposure to programme risks, communication needs and barriers to participation, and identify appropriate engagement methods.
- Develop a risk-proportionate SEP covering information disclosure, participation, feedback and inclusion.
Apply Now ↗
How well do you match?
Get an instant AI match score for this role — free, takes 3 minutes.
Tailor your CV for this role
The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
Tailor My CV to This Job ✍️
Free cover letter for this job
Upload your CV and get a tailored cover letter in seconds — free, no account needed.
Generate a Cover Letter 📝
My Job Concierge
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Almost there
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
ECHO
Your MJC Assistant
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
. Preserve ALL original content word-for-word. If no clear sections, just wrap in
. Return ONLY the HTML. No markdown fences, no explanation, no preamble. Then the user provides the actual job description text. Wait, the user's message has two parts: - First part: "You are a job listing editor..." with rules about removing/keeping stuff, return ONLY cleaned job text. - Second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules. - Then the actual job description text follows. I need to figure out which format to output. The very last instruction says: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And the task is to format the given job description as clean semantic HTML using the specified tags. Let re-read carefully: The user starts with "You are a job listing editor..." but then switches to "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." and gives HTML-specific rules. The final text is the job description. The output should be HTML formatted according to the rules. I will follow the HTML formatting rules, as that's the explicit final task. I need to convert the provided plain-text job description into semantic HTML using
,
, , - ,
. No , no inline CSS, no
. Preserve all content word-for-word.
Let's examine the job description text. It's already mostly in tags with some inline styles (text-align:justify, style=...). But the rule says: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". And "Use
for introductory paragraphs and general text", "Use
for section headers", "Use - for list items", "No CSS classes, no inline styles, no s, no
tags".
So I need to strip the existing tags and formatting, but keep the text content, and wrap/reformat into the required semantic HTML. The instruction says "Preserve ALL original content word-for-word". That means I shouldn't change the wording, but I can restructure the tags as per the rules. The existing text has some formatting like ``, ``, etc. I need to remove inline styles and structural tags that aren't allowed, but keep the text. I'll need to interpret "preserve ALL original content word-for-word" as keeping the exact text strings, but I can re-tag them.
Let's parse the text and plan the HTML structure.
The text starts with:
`
POSITION ANNOUNCEMENT
`
Then `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
`
Then `REF: C/AGRA/020/2026
`
Then `AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
`
And so on.
I need to output ONLY HTML, no markdown fences. So I'll just output the HTML body.
Rules:
- Use for introductory paragraphs and general text
- Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)
- Use - for list items (duties, requirements, qualifications, skills)
- No CSS classes, no inline styles, no s, no
tags
- Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase
- If text has no clear sections, just wrap paragraphs in tags
- Return ONLY the HTML. No markdown fences, no explanation, no preamble.
Key challenge: "Preserve ALL original content word-for-word". I need to make sure every word from the original text appears exactly, but I can change the tag structure. The original has inline styles like `style="text-align:justify;"` which I must remove. It has `` which I can keep or remove? The rule says use for section headers, - for list items. It doesn't say I can't use , but it says "No CSS classes, no inline styles, no s, no
tags". So I should remove inline styles, but can I keep ? It's not explicitly forbidden, but to be safe, I might either keep it as part of text or remove it since the focus is on the structural tags. However, "Preserve ALL original content word-for-word" might mean I shouldn't omit any text, including "POSITION ANNOUNCEMENT". I'll keep the text, and use appropriate tags. I can wrap text in , and for headers use
. I might need to use for bold text if it's part of the original, but the rule says "Use for section headers (e.g. Responsibilities, Qualifications, ...)". The original has `POSITION ANNOUNCEMENT `, `Consultant - ...`, `REF: ...`, `1. GENERAL BACKGROUND`, etc. I need to decide how to handle these. Since the rule says "Use for section headers", I should probably convert section headers to , and maybe keep for other bold text, or just remove formatting and let the text flow. But "Preserve ALL original content word-for-word" suggests I shouldn't lose any words, but I can change tags. I think it's safest to keep the text exactly as is, but strip the inline styles, and re-tag with allowed tags. I'll use for paragraphs,
for what are clearly section headings, and for other bold text, I might just keep them as plain text within
, or use if allowed. The rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . I'll use where the original had , and for section headers like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. But the example list of headers: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", "3. SCOPE OF WORK", "4. DURATION OF ASSIGNMENT, DUTY STATION", "5. PROVISION OF MONITORING AND PROGRESS CONTROLS", "6. FINAL PRODUCTS", "7. REVIEW TIME REQUIRED", "8. REQUIRED QUALIFICATIONS AND DOCUMENTS". These are section headers. I'll use for them.
Let's outline the structure:
- Start with the job title and ref. Maybe wrap in
or
. The original has `
POSITION ANNOUNCEMENT
`, `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
`, `REF: C/AGRA/020/2026
`. I'll keep these as with the text, maybe strip or keep it. To preserve word-for-word, I should keep the text, but I can change tags. I'll use and keep the content, perhaps without since it's not a section header per the example, but the rule says use for section headers. I'll treat "POSITION ANNOUNCEMENT" as part of the intro, maybe
. "Consultant - ..." as title, maybe
? But the example says "Use for section headers (e.g. Responsibilities, Qualifications, ...)". Job title might not be a section header. I'll put the title and ref in a
at the top.
Better approach: I'll parse the text sequentially and wrap each block appropriately.
Let's go through the text line by line (mentally) and assign tags:
1. `
POSITION ANNOUNCEMENT
` -> I'll output `POSITION ANNOUNCEMENT
` (strip but keep text; or keep ? I'll keep since it's not inline CSS/style, and the rule only forbids inline styles, classes, div, br. is a valid HTML tag. But "preserve ALL original content word-for-word" - if I keep , the content includes the tag, but the rule might mean the textual content. I think it's safer to keep the text and use as it's semantic. I'll keep where originally present, as it's part of the content's semantics.)
Actually, re-read: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely means the textual content must be exact, not that HTML tags must be preserved. I can restructure tags. I'll remove inline styles, but keep the text content exactly. I'll use ,
, , - as specified. I'll keep only if it doesn't conflict, but to be safe, I might just keep the text without , or I can use since it's allowed. The rule says "No CSS classes, no inline styles, no s, no
tags". is none of those. I'll use for bold emphasis where the original had it, but I need to be careful not to overuse. Actually, the original has a lot of ``. I'll just keep the text as is, and wrap paragraphs in , and for section headers use
. I'll replace `header` with `header
`, and for body text, use `
`. For lists, use `
- `.
Let's decide: I will convert the entire text into semantic HTML as per rules. I'll strip the `style="text-align:justify;"` inline styles. I'll keep all text content exactly. I'll use `
` for paragraphs, `
` for section headers, `- ` for list items. I'll also keep `` maybe for key terms, but to avoid violation, I'll just use normal text or if it was originally. Actually, the instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say I can't use other tags, but it emphasizes those. I'll use for the main section headers that correspond to those categories. The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. I'll map those to .
Let's plan the HTML structure:
```
POSITION ANNOUNCEMENT
Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
REF: C/AGRA/020/2026
AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
AGRA founded in 2006, is an African-led African-based organization that seeks to catalyze Agriculture Transformation in Africa. AGRA is focused on putting smallholder farmers at the center of the continent’s growing economy by transforming agriculture from a solitary struggle to survive into farming as a business that thrives. As the sector that employs the majority of Africa’s people, nearly all of them small-scale farmers, AGRA recognizes that developing smallholder agriculture into a productive, efficient, and sustainable system is essential to ensuring food security, lifting millions out of poverty, and driving equitable growth across the continent.
AGRA is rolling out a new 5-year strategy to catalyze and sustain an Inclusive Agricultural Transformation in Africa to increase incomes and improve food security for 30 million farmers. Under this strategy, AGRA will deliver through an approach that simultaneously catalyzes change at farmer level, strengthens input and output market systems and puts government at the center to enable and champion private-sector-led agricultural growth at national level.
1. GENERAL BACKGROUND
AGRA is implementing the RE-GAIN Programme, financed by the Green Climate Fund (GCF), to reduce climate-induced food losses and strengthen resilient agricultural value chains. In Ethiopia, the programme focuses on teff and wheat and supports the adoption of Food Loss-Reduction Solutions (FL-RS), including hermetic storage bags, drying tarpaulins, silos, threshers/shellers, communal storage and aflatoxin management. RE-GAIN is implemented in accordance with AGRA's Environmental and Social Management System (ESMS), relevant GCF environmental and social requirements, and applicable international good practice. The ESMS is integrated into AGRA's Programme Operations Manual (POM), including requirements related to environmental and social risk management, stakeholder engagement, gender and accountability. The environmental and social screening for RE-GAIN activities in Ethiopia has been completed. The current requirement is therefore to operationalise and strengthen implementation of the existing ESMS and related accountability and safeguarding arrangements, rather than establish parallel systems. The consultant will provide country-level technical support to AGRA Ethiopia to strengthen implementation of mitigation measures, stakeholder engagement, grievance and feedback mechanisms, safeguarding, accountability and partner assurance. Particular attention will be given to establishing an accessible Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system with appropriate hotline/SMS functionality.
2. OBJECTIVE OF THE ASSIGNMENT
Overall Objective
To support AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
Specific Objectives
The consultancy will:
- Refine and operationalize Environmental and Social Action Plans (ESAPs) for RE-GAIN interventions and partners.
- Develop and support implementation of a risk-proportionate Stakeholder Engagement Plan (SEP).
- Establish and operationalise an AGRA Ethiopia country-level Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system and appropriate hotline/SMS channels as part of FGM.
- Develop a Country Accountability, Safeguarding and Partner Assurance Framework, including minimum safeguarding standards and partner assurance tools.
- Build the capacity of AGRA staff and partner focal points to manage ESMS, accountability, safeguarding and feedback systems sustainably.
3. SCOPE OF WORK
The consultant will undertake the following key activities:
3.1. Environmental and Social Action Plans
- Review screening results, risk categorization and existing mitigation measures.
- Refine ESAPs with clear actions, responsibilities, timelines, indicators and budgets where required.
- Facilitate consultations with implementing partners, suppliers and relevant stakeholders to agreed actions.
- Establish and maintain a consolidated country ESAP tracker.
3.2. Stakeholder Engagement
- Map and analyse key stakeholders, including farmers, women, youth, persons with disabilities, advisors, cooperatives, MSMEs, suppliers, financial institutions, government institutions and relevant community organisations. Assess their interests, influence, exposure to programme risks, communication needs and barriers to participation, and identify appropriate engagement methods.
- Develop a risk-proportionate SEP covering information disclosure, participation, feedback and inclusion.
Apply Now ↗
How well do you match?
Get an instant AI match score for this role — free, takes 3 minutes.
Tailor your CV for this role
The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
Tailor My CV to This Job ✍️
Free cover letter for this job
Upload your CV and get a tailored cover letter in seconds — free, no account needed.
Generate a Cover Letter 📝
My Job Concierge
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Almost there
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
ECHO
Your MJC Assistant
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.
- . No
- for list items", "No CSS classes, no inline styles, no s, no
tags". So I need to strip the existing tags and formatting, but keep the text content, and wrap/reformat into the required semantic HTML. The instruction says "Preserve ALL original content word-for-word". That means I shouldn't change the wording, but I can restructure the tags as per the rules. The existing text has some formatting like ``, ``, etc. I need to remove inline styles and structural tags that aren't allowed, but keep the text. I'll need to interpret "preserve ALL original content word-for-word" as keeping the exact text strings, but I can re-tag them. Let's parse the text and plan the HTML structure. The text starts with: `
POSITION ANNOUNCEMENT
` Then `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
` Then `REF: C/AGRA/020/2026
` Then `AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
` And so on. I need to output ONLY HTML, no markdown fences. So I'll just output the HTML body. Rules: - Usefor introductory paragraphs and general text - Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - Use
- for list items (duties, requirements, qualifications, skills)
- No CSS classes, no inline styles, no s, no
tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs intags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. Key challenge: "Preserve ALL original content word-for-word". I need to make sure every word from the original text appears exactly, but I can change the tag structure. The original has inline styles like `style="text-align:justify;"` which I must remove. It has `` which I can keep or remove? The rule says use
for section headers,
- for list items. It doesn't say I can't use , but it says "No CSS classes, no inline styles, no s, no
tags". So I should remove inline styles, but can I keep ? It's not explicitly forbidden, but to be safe, I might either keep it as part of text or remove it since the focus is on the structural tags. However, "Preserve ALL original content word-for-word" might mean I shouldn't omit any text, including "POSITION ANNOUNCEMENT". I'll keep the text, and use appropriate tags. I can wrap text in, and for headers use
. I might need to use for bold text if it's part of the original, but the rule says "Use
for section headers (e.g. Responsibilities, Qualifications, ...)". The original has `POSITION ANNOUNCEMENT `, `Consultant - ...`, `REF: ...`, `1. GENERAL BACKGROUND`, etc. I need to decide how to handle these. Since the rule says "Use
for section headers", I should probably convert section headers to
, and maybe keep for other bold text, or just remove formatting and let the text flow. But "Preserve ALL original content word-for-word" suggests I shouldn't lose any words, but I can change tags. I think it's safest to keep the text exactly as is, but strip the inline styles, and re-tag with allowed tags. I'll use
for paragraphs,
for what are clearly section headings, and for other bold text, I might just keep them as plain text within
, or use if allowed. The rule says "No CSS classes, no inline styles, no
s, no
tags". It doesn't forbid . I'll use where the original had , andfor section headers like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. But the example list of headers: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", "3. SCOPE OF WORK", "4. DURATION OF ASSIGNMENT, DUTY STATION", "5. PROVISION OF MONITORING AND PROGRESS CONTROLS", "6. FINAL PRODUCTS", "7. REVIEW TIME REQUIRED", "8. REQUIRED QUALIFICATIONS AND DOCUMENTS". These are section headers. I'll use
for them. Let's outline the structure: - Start with the job title and ref. Maybe wrap in
or
. The original has `
POSITION ANNOUNCEMENT
`, `Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
`, `REF: C/AGRA/020/2026
`. I'll keep these aswith the text, maybe strip or keep it. To preserve word-for-word, I should keep the text, but I can change tags. I'll use
and keep the content, perhaps without since it's not a section header per the example, but the rule says use
for section headers. I'll treat "POSITION ANNOUNCEMENT" as part of the intro, maybe
. "Consultant - ..." as title, maybe
? But the example says "Use
for section headers (e.g. Responsibilities, Qualifications, ...)". Job title might not be a section header. I'll put the title and ref in a
at the top. Better approach: I'll parse the text sequentially and wrap each block appropriately. Let's go through the text line by line (mentally) and assign tags: 1. `
POSITION ANNOUNCEMENT
` -> I'll output `POSITION ANNOUNCEMENT
` (strip but keep text; or keep ? I'll keep since it's not inline CSS/style, and the rule only forbids inline styles, classes, div, br. is a valid HTML tag. But "preserve ALL original content word-for-word" - if I keep , the content includes the tag, but the rule might mean the textual content. I think it's safer to keep the text and use as it's semantic. I'll keep where originally present, as it's part of the content's semantics.) Actually, re-read: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely means the textual content must be exact, not that HTML tags must be preserved. I can restructure tags. I'll remove inline styles, but keep the text content exactly. I'll use,
,
- ,
- as specified. I'll keep only if it doesn't conflict, but to be safe, I might just keep the text without , or I can use since it's allowed. The rule says "No CSS classes, no inline styles, no s, no
tags". is none of those. I'll use for bold emphasis where the original had it, but I need to be careful not to overuse. Actually, the original has a lot of ``. I'll just keep the text as is, and wrap paragraphs in, and for section headers use
. I'll replace `header` with `
header
`, and for body text, use ``. For lists, use `
- `.
Let's decide: I will convert the entire text into semantic HTML as per rules. I'll strip the `style="text-align:justify;"` inline styles. I'll keep all text content exactly. I'll use `
` for paragraphs, `
` for section headers, `
- ` for list items. I'll also keep `` maybe for key terms, but to avoid violation, I'll just use normal text or if it was originally. Actually, the instruction says "Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say I can't use other tags, but it emphasizes those. I'll use
for the main section headers that correspond to those categories. The text has sections like "1. GENERAL BACKGROUND", "2. OBJECTIVE OF THE ASSIGNMENT", etc. I'll map those to
. Let's plan the HTML structure: ```
POSITION ANNOUNCEMENT
Consultant - RE-GAIN Programme - Environmental and Social Management System, Accountability and Safeguarding.
REF: C/AGRA/020/2026
AGRA seeks to recruit a consultant who can provide supports to AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
AGRA founded in 2006, is an African-led African-based organization that seeks to catalyze Agriculture Transformation in Africa. AGRA is focused on putting smallholder farmers at the center of the continent’s growing economy by transforming agriculture from a solitary struggle to survive into farming as a business that thrives. As the sector that employs the majority of Africa’s people, nearly all of them small-scale farmers, AGRA recognizes that developing smallholder agriculture into a productive, efficient, and sustainable system is essential to ensuring food security, lifting millions out of poverty, and driving equitable growth across the continent.
AGRA is rolling out a new 5-year strategy to catalyze and sustain an Inclusive Agricultural Transformation in Africa to increase incomes and improve food security for 30 million farmers. Under this strategy, AGRA will deliver through an approach that simultaneously catalyzes change at farmer level, strengthens input and output market systems and puts government at the center to enable and champion private-sector-led agricultural growth at national level.
1. GENERAL BACKGROUND
AGRA is implementing the RE-GAIN Programme, financed by the Green Climate Fund (GCF), to reduce climate-induced food losses and strengthen resilient agricultural value chains. In Ethiopia, the programme focuses on teff and wheat and supports the adoption of Food Loss-Reduction Solutions (FL-RS), including hermetic storage bags, drying tarpaulins, silos, threshers/shellers, communal storage and aflatoxin management. RE-GAIN is implemented in accordance with AGRA's Environmental and Social Management System (ESMS), relevant GCF environmental and social requirements, and applicable international good practice. The ESMS is integrated into AGRA's Programme Operations Manual (POM), including requirements related to environmental and social risk management, stakeholder engagement, gender and accountability. The environmental and social screening for RE-GAIN activities in Ethiopia has been completed. The current requirement is therefore to operationalise and strengthen implementation of the existing ESMS and related accountability and safeguarding arrangements, rather than establish parallel systems. The consultant will provide country-level technical support to AGRA Ethiopia to strengthen implementation of mitigation measures, stakeholder engagement, grievance and feedback mechanisms, safeguarding, accountability and partner assurance. Particular attention will be given to establishing an accessible Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system with appropriate hotline/SMS functionality.
2. OBJECTIVE OF THE ASSIGNMENT
Overall Objective
To support AGRA Ethiopia to operationalize the existing RE-GAIN Environmental and Social Management System (ESMS) and strengthen country-level accountability, safeguarding and partner assurance arrangements.
Specific Objectives
The consultancy will:
- Refine and operationalize Environmental and Social Action Plans (ESAPs) for RE-GAIN interventions and partners.
- Develop and support implementation of a risk-proportionate Stakeholder Engagement Plan (SEP).
- Establish and operationalise an AGRA Ethiopia country-level Grievance and Feedback Mechanism (GFM), including a fit-for-purpose digital complaints and feedback management system and appropriate hotline/SMS channels as part of FGM.
- Develop a Country Accountability, Safeguarding and Partner Assurance Framework, including minimum safeguarding standards and partner assurance tools.
- Build the capacity of AGRA staff and partner focal points to manage ESMS, accountability, safeguarding and feedback systems sustainably.
3. SCOPE OF WORK
The consultant will undertake the following key activities:
3.1. Environmental and Social Action Plans
- Review screening results, risk categorization and existing mitigation measures.
- Refine ESAPs with clear actions, responsibilities, timelines, indicators and budgets where required.
- Facilitate consultations with implementing partners, suppliers and relevant stakeholders to agreed actions.
- Establish and maintain a consolidated country ESAP tracker.
3.2. Stakeholder Engagement
- Map and analyse key stakeholders, including farmers, women, youth, persons with disabilities, advisors, cooperatives, MSMEs, suppliers, financial institutions, government institutions and relevant community organisations. Assess their interests, influence, exposure to programme risks, communication needs and barriers to participation, and identify appropriate engagement methods.
- Develop a risk-proportionate SEP covering information disclosure, participation, feedback and inclusion.
- ` for list items. I'll also keep `` maybe for key terms, but to avoid violation, I'll just use normal text or if it was originally. Actually, the instruction says "Use
- `.
Let's decide: I will convert the entire text into semantic HTML as per rules. I'll strip the `style="text-align:justify;"` inline styles. I'll keep all text content exactly. I'll use `
Apply Now ↗How well do you match?
Get an instant AI match score for this role — free, takes 3 minutes.
Tailor your CV for this role
The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.
Tailor My CV to This Job ✍️Free cover letter for this job
Upload your CV and get a tailored cover letter in seconds — free, no account needed.
Generate a Cover Letter 📝 - as specified. I'll keep only if it doesn't conflict, but to be safe, I might just keep the text without , or I can use since it's allowed. The rule says "No CSS classes, no inline styles, no
- for list items. It doesn't say I can't use , but it says "No CSS classes, no inline styles, no
- for list items (duties, requirements, qualifications, skills)
- No CSS classes, no inline styles, no
. Preserve all content word-for-word. Let's examine the job description text. It's already mostly in
tags with some inline styles (text-align:justify, style=...). But the rule says: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". And "Use
for introductory paragraphs and general text", "Use
for section headers", "Use
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.