PROJECT PLANNING &

MANAGEMENT

DETAILED STUDY NOTES WITH EXAMPLES

Lectures 7 – 13 | Exam-Ready Reference

Risk Management • Proposals • Implementation • Closure • Financial Control •

Scheduling • EVM

■ Lecture 7 ■ Lecture 8 ■■ Lecture 9-10 ■ Lecture 11 ■ Lecture 12 ■ Lecture 13

Risk Fundamentals Proposal Logic Implementation Closure Financial Control Scheduling & EVM
 LECTURE — TABLE OF CONTENTS

Lecture 7: Risk Management

• Core Risk Fundamentals
• Risk Management Process & Risk Register
• Risk Response Strategies
• Sustainability & Logframe Link
• Top Mistakes
Lecture 8: Project Proposals
• Proposal Logic & Anatomy
• Problem Analysis & Stakeholder Mapping
• SMART Objectives & Logframes
• Budgeting, M&E; & Sustainability
• Public-Sector PC-1
• Proposal Rejection Defects
Lectures 9-10: Implementation
• Core Fundamentals & Building Blocks
• Team Roles & Accountability
• Operational Planning & Quality Control
• Communication Management
• Risk Mitigation & Mistakes
Lecture 11: Project Closure
• Closure Fundamentals & Types
• Closure Checklist
• Asset Handover
• Lessons Learned & AAR
Lecture 12: Financial Control
• Budgeting & Cost Classifications
• Donor Compliance
• Variance Analysis
• Financial Risks
Lecture 13: Scheduling & EVM
• Project Scheduling
• Cost Calculation & Baselines
• EVM Core Metrics
• Scenario Diagnostics
 LECTURE 7 — RISK MANAGEMENT

Topic 1: Core Risk Fundamentals

■ CORE CONCEPT

Risk is an uncertain future event that carries negative consequences for a project's cost, time, scope, or
quality — but can be controlled with proactive management.

Formula: Risk = Uncertainty × Impact

■ REAL-WORLD EXAMPLE: NGO Housing Project

An NGO plans to build houses without checking weather patterns. An unexpected monsoon season destroys half-built
structures → massive budget overruns and timeline delays. Proactive risk management would have set aside
emergency funds and schedule buffers BEFORE building starts.

Mnemonic: BEST

B — Budget protection via contingency reserves

E — Escalation prevention by addressing issues early

S — Stakeholder confidence remains high throughout the lifecycle

T — Timelines maintained using structured buffer strategies

Four Risk Categories:

Category Typical Threats Mitigation Example

Financial Cost overruns, delayed donor funding, currency fluctuations, Maintain 10–15% contingency reserve
budget cuts

Operational Staff shortages/turnover, weak PM, supply chain failures SOPs + cross-training backup plans

External Political instability, natural disasters, regulatory changes Continuous external environment monitoring

Technical System crashes, lack of expertise, data security breaches Early staff training + system redundancy

Topic 2: The Risk Management Process & Risk Register

■ CORE CONCEPT

A continuous, repetitive 4-step lifecycle to identify, evaluate, handle, and track threats across the entire
project duration.

■ REAL-WORLD EXAMPLE: Software Development Project

Team identifies early that their lead developer might resign. They: (1) Record it in the Risk Register, (2) Score it as
HIGH severity, (3) Assign it to HR Manager, (4) Cross-train another team member immediately. Without this process,
the project would grind to a halt when the developer eventually does resign.

Mnemonic: I AM

I — Identify — Uncover threats via brainstorming, historical reports, expert interviews, SWOT analysis
 A — Analyze — Rate Probability (1–5) × Impact (1–5) = Risk Score

M — Mitigate/Respond — Execute targeted response: Avoid, Transfer, Accept, or Reduce

+ — Monitor — Track in Risk Register; re-evaluate at every major milestone

Risk Severity Matrix:

Probability \ Impact Low Impact (1–2) Medium Impact (3) High Impact (4–5)

High Prob. (4–5) ■ Moderate ■ Moderate ■ HIGH — Escalate to top management

Medium Prob. (3) ■ Low ■ Moderate ■ Moderate

Low Prob. (1–2) ■ Low ■ Low ■ Moderate

• Low Risk: Monitor only — no immediate action • Moderate Risk: Plan a response, assign an owner, track
deadlines • High Risk: Immediate action required; escalate to top management

Topic 3: Risk Response Strategies

Mnemonic: TEAM

T — Transfer (Shift) — Pass the burden to a third party via contracts, outsourcing, or insurance

E — Eliminate (Avoid) — Change scope, location, or timeline to remove the threat entirely

