Communications Network
Vast Empire  -  New Posts  -  Search  -  Statistics  -  Login 
 
ComNet > Imperial Navy > Archived Navy Main ComNet > A Guide to Reporting - A MUST READ
 
 
 
Author
Topic:  A Guide to Reporting - A MUST READ
Arturus
ComNet Marshal
 
Arturus
 
[VE-NAVY] 2nd Lieutenant
 
Post Number:  1461
Total Posts:  2143
Joined:  Nov 2001
Status:  Offline
  A Guide to Reporting - A MUST READ
July 30, 2006 7:28:51 PM    View the profile of Arturus 
I am sure most of you know that the old wonderful tradition we call weekly reports has declined.  In fact, I would argue it is nearly non-existent save for a devout few who continue to keep it going.  I think we have all complained about them at one time or another and some question why we need them but in fact reports are very important.  When done well, reports convey important information with regards to the level of activity (or inactivity) amongst pilots.  For some pilots who show steady activity, they can be overlooked as those who show bursts at key times get rewarded.  Reports can insure that none get overlooked.

Reporting is required on a weekly basis but it is simple; no creativity required.  A flight member report should take about five minutes from logging into your e-mail to sending.  It is simple but important.  Naturally as you go up the ladder, more information is required because your position means that there are people under you who are reporting to you.  You need to synthesize this information and report on the group as whole.  However, this too is a very simple process.

Therefore, in order to make reports very easy both to write and to read and in order to ensure that all the relevant information is conveyed, I am posting report templates here.  Simply copy this into your e-mail, replace the information with that week's relevant information, and submit.  It's that simple and it aids us tremendously.

Flight Members

Arturus' Report: July 30th, 2006

Activity:
This week I completed scoring the ESC and gave the final results in a meeting after the closing bell.  In addition, I played three games for the ESC and wrote two story posts on the Nazgul story.  Overall I keep updated on a daily basis, was on IRC, and posted where relevant on the Comnet.

Upcoming plans:
Next week I will be working on the new vacation story by developing my own individual character and Talysha's character as well.  I also intend to work on the Wiki project and create a small graphics competition for the navy.

Questions/Suggestions:
None

2nd Lieutenant Arturus
Nazgul 2
ID Line

Flight Leaders

Nazgul 3 Flight Report: July 30th, 2006

Flight's Activity Summary:
This week my flight engaged in a last minute fight to gain points for Nazgul in the ESC.  We were fairly active in gaming but were unable to produce much in the way of creativity.  Overall activity has been strong and everyone is contributing.  Pilot 4 added several posts to the story while Pilots 2 and 3 each played a series of pool matches.  In general, activity has improved since last week.

Statistical Summary:
Arturus - 3 story posts, 2 games
Pilot 2 - 2 story posts, 5 games
Pilot 3 - 1 story post, 4 games
Pilot 4 - 4 story posts, 2 games

Other contributions:
Pilot 4 entered two graphics in the navy's graphics competition.  In addition, pilot 3 continued his work on our website.

Planned Flight Activity:
Next week I will be working with my flight to plan our activity on the vacation story.  Our goal will be to work together in order to build flight unity and general activity.  Since this is possibly a camping vacation we will work on a few story lines dealing with that.

Report/Status:
Arturus - reported/active
Pilot 2 - reported/active
Pilot 3 - reported/on leave for 1 week
Pilot 4- did not report/active

Promotion/Award Recommendations
None

Comments/Questions:
None

2nd Lieutenant Arturus
Three Flight Leader
Nazgul 9
ID Line

Squadron Commanders's Report

Nazgul Squadron Report: July 30th, 2006

Squadron's Activity Summary:
This week the squadron concluded its activity in the ESC.  Overall we finished a close second and it was a strong effort by all.  We have completed the ESC story and I have posted the first post of the next story which is a vacation story.  The ESC story ended in victory as we completed our objectives.

Flight 1 Activity Summary:
Same as Flight Leader's

Squadron Statistical Summary:
Same as flight leader's, simply copy from their reports and in yours for flight one.

Other Contributions:
Copy from your flight leaders, add in your flight and add in anything that was missed.

Planned Squadron Activity:
This week our focus will be on the new vacation story and on continuing to build the squadron website.  We are planning to have a meeting before the Sunday meeting.

Report/Status:
Copy from your flight leaders and add your own flight's in.

