Before you send anything to the editorial desk, here is how we read a submission and where the lines sit. These are working definitions, not legal language, and they apply to every pitch, calendar entry and partner request that lands in the inbox.
A build story is a documented car
We mean a specific chassis, owned or crewed by the person writing, with sessions behind it. Photos from the garage, a dyno sheet, an alignment printout or a set of lap notes all count. A render, a wish list or a car you saw at a show does not.
Numbers need a source
Power figures, lap times, corner weights and tyre pressures are only useful when we know where they came from: which dyno, which circuit, which day, which compound. If a number came off a phone app, say so. We will still read it, we just label it correctly.
Calendar entries are club-level events
Club races, drag meets, rally stages and track days run by regional motorsport clubs fit the listings. Invite-only test days and manufacturer launches generally do not, unless a club member is competing and can send notes afterwards.
Partner placements stay editorial
Workshops, fabricators and parts suppliers can appear in build diaries, technical explainers and event coverage. What we will not do is hand over a page to a sales pitch, hide a paid placement inside a race report, or let a supplier approve copy before it runs.
The weekly dispatch is one email
It collects what went up that week: build diaries, explainers, calendar additions and reader lap notes. It is not a daily feed, and we do not sell the list or pass addresses to partners. Unsubscribing takes one click and works immediately.
What we cannot promise
Publication, response times and placement dates are decided case by case, in conversation. Nothing on this page is an offer, a rate or a commitment to run your material. If a submission does not fit, we will tell you why rather than leave it sitting.