A — Accept (Tolerate) — Acknowledge low-impact items; use passive/active reserves if they occur

M — Mitigate (Reduce) — Take early proactive actions to decrease probability or impact

■ REAL-WORLD EXAMPLE: Construction Project — River Crossing

HIGH Prob + HIGH Impact flood risk → AVOID by re-routing the path entirely. Tool-theft risk → TRANSFER by buying
insurance policy. Minor shipping delays → ACCEPT using a time buffer in the schedule. Concrete quality variance risk
→ MITIGATE by implementing daily quality checks.

Decision Tree for Choosing a Strategy:

Can we ELIMINATE the source? → YES: AVOID | NO ↓ Can we REDUCE probability/impact? → YES: MITIGATE
| NO ↓ Can a 3rd party BEAR it? → YES: TRANSFER | NO ↓ Is impact LOW enough? → YES: ACCEPT | NO:
Reconsider the project

Topic 4: Project Sustainability & The Logframe Link

■ CORE CONCEPT

Project sustainability = the explicit structural ability of project benefits to keep delivering value to a
community AFTER external funding and resources end.

■ REAL-WORLD EXAMPLE: Clean Water Borehole in a Village

International donor builds a borehole system. If they leave WITHOUT setting up a local collection fee or training local
technicians → system breaks down within months and remains abandoned. Proper sustainability planning would
establish: local fee collection, maintenance contracts with local technicians, and government ownership agreements.

Mnemonic: FISE — Four Pillars of Sustainability

 F — Financial — Design local revenue models, user fees, community funds, or government budget lines

I — Institutional — Build government ownership, SOPs, and secure political will

S — Social — Ensure community buy-in, local cultural fit, and train community champions

E — Environmental — Focus on resource efficiency, renewable assets, and climate resilience

Logframe Row Sustainability Focus Key Checklist Question

Impact Long-term lasting value Will benefits continue post-project closure?

Outcome Structural, systemic changes Are maintenance assumptions realistic?

Outputs Durable deliverables Do deliverables include training manuals & handover plans?

Activities Explicit structural tasks Are capacity-building tasks properly budgeted?

Assumptions Critical external dependencies Is community maintenance assumption realistic?

Topic 5: Top Mistakes in Risk & Sustainability Management

■ REAL-WORLD EXAMPLE: Clinic Built But Quickly Closed

Manager designs a perfect clinic but only schedules community handovers and technician training in the FINAL
MONTH of a 3-year project. Staff leave, knowledge vanishes, and the clinic closes within one year. The mistake:
sustainability was bolted on at the end rather than designed in from Day 1.

Mnemonic: CLOSED — Deadly Project Mistakes

C — Confusing outputs with outcomes — Building a clinic (output) ≠ sustained healthcare delivery (outcome)

L — Late phase planning — Bolting sustainability activities onto the END instead of Day 1

O — One-time assessment — Filling a Risk Register at launch and archiving it forever

S — Ignoring low-scoring threats — Assuming low-rated risks won't change over time

E — Empty accountability — Listing threats without a named owner and action date

D — Donor dependency — Planning entirely around external capital with no self-financing transition
 LECTURE 8 — PROJECT PROPOSALS

Topic 1: Proposal Logic & Anatomy

■ CORE CONCEPT

A project proposal is a structured investment document that converts an abstract idea into an
approval-ready project layout — justifying its public value, financial requirements, and operational
feasibility.

Mnemonic: WHICH — Core Questions Every Section Must Answer

W — What will change, for whom, and by when? (Objectives & Results)

H — How will progress, uncertainty, and continuity be handled? (M&E;, Risks & Sustainability)

I — Is the project needed right now? (Background & Problem Statement)

C — Costs: Are they realistic and fully justified? (Budget & Financing)

H — How will specific activities produce the final results? (Methodology & Work Plan)

The Proposal Evidence Stack (6 layers reviewers expect):

Layer What It Covers

1. Policy National/provincial context & development strategies

2. Data Baseline numbers, unemployment rates, service gaps

3. Stakeholders Beneficiary views, employer/market demand feedback

4. Location District profile, access constraints, existing gaps

5. Trend What is improving, worsening, or changing over time

6. Gap Why existing programs are insufficient

Topic 2: Problem Analysis & Stakeholder Mapping

■ REAL-WORLD EXAMPLE: Youth Employment Program

WEAK: 'Youth need jobs' — Too vague, impossible to evaluate. STRONG: 'In District X, 38% of youth aged 18–29 are
unemployed due to a shortage of certified digital technicians.' → This gives reviewers an exact baseline and confirms
the training directly addresses a market gap.

Mnemonic: DIPPER — Stakeholder Categories