Promotion/Award Recommendations:
None

Comments/Questions:
None

2nd Lieutenant Arturus
Nazgul Squadron Commander
ID Line

It's as simple as that.  Now that you know what to report and how to do it, let's see some.  You don't need to go on at length, brevity is nice.  If your report is short that is wonderful; we need the information not an essay.  This is particularly true for flight members.  For those with some command, well, with the fun come a few responsibilities but none of this should take more than 10 minutes for commanders and 5 minutes for flight members.  Any feedback on this would be appreciated, keep in mind this is a guide and not set in stone.  I thought that this might be helpful to those who don't know what to report and as a reassurance to those who complain that this is in fact a rather painless and non-time consuming process.

As an added way to make reporting easy, use the comnet message system instead of e-mail.  It is fast, easy, and you don't need to hunt for e-mail addresses and log into your webmail.  As I said, simple and painfree but required!

-----------------------
WAJ/2LT Corran "Arturus" Hargraves/M-SSD Atrus/VE/VEN/(=A=)(=SA=)(=*MA*=)(=JCPA=)(=SCPA=)[MC:1](x2)[SV][BRC][VC:B][CBV][LSM][LoC]


"The way of war is a way of deception. When able, feign inability; when deploying troops, appear not to be. When near, appear far; when far, appear near. Lure with bait; strike with chaos. If the enemy is full, be prepared. If strong, avoid him. If he is angry, disconcert him. If he is weak, stir him to pride. If he is relaxed, harry him; if his men are harmonious, split them. Attack where he is unprepared; appear where you are unexpected. This is victory in warfare; it cannot be divulged in advance. Victory belongs to the side that scores most in the temple calculations before battle. Most spells victory; least spells defeat; none, surer defeat. I see it in this way, and the outcome is apparent." -- Sun Tzu

"Ultimate excellence lies not in winning every battle but in defeating the enemy without ever fighting." -- Sun Tzu
[This message has been edited by Arturus (edited July 30, 2006 7:31:36 PM)]
DJ234
ComNet Member
 
DJ234
 
[VE-NAVY] Petty Officer 1st Class
[VE-VEEC] Gaming Reporter
 
Post Number:  737
Total Posts:  794
Joined:  Feb 2005
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
July 30, 2006 7:44:32 PM    View the profile of DJ234 
bravo art

it looks like you put some serious work into that.

 
-----------------------
Aegis Squadron
----------------------
I think war might be God's way of teaching us geography~Paul Rodriguez
----------------------
XO/FL/PO1 DJ234/Aegis-5/Phoenix wing/mSSD Atrus/Defensive Fleet/VEN/VE (=A=) (=SA=) [VC:B] [CoB]
Atrick25
ComNet Cadet
 
Atrick25
 
[VE-NAVY] Leading Crewman
 
Post Number:  274
Total Posts:  380
Joined:  May 2006
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
July 30, 2006 8:10:14 PM    View the profile of Atrick25 
Do we have to email them? I've been PM'ing them to Trevor and Shaz and that seems to work.
 
-----------------------
NazgulSquadron

FM/LCRW Atrick25/Nazgul-10/Phoenix Wing/[mSSD Atrus]/1VENF]/VEN/VE (=A=)
~Leading Crewman Atrick25~

Nerds stick together! (Until Football Players storm us, because then we run like the girly men we are!)

Why does Darth Vader want cookies?
DJ234
ComNet Member
 
DJ234
 
[VE-NAVY] Petty Officer 1st Class
[VE-VEEC] Gaming Reporter
 
Post Number:  738
Total Posts:  794
Joined:  Feb 2005
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
July 30, 2006 8:13:28 PM    View the profile of DJ234 
As an added way to make reporting easy, use the comnet message system instead of e-mail.  It is fast, easy, and you don't need to hunt for e-mail addresses and log into your webmail.  As I said, simple and painfree but required!



you dont have to email them use the message center it works faster

 
-----------------------
Aegis Squadron
----------------------
I think war might be God's way of teaching us geography~Paul Rodriguez
----------------------
XO/FL/PO1 DJ234/Aegis-5/Phoenix wing/mSSD Atrus/Defensive Fleet/VEN/VE (=A=) (=SA=) [VC:B] [CoB]
Atrick25
ComNet Cadet
 
Atrick25
 
