Protection Data Technical Assistant Nigeria Maiduguri

for introductory paragraphs and general text 2. Use

for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) 3. Use

• for list items (duties, requirements, qualifications, skills) 4. No CSS classes, no inline styles, no
  s, no
  tags 5. Preserve ALL original content word-for-word 6. If text has no clear sections, just wrap paragraphs in

  tags 7. Return ONLY the HTML Let me parse through the content: 1. Opening paragraph about NRC core values - this is introductory text, use

  2. List of qualifications/requirements - use

  • 3. "2. Behavioural competencies" section header - use

    4. Behavioral competencies list - use

    • 5. "Performance Management" section - this seems like context, not really a job requirement section. But it's part of the job description. I'll include it as a section. 6. "Role and responsibilities" section header - use

      7. "Generic responsibilities" section header - use

      8. Generic responsibilities list - use

      • 9. "Specific responsibilities" section header - use

        10. Specific responsibilities list - use

        • 11. "Critical interfaces" section header - use

          12. Critical interfaces text - this is a paragraph Wait, I need to be careful. The instructions say to use

          for section headers like "Responsibilities", "Qualifications", "Requirements", "Education", "Experience", "Skills", "How to Apply", "Key Duties", "About the Role". But the original text uses tags for some headers like "2. Behavioural competencies", "Generic responsibilities", "Specific responsibilities", "Critical interfaces". These are section headers within the job description. I should convert these to

          tags since they are section headers. Also, there's a mention of "Performance Management" which lists documents used for performance reviews. This seems like part of the job description but more of an administrative note. I should include it as it's part of the role description. Let me also check if there's any salary information mentioned... No, there isn't. Is there a deadline? Not explicitly mentioned in this text. Job ID/reference number? Not mentioned. Contract type/level? Not explicitly mentioned. Location? Not explicitly mentioned in this text either. Company name? Not explicitly mentioned. So I'll focus on what's available: job title (implied from the content), company (NRC), location (Borno and Adamawa mentioned), responsibilities, qualifications, behavioral competencies, performance management details, generic responsibilities, specific responsibilities, critical interfaces. Let me structure this carefully: ```html

          All NRC employees are expected to work in accordance with the organization's core values: dedication, innovation, inclusivity and accountability. These attitudes and believes shall guide our actions and relationships.

          • Diploma or degree in information management, statistics, computer science, social sciences or a related field; relevant practical experience may be considered.

          ...

          Behavioural competencies

          These are personal qualities that influence how successful people are in their job. NRC's Competency Framework states 12 behavioural competencies, and the following are essential for this position:

          • Handling insecure environment
          ...

          Performance Management

          The employee will be accountable for the responsibilities and the competencies, in accordance with the NRC Performance Management Manual. The following documents will be used for performance reviews:

          • The Job Description
          ...

          Role and responsibilities

          Generic responsibilities

          These responsibilities shall be the same for all positions with the same title. The responsibilities shall be short and essential. Details belong in the Work and Professional Development Plan.

          • Adhere to NRC policies, tools, handbooks, protection information management standards and data protection procedures.
          ...

          Specific responsibilities

          These responsibilities shall be adapted to the particularities of the job location and context, phase of operation, strategic focus and type of programme intervention. This section shall be revised whenever a new employee is hired or the context changes significantly.

          ...

          Critical interfaces

          By interfaces, NRC means processes and projects that are interlinked with other departments/units or persons. Relevant interfaces for this position are:

          Protection from Violence Programme Development Manager (PDM), PfV Team Leaders, Of

          ``` Wait, I need to preserve the text exactly. Let me re-read the original carefully. The last line says: "Protection from Violence Programme Development Manager (PDM), PfV Team Leaders, Of" - this seems cut off. I should preserve it as is. Actually, looking more carefully at the instructions: "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" So I should map the section headers appropriately. The original uses tags for some headers. I'll convert those to

          . For "2. Behavioural competencies" - this is a numbered section header. I could keep the number or just use the title. Since the instruction says to preserve word-for-word, I should probably keep the numbering. But actually, looking at the examples given, they don't include numbers. Let me think... The instruction says "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". These examples don't have numbers. So I should probably strip the numbering and just use the title. Actually wait - "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I shouldn't remove the number "2." from "2. Behavioural competencies". Hmm, but the examples given for h4 don't include numbers. I think the safest approach is to keep the numbering since we're preserving word-for-word. Or maybe I should interpret "section headers" as the titles themselves, and the numbering is just a prefix. Let me go with keeping the number since it's part of the original text. Actually, re-reading: "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The examples are just the titles without numbers. I think the intent is to use the title text as the h4 content. The numbering might be considered formatting rather than content. But to be safe and preserve word-for-word, I'll include the number. Hmm, let me reconsider. The instruction says "Preserve ALL original content word-for-word". The "2." is part of the original text. So I should keep it. But actually, looking at the examples more carefully - they're just listing example titles. The numbering in the original ("2. Behavioural competencies") is a heading marker. I think using just the title text in h4 is fine, and the number can be included or excluded. To be safe, I'll include it. Wait, actually I realize I should look at this differently. The original text has: - `2. Behavioural competencies` This is a section header. I should convert this to `

          2. Behavioural competencies

          ` or just `

          Behavioural competencies

          `. Given the instruction to preserve word-for-word, I'll include the number. Let me also handle the "Performance Management" section. It's listed as a numbered item in an ordered list, but it's really a section header within the job description. I'll convert it to h4. Similarly, "Role and responsibilities" is another section header. OK, let me draft the full HTML now. One more thing - the instruction says "No CSS classes, no inline styles, no

          s, no
          tags". So I need to remove all the style attributes from the original HTML. Also, the instruction says to use

          for introductory paragraphs and general text, and

          • for list items. For the behavioral competencies list, each item is just a phrase, so I'll put them in
          • elements. For the performance management documents list, each item is a document name, so
          • elements. For generic responsibilities, each item is a responsibility statement, so
          • elements. For specific responsibilities, each item is a responsibility statement, so
          • elements. Let me also check - the first paragraph mentions "All NRC employees are expected to work in accordance with the organization's core values..." This is introductory text about the organization's values, not directly about the job. But it's part of the job description, so I'll include it. Now let me write the final HTML: ```html

            All NRC employees are expected to work in accordance with the organization's core values: dedication, innovation, inclusivity and accountability. These attitudes and believes shall guide our actions and relationships.

            • Diploma or degree in information management, statistics, computer science, social sciences or a related field; relevant practical experience may be considered.

            • At least two years of relevant experience in data entry, database administration, monitoring data management or programme information support, preferably in humanitarian programming.

            • Good working knowledge of Microsoft Excel, Word, Power BI, email and digital data collection platforms such as Kobo/ODK; ability to use templates, formulas, filters and basic data validation.

            • Demonstrated accuracy in data entry, reconciliation, data cleaning, document control and maintaining clear electronic and physical filing systems.

            • Basic understanding of protection information management, data minimization, informed consent, confidentiality, secure data handling and safe information sharing.

            • Ability to compile and update indicator tracking tables (ITTs), routine monitoring databases and dashboard source datasets under technical guidance.

            • Ability to identify missing, duplicate or inconsistent records, maintain issue logs, follow up on corrections and escalate potential data integrity breaches promptly.

            • Strong organizational skills, written English for routine reporting, ability to prioritize deadlines and work independently with minimal supervision.

            • Knowledge of the humanitarian context in Borno and Adamawa, relevant local languages and experience supporting geographically dispersed field teams are advantages.

            2. Behavioural competencies

            These are personal qualities that influence how successful people are in their job. NRC's Competency Framework states 12 behavioural competencies, and the following are essential for this position:

            • Handling insecure environment
            • Planning and delivering results
            • Empowering and building trust
            • Communicating with impact and respect

            Performance Management

            The employee will be accountable for the responsibilities and the competencies, in accordance with the NRC Performance Management Manual. The following documents will be used for performance reviews:

            • The Job Description
            • The Work and Development Plan
            • The Mid-term/End-of-trial Period Performance Review Template
            • The End-term Performance Review Template
            • The NRC Competency Framework

            Role and responsibilities

            Generic responsibilities

            These responsibilities shall be the same for all positions with the same title. The responsibilities shall be short and essential. Details belong in the Work and Professional Development Plan.

            • Adhere to NRC policies, tools, handbooks, protection information management standards and data protection procedures.
            • Support accurate and timely collection, digitisation, consolidation and validation of PfV monitoring and activity information from the four project LGAs.
            • Maintain updated ITTs, approved protection databases, submission trackers and dashboard source datasets under PDM and MEAL technical guidance.
            • Maintain secure, complete and traceable physical and electronic programme records, including authorized Means of Verification.
            • Identify and promptly flag incomplete, inconsistent, late or potentially compromised data; track follow-up and corrections.
            • Prepare routine data quality and submission reports, attend data review meetings and support timely programme reporting.
            • Coordinate with PfV field teams, MEAL, IMO and relevant partners while respecting access restrictions and information sharing protocols.
            • Plan and deliver assigned tasks with accuracy, integrity, confidentiality and accountability, working under pressure with minimal supervision.

            Specific responsibilities

            These responsibilities shall be adapted to the particularities of the job location and context, phase of operation, strategic focus and type of programme intervention. This section shall be revised whenever a new employee is hired or the context changes significantly.

            • Receive, register and consolidate protection monitoring and activity datasets from Bama, Gwoza, Monguno and Madagali; maintain a submission tracker and follow up on missing or late field returns.
            • Digitize approved hard-copy monitoring forms, activity records and other authorized programme documentation accurately, checking legibility, completeness and consistency against source records.
            • Carry out routine data entry, cleaning, de-duplication and basic validation using NRC-approved tools; flag missing fields, conflicting figures, duplicate entries and unusual trends to the PDM and MEAL for resolution.
            • Support the PDM in maintaining the Protection Monitoring Dashboard by updating validated source datasets, checking dashboard inputs and documenting changes; do not independently approve or publish protection analysis.
            • Update protection indicator tracking tables (ITTs), activity databases and other approved reporting trackers with verified information; reconcile totals, reporting periods, locations and disaggregations with MEAL colleagues.
            • Maintain separate, access-controlled records for protection monitoring, referrals, Individual Protection Assistance (IPA) and protection case management as authorised; do not merge identifiable case records into general dashboards or circulate case-level information without approval.
            • Maintain a data quality and correction log, assign follow-up actions to relevant field focal points and escalate suspected data tampering, unauthorised access, loss or disclosure immediately through NRC reporting channels.
            • Support completeness checks of Means of Verification (MoVs), attendance records, referral documentation and authorised IPA/PCM tracking records, without making case eligibility or assistance approval decisions.
            • Maintain organised and secure physical and electronic filing, version control, naming conventions, restricted access, approved retention schedules and safe archiving of documents in accordance with NRC policies.
            • Coordinate regularly with the four LGA teams and implementing partner data focal points to obtain submissions, clarify data gaps and support consistent use of approved forms and reporting templates.
            • Work closely with NRC MEAL, and IMO colleagues to apply approved data standards, conduct routine reconciliations, support data review meetings and prepare accurate data extracts for authorised reporting.
            • Prepare weekly data submission and completeness updates for the PDM, including progress against reporting deadlines, outstanding issues, data quality risks and corrective actions; provide ad hoc updates as requested.
            • Support timely preparation of validated aggregate information for programme and donor reporting, ensuring figures are traceable to approved source records and do not disclose personally identifiable information.
            • Follow NRC protection information management standards, informed consent, confidentiality, safeguarding, data protection and information sharing protocols; use only authorized systems and report any breach promptly.
            • Prepare and follow a weekly work plan, organize competing tasks, meet agreed deadlines and proactively request guidance when technical decisions or permissions exceed the assistant role.

            Critical interfaces

            By interfaces, NRC means processes and projects that are interlinked with other departments/units or persons. Relevant interfaces for this position are:

            Protection from Violence Programme Development Manager (PDM), PfV Team Leaders, Of

            ``` Hmm, wait. Let me reconsider the structure. The original has: 1. An intro paragraph about core values

  Translated by AI — may not be perfect

  Show original