D — Decision Makers — Approving forums, finance/planning departments, or external donors

I — Implementers — Government departments, contractors, training providers, field staff

P — Primary Beneficiaries — Direct output recipients, segmented by age, gender, income, location

P — Partners — Corporate employers, local government, community leaders, financial institutions

E — Engagement Plan — Strategies for how stakeholders are consulted, informed, and involved
 R — Risk-Affected Groups — Individuals who may lose resource access or need social safeguards

Problem Statement Component Weak Version Strong Version

Target Group 'Youth need jobs' 'In District X, 38% of youth aged 18–29 are unemployed'

Causal Gap 'Training is required' 'Employers report shortages in certified technicians'

Scope 'The project will solve poverty' 'The project will improve employability of 1,000 youth'

Topic 3: Project Logic, SMART Objectives & Logframes

■ IF-THEN Results Chain

Inputs (computers) → Activities (training) → Outputs (1,000 certificates) → Outcome (employment

secured) → Impact (economic growth)

Mnemonic: SMART Objectives

S — Specific — Clear target group, location, and issue (e.g., 'Train 1,000 youth aged 18–29 in District X')

M — Measurable — Explicit success indicators (e.g., 'At least 60% of graduates placed in jobs')

A — Achievable — Realistic within available personnel and funding constraints

R — Relevant — Tied directly to root problem analysis and government policy goals

T — Time-bound — Strict deadline (e.g., 'By Month 10')

Logframe Level Definition Application Example Data Source

Impact Long-term macro change Poverty reduction; economic growth National household surveys

Outcome Behavioral/systemic change at 60% of graduates employed within 6 Tracer surveys & employer verifications
project end months

Output Tangible physical deliverable 1,000 youth trained and certified Training completion reports

Activities Technical work tasks Recruit trainers, build curricula, run Attendance registers
sessions

Topic 4: Budgeting, M&E; & Sustainability

■ REAL-WORLD EXAMPLE: Budget Transparency Example

REJECTED: '$100,000 for training' — Too vague, no visibility. APPROVED: HR (staff months × monthly rate) +
Equipment (qty × market unit cost) + M&E; costs + 15% contingency. → This breakdown demonstrates Value for
Money to auditors and reviewers.

Mnemonic: LIFTS — Sustainability Plan Dimensions

L — Learning — Document lessons learned to inform future replication and scaling

I — Institutional — Define which department legally owns and operates services after closure

F — Financial — Identify how recurrent expenses will be paid after grant funding stops
 T — Technical — Plan how equipment, software skills, and systems will be maintained

S — Social — Cultivate community backing, leadership committees, and cultural inclusion

Monitoring Rhythm (Frequency Ladder):

Daily Records → Monthly Reviews → Quarterly Reports → Mid-Term Reviews → Final Evaluation

VfM Dimension Definition Check Question

Economy Minimizing cost of resources while ensuring Are inputs at competitive market rates using procurement rules?
quality

Efficiency Maximizing outputs delivered relative to inputs What is the cost per trained individual?

Effectiveness Ensuring outputs achieve intended outcomes Did training actually lead to employment?

Topic 5: Public-Sector Planning & The PC-1 Document

■ CORE CONCEPT

PC-1 (Planning Commission-1) = the mandatory government project template required to secure formal
review, technical scrutiny, funding, and implementation authority in the public sector.

■ REAL-WORLD EXAMPLE: Government Training Center

A corporate donor might accept a 10-page pitch deck for a new training center. A government planning ministry will
INSTANTLY REJECT it. → The department must translate the concept into a PC-1 with: capital asset phasing,
regulatory NOCs, and economic cost-benefit calculations.

PC-1 Approval Lifecycle (6 Stages):

Stage 1: Department Drafts: Build technical specs, site plans, and cost details
Stage 2: Administrative Review: Internal ministry vetting for policy alignment
Stage 3: Planning Scrutiny: Senior experts critique feasibility, demand, and VfM metrics
Stage 4: Committee Approval: DDWP / CDWP / ECNEC formally votes on the project
Stage 5: Budget Allocation: Project integrated into PSDP for capital fund allocation
Stage 6: Implementation Begins: Funds released; formal procurement packaging starts

Feature General Grant Proposal Government PC-1

Format Flexible; tailored to donor templates Rigidly standardized government template

Audience Philanthropic boards, corporate CSR managers Planning boards, finance scrutinizers

Core Emphasis Problem, solution design, output changes Technical designs, cost phasing, regulatory
readiness

Post-Approval Operational baseline for progress reporting Legal baseline for government audits & revisions

Topic 6: Critical Defects Leading to Proposal Rejection

