reports
reports 02Nov15
Here on Anomaly we have an IC reports system (see '+help reports' for the
command structure). The report system is not designed to replace roleplay,
but rather to enhance it. A certain protocol needs to be followed so that
the reports flow freely and not bog down. This guide is designed to outline
the protocols. If you have any further questions, you should address them
with the production staff.
All Starfleet officers are able to create reports. Staff will sometimes
create a report as well, under the guise of an NPC, and it is up to the
players to respond to those reports. Usually these reports are plot-related
in some way, and instructions will be added to use +request to inquire
further about the particular report.
Please see: reports2 Top: info
reports2 02Nov15
Reports are divided up into what are called 'areas' or 'buckets'. This is a
method for sorting reports into meaningful groups. Junior officers have
access to two buckets; their departmental bucket and a GEN (for GENeral)
bucket. Senior officers have access to all buckets. Whenever you create a
report, you must specify what bucket to create it in. You can create a
report in any bucket. If you create a report in a bucket that you cannot
normally view, you will not be able to review that report unless it is sent
into a bucket that you have access to. It is often better to create the
report in your departmental bucket and, once complete, then transfer it to
its rightful destination.
Please see: reports3 Top: info
reports3 02Nov15
Here is the bucket list and who has access to them.
CMD The Command Branch bucket.
MED Medical.
OPS Operations department.
SEC Station security.
SCI Science department.
ENG Engineering reports and actions.
GEN General, all access bucket.
CO Commanding Officers (Department Heads)
DTI Department of Temporal Investigations.
CIV Civilians.
DPL Diplomatic access.
CNS Counselor bucket.
ORDER Standing orders.
FLEET General Starfleet bucket.
Please see: reports4 Top: info
reports4 02Nov15
When creating a new report, you should keep in mind that someone will need to
read what you've written. So please be as clear and concise as possible. It
is not necessary (and is generally bad form) to include your character's
opinion inside a report, unless she has specifically been asked for her
opinion. Include as much relevant information as possible. Who, what, when,
where, why and how (the foundations of modern journalism) is a good start.
Sometimes you may not have all the answers to those questions, but you
should provide as much information as you have in as concise a format as
possible.
Once a new report has come into your bucket, it is up to you to review it.
If you have pertinent information that is not otherwise included in the
report, you should add your information. That way, everyone can review all
the facts.
Please see: reports5 Top: info
reports5 02Nov15
Reports have priority (or 'escalation') colors. Green is the lowest priority.
Yellow requires attention sooner than green, and red should be considered top
priority. You can alter these escalation values as needed for urgency. They
show up as color-coded in the main reports screen.
Reports also have a status flag that is set with the /set switch. When a
report is brand-new, its flag is NEW. It can also be ON HOLD, UNDERWAY,
1/4 COMPLETE, 1/2 COMPLETE, 3/4 COMPLETE, or COMPLETE. See '+help reports'
for more information on how to set this flag.
If a report comes into your bucket that doesn't concern your department, you
should feel free to transfer it to the correct place. For instance, a report
about chroniton activity shouldn't be sent to Engineering, but rather it
should be sent to Sciences.
Please see: reports6 Top: info
reports6 02Nov15
Department heads should keep on top of the reports in their departmental
buckets and assign them to people as required.
If you are assigned a report, often that report is tagged with a due-date as
well. It is your responsibility to make sure that the report is completed by
that time. Reports without due dates that are assigned to you are open-ended,
and while you shouldn't drag your feet on them too long, they have no
due-date. Be sure to change the Escalation color or Status Flag as required.
When you are finished with the report, set it to COMPLETE status. That way
the department head knows it is done and can complete it.
Please see: reports7 Top: info
reports7 02Nov15
You can also assign reports to yourself. If you are the Replicator Specialist
in Engineering, and a report comes in about the replicator systems, you can
pretty much assume you will be assigned that report, and you can assign it to
yourself.
Sometimes a report will require the opinion or advice from another
department. For instance, the Science Officer may receive a report about a
junior officer's penchant for spending too much time in the holodeck. The
Science Officer will add his remarks to the report and send it off to the
Medical department's bucket so that they can have the crewman evaluated.
When the crewman evaluation is complete, the Medical department would add
their comments and then send the report back to the Science Department.
Sciences will then either close the report, or send the report up the chain
of command to the Command Officer's bucket if further action is required.
Please see: reports8 Top: info
reports8 02Nov15
Department Heads and command officers should complete and close reports when
there is no further action required. When you close a report, only the /first
comment/ in the report and your closing remarks are posted to the IC Reports
board. So, if there is something in the middle that requires expressing, you
must add them to your closing remarks. You can close the report if you can
say the following about it: 'No more talk is required on this report, here
are your orders.' Only department heads can complete reports.
If you have a report that needs deleting for whatever reason, please use
'+request' and identify which report needs deleting and why. Only the
production staff can delete a report.
Just like in a real command structure, you should handle what you can handle
on your own and not expect the higher ranks to handle it all. If you can
handle the report, then please do so. If you cannot, leave it for someone
who can. Do not send every report up the chain of command to the top.
Top: info
Return to Index