[VE-NAVY] Leading Crewman
 
Post Number:  275
Total Posts:  380
Joined:  May 2006
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
July 30, 2006 8:25:36 PM    View the profile of Atrick25 
Guess I shouldn't skim posts huh?
 
-----------------------
NazgulSquadron

FM/LCRW Atrick25/Nazgul-10/Phoenix Wing/[mSSD Atrus]/1VENF]/VEN/VE (=A=)
~Leading Crewman Atrick25~

Nerds stick together! (Until Football Players storm us, because then we run like the girly men we are!)

Why does Darth Vader want cookies?
Shazam
ComNet Marshal
 
Shazam
 
[VE-NAVY] Commander
[VE-VEEC] Chief Reporter
 
Post Number:  2557
Total Posts:  4197
Joined:  Jun 2003
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
August 6, 2006 1:50:14 PM    View the profile of Shazam 
I may be the only commander that does this, but I don't actually 'require' reports.  The only way they can become required is if a member doesn't post at least three times during the week and post in the Nazgul topic- then you best be reporting.  Otherwise, just as Art stated, its an excellent way to practically point out to your commander "hey- I did this for us..."  If nothing else, you're making it evident that you deserve a promotion or atleast a commendation of some sort.  Besides that though, I really like the way a report can function as a red flag for commanders- we like to know if there is a problem and what simpler way is there than that of a report?  I emphasize that because we can only become better by identifying our problems from the ground and working our way up.  That's my two cents- well done Art.
 
-----------------------
*Flash Was Here...*

CMDR/LtC Shazam/Nazgul 1-1/Phoenix Wing/mSSD Atrus/1VENF/VEN (=A=) (=*SA*=) (=*MA*=) (=*FOCE*=) [LoM] [LSM] [VC:S] [DSM]

NazgulSquadron

Commander of Nazgul Squadron, Phoenix Wing and Training
Mykill Doomslayer
ComNet Initiate
 
Mykill Doomslayer
 
[VE-NAVY] Crewman
 
Post Number:  138
Total Posts:  187
Joined:  Jun 2006
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
August 28, 2006 5:58:54 PM    View the profile of Mykill Doomslayer 
Sorry , I feel as if I don't really belong in this thread , but am I doing what I need to be doing ? Will you tell me when there comes a time I have to check in periodically ? Because sometimes I can go off line for days .

-----------------------
"my soul was cast into the vastness of space for my fear of loneliness" Chronicles of Mykill Doomslayer bk III>chpt 6
[This message has been edited by Mykill Doomslayer (edited August 28, 2006 6:00:34 PM)]
Raigen
ComNet Member
 
Raigen
 
[VE-NAVY] Senior Crewman
 
Post Number:  615
Total Posts:  1386
Joined:  Dec 2005
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
September 21, 2006 3:22:57 PM    View the profile of Raigen 
Hmm, ths may be just my lazy side talking. But half the information in the report could be collected via programming. The rest is just plans for the next week and questions which usually are posted in the squadron topic anyway so, not to offend, but why? and I don't mean because it's tradtion and so you all know we are active. I mean why isn't their an automated system for doing it.
 
-----------------------
FM/SCRW Raigen/Aegis 1/Phoenix Wing/mSSD Atrus/DEF/VEN/VE (=*A*=)(VC:B)

La Resistance
Shazam
ComNet Marshal
 
Shazam
 
[VE-NAVY] Commander
[VE-VEEC] Chief Reporter
 
Post Number:  2647
Total Posts:  4197
Joined:  Jun 2003
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
September 24, 2006 4:12:46 PM    View the profile of Shazam 
For reporting?  If there was a mechanism that would automatically point out the number of post you'd made in a week, indicate where the strengths of your pilot as well as your flight and the rest of the squadron was and where it needed to be worked existed- we'd be using it   Unless you'd like to be more specific.

Basically, these templates are something that should be almost automatic- save a draft and every week go to that draft and send it out: that should be enough.  This should only take a few minutes- its not a whole lot to ask.  Where your thoughts are progressive, immediate gratification isn't always necessary: sometimes you need to work just a little bit.  But again- correct me if I'm presuming to widely here.
 
-----------------------
*Flash Was Here...*