Mnemonic: UNMASK — Fatal Proposal Flaws

U — Unlinked activity costs — Budget items lack rate breakdowns or links to planned tasks

N — No baseline metrics — Ambitious targets listed without verified baseline values or data sources
M — Missing causal logic — Activities don't directly resolve identified root causes

A — Ambitious, non-SMART objectives — Vague goals impossible to measure or deliver

S — Silence on structural risks — Major threats listed without mitigation actions or owners

K — Knowledge/Sustainability gaps — No recurrent budget lines or handover arrangements

 LECTURE 9–10 — PROJECT IMPLEMENTATION

Topic 1: Core Implementation Fundamentals & Building Blocks

■ CORE CONCEPT

Implementation = the phase where approved plans, budgets, and timelines are converted into
organized field actions (procurement, training, fieldwork) to reliably deliver intended outputs and
outcomes.

Mnemonic: TRAM — Four Building Blocks

T — Teams — Human personnel who execute, supervise, support, analyze, and report progress

R — Resources — Cash, materials, equipment, logistics, vehicles, and legal approvals

A — Activities — Real-world field tasks: training sessions, site surveys, awareness workshops

M — Monitoring — Routine, continuous tracking of task quality, indicators, and learning

■ REAL-WORLD EXAMPLE: Youth Training Program Launch

Agency receives authorization to launch a 6-month program. Without coordination: → Months pass without classrooms
being booked or trainers being vetted. Effective implementation means coordinating TRAM so fieldwork begins on time
and stays aligned with target metrics.

Topic 2: Project Team Roles & Structural Accountability

Mnemonic: RACI Matrix Framework

R — Responsible — The team member who DIRECTLY PERFORMS the day-to-day task

A — Accountable — The SINGLE individual with final ownership (only ONE 'A' per task)

C — Consulted — Subject matter experts whose input is gathered before/during the task

I — Informed — Stakeholders kept updated without being directly involved

Project Role Main Responsibility Primary Output

Project Manager (PM) Team conductor; coordinates schedules, delegates Work plans, review meetings, donor progress notes
tasks, manages stakeholders

Field Staff Executes physical ground activities, meets stakeholders, Attendance logs, issue reports, raw field notes
records field realities

M&E; Team Evaluates indicators, verifies data, drives project learning Performance dashboards, KPI track updates

Technical Experts Guides quality, design standards, and technical Training materials, operating manuals, policy guides
relevance

Finance / Admin Manages cash plans, procurements, and transaction files Payment logs, procurement packets, audit trails

Topic 3: Operational Planning, Quality Control & Issue Logs

 ■ REAL-WORLD EXAMPLE: Training Cascade Delay

Training launch set for Monday morning. Finance processes venue payment LATE → locked classrooms. Because the
team didn't link procurement milestones to the activity launch on the Gantt chart → a small procurement lag triggers a
cascade delay across the entire program. FIX: Always link financial milestones to activity start dates on your Gantt
chart.

Mnemonic: CRADLE — Continuous Quality Monitoring Loop

C — Collect data — Routinely gather field outputs, numbers, observations, community feedback

R — Review progress — Analyze target metrics using visual dashboards

A — Assess quality — Physical spot checks, pre/post-tests, supervisor back-checks

D — Diagnose root causes — Evaluate dropouts, trainer variances, supply chain bottlenecks

L — Log active issues — Record every problem immediately in a centralized tracker

E — Execute course adjustments — Adapt schedules to field realities, maintain destination goals

Issue Log Template:

Issue Description Assigned Owner Action Taken Due Date Status

Low training attendance at Field Lead Call dropouts; adjust timing to avoid Friday Open
Center A work hours

Master instructor resigns Training Lead Activate backup roster; adjust Today Escalated
unexpectedly timetable

Survey forms missing critical M&E; Officer Pause collection; run data-entry Wednesday In Progress
data coaching

Topic 4: Communication Management & Channels

Mnemonic: MESH — Choose Channels Intentionally

M — Meetings (Weekly) — Best for reviewing progress, identifying bottlenecks, locking in action owners

E — Email — Best for formal records, documenting scope updates, submitting donor updates

S — Shared Dashboards — Best for immediate visibility over KPIs and tracking red flags

H — Hotline / Daily Chat — Best for urgent field troubleshooting and immediate hazard updates

■ REAL-WORLD EXAMPLE: Silent Stakeholder Withdrawal

Field staff discover a local partner has suddenly withdrawn support but only mention it in a lengthy quarterly report →
management finds out MONTHS TOO LATE. FIX: Establish a weekly review meeting so this blocker is surfaced and
resolved immediately.

Topic 5: Risk Mitigation & Common Implementation Mistakes

