Master Project Cashflow Management

Project Cashflow Management Process

• The process is initiated when a new project is created in PDB and appears in the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours.
• The Project Manager registered in PDB receives a Wrike task to enter income and expenses data in the Project Cashflow Summary Spreadsheet.
• Implementation is initiated when there is significant impact information on income or expenses, or when the Project Manager or Programmes Team edits the Approved Expenses or Approved Income in PDB.
• The Project Manager registered in PDB receives a Wrike task to update the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours of any changes.
• All data entered relates to cash, not obligations or accruals, and excludes costs of HQ-GL personnel, overhead, or anything else in an Area Budget.
• The Internal Project Cashflow Spreadsheet contains past data on income, expenses, and transactions, which should be reviewed for relevance and accuracy.
• Project transaction queries should be reported to the supervisor if they relate to more than $10,000 or more than 5% of the project's Approved Expenses or Approved Income.
• Past months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet to match the actuals calculated from the previous step.
• Future months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet with expected amounts.
• Column D in the and tabs will show as green, orange, or red depending on the accuracy of predicted amounts.
• If Column D is red, the steps above should be revisited to seek a change in PDB, deal with project transaction queries, ensure past months' accuracy, or change future months' predictions.
• Completion of the process is achieved when Column D shows as green or orange, indicating accurate predictions of income and expenses.

Project Cashflow Management Process

• The process is initiated when a new project is created in PDB and appears in the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours.
• The Project Manager registered in PDB receives a Wrike task to enter income and expenses data in the Project Cashflow Summary Spreadsheet.
• Implementation is initiated when there is significant impact information on income or expenses, or when the Project Manager or Programmes Team edits the Approved Expenses or Approved Income in PDB.
• The Project Manager registered in PDB receives a Wrike task to update the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours of any changes.
• All data entered relates to cash, not obligations or accruals, and excludes costs of HQ-GL personnel, overhead, or anything else in an Area Budget.
• The Internal Project Cashflow Spreadsheet contains past data on income, expenses, and transactions, which should be reviewed for relevance and accuracy.
• Project transaction queries should be reported to the supervisor if they relate to more than $10,000 or more than 5% of the project's Approved Expenses or Approved Income.
• Past months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet to match the actuals calculated from the previous step.
• Future months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet with expected amounts.
• Column D in the and tabs will show as green, orange, or red depending on the accuracy of predicted amounts.
• If Column D is red, the steps above should be revisited to seek a change in PDB, deal with project transaction queries, ensure past months' accuracy, or change future months' predictions.
• Completion of the process is achieved when Column D shows as green or orange, indicating accurate predictions of income and expenses.

Project Cashflow Management Process

• The process is initiated when a new project is created in PDB and appears in the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours.
• The Project Manager registered in PDB receives a Wrike task to enter income and expenses data in the Project Cashflow Summary Spreadsheet.
• Implementation is initiated when there is significant impact information on income or expenses, or when the Project Manager or Programmes Team edits the Approved Expenses or Approved Income in PDB.
• The Project Manager registered in PDB receives a Wrike task to update the relevant entity's Project Cashflow Summary Spreadsheet within 24 hours of any changes.
• All data entered relates to cash, not obligations or accruals, and excludes costs of HQ-GL personnel, overhead, or anything else in an Area Budget.
• The Internal Project Cashflow Spreadsheet contains past data on income, expenses, and transactions, which should be reviewed for relevance and accuracy.
• Project transaction queries should be reported to the supervisor if they relate to more than $10,000 or more than 5% of the project's Approved Expenses or Approved Income.
• Past months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet to match the actuals calculated from the previous step.
• Future months of income and expenses should be updated in the Project Cashflow Summary Spreadsheet with expected amounts.
• Column D in the and tabs will show as green, orange, or red depending on the accuracy of predicted amounts.
• If Column D is red, the steps above should be revisited to seek a change in PDB, deal with project transaction queries, ensure past months' accuracy, or change future months' predictions.
• Completion of the process is achieved when Column D shows as green or orange, indicating accurate predictions of income and expenses.

Guide to Writing a Proposal: The Proposal Pie

• Proposal preparation cannot be standardized due to diverse contexts, purposes, and participants.
• Good judgment, good writing, and good background research are crucial for proposal writing.
• Before writing a proposal, it is important to know the project's purpose, content, and donor's interests.
• It is also important to know the budgeting process and degree of competition.
• The Proposal Pie diagram has four outer boxes that represent the knowledge one already has about the project.
• The four inner pieces of the pie focus on the impacts of the project.
• Impacts refer to external and internal results that the project aims to achieve.
• Impacts are the least prominent part of the proposal and need to be expressed through the other pieces of the pie.
• It is important to be aware of the motivation behind the proposal, as it influences how to balance efficiency and ambition.
• Proposals never provide complete information, and gaps need to be addressed to minimize risks in project implementation.
• The Features-Advantages-Benefits framework helps address three levels of reader interest in the proposal.
• Features are what will be done, advantages are why they are useful, and benefits are what they mean to the reader's life.