Resources Field Reference

Exact resource, allocation, capacity, skill, time-off, and utilization fields.

Resources Field Reference

Use this reference for staffing, skills, capacity, allocations, time off, and Copilot assignee recommendations.

Allocation Methods

  • percent
  • hours_per_week
  • full_time

Allocation Types

  • hard
  • soft

Hard allocations are confirmed. Soft allocations are tentative or pipeline planning.

Allocation Fields

FieldTypeNotes
UserUser selectOptional when using a placeholder.
Start dateDateRequired.
End dateDateRequired.
Allocation methodSelectDefaults to percent.
Allocation typeSelectDefaults to hard.
Allocation percentNumber0 to 100, defaults to 100.
Hours per weekNumberPositive, optional.
PlaceholderBooleanUse when no user is selected.
Placeholder roleJob role selectOptional.
NotesTextOptional, max 500 characters.

Allocation Status Values

Capacity status values:

  • ok
  • near
  • over

Allocation approval status values:

  • none
  • pending
  • approved
  • rejected
  • returned

Capacity Fields

Member capacity uses:

  • User.
  • Default weekly hours, up to 168.

Planner and heatmap views use capacity hours, allocated hours, soft allocated hours, time off hours, effective capacity hours, logged hours, allocation percent, utilization percent, and status.

Time Off Fields

Time-off types:

  • leave
  • holiday
  • sick
  • other

Time-off fields include user, start date, end date, type, notes, half-day flag, hours override, and approved flag.

Skills

Skill types:

  • yes_no
  • number
  • level
  • single_choice
  • multi_choice

Skill fields include name, skill type, section, and options.

Member skill values can be boolean, number, string, or string array depending on skill type.

Job role required skills can define required skill values for a job role.

Copilot Notes

  • For "best person based on skills", search team member skills and capacity before drafting an assignee.
  • Do not assign a person only from name similarity if skill/capacity data is available.
  • If no skill match exists, say that skills data is missing or no matching member was found.
  • Allocation approval decisions should follow approval request rules and only update pending requests.