Mnemonic: FABRIC — Common Implementation Failure Points

F — Failures in procurement timing — Delaying material requests until field teams are already deployed
 A — Absence of tracking — Evaluating performance only AFTER THE FACT instead of monitoring in real time

B — Blame culture — Penalizing field teams for reporting complications → they hide bottlenecks

R — Role ambiguity — No clear ownership lines → when everyone is responsible, no one is accountable

I — Ignoring field feedback — Forcing staff to follow obsolete proposal assumptions

C — Communication silos — Field staff, M&E;, and managers working in isolation

Risk Type Threat Example Prevention / Mitigation

Operational Key field staff become unavailable Pre-vetted backup personnel roster; stagger field schedules
(sickness/turnover)

Financial Budget releases face administrative delays Prioritized critical activity matrices; adjust cash plans

Stakeholder Local community partner withdraws support Engage alternative partners; brief senior leadership

External Extreme weather blocks transit routes Buffer time in work plans; backup field dates

Quality Training delivery varies wildly across centers Structured observation checklists; instructor coaching
 LECTURE 11 — PROJECT CLOSURE

Topic 1: Project Closure Fundamentals & Types

■ CORE CONCEPT

Project closure = the formal lifecycle process of finalized evaluation, administrative wind-down, and
contract finalization — it acts as a defensible accountability record confirming all outputs were delivered,
finances settled, and responsibilities transferred.

■ REAL-WORLD EXAMPLE: NGO Primary School Project

NGO finishes building a school facility WITHOUT a closure process: → Financial advances remain unreconciled →
The building lacks a legally signed-over custodian → No one is designated to pay for ongoing operations and
maintenance FIX: Formal closure ensures the facility is safely handed to the local Education Department with a clear
O&M; budget plan.

Mnemonic: FALm — What Happens If Closure Is Ignored

F — Future teams repeat the same avoidable design and execution mistakes

A — Assets disappear, degrade, or remain severely underutilized due to missing ownership

L — Latent risks stay open — unresolved cash advances and donor audit observations

m — Missing clarity for beneficiaries regarding who actually owns and manages the services

Closure Type Context Core Requirement

Normal Closure Deliverables fully finished, verified, and accepted per Implement all standard close-out checklist tasks
baseline plan

Premature Closure Terminated early due to funding gaps, policy shifts, Closure discipline is STILL mandatory to account for
security threats spent resources

Perpetual Closure Risk Project in 'zombie' state — continuously extending Leadership intervention needed to enforce a hard
deadlines completion baseline

Changed-Priority Closure Stopped or merged mid-stream due to strategic Orderly closing discipline to preserve data and settle
priority shifts accounts

Topic 2: The Project Closure Checklist & Governance

Mnemonic: FACTS — Five-Dimension Close-Out Checklist

F — Financial — Reconcile all expenditures, clear advances, prepare audit trail, resolve ineligible expenses

A — Assets & Institutional — Hand over equipment, assign O&M; roles, release personnel, transfer custody

C — Contractual — Close procurement files, settle supplier claims, verify product warranties

T — Technical — Validate outputs against design specs, confirm completion, resolve defects

S — Shared Learning — Document insights, compile final report, archive evidence, share knowledge
 ■ REAL-WORLD EXAMPLE: Water Safety Initiative Sign-Off

PM cannot simply state 'the work is finished' at the final sign-off meeting. Required closing packet: • Reconciled ledger
books (Financial) • Signed community asset handovers (Institutional/Assets) • Archived final project report (Shared
Learning) → Only then can the donor issue official sign-off.

Topic 3: Asset Handover & Financial Audit Readiness

Mnemonic: CLASS — Five-Step Asset Transfer Workflow

C — Custodian assignment — Select the specific local department taking ownership

L — Location and ID tagging — Give every asset a unique ID code, recording value and condition

A — Audit trail verification — Compile all vouchers, revision approvals, purchase orders, bank records

S — Sign-off notes — Secure legal custodian signatures on official handover documents

S — Sustained O&M; planning — Deliver operating manuals, track warranties, confirm staffing and budgets

Dangerous Closure Gaps Mandatory Audit-Ready Evidence

Missing technical inspection reports Approved baseline budgets and formal mid-project budget revisions

Unclosed or hanging purchase orders Receipts, itemized payment documentation, finalized vendor contracts

Undocumented product warranties Comprehensive fixed asset register with unique property IDs

Supplier performance left unrecorded Signed custodian handover notes and management audit responses

Topic 4: Lessons Learned & After-Action Reviews (AAR)

Mnemonic: CRIME — Five-Part Lessons Learned Formula

