YARDtwin

9am: a queue at your gate backing onto the road. 2pm: half your docks sitting empty. Same yard. Same day. Same docks, same crew. So it was never a capacity problem — it was an arrival-curve problem. It happens because every carrier books "first thing". Early protects their day, and nobody booking can see whether your gate, your docks or your crew will actually be free at 9am — so they all aim for it. The predictable result is a wall in the morning and a ghost town after lunch, and you can't staff your way out of either. Capacity-aware scheduling attacks the curve, not the docks. Every slot is offered against your real hourly dock AND labour capacity — not an open calendar. Carriers see genuine availability, so they stop defensive-booking the morning. Throttle and capacity rules put a ceiling on any single hour. And the quiet hours become the easy ones to book. Flatten the curve and the whole day changes: shorter queues, fewer idle docks, more trucks through the same operation. In our modelling that's around 46% off the average gate wait — with the crew you already have. What does your gate look like at 9am versus 2pm — honestly? 👇

There's a simple test for "AI-powered" yard software, and most tools fail it. Not "does it demo well". Every tool demos well now — the deck is gorgeous, the concept video is slick, there's a chatbot bolted to the corner. The test is: does the AI remove real work on a real shift, or does it only appear in the sales meeting? Here's the honest version of the difference. AI that demos well: slideware, a generic assistant that knows nothing about your yard, and a roadmap where the roadmap *is* the product — everything good is "coming soon". AI that clocks in: vision OCR that reads plates, seal numbers and GMP paperwork so nobody hand-keys them — live today. A multilingual assistant that answers your actual team in 26 languages, in the context of your actual yard — live today. Anomaly flags that surface unusual dwell, weights and patterns before they become problems — live today. And yes, we have a roadmap — agentic orchestration is genuinely next. But we'd rather show you what's working on the floor now than sell you what might work someday. If you're evaluating "AI" tooling, ask one question: what's live today versus what's on a slide? What's the most over-hyped "AI" feature you've been pitched in logistics? 👇

The 11 rule types and how they enforce yard policy automatically: https://lnkd.in/deujAzu4

A dock built to hold the most pallets is not the same as a dock built to move the most trucks safely. We treat dock doors as if they're interchangeable — a hole in the wall a trailer backs up to. They're not. The right process for a pallet of pharma finished goods (seal check, weighbridge, full document pack, temperature log) is completely wrong for a bulk raw material, and both are overkill for packaging. When those controls live in people's memory, they get skipped — usually on the busiest day, usually by the newest person, usually on the load where it matters most. The fix is boring and it works: configure each dock and each material type once, with its own controls. Seal required? Weighbridge required? Which documents? Temperature logging? Set it at setup, and the right checks fire automatically for every matching load — by rule, not by whoever happens to be on the gate. Compliance stops being a thing people remember to do and becomes a thing the system does. Which control gets skipped most on your busiest days — seals, weights, or paperwork? 👇

Ask anyone how your yard is *allowed* to run, and you get pointed at a person. "Ask Deirdre — she knows which carriers get priority, which dock takes hazmat, when the gate's too full to accept another booking." Deirdre is brilliant. Deirdre is also on leave next week, and the yard doesn't run the same way when she's not standing in it. That's the real risk in most yards: the operating policy lives in one supervisor's head. Not written down in a way the yard can act on — just known, by one or two people, most of the time. A rules engine takes that judgement and makes it structural. Eleven rule types — hazmat routing, carrier priority and blocks, capacity caps, gate throttling, blackout windows, inspection triggers, dwell alerts, vehicle compatibility, product routing and more — enforce the policy automatically. On every booking. Every arrival. Every shift, including the night one nobody's watching. The goal isn't to replace your best supervisor's judgement. It's to make the whole yard run on it, even when they're not there. Where do your yard's rules actually live right now — a person, a laminated sheet, or a system? 👇

