Review project requests describing database user needs to estimate time and cost required to accomplish project.

“Review project requests describing database user needs to estimate time and cost required to accomplish project.” is a task performed by Database Architects. Among the occupation's 25 rated tasks, workers place it 6th by importance (#20 most important). About 90% 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.

• Estimate project development or operational costs. in Estimating the Quantifiable Characteristics of Products, Events, or Information

AI exposure

The OpenAI / Eloundou “GPTs are GPTs” study rates this task E2. Exposure with tools — software built on top of a language model (not the model alone) could cut the time 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 0.50. Automation potential label: T2.

Other tasks in this occupation

• Develop and document database architectures. · importance 4.5
• Collaborate with system architects, software architects, design analysts, and others to understand business or industry requirements. · importance 4.5
• Develop database architectural strategies at the modeling, design and implementation stages to address business or industry requirements. · importance 4.5
• Design databases to support business applications, ensuring system scalability, security, performance, and reliability. · importance 4.4
• Develop data models for applications, metadata tables, views or related database structures. · importance 4.1
• Design database applications, such as interfaces, data transfer mechanisms, global temporary tables, data partitions, and function-based indexes to enable efficient access of the generic database structure. · importance 4.1
• Develop methods for integrating different products so they work properly together, such as customizing commercial databases to fit specific needs. · importance 4.0
• Create and enforce database development standards. · importance 4.0
• Document and communicate database schemas, using accepted notations. · importance 4.0
• Develop data model describing data elements and their use, following procedures and using pen, template or computer software. · importance 4.0
• Work as part of a project team to coordinate database development and determine project scope and limitations. · importance 3.9
• Set up database clusters, backup, or recovery processes. · importance 3.9
• Identify and evaluate industry trends in database systems to serve as a source of information and advice for upper management. · importance 3.9
• Demonstrate database technical functionality, such as performance, security and reliability. · importance 3.8

See all tasks on the Database Architects 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-21656,
  title  = {Review project requests describing database user needs to estimate time and cost required to accomplish project.},
  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-21656}
}