Insights

Most freight writing is produced for people who are about to buy software. This section is written for the person who has to run the operation on Monday whether or not anything is bought: the planner rebuilding a sequence after a customer moves a window, the billing clerk holding an invoice line nobody recognises, the operations manager deciding whether a lane is worth keeping. Two articles are published here, and the cards above are both of them. That is a small library and it will grow slowly, because the standard described below costs more per article than the writing does: a source for every figure about the world, fetched and checked against the live page before anything ships. A section of thin posts would rank for a while and would be worth nothing to the person it claims to be written for. If what you want today is help choosing software rather than help running the operation, that work sits in the software comparison pages instead, written to the same standard for a reader who is buying. What follows is what these articles are for, how they are written, and where the writing stops.

What this section covers

The scope is land-based freight — the movement of goods by road between a shipper, a network of facilities and a receiver — and the systems that plan, track and settle it. Inside that boundary the subjects repeat, because the problems do: building a route out of real constraints rather than a spreadsheet, running the middle leg between facilities, executing the last leg to a door with a signature that has to hold up, taking goods back the other way, and turning all of it into an invoice and a carrier payment that agree with each other.

Each article owns one question and answers that one. A question about what a word means belongs in the logistics and supply chain glossary, not here — a term such as detention on a delayed trailer is defined once, in one place, and every article links to it rather than re-explaining it in a paragraph of its own. A question about what the product does belongs on its module page in the platform, which is written as a specification rather than as prose. This section is the third thing: the reasoning between the definition and the feature, which is the part a vendor site normally leaves out because it is the part that takes work.

How these articles are written

Every article compiles from one Markdown file through the same build as this page, and the build refuses to publish several things that are ordinary elsewhere. A number without a source in the same sentence is one of them: every figure about the world carries a citation to the organisation that produced it, that citation is fetched and checked against the live source before the article ships, and the check is re-run on a schedule so that a figure quietly withdrawn by its publisher stops being quoted here. A statistic about Shyftbase itself is held to a stricter rule again — it ships only if the business has confirmed it in writing, which is why these pages carry far fewer first-party numbers than a vendor blog usually does.

The register is the second half of it. The phrases that sound like evidence while naming none of it — the ones that hang a percentage on unnamed studies, on unnamed industry data or on unnamed experts — are listed in the build and fail it. So are the adjectives that survive deletion: if a sentence is still true and still specific once the adjective is removed, the adjective was decoration. What is left has to earn its place by being specific: the sequence of events, the document that records them, the field somebody fills in, the arithmetic with its assumptions written down so a reader can substitute their own numbers. An article that could have been assembled from three competitor blog posts in an hour is cut rather than expanded, and a section that carries no mechanism, no calculation, no decision rule and no failure mode is deleted rather than padded to length.

Attribution is organisational and stated plainly: these articles are written and reviewed by the Shyftbase editorial team, and drafting is assisted by AI with a human checking every claim against its source before publication. Nobody's invented headshot appears on this site, and no article carries a byline belonging to a person who does not exist.

What this does not do

This section is not documentation and it is not a substitute for advice about your own operation. The articles describe how the work is generally structured and where the money usually leaks; they cannot tell you whether a specific lane, contract or tariff is worth keeping, because that answer depends on rates, volumes and commitments that are not on this website. Where an article works through arithmetic, the assumptions are printed beside it precisely so that you can replace them — the conclusion belongs to the assumptions, not to us.

Nor does it cover freight this company does not run. Air, ocean, port drayage beyond the terminal gate and customs brokerage are all outside the boundary, and an article that wandered into them would be repeating other people's material rather than reporting anything. Regulated cold chain, pharmaceutical chain of custody and hazardous materials are treated the same way: they are real disciplines with real rules, and a general logistics article that gestures at them does more harm than silence. Finally, nothing here is a product announcement. When an article describes a capability, it links to the module page that specifies it and the specification is what is binding.