Written for manufacturers, not for IT press

These demonstrate the voice and the treatment. Every one is a topic, not a report of a specific event: evergreen by design, because a plant manager reading this in eighteen months should still get something out of it.

THREATS HITTING MANUFACTURERS · 4 min · Community

The fake purchase order is still the most effective attack on a plant

Sample It arrives as an attachment, from a name that looks like a customer you already sell to, on a day when order entry is busy. It works because opening a PO is somebody's job, not a lapse in judgement. Here's the shape of it, the two checks that catch nearly all of them, and why blaming the person who opened it guarantees a repeat.

COMPLIANCE & CUSTOMER REQUIREMENTS · 6 min · Community

What your customer's security questionnaire is really asking

Sample Most supplier questionnaires ask forty-odd questions in language borrowed from a framework nobody in your building has read. Behind the wording, they're asking six things. We go through what each block is actually checking, and how to write "no, and here's our plan" in a way that keeps the contract.

DOWNTIME & CONTINUITY · 5 min · Member

Your backup is not tested until something has been restored from it

Sample A green tick in a backup console means the job ran. It does not mean the data is usable, that the restore fits inside your shipping window, or that anyone in the building knows the order to bring systems back in. The gap between "backed up" and "recoverable" is where most bad fortnights come from.

TECHNOLOGY WORTH THE MONEY · 4 min · Community

Three IT purchases that pay for themselves in a plant, and two that don't

Sample Not everything sold to manufacturers is worth buying, and some of it is sold by people like us. We name what consistently earns its cost on a plant floor, what almost never does, and the one purchase that depends entirely on whether you run more than one site.

THREATS HITTING MANUFACTURERS · 5 min · Member

Why the supplier bank-detail change always lands near month-end

Sample It's not a coincidence. The request arrives when AP is busiest, the approver is least available and everyone wants the run closed. One control stops it, it costs nothing, and it works even when everything else fails: call the number you already had on file.

COMPLIANCE & CUSTOMER REQUIREMENTS · 7 min · Member

NIST is not a certificate, and the people asking you for one may not know that

Sample Customers increasingly write "NIST certified" into questionnaires and contracts. No such certification exists for the Cybersecurity Framework. What you can produce is a profile, a plan and an evidence package: and in almost every case, that is what satisfies the person asking.

DOWNTIME & CONTINUITY · 6 min · Community

What the first hour of a ransomware event looks like on a production line

Sample Not the version from a vendor webinar. The version where the ERP is unreachable, product is still moving, the shift supervisor doesn't know whether to keep running, and the person who knows the backup password is on holiday. A timeline, and the four decisions that determine how the fortnight goes.

TECHNOLOGY WORTH THE MONEY · 5 min · Member

Multi-factor authentication on a plant floor, without stopping the line

Sample The objection is real: gloved hands, shared terminals, no personal phones on the floor, and a login that has to take four seconds. There are workable answers, badge sign-on, PINs, hardware keys, scoped exemptions with compensating controls, and there are answers that will get quietly bypassed by week two.

Access: Member. Free.

One email a month, written for someone who reads it standing up.

The name: three options

Recommended: The Handover. It does the most work with the least explanation, it's the only one of the three that's genuinely hard to confuse with someone else's product, and the monthly cadence has a natural logic in the name: every month, we hand over what we learned.

Cadence

Monthly. Not weekly, not quarterly.

Weekly is unread by a plant manager and everybody involved knows it. Quarterly never builds a habit, by the third issue nobody remembers subscribing. Monthly matches the rhythm your plant already runs on: the safety committee meeting, the toolbox talk topic, the month-end close. It arrives often enough to be expected and rarely enough to be opened.

Send on the first Tuesday of the month, 07:00 local time to each region, so it's sitting there at shift start rather than lost in a Monday inbox.

Length and time to read

600–750 words. Under four minutes. Hard ceiling. Six segments, none longer than 150 words, every one skippable without losing the thread. If a segment needs more room, it becomes an article on this page and the newsletter links to it.

The fixed six-segment structure

Same six, same order, every issue. Predictability is the feature, readers learn where their bit is.

1. What changed this month: one thing, explained in plain language. Not a roundup.
2. One thing to fix this week: a single concrete action, doable inside an hour, by a named role.
3. From the floor: something an operator told us, anonymised. The bit people read first.
4. Coming up: two or three events, with a link. Short.
5. New in the library: what we published, what it's for, who should grab it.
6. Member perks: one benefit, explained properly, rotating each issue.

Sign-up form (in-page block and footer):

THE HANDOVER One email a month. Under four minutes. Written for a plant, not an inbox. What changed, one thing to fix this week, and something an operator told us.

[ Work email ][ Country ▾ ] [ Get the newsletter, free ]

No card, no sales call, no list sharing. Unsubscribe in one click and we won't chase you.

Double opt-in, on-screen after submitting:

Nearly there, check your email. We've sent a confirmation link to [email]. Click it and you're on the list. Nothing arrives until you do: that's deliberate, so nobody signs you up for something you didn't ask for. Didn't get it? Check the junk folder, then [resend the link]. Still nothing? Your mail filter may be blocking us: ask IT, or whoever does IT, to allow our sending domain.

Confirmation email, subject and body:

Subject: Confirm your Handover subscription

One click and you're on. [ Confirm my subscription ] If you didn't ask for this, ignore this email. Nothing happens and we won't email you again. SafeIT, a Kearns Technology Inc. company

Welcome email, subject and body:

Subject: You're on the list. Here's what to expect.

Thanks for subscribing to The Handover.

What arrives: one email, first Tuesday of the month, under four minutes to read. Six sections, same order every time: what changed, one thing to fix this week, something from the floor, what's coming up, what's new in the library, and one member benefit explained properly.

What doesn't arrive: sales sequences, product announcements, event spam, or anything from anyone we've sold your address to, because we haven't and we won't.

While you wait, three things worth ten minutes:

• The policy pack: sixteen IT policies written for a plant. Adopt them in an afternoon.
• Run a free baseline phishing test: one message, one number, no obligation.
• Book a free assessment: and you keep the report either way.

Reply to this email if you want something specific covered. A real person reads it, and member questions set what we write next.

Unsubscribe page:

You're unsubscribed. Done, immediately. No confirmation step, no "are you sure," no win-back sequence. You won't hear from The Handover again.

Before you go, would you rather just get less? [ Events only ][ New library material only ][ Quarterly instead of monthly ]

Or tell us why, in one line. It genuinely changes what we write. [ Too often · Not relevant to my plant · Too long · I didn't sign up for this · Something else ]

Unsubscribing does not affect your SafeIT membership, your library access or your event seats. Those stay exactly as they were.