C — Context — Exact background setting, timeframe, and location where the event occurred

R — Reasoning — Root operational causes (why was there a gap between plans and reality?)

I — Implication — Clear operational consequences: the 'so what?' of the event

M — Meaningful action steps — Clear recommendations: what to duplicate or avoid

E — Evidence finding — Quantified findings backed by recorded project milestones

■ REAL-WORLD EXAMPLE: Agricultural Project with Late Fund Release

Funds released LATE → compressed execution timeline → massive delays. AAR captures: Context (District Y, Month
2), Reasoning (donor administrative delays), Implication (6-week compression, quality issues), Meaningful Action
(insert 60-day startup buffer), Evidence (milestone log showing activities starting 6 weeks late).

AAR Four Core Questions:

• What was expected to happen? → Maps to Project Targets & Logframe Goals
• What actually happened? → Extracts Concrete Implementation Evidence
• Why was there a difference? → Isolates Root Causes & Design Defects
• What should we change? → Produces Actionable Lessons-Log Entries
 LECTURE 12 — FINANCIAL PLANNING & CONTROL

Topic 1: Project Budgeting, Logic & Cost Classifications

■ CORE CONCEPT

Budget = the financial baseline that maps technical work configurations into quantified, costed line items.
Formula:

Line Item Cost = Quantity × Unit Cost × Frequency

■ REAL-WORLD EXAMPLE: Workshop Budget Example

REJECTED: '$20,000 for training' — No visibility, donor will reject. APPROVED breakdown: • Venue: 5 days × Rs.
8,000/day = Rs. 40,000 • Trainer: 1 expert × Rs. 15,000/day × 5 days = Rs. 75,000 • Participant Meals: 30 participants
× Rs. 500/meal × 2 meals × 5 days = Rs. 150,000 • Travel: 30 participants × Rs. 1,000 avg. = Rs. 30,000 → Total: Rs.
295,000 with full justification

Mnemonic: BASES — Bottom-Up Budget Estimation

B — Break the project down into clear, granular technical work packages

A — Add mandatory taxes, inflation protections, and contingency margins

S — Set up itemized tracking under standard budget heads (direct, indirect, fixed, variable)

E — Estimate quantities, current market unit costs, and recurrence frequencies

S — Scrutinize financial summaries directly against logframe deliverables

Cost Type Definition Example

Direct Costs Explicitly linked to a distinct project activity Hired trainers, field travel per diems, workshops

Indirect Costs Shared across multiple operations; can't map to a Central office rent, shared internet, utilities
single block

Fixed Costs Remain static regardless of activity volume Dedicated office lease, permanent management salaries
changes

Variable Costs Scale in direct proportion to activity volume Field vehicle fuel, training meals, survey printing

Topic 2: Financial Proposal Components & Donor Compliance

Mnemonic: RTC — Three Core Compliance Standards

R — Realism — All costs reflect current local market prices, inflation pressures, and field conditions

T — Transparency — All costs fully visible, explained via text justifications, and mathematically traceable to
activities

C — Compliance — All costs conform to funder rules: eligible inputs, procurement thresholds, taxes, overhead
caps

Procurement & Finance Control Loop:

Step 1: Need Identified → Technical demand logs from work plan
 Step 2: Budget HEAD Checked → Finance validates line-item availability before launch
Step 3: Procurement Rules Enforced → Competitive quotes & threshold approvals
Step 4: Verification & Payment → Payment released only after matching receipts & delivery verification

Topic 3: Financial Monitoring, Variance Analysis & Control Tools

■ VARIANCE FORMULA

Variance = Actual Expenditure − Budgeted Expenditure

Positive variance = OVER budget (actual > budgeted) | Negative variance = UNDER budget (actual <
budgeted)

■ REAL-WORLD EXAMPLE: Mid-Year Budget Trap

Report shows only 30% of training budget spent at mid-year. LOOKS LIKE: Savings! EVM REVEALS: Major
implementation bottleneck — a delay in tool procurement has stalled training workshops. → Immediate action: adjust
cash flow plan and unblock procurement.

Mnemonic: Rhythm — Four-Stage Financial Control Loop

R — Review direct lines — Monthly budget-vs-actual reviews to isolate spending deviations

H — Handle variance flags — Diagnose whether deviations stem from price volatility, delays, or
non-compliance

T — Track cash velocity — Balance donor inflows against procurement milestones

M — Maintain audit trails — Keep all invoices, vouchers, approvals, and delivery records indexed

Variance Status Root Causes Management Response

Positive (Over budget) Actual Cost escalation, market inflation, overspending, weak Prepare variance note, trim non-essential tasks,
> Budget baseline planning request budget revision

