Quick answer

When workers are slow, separate four questions before changing the business:

  1. Player Handicraft: a developer reply in the current Steam discussion says the player's Handicraft skill affects worker productivity or business efficiency.
  2. Employee skill: the official economy diary says age and skill affect hiring cost, so a worker's starting profile is part of the hiring decision.
  3. Training and promotion: the official source says an apprentice can be trained and promoted to journeyman, which boosts productivity.
  4. Task assignment: repeat or batch assignment changes management effort, not the worker's underlying skill.

Use these as separate tests. The current sources do not publish a universal production percentage, generic worker-exhaustion penalty or accident-rate multiplier for Handicraft. If the output is slow, first check the assigned task and inputs, then test worker skill, training and the player's Handicraft context one change at a time.

This page owns worker productivity, hiring and training. Use Automation, Carts & Workers for repeat tasks and business-master behavior, and Raw Materials Missing? when the worker is waiting on an input.

What Handicraft means here

The player-character's Handicraft is not the same thing as an employee's job assignment. The developer response reviewed for this task connects the player's Handicraft skill with worker productivity or business efficiency, while the official economy material separately explains employee age, skill, training and promotion.

That makes Handicraft a factor to test in the current character and business context, not a reason to copy a single number into every workshop. Record the business, worker, task and build when comparing results.

Hiring: buy the starting profile or train it

The official economy diary says hiring cost depends on a worker's age and skill. A young and skilled worker can cost more than an older or inexperienced worker. If the upfront cost is the constraint, hiring an unskilled worker and training them is a different path rather than proof that the worker is equivalent immediately.

Before hiring, write down:

  • the task the worker must perform;
  • the current skill shown by the game;
  • the hiring cost;
  • whether training time fits the production window; and
  • whether the business has enough inputs and storage for the worker to matter.

This prevents the common mistake of treating a higher hiring cost as a guaranteed profit result. It is a trade between time, money and the current task.

Training and apprentice promotion

The official source says workers can be trained and that promoting an apprentice to journeyman boosts productivity after the required time. The exact interface, cost and timing should come from the current client rather than an old demo screenshot.

Use a controlled training check:

  1. Capture the worker's current role and skill.
  2. Confirm the business has a stable task and enough input.
  3. Apply one training or promotion step shown by the client.
  4. Compare the next comparable production cycle.
  5. Keep the result tied to the worker, task and build you tested.

If the next cycle changes, record whether the cause was training, input supply, assignment, storage or a separate event. Do not attribute every change to Handicraft.

Productivity versus automation

Automation reduces the attention required to reassign work. It does not prove that the worker produces faster. The current demo supports batch assignment and repeat tasks, while the Early Access roadmap describes a first business-master layer. Keep those management controls separate from skill and productivity tests.

If a repeating task stops, check the automation boundary and the input chain before replacing trained workers. If the task is available and supplied but the result remains slow, compare worker skill and training in the same business context.

What the current sources do not quantify

The current public material supports the factors above but does not give a launch-safe formula for:

  • a fixed Handicraft percentage;
  • a universal production-time reduction;
  • a generic worker fatigue or exhaustion penalty;
  • an accident-rate effect attributable to Handicraft; or
  • one best worker profile for every profession and city.

Events can also affect the wider economy and population. The official diary describes examples such as harsh weather or outbreaks affecting productivity, but those examples do not replace a current in-game check for a specific worker problem.

Current build boundary

The official Steam record checked on September 13, 2026 schedules Early Access for September 17, 2026. The economy and employee notes were written during active development. Recheck Handicraft labels, training controls and productivity behavior in the launch client before treating a result as a stable rule.

Frequently asked questions

Does Handicraft affect worker productivity in The Guild 1 Remake? A developer reply in the current Steam discussion says the player's Handicraft skill affects worker productivity or business efficiency. Test it with the same business, task, inputs and build; the public sources do not give a universal percentage.

Should I hire a skilled worker or train an apprentice? Compare the current hiring cost, skill, training time and production window. The official economy diary supports both the age-and-skill hiring trade-off and apprentice-to-journeyman promotion.

Does assigning repeat tasks make workers more productive? Repeat assignment changes management effort. It does not by itself prove a faster production rate; keep the automation question separate from worker skill and training.

Do workers have a generic exhaustion penalty? The current approved sources do not publish a general exhaustion formula that can be applied to every worker. Check the current client state instead of importing a rule from another Guild game or an older demo.

Why is my workshop still slow after training? Check inputs, storage, task assignment, the worker's current skill and any visible event or business condition. One training step does not establish that every other bottleneck is gone.

Sources

Last verified: September 13, 2026. Recheck the current Handicraft, training and employee panels after the Early Access build is live.