Block physical access to restricted areas

Little of this can be handed to software today.

This happens in the physical world, so software agents do not touch it. Automation here means robotics and machinery, which is a different market from the one mapped on this site, on a much slower clock.

Key facts about this work activity
How automatableBarely automatable
Kind of workPhysical, manual and inspection work
Jobs that do it7 occupations
Tool categories that applyNone
O*NET activityPerforming General Physical Activities (4.A.3.a.1)

What this looks like on the job

Not our paraphrase. These are real task statements recorded against this activity, spread across the 7 occupations that perform it.

  • Secure entrances and exits by locking doors and gates.
  • Restrict public access and recreational use of forest lands during critical fire seasons.
  • Block or rope off scene and check perimeter to ensure that entire scene is secured.
  • Perform traffic control duties such as setting up barricades and temporary signs, placing bags on parking meters to limit their use, or directing traffic.
  • Lock doors and gates of entrances and exits to secure buildings.
  • Close entry areas following security breaches or reopen areas after receiving notification that the airport is secure.
  • Post warning signs and lock building doors to secure area to be fumigated.

What we would actually use

Nothing in our landscape addresses this work. That is the honest answer rather than a padded list: this activity needs a person present, or a machine rather than a software agent.

Our pickBuy nothing

Nothing on this site applies. Automation here is robotics and machinery, a different market on a much slower clock, and no software subscription moves it.

Chosen for the cheapest thing that does the job, not the best funded. Nothing on this site is sponsored, and the full landscape is there when you want to disagree with us.

Method. The activity, its taxonomy placement and the occupations that perform it come straight from the public-domain O*NET 30.3 database. The automatability band is ours: we map each of O*NET’s 41 generalized work activities to how much of its output current software can produce, assuming a person still reviews and owns the result. It is a coarse three-way judgment on purpose. A precise-looking percentage here would be invented.