NGO Project Manager Job Description: Responsibilities, Skills and Tools

Most NGO project manager job descriptions are copied from the last recruitment, padded with generic phrases and silent on the two things that decide whether the person succeeds: the donor rules they will apply and the tools they will run. This article gives a usable NGO project manager job description, for the recruiter who publishes it and the candidate who reads between its lines. It sits inside our project management for NGOs guide and complements the MEAL officer job description.

The NGO project manager job description in one paragraph

The project manager is accountable for delivering one or several funded projects on time, within the approved budget and in compliance with the funding agreement. They report to a country director, head of programmes or desk officer at headquarters. They manage the project team (field officers, MEAL officer, sometimes a project accountant or logistician) and coordinate finance, HR and logistics without line authority over them. They are the organisation's first interface with the donor on technical and contractual matters, with headquarters on reporting and strategy, with the field on daily implementation, and with partners on sub-grants and joint activities. One person holds the thread between the proposal that was signed and the reality on the ground.

Main responsibilities in five blocks

1. Design and proposals

• Lead or contribute to needs assessments and feasibility studies.
• Build the intervention logic: theory of change, logical framework, indicators and targets.
• Draft the technical narrative and build the project budget with finance, in the donor's format.
• Answer donor clarifications and negotiate the final agreement.

2. Planning and implementation

• Produce and maintain the work plan, procurement plan and recruitment plan.
• Run weekly planning, track progress against the chronogram, decide corrective action.
• Manage amendments, no-cost extensions and reallocations under each donor's rules.
• Lead project closure: handover, asset disposal, archiving.

3. Budget and compliance

• Hold the budget: monthly follow-up, burn rate, forecast to end of project.
• Approve expenditure within the delegation of authority; check eligibility before commitment, not after invoice.
• Apply the donor's procurement thresholds and documentation requirements.
• Keep the project audit-ready: supporting documents, timesheets, contract and partner files.

4. MEAL and reporting

• Supervise the MEAL plan with the MEAL officer: data collection, indicator tracking, complaint mechanism.
• Write narrative reports and validate the financial report with finance, within donor reporting deadlines.
• Run reviews and lessons-learned sessions; feed findings into the next proposal.
• Host donor field visits and respond to monitoring findings.

5. Team, partners and security

• Recruit, brief, supervise and appraise the team; validate timesheets and leave.
• Manage partners: due diligence, sub-grant agreements, capacity support, report review, monitoring visits.
• Represent the project in clusters, working groups and with local authorities.
• Apply the security plan, validate movements, escalate incidents.

Required skills: hard and soft

Hard skills, to be tested rather than read on the CV:

• Project cycle management: the full cycle from identification to evaluation, as in our PCM guide, with the PMD Pro vocabulary most INGOs use.
• Logframe and indicators: write a SMART indicator, set a baseline and a target, explain output versus outcome without hesitation.
• Budget management: read a budget versus actual table, compute a burn rate, spot an over-commitment, understand shared cost allocation.
• Donor rules: working knowledge of at least two of EU/ECHO (Single Form, cost eligibility), AFD (expenditure verification, co-funding), UN agencies (PCA/FLA formats) and bilateral donors such as USAID where relevant.
• Procurement basics: thresholds, three quotes, tender committees, conflict-of-interest declarations, a complete procurement file.

Soft skills, the difference between a manager who survives and one who delivers:

• Remote management of a team spread across a base and several sites, with weak connectivity and irregular visits.
• Negotiation with the donor on a reallocation, with a partner on a late report, with headquarters on an unrealistic target.
• Writing: clear, factual narrative in the donor's language. A manager who cannot write a report alone will cost the organisation a consultant.
• Prioritisation: knowing which of this week's twelve urgent things carries a contractual risk.

Profile, experience and compensation

A typical profile combines a master's degree (development, public health, engineering, social sciences, management) or equivalent experience, three to five years in the sector including one full project cycle as deputy or assistant project manager, and prior exposure to the donor funding the position. Field experience in a comparable context weighs more than the diploma. Reports will be written in English or French; the team will be managed in the local language.

On compensation, be honest rather than precise. The salary is set by the organisation's salary scale, adjusted for the country of posting and national or international status, and capped by what the donor accepts as an eligible staff cost. Publish the grade and scale reference, the status and the benefits package (housing, R&R, insurance, per diem policy), and let the HR system hold the actual figures. Candidates read "attractive salary" as a warning sign; a grade and a scale read as transparency.

Tools in an NGO project manager job description

The tools line is usually reduced to "proficiency in MS Office". In 2026 that is a red flag in both directions. A candidate whose only tool is a spreadsheet has never worked with a budget that updates when finance posts an invoice. An organisation whose only tool is a spreadsheet is telling the candidate that budget follow-up, commitments, timesheets and indicators will be rebuilt by hand every month, with the risks of spreadsheet-based financial management carried into every audit. The job description should name what the manager will actually run:

• A budget follow-up tool by donor line, with commitments and forecast, not just actuals.
• A MEAL tool for the logframe, indicator values and the complaint mechanism, shared with the MEAL officer.
• A planning tool (work plan, Gantt or kanban) the whole team sees.
• Timesheets and leave management, because staff costs charged to the donor must be traceable.
• A document repository where contracts, procurement files and reports are attached to the project, not to a personal laptop.
• Field data collection tools with offline capability.

The essential project management templates remain a useful common language, but they are the format, not the system.

Interview grid: five questions

1. "Walk me through a budget you managed: what was the burn rate at month six, and what did you do?" A good answer gives a figure, names the under- or over-spent lines and describes a concrete decision (reallocation request, rescheduling, faster procurement) with its timing.
2. "Describe an indicator you had to revise during implementation." Expect why the original was unmeasurable or misleading, how the change was documented, and whether the donor was told before or after the report.
3. "A partner sends a financial report with missing supporting documents three days before your donor deadline. What do you do?" Look for a sequence: assess materiality, contact the partner, decide what can be included, flag it to finance and the donor. Absorbing it silently is the wrong answer.
4. "How do you manage a field team you see once a month?" A strong answer describes routines (weekly call, shared work plan, written briefs), delegation rules and early warning signals, rather than trust alone.
5. "What is the most important rule of the donor funding this position?" No need for the article number, but the candidate should name a real constraint (eligibility period, procurement threshold, visibility, reporting format) and explain how it changes daily practice.

How Abvius supports the project manager

Abvius was built for the position described above: one person who needs budget, logframe, team and documents in the same place.

• Budget by donor line with actuals, commitments and remaining balance: a purchase is checked against available budget before approval, not after.
• Logframe and indicators next to the budget in the MEAL module: progress and spending on one screen.
• Timesheets filled in by the team, validated by the manager, and used to compute the staff time charged to the project, as explained in our article on timesheets and donor audits.
• Documents (contract, quote, partner report, mission order) attached to the record they justify, which is what an auditor asks for first.
• Reports built from the data already entered, in the donor's format; the HR module holds the salary scale and contract data.

In practice

If you are recruiting, rewrite the tools section first and add the five questions to your interview grid; the answers will tell you more than the CV. If you are a candidate, read the NGO project manager job description for what it does not say: if neither the donor nor the tools are named, ask. In both cases, the project manager's daily success depends on having budget, logframe, team and documents in a single system. Start a free Abvius trial to see it on a real project, or contact us for a demo.