RE

Consultancy for YIGA Baseline Study

Contractor Arua, UG
Posted 3 days, 6 hours ago 77 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor. - I receive raw scraped text from a job website. - My job: extract ONLY actual job information, return clean, readable format. - Must REMOVE: social sharing text, author bylines, "you may also like", navigation, comments, ads/promotions, cookie/subscription notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts. - Must KEEP and STRUCTURE: job title, company/org, location, job description/responsibilities, requirements/qualifications, how to apply, salary (if mentioned), deadline/closing date, job ID/reference number, contract type/level. - Return ONLY the cleaned job text. No commentary, no headers like "Here is the cleaned version", no markdown formatting. Just the clean job listing text. Wait, the actual prompt I'm given is a bit different. It says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then there are 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. Then there's the job description text provided. Important: The prompt says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." And the HTML rules are specific:

    ,

    ,
    • , no classes, no inline styles, no
      , no
      . But the source text has inline styles like `font-size: 10pt; font-weight: bold` etc. The rule says "No CSS classes, no inline styles, no
      s, no
      tags". So I need to strip out the inline style attributes, but preserve the text content word-for-word. Also, the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This conflicts slightly with removing inline styles, but I think the intent is to preserve the textual content, not the formatting markup. I should strip the `style="..."` attributes but keep the text inside. Also, the first part of the prompt describes a different task (job listing editor, remove/keep certain things), but the actual instruction I need to follow is the one about formatting as clean semantic HTML with those specific tags. The user probably combined two prompts, but I should follow the explicit instructions given: "Your ONLY job is to format it as clean semantic HTML." with the listed rules. Let me re-read carefully: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML. 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." Then the job description text is provided. I need to convert this text into HTML using only

        ,

        ,
          ,
        • , and plain text content, stripping all `style="..."` attributes, and keeping all original content word-for-word. Let me parse the job description text and structure it. First, let's identify sections and content: The text starts with: `

          Apply By Friday, 9th October 2026 at 5:00 PM (E.A.T)

          ` Then `



          ` etc. I need to strip all `` and just keep the text, or wrap appropriately. Let me go through the text systematically and extract content, ignoring the inline styles, and structure with

          for section headers,
          • for lists,

            for paragraphs. The text has these apparent sections based on headers: - Apply By Friday, 9th October 2026 at 5:00 PM (E.A.T) - CONSULTANCY OPPORTUNITY - Restless Development Uganda - Call for Consultant: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA). - About Restless Development - Our approach to safeguarding - Consultancy Overview: - Assignment: - Project Summary. - Project Title: - Project Duration: - Type of Study: - Project Location: - Donor: - Duration of assignment: - Expected start/ end of assignment: - Project Background - Purpose of the Consultancy - Duration of assignment and Budget - Qualifications: - Experience: - Skills / Technical Knowledge: - Other Requirements: - Application Process - Submission Deadline: - To Apply: - Note: Restless Development does not charge fees at any stage of the recruitment process. - Click here to return to our website. I need to map these to the specified headers: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. But the rule says "Use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It says "e.g.", so I should use appropriate headers based on the content, or use exactly those? It says "Use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". I think I should use

            tags for section headings, and the text inside should be the original section titles or appropriate labels. But the rule also says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is tricky if I need to change "Qualifications:" to "Qualifications" as an

            , that's not rephrasing, it's just markup. I think I can wrap the section titles in

            and then the content below in
            • or

              . Let me look at how the text is structured. The original text has spans with `font-weight: bold` acting as headers. I'll extract the text content, strip the span tags, and use

              for what were bold headers, and

              or

              • for the rest. But the rule "Preserve ALL original content word-for-word" means I shouldn't alter the text itself. So if a line says "Qualifications:", I should keep "Qualifications:" exactly. I can put it as

                Qualifications:

                or just

                Qualifications

                . The colon might be part of the content. I'll keep it as is. Let me parse each part: 1. `

                Apply By Friday, 9th October 2026 at 5:00 PM (E.A.T)

                ` -> Text: "Apply By Friday, 9th October 2026 at 5:00 PM (E.A.T)". I'll wrap in

                or maybe it's a deadline. The rules say use

                for introductory paragraphs and general text. I'll put it in

                . 2. `



                ` -> empty paragraphs with line breaks. The rule says no
                tags. I should probably omit empty

                tags or just keep them as

                ? But "Preserve ALL original content word-for-word" - empty lines might be considered content? I think I should omit purely presentational empty paragraphs, but the rule says no
                tags, and these are just `



                `. I'll likely skip them or handle as needed. Actually, the rule says "If text has no clear sections, just wrap paragraphs in

                tags". I'll try to structure meaningfully and omit empty ones. 3. `

                CONSULTANCY OPPORTUNITY - Restless Development Uganda

                ` -> "CONSULTANCY OPPORTUNITY - Restless Development Uganda" 4. `

                Call for Consultant: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA).

                ` -> Text: "Call for Consultant: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA)." Note the colon is inside the second span? Actually it's "Call for Consultant" then ": Baseline...". I'll keep the whole thing as text. 5. `


                ` - skip 6. `

                About Restless Development

                ` -> "About Restless Development" 7. The long paragraph about Restless Development. I'll put in

                . 8. `

                Our approach to safeguarding

                ` -> "Our approach to safeguarding" 9. Paragraph about safeguarding.

                . 10. `

                Consultancy Overview:

                ` -> "Consultancy Overview:" Then `

                Assignment: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA).` -> I'll combine: "Assignment: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA)." 11. `


                ` skip 12. `

                Project Summary.

                ` -> "Project Summary." 13. Then several `

                Project Title:
                Promoting Youth Inclusion in Governance and Decision making.

                ` etc. There are `
                ` tags inside some paragraphs. Rule says no
                tags. I need to handle this. The text after `
                ` is on a new line. I can either merge them into the same

                or create separate

                tags. Since I can't use
                , I'll just put them in the same

                with a space, or use

                for each. But the rule says "Preserve ALL original content word-for-word". If I merge with a space, it's still word-for-word, just formatting changed. I think it's okay to put them in the same

                or separate. Given the structure, I'll likely put each key-value pair as a

                or use

                • if it's list-like. But many are not strictly lists; they're formatted as bold label then normal text. I need to decide. Let's look at the pattern: `

                  Project Title:
                  Promoting Youth Inclusion in Governance and Decision making.

                  ` This is a paragraph with a bold label and then text on a new line. Without
                  , I can just write "Project Title: Promoting Youth Inclusion in Governance and Decision making." in a single

                  . But the rule says "Preserve ALL original content word-for-word". Adding a space between colon and text is fine, it's still the same words. I'll merge them. However, some are clearly list items later on, like under Qualifications, Experience, etc., which use `

                  • ...
                  `. Those I'll keep as
                  • with the text. Let me reorganize the entire text into a structured HTML format. I'll go through each line, extract text, strip span tags and style attributes, and reconstruct. Goal: Use

                    for section headers,
                    • for lists,

                      for other text. No inline styles, no
                      , no

                      . I need to identify natural sections. The text has sections like: - About Restless Development - Our approach to safeguarding - Consultancy Overview (with Assignment, Project Summary, etc.) - Project Summary (with Title, Duration, Type, Location, Donor, etc.) - Project Background - Purpose of the Consultancy - Duration of assignment and Budget - Qualifications - Experience - Skills / Technical Knowledge - Other Requirements - Application Process - Submission Deadline - To Apply - Note - Click here to return to our website Some of these can be

                      , some

                      , some

                      • . The rule says: "Use

                        for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" and "Use
                        • for list items (duties, requirements, qualifications, skills)". So I should use

                          for main section headings, and
                          • for lists of items. For prose paragraphs, use

                            . Let me map the content: - "CONSULTANCY OPPORTUNITY - Restless Development Uganda" could be part of

                            or

                            . Maybe

                            "Consultancy Opportunity" or just

                            . I'll see. - "Call for Consultant: Baseline and Inception Benchmark Assessment for the West Nile Extension of the Promoting Youth Inclusion in Governance and Decision-Making Project (YIGA)." could be

                            or

                            . I'll put as

                            . - "About Restless Development" ->

                            About Restless Development

                            - The long paragraph about Restless Development ->

                            ...

                            - "Our approach to safeguarding" ->

                            Our approach to safeguarding

                            - Safeguarding paragraph ->

                            ...

                            - "Consultancy Overview:" -> this is a header. I'll use

                            Consultancy Overview

                            Then under that, we have Assignment, Project Summary, etc. These are not necessarily lists, but key-value pairs. I could put them as

                            pairs, or as

                            • if I treat them as items. Given the later sections use
                              • for qualifications etc., I might use
                                • for the project summary items too. But the rule says "Use
                                  • for list items (duties, requirements, qualifications, skills)". Project summary items like "Project Title: ...", "Project Duration: ..." are not exactly duties/requirements/qualifications/skills, but they could be considered information items. I'll likely use

                                    for those, or

                                    • if it feels right. Let's see the qualifications section: it has `
                                      • Educational Background:
                                          ...` which is nested. I need to handle that. Actually, looking at the qualifications section: `
                                          • Educational Background:
                                            • PhD or MSc in fields such as Public Policy, Governance, Human Rights, Policy Analysis, Social works or other areas relevant to the study.
                                            • Qualifications in Monitoring and Evaluation (M&E) will be considered an added advantage.
                                          • ` This is a list within a list. I need to preserve content word-for-word. I'll simplify the nesting but keep all text. Since I can't use
                                            or classes, I'll just use
                                            • appropriately. Maybe I'll flatten it or keep the structure. The rule says "If text has no clear sections, just wrap paragraphs in

        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 📝

        Join Our Uganda Channels

        Get free job alerts on your phone

MJC
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.

How was your experience with ECHO?