Differences

This shows you the differences between two versions of the page.

--- progressnotes [2022/02/18 14:06]
edgare
+++ progressnotes [2022/06/21 13:06] (current)
acloud
@@ Line 2: / Line 2: @@
-{{ :modify-progress-note.png?nolink&600|}}
+{{ :modify-progress-note.png?nolink&400|}}
-Progress notes are added to [[workplan#tasks|Task]]-level items. There is one progress note per quarter for each task. Throughout the quarter, project staff should be diligent in filling it out with any important notes on progress of the specific task. As a convention, progress notes should start with the date or week you are writing for easy recall later, a subject, and then further details. It may be thought of as a diary entry. Using formatting can help make key details stand out, as shown in the example to the right.
+Progress notes are a helpful tool for tracking the team's progress over time. These can be utilized for creating regular updates to the client, compiling progress over the reporting period as a start to quarterly progress reports, and providing regular updates to management. Progress notes are added to [[workplan#tasks|Task]]-level items. There is one progress note per quarter for each task. Throughout the quarter, project staff should be diligent in filling it out with any important notes on progress of the specific task. As a convention, progress notes should start with the date or week you are writing for easy recall later, a subject, and then further details. Using formatting can help make key details stand out, as shown in the example to the right.
-Progress notes can be read by managers and other members of the team to get a quick overview on what has occurred with a task. It is also a helpful feature that is linked to quarterly report templates, enabling useful progress details on the task/deliverable to be pulled into the quarterly report template. It also helps in avoiding the loss of recall at quarterly reporting.
+Progress notes can be read by managers and other members of the team to get a quick overview on what has occurred with a task. Also helpful, the progress note from the entire quarter can be easily combined into one document, enabling useful progress details on the task/deliverable to be pulled into the quarterly report template. This helps avoid the loss of recall at quarterly reporting.
 A separate field is dedicated for Critical Assumptions/Problems Encountered/Follow Up.
@@ Line 13: / Line 13: @@
 ==== Creating or Editing a Progress Note ====
-If a progress note is not present for your quarter, you may create one using the 'Add a progress note' button. Existing progress notes may be opened by clicking the hyperlink with the relevant quarter.
+(UPDATE FOR WORKPLAN-ACTIVITY) If a progress note is not present for your quarter, you may create one using the 'Add a progress note' button. Existing progress notes may be opened by clicking the hyperlink with the relevant quarter.
-{{:create-or-edit-progress-note.png?nolink|}}
+{{:progress-notes-from-workplan.png?nolink|}}
+Alternatively, progress notes can be created or edited from the [[workplan#tasks|Task]]-level page.
 ==== Viewing Progress Notes ====
@@ Line 21: / Line 23: @@
 Progress notes are compiled across the activities. To view these compiled reports, visit the [[reports | Reports]] page, and click the {{:progress-notes-icon.png?nolink|}}icon for the activity and quarter of interest. The compiled progress notes will generate for the activity.
-==== Example Complied Progress Notes Report ====
-{{:progress-notes-compiled-example.png?nolin|}}
+|  **Example Complied Progress Notes Report**  ^
+^ {{:progress-notes-compiled-example.png?nolink&800|}} |

MandE2.0 Guidance

User Tools

Site Tools

Differences

Page Tools