Editorial team — Hospitality Ops Intel

Hospitality Ops Intel is edited by a small team with operational experience across hotel, resort, and casino operations. The pages below describe how the publication is run.

Who edits this publication

The editorial team is a mix of full-time editors and contracted contributors. Collectively, the team draws on backgrounds that include former general managers at full-service hotels, directors of security at integrated resort properties, casino surveillance leaders with experience in regulated gaming markets (Nevada, New Jersey, tribal compacts), hospitality IT directors who have run PMS migrations, and front-of-house operators who have managed high-occupancy properties through both peak and low-demand cycles.

We do not list named individual editors at article level. Operations editorial often involves current practitioners whose employers would not sanction visible bylines, so the editorial team operates as a single collective voice. Bylines would be misleading; collective attribution is the honest framing.

Editorial review process

Every article passes through two reviews before publication. A factual-accuracy review checks claims against primary sources where available — regulatory text, standards documents, vendor technical documentation, and operator interviews. A separate vendor-bias review flags language that reads as advertorial, recommends a specific vendor without justification, or omits relevant alternatives.

Articles citing specific standards identify the version and section. Where a standard has been revised in a way that materially changes the operational picture, the article notes which revision is reflected and when the article was last reviewed against the current version.

Standards we reference

Articles cite specific standards where they are directly relevant to the operational topic. Across the publication, the standards we draw on most frequently include AHLA Lodging Industry Standards, NFPA 13/72/101 for fire and life safety in commercial properties, PCI DSS for payment-card handling, Nevada Gaming Control Board MICS for casino floor surveillance, and ASHRAE 62.1 for indoor air quality.

We do not present standards as a complete picture of operational reality. Standards establish a floor; operations live above it, shaped by local regulators, insurer requirements, and the judgment of practitioners on the ground.

Conflict of interest policy

We do not accept sponsored content, paid placements, or 'editorial partnerships' with vendors. Vendors can pitch topic ideas; they have no influence over whether or how we cover them. No member of the editorial team holds equity in a vendor whose product is covered by name in the publication.

When an editor or contributor has prior employment history with a vendor or operator named in an article, that history is disclosed to a second editor during review, who decides whether the article goes ahead, is reassigned, or requires additional balancing material.

Corrections and reader feedback

Factual errors can be reported to editor@hospitalityopsintel.com with the article URL and the correction. Corrections are noted at the bottom of the affected article with the date the correction was applied.

We welcome pitches from working practitioners who want to contribute. The contributor model is described above; for pitch inquiries the editorial address is the same.