About this site

Published 1 September 2026

Editorial sites about technology purchases should say plainly who pays for them. Here is who we are and what we will not do.

Event Tech Notes is an independent editorial project published by Event Tech Notes. It exists because the practical mechanics of event technology, what the systems actually do, how the contracts actually read, what actually fails at 8 a.m. on day one, are mostly documented in vendor marketing, which has other priorities.

What this site is

A set of working notes for people who choose and run technology for in-person and hybrid events: corporate planners, association staff, agency producers, and the operations people who inherit whatever got signed. The notes cover the whole stack, from registration through AV to post-event reporting, and they try to be useful at the moment decisions get made, which is usually before a contract signature.

The method is consistent across pages. Describe the mechanism, not the brochure. Name what goes wrong and why. Tell you what to check, in the demo or in the contract, while you still have leverage. Where a real authority exists, a regulator, a standards body, we link to the primary document. Where a number depends on your event, we say what drives the number and tell you to get it from the vendor in writing, because a price printed on an editorial page is stale the day it is published and misleading thereafter.

What this site does not do

No sponsorship. No vendor pays for coverage, placement, or mention.
No paid placement. Nothing on this site is an advertisement, labeled or otherwise.
No commissions. There are no affiliate links and no referral arrangements with any vendor. If we name a product or a company, it is because a durable, uncontroversial fact about it is useful to you, and we gain nothing either way.
No lead generation. We do not collect your details to sell to vendors, which, given the subject matter of our data and privacy page, would be a little rich.

We name specific vendors rarely and categories often. This is deliberate. Products change monthly; the mechanisms by which they succeed, fail, and lock you in change barely at all. A page about mechanisms stays true; a page ranking this year's platforms is wrong by next spring and nobody comes back to fix it.

What this site is not

This site has no connection to any publication previously operated on this domain. Domains change hands; if you arrived here expecting an earlier site by a different publisher, that publication is unrelated to this one, and nothing here should be read as its continuation or endorsement.

We are also not consultants, brokers, or resellers. We do not run procurements, take briefs from vendors, or match organizers with platforms. The site's only output is the writing on it.

Corrections and contact

We prefer being corrected to being wrong. If a page misstates a mechanism, cites something that has changed, or links to a document that has moved, tell us and we will fix it. The same address works for suggestions: if there is a part of the event-tech machine you wish were documented with this site's approach, say so.

Reach the editor at editor@eventtechguide.com. We read everything. Vendor pitches for coverage will be read too, and then declined, for the reasons three paragraphs up.

How to use these notes

Start with the overview, which maps the stack and points to where your current decision lives. If a contract is on your desk, the buying guide and the RFP questions are the pages built for that hour. The rest will still be here after you sign, which is traditionally when people discover why they should have read it first.