{
  "platformId": "chatgpt-work",
  "taskSlug": "task-21466",
  "directAnswer": "Use ChatGPT Work to turn an approved project baseline and human-supplied delivery evidence into a plan-change packet: objectives, scope, technology assumptions, schedule and dependency logic, funding and staffing scenarios, constraints, decision requests, and unresolved conflicts shown against the current baseline. It can expose the shape and consequence of a proposed plan; it cannot set priorities, choose a technology, allocate people or money, approve a change, commit a date, create a staffing obligation, or make the plan operative. O*NET has not published task ratings for this occupation, so the attached centrality figures are unavailable rather than invented; the guide is a controlled preparation pattern, not a claim about current adoption.",
  "topUseCases": [
    {
      "interventionId": "task-21466:task-21466-scaffold:assist",
      "taskId": "task-21466",
      "task": "Develop or update project plans including information such as objectives, technologies, schedules, funding, and staffing.",
      "workflowId": "task-21466-scaffold",
      "authorityMode": "assist",
      "centralityScreen": {
        "value": null,
        "importance": null,
        "occupationalRelevance": null,
        "frequency": {
          "kind": "unavailable",
          "reason": "O*NET 30.3 publishes the task statement for 13-1082.00 while task-rating collection remains in progress; no importance, relevance, or frequency rows are available.",
          "sourceField": "onet-30.3:Task Ratings[13-1082.00]=no-rows"
        }
      },
      "agentFit": {
        "value": 0.9025,
        "sourceField": "rule:digital-feasibility-and-capability-fit-single-count.v2"
      },
      "distribution": {
        "value": 0,
        "sourceField": "roles-kv:role-13-1082-00.aiPlaybook=null;rule:unavailable-evidence-conservative-zero.v2"
      },
      "evidenceConfidence": "unavailable",
      "withinGateScore": null,
      "gate": {
        "status": "limited",
        "reason": "Authority remains below an approval-required intervention."
      },
      "capabilityIds": [
        "connected-apps-files",
        "deliverable-generation"
      ],
      "expectedArtifact": "Plan-change packet with baseline diff, dependency and resource scenarios, assumption register, decision requests, and unresolved-conflict ledger",
      "humanReviewPoint": "The accountable sponsor, project lead, technical owner, finance owner, and people manager verify assumptions and approve objectives, technology, funding, staffing, schedule, scope, and change decisions.",
      "riskLevel": "medium"
    }
  ],
  "workflows": [
    {
      "id": "task-21466-scaffold",
      "goal": "Turn a human-supplied project baseline and delivery evidence into a traceable plan-change packet that makes alternatives and constraints inspectable without changing the plan or committing resources.",
      "inputs": [
        "Approved baseline covering objectives, scope, deliverables, technologies, schedule, dependencies, funding, staffing, and acceptance criteria",
        "Human-supplied status, estimates, capacity, budget, risk, issue, decision, change, vendor, and dependency evidence with source dates",
        "Authorized governance, security, procurement, people, finance, and customer or stakeholder constraints"
      ],
      "connectedSystems": [
        "Read-only approved plan, roadmap, schedule, and decision records",
        "Read-only human-supplied delivery, capacity, finance, and technical evidence"
      ],
      "steps": [
        "Inventory the baseline and proposed inputs by source, as-of date, owner, and status; label any missing estimate, unresolved dependency, capacity assumption, or conflicting instruction rather than filling it in.",
        "Construct a baseline diff across objectives, scope, technology, schedule, funding, staffing, dependencies, risks, and acceptance conditions, keeping facts, estimates, options, and decisions distinct.",
        "Model only the supplied alternatives and their stated constraints, sequencing dependencies and showing where a date, cost, staffing level, or technical path depends on a human decision or external confirmation.",
        "Produce a plan-change packet with decision requests and stop before changing a plan, assigning work, reserving people or funds, selecting technology or a vendor, committing a date, approving procurement, or communicating a commitment externally."
      ],
      "expectedArtifact": "Plan-change packet with baseline diff, dependency map, schedule and resource scenarios, assumption register, and decision ledger",
      "starterPrompt": "Using only the approved project baseline, governance constraints, and dated delivery, technical, capacity, and finance evidence I provide, prepare a plan-change packet. Show the baseline diff across objectives, scope, technology, schedule, funding, staffing, dependencies, risks, and acceptance criteria; label each item FACT, ESTIMATE, OPTION, CONFLICT, MISSING, or HUMAN DECISION; and identify the decisions each scenario needs. Do not change the plan, assign work, reserve people or funds, select technology or vendors, commit a date, approve procurement, or communicate any commitment.",
      "humanReviewPoint": "The accountable sponsor, project lead, technical owner, finance owner, and people manager validate evidence and own every objective, scope, technology, resource, funding, schedule, and change decision.",
      "commonFailure": "Treating a scenario as a plan, a capacity estimate as a staffing commitment, a dependency sketch as a delivery date, or a technical option as an approved architecture."
    }
  ],
  "setupRecommendations": [
    {
      "item": "Use a project- and decision-scoped, read-only workspace containing the approved baseline and dated delivery evidence; keep plan writes, ticket assignment, calendar, staffing, finance, procurement, vendor, and customer-communication access disconnected.",
      "rationale": "The useful result is a transparent baseline diff and decision packet. Objectives, architecture, capacity, staffing, funding, schedule, procurement, and external commitments need accountable human authority.",
      "capabilityIds": [
        "connected-apps-files",
        "approval-enterprise-controls"
      ]
    }
  ],
  "prompts": [
    {
      "id": "task-21466-starter",
      "title": "Prepare a project plan-change packet",
      "prompt": "Here are the approved project baseline, governance constraints, and dated delivery, technical, capacity, and finance evidence. Build a plan-change packet that shows the baseline diff across objectives, scope, technology, schedule, funding, staffing, dependencies, risks, and acceptance criteria; labels every item FACT, ESTIMATE, OPTION, CONFLICT, MISSING, or HUMAN DECISION; and lists the decisions required for each scenario. Do not alter the plan, assign work, reserve people or funds, choose technology or vendors, commit a date, approve procurement, or contact stakeholders.",
      "expectedArtifact": "Baseline-diff plan packet with dependency, resource, assumption, and decision ledgers",
      "humanReviewPoint": "The accountable sponsor, project lead, technical owner, finance owner, and people manager verify the evidence and retain every plan and resource decision."
    }
  ],
  "humanOwnedResponsibilities": [
    "Baseline-authority law: the approved objective, scope, deliverable, schedule, funding, staffing, technology, and acceptance baseline has a named owner and is the only starting point for a proposed change",
    "Fact-option-decision law: observed status, an estimate, a constraint, an option, a forecast, and an approved decision remain distinct and cannot borrow one another's authority",
    "Dependency-and-date law: a dependency map describes stated conditions; it does not prove availability or authorize a delivery date, sequence, handoff, or external commitment",
    "Resource-and-people law: capacity data, a role label, and a scenario are not consent, allocation, assignment, hiring, contractor engagement, budget approval, or workload authorization",
    "Change-and-release law: scope, architecture, security, procurement, funding, staffing, plan writes, stakeholder communication, and external commitments change only through the authorized human governance path"
  ],
  "risks": [
    {
      "id": "task-21466-scaffold-risk",
      "level": "medium",
      "description": "A coherent-looking plan can silently turn a stale estimate into a staffing promise, a technical option into an architectural decision, an unresolved dependency into a date, or a proposed budget into authority to spend.",
      "mitigation": "Anchor the packet to the approved baseline; retain source dates, ownership, evidence states, conflicts, and missing inputs; show alternatives as conditional scenarios with decision gates; and require the accountable sponsor, project, technical, finance, and people owners to approve every operative change."
    }
  ],
  "sources": [
    {
      "id": "occupation-project-management-specialists",
      "title": "Project Management Specialists occupational render model",
      "url": "https://singulariki.com/roles/project-management-specialists",
      "publisher": "gold.onet_role_starter_surface",
      "lastReviewedAt": "2026-06-03"
    },
    {
      "id": "openai-chatgpt-work",
      "title": "ChatGPT Work and Codex",
      "url": "https://help.openai.com/en/articles/20001275-chatgpt-work-and-codex",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-work-deliverables",
      "title": "Creating and editing documents, spreadsheets, and presentations with ChatGPT Work",
      "url": "https://help.openai.com/en/articles/20001278-creating-and-editing-documents-spreadsheets-and-presentations-with-chatgpt-work",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-work-cloud-browser",
      "title": "Using cloud browser in ChatGPT",
      "url": "https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-work-desktop-browser",
      "title": "Using the built-in browser in the ChatGPT desktop app",
      "url": "https://help.openai.com/en/articles/20001277-using-the-built-in-browser-in-the-chatgpt-desktop-app",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-chatgpt-skills",
      "title": "Skills in ChatGPT",
      "url": "https://help.openai.com/en/articles/20001066",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-chatgpt-scheduled-tasks",
      "title": "Scheduled Tasks in ChatGPT",
      "url": "https://help.openai.com/en/articles/10291617-tasks-in-chatgpt",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    },
    {
      "id": "openai-workspace-agents",
      "title": "ChatGPT Workspace Agents for Enterprise and Business",
      "url": "https://help.openai.com/en/articles/20001143",
      "publisher": "OpenAI",
      "lastReviewedAt": "2026-07-11"
    }
  ],
  "freshness": {
    "platformVersion": "2026-07-09-launch",
    "platformReviewedAt": "2026-07-11",
    "occupationalDataVersion": "O*NET 30.3",
    "occupationalDataGeneratedAt": "2026-06-03T05:05:52.989984+00:00"
  },
  "quality": {
    "uniqueOccupationalOrTaskEvidence": false,
    "validPlatformSpecificWorkflow": false,
    "clearOutputArtifact": false,
    "realCapabilityMatch": true,
    "meaningfulHumanReviewSection": false,
    "sourcesAndFreshness": false,
    "distinctInternalRelationships": false,
    "noUnresolvedFactualOrProductVersionFailure": false,
    "indexable": false
  }
}