AI coworker roles need a nonhuman position record

Classify the position before counting the capacity

Decide what the persistent agent represents in the workforce model. It may be a nonhuman service position attached to an organization, a capability assigned to an existing human job, or temporary project capacity. It should not silently become an employee, a filled human position, a vacancy closure, or a full-time-equivalent unit because the product calls it a coworker. Record the classification, the affected job family and organization, the planning purpose, the accountable CHRO and business owners, and the authority that approved its use in staffing assumptions.

Create a durable position record with an immutable identifier, role name, nonhuman classification, organization, cost center, budget owner, service owner, planned start and end, approved responsibilities, affected human positions, capacity unit and method, expected availability, dependencies, current status, workforce-plan version, and next review. Keep fields that imply employment, compensation, benefits, tenure, protected characteristics, or worker eligibility empty or explicitly inapplicable. A directory entry can describe technical presence; it cannot decide how the organization counts work or people.

Keep the position, account, and task assignment separate

The position record answers where the organization places the capacity and which staffing decision depends on it. The Workspace account and runtime identity answer which system acts. Individual assignments answer what work was actually requested. Link the records, but do not collapse them. One position may use several technical identities or temporary subagents, and one account may perform assignments whose volume changes over time. Without that separation, an active account can be mistaken for productive capacity and a disabled account can leave an approved staffing assumption behind.

For each link, preserve the effective dates, responsible owner, approved role version, organization, funding source, and reconciliation method. Identify which record is authoritative when the directory, workforce plan, finance plan, service catalog, and operational queue disagree. The CHRO does not need to own credential administration, but must be able to show which nonhuman position a technical identity supports and which workforce assumption must be reopened when that relationship changes.

Reconcile the position with headcount and workforce plans

Start from the approved workforce baseline: filled employee positions, vacancies, contingent labor, outsourced service, planned hires, demand, workload, and budget. Show whether the nonhuman position adds capacity, substitutes for a planned service, defers a hire, changes a vacancy, or changes the work content of an existing job. Preserve the alternative that leadership would use without it. A provider example or estimated time saving cannot establish that a vacancy is closed, a role is redundant, a span can widen, or demand can be served with fewer people.

State the unit used to compare capacity and its limits. Hours available, tasks attempted, cases completed, response coverage, and accepted outcomes measure different things. Include human preparation, review, exception handling, repair, coordination, and service gaps. Reconcile the nonhuman position with the financial plan without presenting software spend as payroll or treating an account count as headcount. Record who can approve a change to the capacity assumption and which hiring, scheduling, redeployment, or restructuring decision must wait for local evidence.

Define a reporting relationship without inventing personhood

Assign a business sponsor and a manager accountable for the service outcome, backlog, priorities, exceptions, and continuity. That relationship is governance for a service position; it does not make the agent an employee, manager, supervisor, or holder of employment authority. Do not place people under an AI agent in an HR system, count it in managerial span, or let its generated assessment become a management decision merely because the product presents a team-member metaphor.

Document how the nonhuman position appears in organization charts, team rosters, directories, planning tools, and management reports. Use a visible classification and consistent label so leaders do not infer headcount, seniority, succession coverage, or decision rights from placement alone. If the organization chooses to show the position beside human roles, preserve the human leader who remains responsible for work allocation, employee support, performance, safety, accommodation, and employment decisions.

Reopen staffing decisions when the position changes or closes

Set reapproval triggers for a new organization, sponsor, job family, responsibility, work volume, schedule, channel, tool, cost model, capacity claim, or relationship to a human position. Update the workforce and financial plan together, record the old and new assumption, and identify any hiring, vacancy, contingent-work, role-design, or workload decision affected. A technical feature change should not alter the staffing model without the CHRO and business owners seeing the consequence.

When the nonhuman position closes, remove its capacity from the next plan, identify unfinished demand, restore or replace the affected service, and reconcile any vacancy or hiring assumption that depended on it. Preserve the final position status, effective date, workload disposition, budget treatment, responsible owners, and evidence used for the replan. Google establishes current product positioning for a persistent agent with a defined role. Only the organization's position record can establish how that capacity enters and leaves its job architecture and workforce plan.

Turn this source into a reviewable decision

For AI for CHROs, use this briefing as a dated decision record rather than a substitute for the source. Preserve Google Cloud: Welcome to Gemini at Work 2026, the exact URL, the October 9, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Workforce and capacity planning; Skills intelligence and internal mobility; HR policy and employee service; Workplace AI governance and change. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

Google Cloud is the provider source. Its October 8, 2026 announcement describes Gemini agent roles, persistence, accounts, channels, identity, and provider-selected customer examples. The page does not establish a buyer's entitlement, tenant configuration, job architecture, position classification, headcount treatment, capacity method, staffing or financial plan, human workload, role cost, hiring or employment decision, legal obligation, or workforce outcome. Current contracts and product documentation, job and position inventories, organization and workforce-plan records, reconciled finance and service data, representative capacity and workload evidence, and qualified HR, workforce-planning, finance, operations, labor, employment, accessibility, privacy, security, risk, procurement, records, and legal review control.