STF Checklists - Input Requested

Posted March 29, 2021, 2:36 p.m. by Vice Admiral Daniel Lerner (Vice President / Procedures Guru / Personnel Director) (Daniel Lerner)

Posted by Fleet Captain Russell Watt (Public Nuisance for Life / AEDir) in STF Checklists - Input Requested

Posted by Vice Admiral Sarah Hemenway (President) in STF Checklists - Input Requested
Hi everyone,

One thing that I noticed this term is some uncertainty about who had done what when getting people fleet report access and things like that, so I mentioned to Dan the idea of putting together a sort of add/remove checklist for various positions and he ran with it, creating this fantastic document.

Please let us/him know if you see anything missing or have any thoughts about it so that we can incorporate any revisions and then move it from Google Docs to a static page: https://docs.google.com/document/d/1K1tGP0dC3MNeUsgFFYHfp6AmeP-Xszcn3_DxalzcTmw/edit?usp=sharing.

Note: the response times are still in the works; we are only looking for thoughts about whether this covers all of the tasks.

Sarah, Prez

I made some commentary on the google document.

EDIT: I am in proof reading mood at the moment for my assessments, so most are more nitpicky than anything else, take or leave as you see fit.

Russell

While I am still on an LOA, I was able to reply to some comments in the Google Doc, so thanks everyone for that.

Just a reminder, there are two goals with these checklists:

Identify what tasks need to be done when a change/appointment is made, and who is responsible. Some of these are obvious, but human nature being what it is, things get missed. A common one recently has been given people admin access to do a ship report (it’s the FComm who does that in their fleet admin menu), or forgetting to give a new CO admin access on a ship :).

Creating and closing communications loops. There are two issues being addressed here:

The last couple terms have shown that we're not always on the same page on what tasks get done automatically and what tasks require requests to be made. So by creating communication loops, we now have confirmations on important tasks they are done.
As part of closing those communication loops, we need to create some expectations of the timing before follow-up is done. For now, with one exception, I chose two time frames: 3 days for more urgent tasks (like admin access to a ship), and 7 days for less urgent matters (like MOTD updates or ship report access).

Comments would be useful on (a) any appointments/changes that aren’t listed, (b) any tasks missing or needing to be changed, (c) turnaround times for those communication loops, and (d) any other changes or things that might have been missed.

Thanks,
Daniel

Previous post | Parent | Reply | Start New Thread Next chronologically

Posts on The Command Ship

The Meridian Fleet Report - March 2024 on The Command Ship
April 13, 2024, 12:41 p.m.
Commodore Jennifer Ward (Fleet Commander, Meridian Fleet)
Starfleet Academy Report - March 2024 on The Command Ship
April 14, 2024, 2:30 p.m.
Captain Mika Jackson (Academy Commandant)

RSS Feed