Michael McKelvey, Miriam Keep, and Morgan White met to finalize the discussion of how to structure iCAP Recommendations. We came to an agreement on the structure which we diagrammed online. Recommendations will be patterned after Metrics. If a Recommendation update warrants a Project Update, that will need to be added manually; it will not happen automatically with this approach.

Summary of structure:

• A Recommendation can be associated with a Project and an Objective and contains some additional general information
• A Recommendation can have many "tracking" updates including at least a status, date, and some notes

Detailed structure:

• iCAP Team
  • Title
  • Description
  • Theme [references one of our 10 themes, optional]
• Recommendation
  • Title
  • iCAP Team [references an iCAP Team]
  • Supplanted by [references another Recommendation, optional]
  • Associated Project(s) [references a Project, optional]
  • Objective [references an iCAP Objective, optional]
  • Description / "Specific actions/policy recommendations"
• Recommendation Tracking
  • Title
  • Recommendation [references a Recommendation]
  • Description
  • Date (M/D/Y field)
  • Status (dropdown list)
  • Internal Notes
  • Public File(s)
  • Private File(s)
  • Next step (dropdown list)
  • Next step due date (M/D/Y field)

Additionally, we do not plan to use the iCAP Portal to collect Recommendation feedback - a shared Word Doc on Teams is more conducive to this process. Certain fields in a recommendation will be added to the iCAP Portal Recommendation, and the uploaded document will contain more details, including comments.