Valheim Co-op Ore Cart Haul Handoff Worksheet

Why ore hauls need a named owner

Ore and refined metal are personal inventory and world objects with group consequences. A player who "just takes the cart" is not only moving cargo; they set the pace for everyone else on the road, the dock, and the smelter line. Groups that rely on vibes usually discover the gap at the worst moment: mid-slope with night falling, or at a beach with a half-empty longship and no clear plan for the next trip.

An ore-cart haul handoff is not a spreadsheet of every copper scrap. It is a role assignment for one event: who decides the leave threshold, who drives or escorts the cart, who owns ship or dock loading, and who is allowed to call abort when the route is unsafe. Without that, the loudest player becomes logistics lead, and quiet players with full inventories get left behind or blamed for a tip they did not cause.

Write the assignment once per haul event, not once per forever. A Black Forest copper cart to the starter beach is not the same job as a Mountains silver run to a distant hub. Reusing yesterday's "I always drive" is fine only if that person is present and accepting the role for this event ID.

The minimum fields before the first load leaves camp

Fill each field or mark it UNKNOWN with the name of the person who will resolve it before the haul starts:

• Event ID and goal — short label: copper cart to Beach-A, iron barge to Hub-Swamp-S, silver to Mountain-Drop. One destination plan per sheet.
• Haul lead — the single person who owns go/no-go on load readiness and leave timing. Not necessarily the best fighter; the clearest route caller.
• Cart / land mover — who controls the cart (or pack animal alternative if the group uses one) and calls tip risk on slopes.
• Ship / dock owner — who owns loading the vessel, casting off, and confirming the unload dock name. Mark N/A for pure land hauls.
• Escort / clear owner — who walks ahead or covers the cart against creatures while the mover focuses on the path.
• Smelter / drop owner — who receives cargo at the destination kiln/smelter line and confirms drop-zone chest labels.
• Cargo list (qualitative) — what is being moved this trip (ore type family, wood/stone support stacks, empty return plan). No invented stack counts required; mark counts UNKNOWN if you are not counting.
• Leave threshold — one sentence the group agrees on. Example: "Leave when the cart is stable for the planned slope and the ship has a named return dock, even if the mine still has loose ore."
• Route and staging names — path description plus portal hub or map pin names that match your portal convention. Prefer written labels over "the usual beach."
• Go time and abort window — when the haul starts, and until which landmark the group will still abort for a missing escort, bad weather call, or broken leave threshold.
• Callouts — exact short phrases: "load check," "cart tip risk," "dock hold," "haul go," "haul abort," "drop confirmed."
• Post-event note owner — who writes one line if cargo was lost, split across two trips without a plan, or dumped at the wrong hub.

The leave threshold is the field groups skip and then argue about. "The cart looks full" is not the same as "we hit the threshold we wrote." If the group cannot agree on the threshold in one sentence, do not start the slope.

A worked example with a synthetic group

In this example, Bo is on the cart while Rin walks ahead. Kai reports the Karve still has a prior wood load that was never sorted. The correct move is "dock hold," not "we will squeeze it." Nest marks free hold space as a soft miss until Kai offloads or the leave threshold is revised in writing for this event only. Revising after the cart is halfway down the slope is how silent disagreements become tip recoveries.

If Rin calls night risk before the dock and the group has no light plan, Nest calls "haul abort" or resets go time. Starting a coastal transfer because someone is impatient is the same as leaving with UNKNOWN escort coverage.

Handoff sequence the group can run in under three minutes

Use this order at the mine staging pin or dock. Do not rearrange under pressure; rearranging is how the escort gets skipped while the cart is already rolling.

1. Haul lead announces event ID and destination — everyone confirms the same hub and unload dock names.
2. Cargo check — cart mover and dock owner report what is loaded qualitatively and whether metal is incorrectly staged near a portal.
3. Leave threshold check — haul lead reads the one-sentence threshold; each role answers ready, shortfall, or UNKNOWN.
4. Escort and route check — escort confirms path clear enough for the plan, or names the blocker.
5. Soft miss handling — any missing escort, blocked dock, or unstable load becomes a delay with a named fixer, or an abort.
6. Haul go or haul abort — only the haul lead says these words. Others may request abort; they do not override go.
7. Segment locks — after haul go, no new mining requests until the abort window closes or the drop is confirmed. Mid-haul "one more dig" is how carts sit alone on roads.
8. Drop confirmed — drop owner calls when cargo is in the agreed chests or smelter input; only then is the event closed.

