You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Historical

WPP used to send Progress Reports to 1-4 external reviewers, who would then access reports via a portal, add comments/decisions, etc. As of summer 2023, this stage of review has been removed, removing the need for many workflow steps and fields. For information about the old workflow refer to the Fluxx Progress Report Review Workflow and Build (prior to August/September 2023) page.

Overview

Progress reports are Requirements records that awarded grantees fill out periodically to provide an update on their project and spending progress. Once submitted, they go through technical review (financial, NSQ, and program officer) and, if needed, are bundled and sent to administrative review. All reviewers are WPP staff, so the entire workflow is completed within the 3.2 Requirements Dashboard.

As part of this review structure we've also implemented side-by-side review for technical review. When a progress report is submitted both the finance team and program officer are notified, and the report appears in the Finance and Program Officer cards on the dashboard. NSQ review happens after Finance review is done, and once all review is completed the Program Officer is notified and they either approve the report or forward it to administrative team review (though bundling happens first). 

*The team has opted out of the Optional reminder email. If issues arise we can revisit adding this.

How it Works

Forms

The following forms follow the Progress Report workflow:

  • OAC Interim Progress Report
  • OAC Interim/Final Progress Report
  • OAC Final Progress Report
  • PERC Interim/Final Progress Report
  • PERC Strategic Progress Report

Note that this change also applies to the old versions of these forms (ex. OAC Interim Progress Report (legacy) ). The old forms have been updated to the new workflow but replaced so as to retain historical external reviewer information without cluttering the form.

Take Note

There are other Requirements forms that do not follow this side-by-side review process, often because they don't require both finance and program officer review. The Finance, NSQ, and Program Officer Review workflow status applies only to progress reports.

Workflow

  1. Submitted progress reports enter the Finance, NSQ, and Program Officer Review state. 
    • Email Finance Team for Report Review notification is sent to the finance team
    • Email Program Officer If They Must Review email notification is sent to the Program Officer
  2. There following steps can happen in any order (except that NSQ review must come after Finance review):
    • Finance team records comments in the Finance Review field
      • Progress Report Ready for NSQ Review (side-by-side review workflow) notification is sent to Jon
    • NSQ reviewer records comments in the NSQ Review field
      • Progress Report Ready for Program Officer Review/Decision (side-by-side review workflow) notification is sent to the Program Officer
    • Program Officer records comments in the Program Officer Review field
  3. The program officer takes one of the following actions:
    • Approve the progress report → The progress report appears in the Approved card on the dashboard.
    • Send the progress report for admin team review
  4. If the progress report is sent to admin team review, it is first sent to the Bundling state before it reaches Administrative Leadership Review. The admin team can record their decision in the Administrative Leadership Team Review (opt) field and eventually set the status to Approved.

Notifications and Fields

The notifications from step 2 are triggered based on which fields have been filled out. There are four text-based fields to support this workflow:

  • Progress Report Review - Finance Review (Required)
  • Progress Report Review - NSQ Review (Required)
  • Progress Report Review - Program Officer - Comments (Required)
  • Progress Report Review - Administrative Leadership Team - Comments

Take Note

Remember that not all requirements follow this workflow, thus when updating notifications pay attention to whether it's unique to the side-by-side review or if it's triggered only when moving from another state (ex. from Finance Review). 






  • No labels