DevComm Weekly Reports
Each Friday, members of DevComm send the DevComm Director a Weekly Report. The purpose of the report is to give the weekly meetings some structure and help the director know the status of the department. Any challenges, projects worked on during the week, or new ideas can be discussed in the weekly report. These reports also help the director with their weekly meeting with the National Director.
While the DevComm staff sends a Weekly Report to the DevComm Director, the DevComm Director also sends a Weekly Report to the National Director before their weekly meeting. See templates below.
DevComm Staff/ Intern Weekly Reports
This report should be emailed to the DevComm Director weekly on Friday mornings. The subject line for these emails should be "[initials] Weekly Report [date]" Below is the information asked for in the reports. As new time passes, directors should feel comfortable changing the prompts.
1. Projects and tasks you worked on during the week. Include the number of items you went through or completed if the task is structured that way (For example, number of contributions entered or number of fulfillment requests completed. This can be an estimate.).
In this section, you should include information on each departmental task you are responsible for. For ongoing/long-term projects or tasks, include a projection of when you will finish.
Feel free to also request any support you may need along the way.
2. Challenges you've had during the week. Have you overcome them? Do you need assistance from me (DevComm director) or others?
3. Ideas of any sort you may have for the department. Do you have any suggestions, ideas, projects you think we should pursue?
4. What you hope to accomplish within the next week.
5. Anything else you would like me to know.
In this section, you should include information on each departmental task you are responsible for. For ongoing/long-term projects or tasks, include a projection of when you will finish.
Feel free to also request any support you may need along the way.
2. Challenges you've had during the week. Have you overcome them? Do you need assistance from me (DevComm director) or others?
3. Ideas of any sort you may have for the department. Do you have any suggestions, ideas, projects you think we should pursue?
4. What you hope to accomplish within the next week.
5. Anything else you would like me to know.
DevComm Director Weekly Report
This report should be emailed to the National Director before your weekly meeting. The purpose of this report is to update the National Director on the department and help guide the meeting. The report includes a link to an updated version of our DevComm Tasks sheet, a list of what was worked on this week for Development and for Communications, and any other department updates. Feel free to add anything else you’d like to the email, including successes and difficulties.Below is the format for this email:
Hello [National Director],
Here is my weekly report.
This link will take you to an updated DevComm Tasks Google Sheet. https://docs.google.com/spreadsheets/d/1-N4sH2P-cuhBDlBMw-8JMJ6vw5wLKL1581EV8o4fmSo/edit
Development:
(i.e. RN-5 dropped Wednesday)
Communications:
(i.e. we sent out the Blog Wrap-Up email)
Other:
(i.e. we will be receiving a new intern Monday)
Challenges/ Successes:
(We were very busy with data entry this week making it challenging to get anything else done)
(We got 2 stories placed in the media!)
Here is my weekly report.
This link will take you to an updated DevComm Tasks Google Sheet. https://docs.google.com/spreadsheets/d/1-N4sH2P-cuhBDlBMw-8JMJ6vw5wLKL1581EV8o4fmSo/edit
Development:
(i.e. RN-5 dropped Wednesday)
Communications:
(i.e. we sent out the Blog Wrap-Up email)
Other:
(i.e. we will be receiving a new intern Monday)
Challenges/ Successes:
(We were very busy with data entry this week making it challenging to get anything else done)
(We got 2 stories placed in the media!)
