Intranet: what a small company actually needs it to do
Most intranet projects fail on maintenance, not on features. Deciding who owns each page before launch matters more than which platform you pick.
A modern slavery statement is public, annual and signed by the board. What has to be in it, where it goes, and the sentences that make it worse than saying nothing.
A modern slavery statement is an annual, public account of what a company has done to check that forced labour and human trafficking are not present in its business or its supply chain. It is unusual among compliance documents in being written for strangers: customers, campaigners, journalists and prospective employees read it, and increasingly so do the procurement teams of your larger clients. That audience is why the statement written to satisfy a legal minimum tends to do more harm than good — it is visibly a statement about nothing, published under the company name.
The sentences to delete are the ones that assert an outcome you have not verified. "We have zero tolerance and there is no modern slavery in our supply chain" is a claim about several thousand people you have never met, and it is the line campaigners quote back. "We have assessed tiers one and two, we have not assessed beyond that, and here is what we intend to do next year" is weaker prose and a far stronger document.
Ettex Sites is where the statement should be published: a stable page on your own domain, linked from the homepage, with previous years kept rather than overwritten. That last point is the one most companies get wrong — replacing the file each year destroys exactly the year-on-year comparison that makes the document persuasive. The evidence behind it, the supplier assessments and the audit findings, belongs in your supplier records rather than in the published text. Ettex does not assess supply chains and this is not legal advice; the thresholds, deadlines and registration requirements differ by country and change.
Not legally in most regimes, but larger customers increasingly require one from suppliers of any size as a procurement condition. Many companies below the threshold publish voluntarily for exactly that reason.
Republishing substantially the same text is legal in most places and is the single clearest signal to a reader that nothing happened. If genuinely little changed, say what was reviewed and what the plan is, rather than reprinting.
Finding something is the expected outcome of looking properly, and handling it well is the strongest thing you can report. The wrong instinct is to cut the supplier immediately — that usually harms the workers involved and removes your leverage to fix anything.
Most intranet projects fail on maintenance, not on features. Deciding who owns each page before launch matters more than which platform you pick.
An SPF record lists who may send mail as your domain. Two limits — one record and ten DNS lookups — cause most of the failures.
Hreflang is the tag that stops your German page competing with your English one. It is also the tag most often implemented wrongly — and a broken implementation is worse than none at all.