XRHQ

Submission Guide

XRHQ is a curated library of real-world VR, AR, and spatial computing deployments. This guide will help you submit a case study that gets approved quickly.

What belongs on XRHQ

XRHQ catalogues organizational 3D and spatial deployments — who deployed what, where, and to what effect. A project is in scope when all four of these hold.

Immersion is not the gate — it is a descriptor recorded on a spectrum. A flat panel is fine. Vendor language ("immersive", "hologram", "metaverse", "XR-ready") is never the test.

1. Genuine 3D / spatial content

A real-time 3D scene, spatial model, or immersive media.

Not 2D dressed up: a BI dashboard with a 3D chart, slides, plain video, a 2D web app, maps and documents all fail this floor.

2. Organizational / non-consumer

Deployed by a company, public body, or institution.

Not a consumer product or self-directed play.

3. Serves a defined objective

Training, operations, design, marketing, visitor experience, therapy, wayfinding, and so on.

4. A deployment, not a product

A deployed instance solving that objective in a real setting.

Not a vendor's tool, SaaS, platform, or capability demo.

A deployment, not a product

This is the one that decides most cases. We are not a vendor directory — we record what an organization did with a technology, not what a technology can do.

In scope
Brand X deployed Threekit and cut returns 18%
Out of scope
Threekit, the configurator product
In scope
LaGuardia deployed a Proto concierge for wayfinding
Out of scope
Proto sells hologram displays

Commonly out of scope

  • Consumer or hobbyist projects — though a brand's activation inside one is organizational marketing, so that is in
  • Vendor product listings with no deployed instance
  • Anything purely 2D — dashboards, videowalls, signage, control rooms, interactive whiteboards — regardless of screen size

When genuinely unsure, an honest skip beats a forced fit. Do not stretch a flat-panel 2D deployment into an experience type to make it fit — a moderator rejecting it downstream costs more than your skipping it.

Writing a good entry

Once a project is in scope, these are what separate a strong entry from a thin one.

Write a neutral case study

The best entries read like factual project reports, not marketing copy. Describe what was built, who it was for, and what outcomes were observed. Avoid superlatives and promotional language. Let the work speak for itself.

Focus on facts, context, and outcomes rather than selling.

Check existing projects first

Before submitting, search XRHQ to see if the deployment is already listed. If it is, you can suggest edits to the existing entry instead of creating a new one. Multiple entries about the same deployment are merged during moderation.

Search the platform to make sure the project is not already listed.

Provide sufficient detail

A complete submission helps us review it faster. Fill in the required fields listed below, then add as much as you can across each tab — hardware, software, outcomes, and sources all make an entry more useful to the people who read it.

Complete all required fields and fill in as much detail as you can.

Required fields

Your submission must include at least these fields to be reviewed.

  • Title
  • Industry
  • At least one location (with country)
  • At least one experience type

How it works

1

Submit

Fill in the form with your project details — the narrative, taxonomy, hardware, software, and sources.

2

Review

Our moderation team reads every submission. We may edit it, ask you for more detail, publish part of it, or decline it. We will email you the outcome.

3

Published

Once approved, your project goes live on XRHQ and becomes part of the global evidence base for immersive technology.

What happens to your submission

Submitting grants XRHQ a licence to publish what you send. The short version is below; the submission terms are what actually applies, and you accept them each time you submit.

Published under CC BY 4.0

You keep the copyright in what you write. You give us permission to publish and edit it, and to let anyone else reuse it under Creative Commons Attribution 4.0 — including commercially. Images and video you upload are shown with your permission but are not placed under that licence.

Credit goes to XRHQ

Your entry is credited to your XRHQ profile on the site. But when other people reuse the content under CC BY, the name they must credit is XRHQ, not you individually. Tell us if you would rather be credited differently, or not at all.

The licence cannot be recalled

Ask us and we will take your submission off XRHQ. The permission you gave does not end, though — anyone who already received the content under CC BY keeps that licence. Removal changes what XRHQ shows; it cannot recall a licence already circulating.

Ready to submit?

Help build the world's most comprehensive library of real-world immersive technology deployments.