Worker Roles & Assignments Explained

Base productivity in Palworld is rarely limited by raw stats. Most slow or inefficient bases fail because Pals are doing the wrong jobs, switching tasks constantly, or wasting time moving around.

This guide explains how to think about work suitability, roles, and assignments so your base runs smoothly without micromanagement.

The core idea: suitability beats Work Speed

Every Pal has a set of work suitabilities — the specific base jobs it's capable of, each rated on a level 1–4 scale. A Pal only contributes to a job it has suitability for, and a higher suitability level means it does more work per cycle at that job.

This is the part new players miss: Work Speed is a multiplier on top of suitability, not a substitute for it. A Pal with no Mining suitability will never mine no matter how high its Work Speed; a level 4 miner with mediocre Work Speed still out-mines a level 1 miner with great Work Speed. Match the Pal to the job first, then optimize the stat.

For how the stat layers on top, see Work Speed Explained.

The 12 work suitabilities

There are 12 work types in the game. Every base job maps to one of them:

A single Pal usually has two to four of these. That overlap is exactly what causes the task-switching problems below.

Specialization beats flexibility

A Pal that can do many things is often worse than a Pal that does one thing well and consistently, because:

• task switching kills uptime
• pathing time between jobs adds up fast
• high Work Speed means nothing if the Pal keeps leaving the station

Your goal is predictable behavior, not theoretical flexibility.

The main worker roles

Almost every base breaks down into a few functional roles.

1) Dedicated crafters

These Pals should stay at crafting and production stations, avoid transport and harvesting where possible, and focus on long production chains. Assign them near the stations they use, don't give them competing tasks, and pair them with separate transport Pals. This is where Handiwork suitability and Work Speed matter most — a level-4 handiwork Pal like Anubis parked at a workbench is the backbone of most mid-game bases.

2) Harvesters / gatherers

These Pals collect raw resources (Gathering, Lumbering, Mining), often work in bursts, and benefit from consistency over speed. The common mistake is letting harvesters also craft — they abandon stations mid-task to go chop a tree, and nothing finishes.

3) Transport-only workers

Transport Pals are productivity multipliers. Their whole job is to move items, keep stations supplied, and prevent crafters from leaving their posts. A small number of dedicated transporters — a level-4 hauler like Wumpo — often outperforms many mixed-role workers or high-speed crafters that keep wandering off to deliver their own output.

Passives that reinforce a worker role

Passive skills should reinforce the role, not fight it. These are the ones that actually matter for base work, with their real values:

The "infinite worker" build is Artisan + Lucky + Workaholic + Diet Lover — see Passive Skills Explained for the full template and how to breed it.

Avoid these on workers

If any of these show up, that Pal is a bad worker:

• Slacker (−30% Work Speed)
• Clumsy (−10% Work Speed)
• Glutton / Bottomless Stomach (faster hunger — workers starve and stop)
• Destructive / Unstable (faster SAN drain — workers break down)

Note that Musclehead (+30% Attack, −50% Work Speed) is a combat passive. Putting it on a worker halves productivity. Tier doesn't equal value for the role.

Base layout matters more than stats

Even perfect workers fail in bad layouts. Keep storage close to producers, avoid long walking paths, don't overcrowd stations, and leave clear routes. If a Pal spends half its time walking or stuck, no passive will save you — that's the Pathing & AI problem.

Common mistakes (and fixes)

Mistake: "More workers = faster"

Fix: fewer, better-assigned workers outperform chaos. You also have a hard Pal cap per base, so quality matters more than quantity.

Mistake: letting everyone transport

Fix: assign dedicated transport Pals so crafters stay put.

Mistake: chasing Work Speed before fixing suitability and layout

Fix: match suitability to the job and fix the layout first, then optimize stats.

Mistake: ignoring role clarity

Fix: decide what each Pal is allowed to do, and breed/assign so its suitabilities don't pull it off-task.

A simple role assignment checklist

Before you call a base "finished":

• Does each Pal have a clear primary role backed by real suitability for it?
• Are crafters staying at their stations?
• Are transport tasks handled by dedicated haulers?
• Is storage close to production?
• Is task switching minimal?

If most answers are "yes," your base will run smoothly.

Related

• Work Speed Explained — the multiplier that sits on top of suitability
• Pathing & AI Explained — why workers wander, get stuck, or stop
• Passive Skills Explained — the worker passive templates
• Workforce Composition Planner — model your base's output