Sitework Journal runs work from people on the job: estimators, PMs, supers, specialist contractors, and the engineers who get called when it goes wrong. Bring something specific and checkable.
What earns a yes
- A cost or a schedule that moved, with the takeoff logic or the sequence that moved it, and the region and year it applies to.
- A method or an assembly you have built, including where it underperformed and what you would detail differently next time.
- A failure and its remedy — the kind of thing normally settled quietly and never written up.
- A piece of kit or software you have run through a full job cycle, with what it does badly as well as well.
What gets a no
- A rewrite of something already out there.
- A product launch wearing an article’s clothes. Promotional material has a home here — partner content, labelled — and that is a separate conversation.
- Claims nobody can check. If it carries weight, it gets a source.
- Machine-written drafts sent unread. It shows on the page.
How to pitch
Email editor@siteworkjournal.com. Lead with the point, then what it rests on, then one line on why you are the one writing it. A full draft is welcome, not required. Pitching for a client is fine — say so in the first line and we skip a round of email.
What happens next
We try to come back within five working days either way. Accepted work is edited for accuracy, structure and house style, and you see it before it runs. The byline is yours and we link your site or profile once from the author line. Commercial links do not go into editorial, and we do not take money to publish it.
Worth reading the editorial policy first.