If nearly half your warehouse floor turns over in a year, onboarding isn't an event. It's the permanent state of your operation. BLS-derived figures put warehouse separation rates around 49% — roughly one in two workers gone within twelve months. Add seasonal peaks and agency cover, and there is never a moment when your whole team is "trained up". You are always putting someone new on the gate. So the question isn't "how good is your training programme". It's "how forgiving is your yard tooling to someone on their first shift, in a language that might not be their first". That's a design choice, and it's usually made badly. The tools that survive high turnover share a few traits: a role-based screen that shows the gate job and nothing else, a guided flow that leads step by step, one-tap actions instead of free-text fields to get wrong, and — the one most tools skip — an assistant that answers "what do I do now?" in the worker's own language. Ours does that in 26. Put someone new on the gate this morning, and they're productive this morning. The audit trail behind them means it's safe to learn by doing. How much of your week goes to training and re-training on the floor? 👇

The barrier was never your gate's bottleneck. The check-in was. Watch a manual gate for an hour. The truck rolls up — then everything stops. ID checked. Booking found. Registration keyed in by hand. Paperwork shuffled. Warehouse radioed. Five jobs, and the truck is standing still for all of them while the queue builds behind it and spills onto the road. None of those five jobs actually needs to happen AT the barrier. Move them earlier — onto the driver's own phone, before they arrive — and the gate stops being a full stop. A QR gate-pass lets the driver pre-register and self check-in: no app to download, booking and registration already matched, a live status page showing their ETA and queue position. At the barrier, your gate team does one thing: scan, and approve in a tap. The check-in doesn't get faster. It moves off the critical path entirely. That's the difference between a gate that meters your whole yard's throughput and one that just waves a prepared arrival through. What's the longest gate queue you've seen back onto a public road? 👇

Most "dock capacity problems" are actually 9am problems. Here's the pattern we see when we model a yard: total daily volume fits comfortably. Hourly volume doesn't — because trucks don't arrive evenly. They arrive wherever the booking calendar let them. And every carrier clicks the same thing: first thing. So the gate queues at 9, the crew drowns until noon, and by mid-afternoon the same docks sit idle. Then someone writes the business case for more doors or more people — to solve a peak that scheduling created. The fix isn't more capacity. It's capacity-aware booking. Smart Slots scores each requested slot against hourly dock and labour availability and nudges arrivals into the gaps. Carriers still self-serve — the curve just comes out level. The typical modelled outcome: ~46% lower average gate wait, and more trucks per shift with the same crew. In our benchmark model, that's worth roughly €32k per site, per year — no new doors, no new headcount. Your docks were never the bottleneck. Your arrival curve was. What does your gate look like at 9am versus 2pm? Reply in comments below... #YardManagement #DockScheduling #SupplyChain #OpEx

I've spent years in operations where the inside of the building was measured to two decimals. The twenty metres outside the dock door were a black box. This table is the fix. The footer is the uncomfortable bit: the left column falls out of your WMS automatically. The right column usually has no system of record at all. How many of the right-hand five could your site produce for last week?

Bad KPIs make warehouse and yard teams fail each other. Walk from the pick face to the gatehouse and you cross the widest measurement gap in operations. Inside the building: pick rates to two decimals, cycle counts on a cadence, cost per line in the monthly pack. Outside: "the gate feels busy lately." And here's the mistake teams make when they try to close that gap — they drag warehouse KPIs outside. It fails, because the two operations answer different questions: → Warehouse KPIs measure WORK PER HOUR: how productive is the building? → Dock & yard KPIs measure TIME BETWEEN WORK: how long does work wait? Same site. Different maths. The table below pairs them up: five dimensions — productivity, flow, utilisation, reliability, cost — each measured twice, formulas included. Three worth a highlight: 🚛 Truck turnaround time is the yard's pick rate — and the number carriers quietly price into next year's rates. 🚪 Dock utilisation only means something if you count ACTIVE hours. A trailer sitting idle on a door isn't utilisation; it's blockage. ⏱️ On-time arrival % is the honesty test — it tells you whether your schedule is real, or fiction by 09:30. The footer of the table is the whole story: the left column falls out of your WMS automatically. The right column usually has no system of record — which is why the yard "feels" busy instead of being KNOWN busy. Save the table for your next ops review. Honest audit: how many of the right-hand five could you produce for last week — without a spreadsheet safari? 👇 #WarehouseOperations #YardManagement #KPIs #SupplyChain #Logistics