Negative (Under budget) Price savings, implementation delays, procurement Investigate delays, update procurement timelines,
Actual < Budget blocks, unexecuted activities adjust cash flow forecasts

Topic 4: Project Financial Risks, Failures & Mitigation

Mnemonic: FODIL — Five Primary Financial Risks

F — Fraud or Misuse — Prevented by segregation of duties, multi-level authorizations, spot checks

O — Overspending — Controlled via monthly budget reviews and pre-approval loops for revisions

D — Delayed Payments — Mitigated by updating cash-flow forecasts and tracking disbursement milestones

I — Inflation/Exchange Pressure — Handled through price validations and contingency budget heads

L — Lack of Documentation — Avoided by pairing all expenditures with sign-in sheets and delivery notes

■ REAL-WORLD EXAMPLE: Community Meeting Audit Failure

Team reports completing community mobilization meetings but FAILS to collect attendance logs or photos. During
audit: these expenses are flagged as INELIGIBLE because financial claims cannot be verified. RULE: Every rupee
spent must be linked to a physical output record.
 LECTURE 13 — SCHEDULING, COST BASELINES & EARNED VALUE
MANAGEMENT

Topic 1: Project Scheduling & Time Roadmaps

■ CORE CONCEPT

Scheduling maps the Work Breakdown Structure (WBS) onto a time-bound calendar by sequencing
activities based on logical dependencies and durations. It is the active control baseline tracking whether
progress matches planned timelines.

Mnemonic: DATE — Four Scheduling Steps

D — Duration estimation — Assign realistic time limits using expert judgment or historical metrics

A — Activity sequencing — Arrange tasks in logical order by identifying clear prerequisites

T — Track milestones — Embed zero-duration checkpoints to signal completion of major phases

E — Enforce the critical path — Isolate the longest continuous sequence of dependent tasks

■ REAL-WORLD EXAMPLE: Data Collection Campaign

Without scheduling: tool translation, enumerator training, and field deployment will all bottleneck. With scheduling
(WBS + Gantt): • Tool translation (Week 1–2) → must FINISH before • Enumerator training (Week 3) → must FINISH
before • Field deployment (Week 4+) → This is a Finish-to-Start (FS) dependency chain.

Dependency Type Rule Example

Finish-to-Start (FS) Task B cannot begin until Task A is Curricula design must finish before training sessions start
completely finished

Start-to-Start (SS) Task B can launch simultaneously Data entry can start as soon as the first field surveys begin
with Task A

Critical Path Method Zero slack/float; any delay directly Used to pinpoint high-risk milestones requiring intensive oversight
delays the final deadline

Gantt Charts Visual bar chart mapping tasks Compare baseline schedule against actual real-time completion
against calendar weeks

Topic 2: Multi-Head Cost Calculation & Baselines

■ COST FORMULA

Total Cost = Quantity × Unit Rate × Frequency

Once approved, these line items form the Cost Baseline — the authorized spending target against which
financial burn rates are measured.

■ REAL-WORLD EXAMPLE: Monitoring Field Visits Budget

Monitoring team plans 12 field visits across Rawalpindi and Islamabad. WRONG: 'Rs. 50,000 for field visits'
CORRECT: 12 visits × Rs. 4,200/visit (fuel + vehicle rental) = Rs. 50,400 → Each visit cost is broken down into: fuel
(distance × rate) + daily vehicle hire. This is audit-ready and traceable to specific districts.
 Mnemonic: LOFT — Four Core Budget Heads

L — Labor costs — Working days/months × verified staff compensation rates

O — Overheads & Admin — Shared org expenses (central office rent, utilities, internet)

F — Field logistics & Travel — Total distance/trips × verified local transport rates

T — Technical equipment — Capital assets priced at verified market vendor quotes

Topic 3: Earned Value Management (EVM) Core Metrics

■ CORE CONCEPT

EVM = an integrated control methodology that evaluates project schedule and budget health
simultaneously by comparing actual work performed against the planned baseline. Replaces simple cost
tracking with objective physical progress assessment.

Three EVM Building Blocks:

Metric Also Known As Definition

Planned Value (PV) BCWS — Budgeted Cost of Work Scheduled Authorized budget for work PLANNED to be completed by the
review date

Earned Value (EV) BCWP — Budgeted Cost of Work Performed Budgeted value of work ACTUALLY completed by the review
date

Actual Cost (AC) ACWP — Actual Cost of Work Performed Total realized money SPENT on executing the work completed

EVM Variance & Efficiency Indicators:

Indicator Formula Status (negative=bad, positive=good) Action Trigger

