Manifest Sheet Bays
The bay where each load declares itself before it reaches the ramp. Fields, stamps and review marks are laid out so a sheet can be read at a glance in poor light.
Sheet railComputer integrated systems design for freight yards
A yard that thinks
like a system,
RAMP
Hrs Carrier Ltd. builds the quiet machinery behind a working yard: manifest sheets that talk to each other, ramp logs that record every crossing, and driver notes that land in the right place. From our base at 40 Alabaster Dr, Brampton - L6V 4G7, Canada (CA), we design integrated dispatch systems for carriers who cannot afford a gap between the gate and the dock. See how each run works and you will find a pattern you can recognise on your own apron within a week.
Book a yard booking windowWhat the yard actually needs
Six runs, one board, no loose paper
Most freight operations are not short of software. They are short of agreement about where a fact lives. A trailer arrival is written on a manifest, noted in a ramp log, mentioned in a driver note and then argued about at the dispatch window. Hrs Carrier Ltd. was founded to remove that argument by designing the yard as one system rather than five separate habits.
Our work sits inside computer integrated systems design: we map the physical routes people take across a dock, then build the digital runs that mirror them. The result is a setup where a driver who walks the apron once can find every record connected to the load, and a planner who opens a screen can see the same truth without calling the yard.
The board comes first
Every engagement starts with the manifest board. We ask what a sheet has to answer before a vehicle is allowed on the ramp, what it has to answer while the vehicle is on the tail lift, and what it has to answer after the gate closes. Those three questions shape the fields, the review rounds and the escalation rules that follow. Only then do we talk about interfaces, database engines or the shape of a screen.
This order matters because a yard is a physical place with real constraints. A ramp has limited width, a dock light throws a fixed circle of usable light, and a chock sits against a wheel that is already rolling. Software that ignores these facts will be worked around within a fortnight, and workarounds are where errors are born.
The people come second
We spend time with the dispatcher, the yard marshaller, the driver and the gate clerk because each one reads the same load differently. The dispatcher wants a forecast; the marshaller wants a position; the driver wants an instruction that fits in one breath; the gate clerk wants proof. Our systems express one underlying record in four voices so that nobody has to translate on the fly.
Integration, in our reading, is not a matter of connecting more applications. It is a matter of reducing the number of times a fact has to be retyped, restated or re-argued. When that number falls, throughput rises without anybody being asked to move faster.
A yard is not a queue of trucks. It is a sequence of decisions, and every decision needs a place to be written down.
Built for the Brampton apron
Our designs are calibrated to mid-sized yards with tight aprons, shared docks and a mix of own-fleet and partner vehicles. The 40 Alabaster Dr base in Brampton is where we prototype the desk layout, the lamp arm positions and the board spacing that carry over to client sites. Nothing is proposed until it has survived a week on our own floor.
We also design for the partner side of the business. Subcontracted carriers, overflow yards and seasonal surge capacity all need to read the same board without being granted full access. Role boundaries, review stamps and handover windows are therefore part of the core design, not an afterthought added at the end of a project.
Measured in fewer phone calls
The simplest measure of a well-integrated yard is the number of calls that do not happen. When a ramp log is written at the moment of crossing rather than reconstructed from memory, the morning reconciliation call disappears. When driver notes are captured at the desk nearest the gate, the afternoon query about damage or seal numbers disappears with it.
We report on these quiet savings in plain language, because a yard supervisor should not need to read a dashboard to know whether the system is working. If the apron is calmer, the design is doing its job.
The six runs on the board
Each sheet below is a working run that Hrs Carrier Ltd. installs and tunes for a carrier yard. They are read together, in order, on the same board.
Ramp Log Runs
Every crossing of the dock edge is recorded with a time, a vehicle and a reader. The log is written live, not reconstructed later, which keeps reconciliation short.
Edge recordDriver Note Desks
Notes are captured at the desk beside the gate while the facts are fresh. Short forms, fixed vocabulary and a clear route to the board keep the record usable.
Desk captureDispatch Check Windows
A controlled window where dispatch confirms the load before release. The check is short by design and always leaves a trace on the board.
Release gateLoad Review Rounds
Scheduled rounds that revisit open loads and settle exceptions. Rounds are timed to the shift, not to a calendar reminder.
Round markYard Booking Sittings
Booked sittings where carriers reserve ramp space and a window for loading. Sittings are published on the same board so nothing is promised twice.
Reserve lineHrs Carrier Ltd. opens its yard booking window for the coming week on the same board where every ramp log and manifest sheet already sits, so a carrier can hold a ramp without leaving the record. Hold a ramp window
How an engagement runs
From the first walk to the settled board
We do not arrive with a product to install. We arrive with a method for reading a yard and a set of run patterns that have already been proven. The sequence below is how a typical engagement with Hrs Carrier Ltd. moves from first contact to a board the crew trusts.
Walk
Walk the apron with the people who use it
We spend a shift on the yard, following a load from gate to dock and back out. The route reveals where records are lost, where duplicate entries appear and where a short form would save a minute. Nothing is designed until this walk is finished.
Map
Map the six runs to your existing habits
Each of the six services is matched to a current habit, then tightened. Manifest Sheet Bays replace loose sheets; Ramp Log Runs replace memory; Driver Note Desks replace radio calls that vanish. The mapping is written down so the crew can object to it early.
Build
Build the board and the thin layer beneath it
We build the board first, in the yard, at the spacing it will actually be read from. The software layer is thin and deliberate: capture, validate, publish, review. Anything that cannot be justified by the walk is cut.
Tune
Tune the review rounds and booking sittings
After two weeks we adjust Load Review Rounds to the real rhythm of the shift and set the Yard Booking Sittings to the capacity the apron can honestly hold. This is where the calmer apron becomes visible.
Settle
Settle the board and hand over the routine
The final stage is a written routine that any supervisor can follow without calling us. Dispatch Check Windows are documented, driver notes have a clear desk, and the yard runs on its own record.
Who we work with
Carriers, yards and the people in between
Our clients sit in freight, distribution, cold storage and regional courier work, mostly in Southern Ontario, though the designs travel well. What they share is a dock that has outgrown its paperwork and a crew that has been asked to remember too much.
Regional carriers
Fleets with ten to eighty power units that run a single main yard and one or two satellite aprons. They need a board that travels, so we design records that survive being read on a phone at the gate.
Contract warehouses
Facilities that receive freight from many carriers and must reconcile quickly. Ramp logs and manifest sheets become the shared language between the warehouse crew and the visiting driver.
Partner yards
Overflow and seasonal sites that need to read the same board without full access. Role boundaries and handover windows are built in from the first design meeting.
Owner operators
Independent drivers who want their note to arrive intact rather than be relayed three times. Driver note desks and a simple dispatch window make their day predictable.
Why Hrs Carrier Ltd.
A design practice that lives on a dock
We are a small practice by choice. Every engagement is led by the same people who will walk the apron and tune the board, which keeps the design honest and the handover clean. You will not be passed to a delivery team that has never seen a tail lift.
Integrated by design, not by integration project
Integration projects often begin with a list of systems and end with a list of bridges. We work the other way: the record is designed once, and the systems that touch it are shaped around that record. The result is fewer moving parts and a far shorter path from event to entry.
This approach fits the computer systems design and related services work we are registered for, and it suits the professional services habits of our clients, who want a clear scope and a visible routine rather than an open-ended programme.
Documents that respect the reader
A manifest is read under a dock light at four in the morning. A ramp log is scanned by a supervisor who has three minutes. A driver note is written by someone standing at a desk with gloves on. We design for those conditions, and we test the board against them before a client ever sees it.
If you would like to see the board spacing and the run patterns in person, we can arrange a visit at the 40 Alabaster Dr yard. The details are on the contact page, including the booking hours and the quickest route to the ramp.
Good integration is invisible in the moment and obvious in the quiet. If the apron is calm, the work was done correctly.
Perim.
A ring of small decisions around one record
The six runs are not a product menu. They form a perimeter around a single load record so that every person who touches that load meets the same facts in a form suited to their hands. Manifest Sheet Bays hold the declaration, Ramp Log Runs hold the crossing, Driver Note Desks hold the texture, Dispatch Check Windows hold the release, Load Review Rounds hold the exceptions and Yard Booking Sittings hold the promise. Remove one and the others start to lean on memory, which is where errors enter a yard. For a carrier deciding where to begin, the honest advice is to start with the run that currently causes the most repeat phone calls and let the perimeter close in stages over a few weeks rather than all at once.
Start with one walk of your apron
Tell us where the paperwork breaks down and we will tell you which of the six runs to fix first. No obligation, no pitch deck, just a working conversation.