Which of the following is NOT a recommended characteristic for incident objectives?

The answer

The characteristic that is NOT recommended is any option describing objectives as "stated in broad terms to allow for flexibility." This is the trap answer on FEMA IS-200 and related ICS exams because it sounds reasonable—flexibility feels like a virtue—but it directly contradicts how ICS defines a usable objective.

In the Incident Command System, incident objectives must be concrete enough that the Operations Section can build strategies and tactics around them and that Planning can measure progress at the end of each operational period. An objective written in broad terms ("improve the situation," "handle the fire") gives responders nothing to execute against and nothing to evaluate. So the broad/flexible wording is precisely the quality ICS wants you to avoid.

The recommended characteristics (the SMART memory aid)

FEMA describes strong incident objectives using the familiar SMART framework:

• Specific — clearly states what is to be accomplished, with no vagueness.
• Measurable — you can tell objectively whether it was met.
• Attainable (and action-oriented) — realistic given available resources.
• Relevant — within the Incident Commander's authority and jurisdiction.
• Time-sensitive — includes a standard and a timeframe (usually tied to the operational period).

Every correct answer choice on this question maps to one of those traits: "measurable and attainable," "includes a standard and timeframe," and "within the authority of the Incident Commander." The one option that maps to none of them—the broad/flexible one—is the exception the question is hunting for.

Why the other options are wrong (i.e., they ARE recommended)

• "Measurable and attainable" is a core SMART trait; objectives you cannot measure or realistically reach are useless for planning. This is recommended, so it is not the answer.
• "Includes a standard and timeframe" captures the Time-sensitive element—objectives are tied to the operational period. Recommended, not the answer.
• "Within the authority of the Incident Commander" reflects relevance and legal/organizational scope; an IC cannot set objectives outside their delegated authority. Recommended, not the answer.

That leaves the broad-terms option standing alone as the un-recommended trait.

The bigger picture

Incident objectives sit at the top of the ICS planning cycle (the "Planning P"). The Incident Commander sets them; the Operations Section Chief develops strategies and tactics to meet them; and they become the backbone of the written Incident Action Plan (IAP) for each operational period. Because the entire IAP is measured against these objectives, they have to be specific and measurable—otherwise there is no way to brief crews, assign resources, or judge success at the operational-period debrief. Flexibility in ICS comes from strategies and tactics, which can be adjusted freely; the objectives themselves stay tight and clear.