Identify or document backup or recovery plans.

“Identify or document backup or recovery plans.” is a core task performed by Web Administrators. Among the occupation's 35 rated tasks, workers place it 34th by importance (#2 most important). About 95% of workers say it is relevant to their job.

This is a single occupation-specific task statement from O*NET. The figures below describe how central the task is to the job and what independent studies measure about AI and this kind of work — not a prediction that the task will be automated.

Work activities this task rolls up to

O*NET groups concrete tasks into broader work activities shared across many occupations.

• Develop contingency or emergency response plans. in Thinking Creatively
• Maintain operational records. in Documenting/Recording Information

AI exposure

The OpenAI / Eloundou “GPTs are GPTs” study rates this task E1. Direct exposure — a language model could plausibly cut the time to do this task by at least half.

Exposure measures whether a model could meaningfully speed the task up — it is an estimate of overlap with model capabilities, not a measure of whether the work will be done by software. The study's intermediate score (β) for this task is 1.00. Automation potential label: T3.

Other tasks in this occupation

• Monitor systems for intrusions or denial of service attacks, and report security breaches to appropriate personnel. · importance 4.8
• Back up or modify applications and related data to provide for disaster recovery. · importance 4.6
• Identify, standardize, and communicate levels of access and security. · importance 4.5
• Correct testing-identified problems, or recommend actions for their resolution. · importance 4.5
• Determine sources of Web page or server problems, and take action to correct such problems. · importance 4.3
• Implement updates, upgrades, and patches in a timely manner to limit loss of service. · importance 4.3
• Implement Web site security measures, such as firewalls or message encryption. · importance 4.2
• Collaborate with development teams to discuss, analyze, or resolve usability issues. · importance 4.2
• Test issues such as system integration, performance, and system security on a regular schedule or after any major program modifications. · importance 4.1
• Perform user testing or usage analyses to determine Web sites' effectiveness or usability. · importance 4.1
• Track, compile, and analyze Web site usage data. · importance 4.0
• Document application and Web site changes or change procedures. · importance 4.0
• Test backup or recovery plans regularly and resolve any problems. · importance 3.9
• Recommend Web site improvements, and develop budgets to support recommendations. · importance 3.9

See all tasks on the Web Administrators page.

Sources for this page

Every figure above traces to a named public dataset and the exact release below — not hand-written opinion. See the full methodology for what each measure does and does not mean.

• O*NET 30.3 U.S. Department of Labor / National Center for O*NET Development
• “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130 OpenAI / academic

Data compiled June 2, 2026. Figures are estimates, not advice.

@misc{singulariki-task-14741,
  title  = {Identify or document backup or recovery plans.},
  author = {{Singulariki}},
  year   = {2026},
  note   = {O*NET 30.3; “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130. Accessed June 7, 2026},
  url    = {https://singulariki.com/tasks/task-14741}
}