SC/CMD Shazam/Nazgul 1-1/Phoenix Wing/mSSD Atrus/1VENF/VEN (=A=) (=*SA*=) (=*MA*=) (=*FOCE*=) [LoM] [LSM] [VC:S] [DSM]

NazgulSquadron

Commander of Nazgul Squadron, Phoenix Wing and Training
etan evnstar
ComNet Novice
 
etan evnstar
 
[VE-NAVY] Crewman
 
Post Number:  51
Total Posts:  423
Joined:  Oct 2006
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
November 6, 2006 6:16:19 PM    View the profile of etan evnstar 
I kinda asked this very question in my Kaph squadron topic. I'm kinda glad I read here. I don't think any of these tasks are that difficult.

I  just want an example on my squadrons posts so I can follow the leader. I guess I could just kind of look there?

-----------------------
Grammer, mechanics, punctuation, spelling, diction, effectiveness in the science, and larger elements are the facts at hand.
[This message has been edited by etan evnstar (edited November 8, 2006 11:43:12 PM)]
C-3PX2
ComNet Member
 
C-3PX2
 
[VE-NAVY] Master Chief Petty Officer
[VE-VEEC] Journalist
 
Post Number:  321
Total Posts:  619
Joined:  Jul 2006
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
November 12, 2007 8:08:04 PM    View the profile of C-3PX2 
For the fact that we are getting new members into the VEN who may have questions on how to properly report. I am bumping this topic up. For some reason it is not sticked, though it should be.

>> BUMP <<
> : There is nothing wrong with fear.
> : You need never be ashamed of it, as long as it doesn't stop you functioning.
> : Fear is your natural warning system; it keeps you alive so
> : that you can can fight. Show me a man who isn't afraid,
> : and I'll show you a fool who is a danger to his entire ship.
===================================================================================
-= Viper Squadron =- : "We Fly, You Die.."
===================================================================================
|| XO & FL / MCPO C-3PX2  / Viper 9 / Phoenix Wing (Wing 1) / mSSD Atrus / 1Fl / VEN / VE / (=A=), (=SA=), [MC2], [MC1] ||
|| Vast Empire Imperial Naval Academy Operation Level 1 (O-1) |=|=| Author / JRN C-3PX2 /Lotaith / VET / VE ||
Shazam
ComNet Marshal
 
Shazam
 
[VE-NAVY] Line Captain
[VE-VEEC] Journalist
 
Post Number:  3260
Total Posts:  4197
Joined:  Jun 2003
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
November 13, 2007 8:17:22 PM    View the profile of Shazam 
Stickied   Thanks, C.  Note also that this is on the Naval Wiki underneath all those categories.  *Jumps out window.*
*Flash Was Here...*

WC|NTO/LCP Shazam/Phoenix 1-1/Phoenix Wing/mSSD Atrus/1VENF/VEN (=A=) (=*SA*=) (=MA=) (=*FOCE*=) [CBV*] [LoM] [LSM] [MC2] [VC:S] [SV*] [DSM] {Platinum Writing Medal}

Phoenix Wing Commander and Training Officer
Shazam
ComNet Marshal
 
Shazam
 
[VE-NAVY] Line Captain
[VE-VEEC] Journalist
 
Post Number:  3491
Total Posts:  4197
Joined:  Jun 2003
Status:  Offline
  RE: A Guide to Reporting - A MUST READ
March 1, 2008 7:28:45 PM    View the profile of Shazam 
Since we now have this article on the VEwiki and it appears to be rarely referenced in its ComNet form, I'm going to unsticky it now.  Thanks again for the templates, Art.
*Flash Was Here...*

WC|NTO/LCP Shazam/Phoenix 1-1/Phoenix Wing/mSSD Atrus/1VENF/VEN (=A=) (=*SA*=) (=MA=) (=*FOCE*=) [CBV*] [LoM] [LSM] [MC2] [VC:S] [SV*] [DSM] {Platinum Writing Medal}

Phoenix Wing Commander and Training Officer
ComNet > Imperial Navy > Archived Navy Main ComNet > A Guide to Reporting - A MUST READ  |  New Posts    
 

All times are CST. The time now is 1:23:52 PM
Comnet Jump:

Current Online Members - 0  |  Guests - 180  |  Bots - 2
 
< Contact Us - The Vast Empire >
 
Powered by ComNet Version 7.2
Copyright © 1998-2025 The Imperial Network
 
This page was generated in 0.911 seconds.