This document walks through the weekly progress report template to illustrate bad and better responses for each section of the report.

Team [name goes here]
Rice University

Weekly Progress Report XX
[Date goes here]

Activities this week:

Bad example (single sentence responses that contain no information on what specifically was accomplished)

• We continued constructing the prototype.
• We're trying to finish the team cycle.

Better example (provides specifics on team accomplishments and progress toward objectives)

This week we continued developing the LabVIEW mobile user interface. We ordered the last several materials needed for the prototype.  The team tweaked/optimized the photodiode circuit to achieve an ideal level of intensity of emitted light through nanoshell samples in the current photometer setup. Additionally, testing was started integrating the various components of the system. The photometer was tested against a standard lab spectrophotometer with good results. Additionally, an assay of plain (without conjugated antibodies or PEG coating) nanoshell dilutions were tested and determined to have a linear transmitted light versus concentration curve. Another activity this week was the poster design.

Problems encountered:

If no problems arose, it is fine to simply state as such. But remember that a “problem” may mean not progressing as far as projected the week before, or a delay receiving a part, or the absence of a team member. Please honestly report status, as in the example below:

We are still awaiting the arrival of the microscope used in the Diagnostic Lab-in-a-Backpack. Additionally, Regis was unable to work Friday due to graduate school interviews.

Time devoted to project this week:

Bad example (report lists only a total time, not broken down by team member or providing specifics on what each team member did)

Each member of the team spent 9 hours on the project since the last weekly report. The total time spent by our team was 45 hours.

Better example (Lists accomplishments and actual time worked by team member.
A table, as shown below, is a great way to organize this. Have each team member track work during the week and provide lists to person drafting the reports.

Expenditures this week:

Bad example: Listing an amount (under $30) without providing any information on what was purchased.

Better example (provides specifics on what was ordered)
We ordered extra photodiode/op amps [TI opt101] from Digi-Key (under $40) and the Alcore aluminum honeycomb ($10 shipping, donated sample)

Activities planned for next week:

Bad example (as with accomplishments, provides only vague information on what team plans to do)

• Finish constructing the prototype.
• Test the prototype.

Better example (sets goals and provides clear set of tasks for team)

This week we are going to:

• Run tests on the sensitivity and precision of the optical device
• Print modified circuit boards and backups
• Look into methods of focusing light and improving optical device
• Modify optical device casing a final time on solidworks and reprint it
• Continue developing, testing and modifying the nanoshell assay with a laboratory spectrophotometer
• Print modified collection device on the 3D printer, modify the device, reprint and begin to build in it in the machine shop.
• Further assay testing on the photometer
• Paint the photometer black to minimize reflected light

Additional Comments and Questions for Dr. Oden, TA or Mentor:

While you are not expected to come up with questions or comments if you don’t have any, it is expected that you should use this space to get legitimate queries answered and to tap into the expertise of your advisors, mentors, and sponsors. Please use this space thoughtfully, e.g.:

• Do you have any suggestions who we can ask about controlling the laser intensity?
• Can Carlos order a part for us overnight now that we are at the end of the semester?