TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
This is basically the same format as the weekly status reports I do. One
of the important parts of status reports is that it's a written record
of what you've done or tried to do (as in CYA). The managers especially
need to see the "Challenges" area: either that you're solving problems
routinely yourself, or they're not getting attention and you need
someone's intervention. The issues start out as simple issues, then
escalate to "yellow flag" status (a warning that your questions haven't
been answered) or "red flag" status if your work is blocked and you need
help.
> -----Original Message-----
> <<
> Those of you who have some sort of formal/semi-formal way of
> reporting your progress on documentation projects, what do
> you do?
> >>
>
> I do weekly status reports and send them to my contracting company,
> boss, boss's boss, and a couple of other random bosses who have some
> reason to want to know what I am doing.
>
> The format is very simple: Accomplishments, Plans for Next Week, and
> then I put any "Challenges" (if there are any) and requested time off.
>
>
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
