A project blog [19, 19] linked to a project document repository is a potential partial solution to this problem. Instead of sending email when creating or revising documents, project members simply add an entry to the blog. This requires less work than sending email and has other attractive features discussed below. The result is an easily-skimmed chronologically-ordered record of the important information events of a project. These include status changes of project documents in the associated repository. Project blogs are collaborative; any team member can add an entry.