Cost Variance (CV) CV = EV − AC Negative = Over budget | Positive = Negative → isolate high-cost tasks, trim
Under budget non-essential inputs

Schedule Variance SV = EV − PV Negative = Behind schedule | Positive = Negative → review critical path, reallocate
(SV) Ahead of schedule staff

Cost Performance CPI = EV / AC < 1.0 = Over budget (poor) | > 1.0 = Dictates burn rate predictions for remaining
Index (CPI) Under budget (good) tasks

Schedule Performance SPI = EV / PV < 1.0 = Behind schedule | > 1.0 = Ahead Measures schedule efficiency; signals
Index (SPI) of schedule timeline delay risks

Topic 4: Comprehensive Exam-Scenario Diagnostics

■ EXAM SCENARIO 1
 Given: PV = Rs. 500,000 | EV = Rs. 400,000 | AC = Rs. 465,000

Calculations:

SV = EV − PV = 400,000 − 500,000 = −100,000 (BEHIND SCHEDULE)

CV = EV − AC = 400,000 − 465,000 = −65,000 (OVER BUDGET)

SPI = 400,000 / 500,000 = 0.80 (progressing at only 80% of planned pace)

CPI = 400,000 / 465,000 = 0.86 (earning only Rs. 0.86 of value per rupee spent)

Diagnosis: The project is BEHIND SCHEDULE and OVER BUDGET — urgent corrective action required.

■ EXAM SCENARIO 2 — Traditional Budget Variance

Given: Asset line item authorized allocation = Rs. 200,000 | Actual expenditure = Rs. 235,000

Calculation: Variance = Budget − Actual = 200,000 − 235,000 = −Rs. 35,000

Interpretation: Negative = Line item is OVER BUDGET. Investigate root cause (market price spikes? poor
estimation?) and file a formal variance correction note.

■ CRITICAL EXAM INSIGHT

NEVER evaluate spending data in a vacuum!

A project significantly UNDER BUDGET may look like a success — but EVM can reveal that
underspending is caused by SEVERE IMPLEMENTATION DELAYS that stall output delivery.

Always integrate: Gantt (WHEN) + Cost Baseline (WHAT it costs) + EVM (combined time & cost health).

LECTURE — MASTER MNEMONICS QUICK REFERENCE

Mnemonic Stands For Topic/Lecture

BEST Budget, Escalation, Stakeholder confidence, Timelines L7 — Why do proactive risk

management

I AM (+ Monitor) Identify, Analyze, Mitigate, Monitor L7 — 4-step Risk Management

Process

TEAM Transfer, Eliminate/Avoid, Accept, Mitigate L7 — Risk Response Strategies

FISE Financial, Institutional, Social, Environmental L7 — Four Pillars of Sustainability

CLOSED Confuse, Late, One-time, Scoring low, Empty, Donor L7 — Top Management Mistakes

WHICH What, How, Is it needed, Costs, How activities L8 — Proposal Review Questions

DIPPER Decision-makers, Implementers, Primary beneficiaries, Partners, L8 — Stakeholder Categories

Engagement, Risk-affected

SMART Specific, Measurable, Achievable, Relevant, Time-bound L8 — Objective Design

LIFTS Learning, Institutional, Financial, Technical, Social L8 — Sustainability Plan

UNMASK Unlinked, No baseline, Missing logic, Ambitious, Silent risks, Knowledge L8 — Proposal Rejection Causes
gaps

TRAM Teams, Resources, Activities, Monitoring L9 — Implementation Building Blocks

RACI Responsible, Accountable, Consulted, Informed L9 — Accountability Matrix

CRADLE Collect, Review, Assess, Diagnose, Log, Execute L9 — Quality Monitoring Loop

MESH Meetings, Email, Shared dashboards, Hotline L9 — Communication Channels

FABRIC Failures, Absence, Blame, Role, Ignoring, Communication L9 — Implementation Failure Points

FACTS Financial, Assets, Contractual, Technical, Shared learning L11 — Closure Checklist

FALm Future, Assets, Latent, Missing L11 — Effects of Ignoring Closure

CLASS Custodian, Location, Audit, Sign-off, Sustained O&M; L11 — Asset Transfer Workflow

CRIME Context, Reasoning, Implication, Meaningful action, Evidence L11 — Lessons Learned Formula

BASES Break, Add, Set up, Estimate, Scrutinize L12 — Budget Estimation Steps

FODIL Fraud, Overspending, Delayed payments, Inflation, Lack of docs L12 — Financial Risks

DATE Duration, Activity sequencing, Track milestones, Enforce critical path L13 — Scheduling Steps

LOFT Labor, Overheads, Field logistics, Technical equipment L13 — Budget Heads