Narrative:

We have been working a lot of weird traffic situations with weird routes and complex traffic flows in our area due to vip movement. Last night; the operations manager (OM) told me that in 15 minutes; some airspace was going to go hot because of vip movement; but that they didn't know which airspace. He also advised that he suggested we start considering the tfr's hot; but no one in the area knew what he was talking about. There had been something on cedar that we read before our shift; but it just talked about TRACON's class B lateral boundary; so we didn't know it applied to us. I had to get out a sectional; try to use a blank flight strip to make a ruler; and we tried approximating the boundary of the tfr based on those rough calculations. No one briefed us on what impact the tfr would have; and it wasn't put in plain language for us to be able to decipher or to have any real valuable information on where to draw the tfr boundaries on our scopes. Not only that; but we were officially told that it was in fact the tfr's going hot two minutes after they actually went hot.I know things can be fluid when it comes to vip movement. However; the paperwork/ information about a tfr needs to be given to controllers in a way they can actually use. Specific dimensions and what that means to the area should be on a hot sheet or something. Ideally; it would be nice to get a verbal briefing in case we have questions about the tfr. Also; the added traffic and complexity needs to be taken into account and traffic should be slowed down going into areas affected by vip movement.

Google
 

Original NASA ASRS Text

Title: Center Controller reported confusion when the Front Line Manager walked by and said some airspace was going hot; but did not know which airspace.

Narrative: We have been working a lot of weird traffic situations with weird routes and complex traffic flows in our area due to VIP movement. Last night; the Operations Manager (OM) told me that in 15 minutes; some airspace was going to go hot because of VIP movement; but that they didn't know which airspace. He also advised that he suggested we start considering the TFR's hot; but no one in the area knew what he was talking about. There had been something on CEDAR that we read before our shift; but it just talked about TRACON's Class B lateral boundary; so we didn't know it applied to us. I had to get out a sectional; try to use a blank flight strip to make a ruler; and we tried approximating the boundary of the TFR based on those rough calculations. No one briefed us on what impact the TFR would have; and it wasn't put in plain language for us to be able to decipher or to have any real valuable information on where to draw the TFR boundaries on our scopes. Not only that; but we were officially told that it was in fact the TFR's going hot two minutes after they actually went hot.I know things can be fluid when it comes to VIP movement. However; the paperwork/ information about a TFR needs to be given to controllers in a way they can actually use. Specific dimensions and what that means to the area should be on a hot sheet or something. Ideally; it would be nice to get a verbal briefing in case we have questions about the TFR. Also; the added traffic and complexity needs to be taken into account and traffic should be slowed down going into areas affected by VIP movement.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.