If someone portals in late to "help," they do not inherit a silent job. The haul lead assigns them escort, dock, or standby. Late joiners grabbing the cart without a role are a common tip source.

Rules that prevent the usual failures

Agree on these once, then point to them when chat gets noisy:

• One haul lead per event. Advice from others is welcome; go/abort is not a vote mid-slope.
• Portals are not ore pipes. Keep metal movement on carts and ships unless your group has a different written rule for a specific exception. Do not argue physics in chat during the handoff.
• No inventing capacities in chat. If someone needs exact cart or ship limits, check the game UI later; do not block the handoff with unverified numbers.
• Tip risk stops the clock. "It will be fine" on a steep path is not ready. Mark tip risk and fix the load, change the route, or abort.
• Dock hold beats optimism. If the vessel is not ready or the unload dock name is ambiguous, the cart does not roll to the beach yet.
• Soft miss needs a named fixer. "Someone should clear the road" is not a plan. "Rin clears to the river bend, Bo waits" is a plan.
• Abort is cheap before cast-off. After the ship leaves, problems become recovery problems; before it leaves, they are handoff problems.
• Death does not reset the haul lead without a new event ID. If you wipe on the road, open a recovery sheet, then a new haul sheet or a clearly tagged retry so notes stay sortable.

Crossplay and platform differences can affect how people join and hear callouts; keep phrases short so they work when voice is uneven. If a join or sync problem looks like a product bug, use your observation worksheets and Iron Gate support rather than blaming the cart driver.

How this sheet connects to portals, death, and smelting

Ore haul readiness is a logistics entry condition, not a substitute for base storage discipline. Destination chest labels and smelter input ownership should match the drop-owner field. If the group routinely dumps ore in unlabeled piles, fix storage language in your shared note before the next H-ID; the ore transport logistics guide is the longer reference for route patterns.

Portal naming from the portal hub label convention keeps player movement separate from cargo movement. "Meet at the forest portal" while the cart is at a different pin is how escorts and movers split without noticing.

If a wipe happens on the path, the death recovery priority worksheet takes over. The haul lead is not automatically the recovery runner. Recovery roles follow gear and path risk; haul lead only speaks to whether survivors still meet the leave threshold before a second push, and whether abandoned cargo gets a new event ID or a deliberate abandon note.

After a boss-related dig, you can still use a short haul sheet even if the fight used a boss attempt debrief. Keep fight notes and cargo notes on separate lines so "we won" does not hide "we left the cart on the ridge."

A one-page template to copy

Copy these lines into your shared note for each haul:

• Event ID / goal / destination hub
• Haul lead / cart mover / ship-dock owner / escort / drop owner
• Cargo list (qualitative) + leave threshold (one sentence)
• Route pins / portal labels / dock names
• Go time / abort window
• Callouts used
• Outcome: haul go / dock hold / haul abort / tip or loss / drop confirmed
• One change for next time (single sentence)

The outcome line matters for habits. If the outcome is repeatedly "soft miss ignored" or "cart left alone," the group does not have a mining problem; it has a handoff discipline problem, and the next change should say so in one plain sentence.

Assumptions and limits

All examples are hypothetical. Valheim patches, cart and ship behavior, portal rules, world modifiers, server settings, and crossplay behavior can change; this page does not claim hands-on testing of a specific build and does not replace Iron Gate's FAQ or support channels when something looks like a bug or unexpected product behavior. No stack-size tables, optimal load math, or exploit claims are made here. Inventory and character risk on online play is real; treat online sessions with the caution the official FAQ describes. Check the stated assumptions before adopting the worksheet.

Sources and method

• Iron Gate: Valheim FAQ — retrieved 2026-10-31
• Iron Gate: Valheim support — retrieved 2026-10-31

AI-assisted writing with automated source, calculation and editorial checks. No hands-on testing or professional certification is claimed. Check the stated assumptions before applying this guide.