HQ OS runs as a persistent connection between your operational infrastructure and the HQ backend engine. Confirm that your environment meets the following requirements before proceeding.
Server environment
A server that runs persistently — cloud or on-premise. AWS, Google Cloud, Azure, or equivalent.
Confirmed
Internet connectivity
Stable outbound internet connection. HQ OS communicates with the HQ backend for processing. No inbound ports required.
Confirmed
API access
API access to the operational systems you wish to connect — email, document management, communications platforms.
Confirmed
IT contact
A designated IT administrator or technical contact who will complete the connector configuration and hold the licence key.
Confirmed
What installs on your infrastructure
A lightweight connector — a small, encrypted process that runs on your server, reads from your connected data streams, and sends structured data to the HQ backend for processing. The HQ engine, the governing sequence, and all IP remain in the HQ backend. Nothing sensitive is stored on your infrastructure.
Step 1 of 7
Step 02 of 07
Organisation Profile
Basic organisational identity. HQ OS uses this to calibrate the seven living standards to your specific sector, cultural context, and operational scale.
The person responsible for managing the HQ OS installation
Step 2 of 7
Step 03 of 07
Data Stream Connectors
Select the operational data streams you are connecting to HQ OS. Each connector links that data source to the HQ monitoring layer. Select all that apply to your organisation.
Communications
Email
Internal and external email. Primary source of interpersonal and trust signal moments.
Communications
Messaging platforms
Slack, Teams, or equivalent. Real-time communication signal source.
Documents
Document management
Shared drives, SharePoint, Google Workspace. Policy and document signal source.
Operations
HR systems
HRIS platforms. Hiring, performance, and people-related signal moment detection.
Operations
CRM
Customer relationship data. External interaction and trust signal source.
Operations
Project management
Jira, Asana, or equivalent. Decision and pressure signal moment detection.
Any operational system not listed above
Step 3 of 7
Step 04 of 07
Department Links
Link each department to its primary data stream and set its monitoring priority. HQ OS calibrates detection sensitivity per department based on its function and the standards most likely to activate within it.
Department
Primary data stream
Priority
Step 4 of 7
Step 05 of 07
Alert Routing
Define who receives HQ OS alerts at each level. HQ generates three alert levels — Critical Path, Requires Monitoring, and Guidance Available. Each routes to a designated recipient within your organisation.
Alert level
Primary recipient — role
Secondary recipient — role
Critical Path
Requires Monitoring
Guidance Available
How often HQ OS delivers a consolidated operational summary
Step 5 of 7
Step 06 of 07
Detection Threshold
Set the sensitivity of HQ OS detection across your organisation. A lower threshold catches more signals — producing more alerts. A higher threshold filters to the most significant signal moments only. This can be adjusted at any time from the dashboard.
Standard — balanced detection across all seven living standards.
Focused — critical and high-significance signal moments only. Lower alert volume.
Select up to three standards HQ OS should weight most heavily for your organisation
S1
Sensory Awareness
S2
Intuitive Recognition
S3
Cultural Memory
S4
Adaptability Under Pressure
S5
Creativity from Experience
S6
Physical-Emotional Alignment
The Pre-Read — Always active
The Pre-Read
The Pre-Read fires at every signal moment unconditionally. It cannot be deselected.
Step 6 of 7
Step 07 of 07
Licence & Activation
Select your licence tier and authorise the installation. Your licence key will be generated and your deployment package prepared. The IT administrator installs the connector on your server. HQ OS activates.
Standard
HQ OS Core
All seven standards. All connectors. Real-time detection. Annual licence.
Advanced
HQ OS Full
Core plus divergence analysis, historical pattern tracking, and quarterly calibration.
Enterprise
HQ OS Enterprise
Full plus multi-site deployment, dedicated calibration, and HQ Verify integration.
I confirm that I am authorised to install HQ OS on behalf of this organisation and that the information provided is accurate. I authorise HQ to process operational data from the connected systems under Platform Guidelines G1–G5. I understand that the HQ engine and all IP remain in the HQ backend and are not installed on the organisation's infrastructure.
Step 7 of 7
HQ
Generating licence & preparing deployment
⬡ HQ OS — Licence Issued
Licence key — deliver to IT administrator
Deployment package
HQ OS Connector
Lightweight encrypted connector — installs on your server infrastructure
Configuration file
Pre-configured to your organisation's parameters and connected systems
Installation guide
Step-by-step technical installation instructions for your IT administrator
After installation
01IT administrator installs the HQ OS connector on your server using the installation guide. The connector requires the licence key to activate — without it, it does not run.
02Connector connects to your selected data streams using the pre-configured API settings. Each department link activates according to the priority you set.
03HQ OS activates. The engine begins monitoring immediately. The first signal moment detection typically occurs within 24 hours of installation in an active operational environment.
04Access your HQ OS dashboard to monitor engine status, view signal moment detections, and track standards activation across your organisation in real time.
Organisation
HQ OS — Engine Running
0
Signal moments detected today
0
Critical path alerts
0
Under monitoring
0
Guidance issued
Live signal moment feed
Live
Standards activation
The Pre-Read — Last pre-signal
The Pre-Read
Awaiting first detection
The Pre-Read fires before every signal moment assessment. Pre-signal will appear here once the first signal moment is detected.
Department status
Erase File History →
HQ OS · Alert Assessment
SITUATION CONTEXT
DEPARTMENT IN SCOPE (optional)
Threshold:
HQ does not store what you submit. It does not store what it returns to you. Your results live on your systems, not ours.
About HQ
What is HQ?+
HQ — Human Quotient is a technology platform that assesses biological and behavioural alignment within organisations. It exists because AI's advancement into organisational operations has outpaced the human standard required to govern what AI produces. HQ is that standard — built to operate at the point where human judgment and AI output meet. It runs through three portals — HQ Select, HQ Verify, and HQ OS — each serving a different organisational need. There is no human consultant involved at any point.
Is there a human involved at any point?+
No. HQ is fully automated across all three portals. No consultant, analyst, or operator participates in any assessment, read, or monitoring function. The platform processes your submission and returns the result independently.
How does HQ produce its results?+
HQ processes each submission through its assessment engine and returns a determination. The result tells you what was found and, where relevant, what the recommended course of action is. The method behind the assessment is proprietary and is not disclosed.
HQ OS
What is HQ OS?+
HQ OS installs across your operational infrastructure and runs without stopping. It monitors continuously, detects when something requires attention, classifies it by urgency, and routes the alert to the right person in your organisation. Where AI is embedded in your operations, HQ OS maintains the human standard against which AI output is measured — continuously, not periodically. It covers the full organisation. It cannot be scoped to a single department.
What are the three alert levels?+
Critical — requires immediate attention, routed directly to the designated recipient without delay. Monitor — flagged for review within your defined review cycle. Guidance available — noted and logged, no immediate action required, guidance is appended to the alert.
Is there an HQ mark for HQ OS?+
Yes. Organisations operating HQ OS receive a mark that reflects continuous operational monitoring. It is included in the OS subscription and does not carry a separate licence fee.
What is the three-month pilot?+
New HQ OS clients begin with a three-month commitment period. This gives the organisation sufficient time to experience continuous monitoring and gives HQ OS time to calibrate to your operational environment. At the end of the pilot, the arrangement converts to your chosen billing cycle.
Data & Security
Where does my submitted content go?+
Your submission is transmitted over an encrypted channel to HQ's processing engine. The engine assesses it and returns the result to you. HQ does not store submission content. Nothing from what you submitted is retained after the result is delivered.
Who has access to my submission?+
No one. The submission is processed by the engine automatically. No human at HQ reads, reviews, or accesses your submission content at any point.
What security measures protect my submission?+
All transmissions between your systems and HQ's processing engine are encrypted end-to-end. Each transaction uses a unique, time-limited route that expires immediately after use. No fixed endpoint exists that could be identified or probed.
Getting Started
How do I register?+
Select HQ OS from the main page. Complete the registration form with your organisation name, sector, size by headcount, operational headcount by department, and contact details. Access is confirmed within one business day following verification of your registration details.
I have registered. What happens next?+
You will receive your access credentials, integration credentials, and a link to the HQ OS onboarding tutorial. Read the tutorial before beginning setup. Follow it in order — no step may be skipped.
Setup & Monitoring
How is HQ OS set up?+
Following registration and billing confirmation, you will receive the HQ OS onboarding tutorial and your integration credentials. The tutorial covers every step of the setup process in order. Setup is completed by following the tutorial exactly. No step may be skipped. Contact support only if a specific step in the tutorial fails to produce the stated outcome.
What does the HQ OS tutorial cover?+
The tutorial covers: connecting HQ OS to your operational environment using your integration credentials, setting your monitoring objectives and thresholds at deployment, defining alert routing — who in your organisation receives which alert level — and verifying that the connection is live and active. Follow the tutorial in order. Steps completed out of sequence will not produce the stated outcomes.
How does the monitoring work?+
Once connected, HQ OS runs continuously across the data streams and operational layers you defined at setup. It detects, classifies, and routes. You do not need to initiate or request a monitoring cycle — it runs without instruction.
Who receives the alerts?+
Alerts are routed to the recipient you designated at setup. This is defined per alert level — a critical alert may go to the department head, a monitor alert to the HQ desk, and guidance available to a defined review log. Routing is set at deployment and can be updated through your account settings.
Can I adjust my monitoring parameters after setup?+
Yes. Objectives, thresholds, and alert routing can be updated through your account settings at any time. Changes take effect from the next monitoring cycle. The calibration cycle — where HQ OS refines its thresholds based on your organisation's evolving patterns — runs automatically and does not require your input.
What happens at the end of the three-month pilot?+
At the end of the pilot period, your account is notified and you are prompted to confirm your billing arrangement going forward. If no action is taken within the stated window, the subscription continues on the same billing cycle automatically. If you wish to cancel, you must do so before the pilot period closes.
Billing
How does billing work for HQ OS?+
HQ OS is billed as a monthly retainer based on the size of your organisation by headcount. Annual billing is available and includes two months at no charge. A three-month conditional pilot period applies before a pure month-to-month arrangement is available.
My organisation has grown. Does my tier still apply?+
HQ OS billing is based on headcount at registration. If your organisation has grown beyond your current tier, log in to your billing account and update your headcount. A billing adjustment notification is generated before the change is confirmed. Monitoring continuity is not lost during the transition.
How do I cancel?+
Cancellation is managed through your account Billing settings. Select Cancel Subscription and confirm. If you are in the three-month pilot period, you must cancel before the pilot period closes. Cancellation takes effect at the end of your current billing period.
File History
This action permanently erases all assessment records stored in this browser for the current organisation. Records cannot be recovered or reproduced. This action cannot be undone.
HQ OS — Troubleshooting
No alerts are arriving and I am not sure whether monitoring is running.+
Check the connection status indicator in your HQ OS account dashboard. If the status shows inactive, the most common cause is a change to your operational environment after setup — a system update, a credential change, or a firewall rule. Return to the tutorial, specifically the connection verification step, and run it again. If the connection cannot be restored, contact support with your account reference and a description of any changes made to your environment since setup.
The connection shows active but alerts are not arriving.+
Check your alert routing settings and confirm that the designated recipient for each alert level is correctly specified and current. Update routing in your account settings if recipient details have changed. If routing is correct, check whether your monitoring thresholds are set too high — if nothing is crossing the threshold, no alert is triggered. This is not a fault. If you believe a threshold crossing occurred and no alert was generated, contact support with your account reference and the date and nature of the expected event.
Alerts are being delivered to the wrong person.+
Each alert level has a designated recipient that can be set independently. Navigate to your account settings, select Alert Routing, and update the relevant recipient. Changes take effect from the next monitoring cycle. If routing changes are not taking effect after 24 hours, contact support with your account reference.
My organisation has grown and I am not sure whether my current tier still applies.+
HQ OS billing is based on headcount at registration. If your organisation has grown beyond your current tier, log in to your billing account and update your headcount. A billing adjustment notification is generated before the change is confirmed. Monitoring continuity is not lost during the transition. The same process applies if your headcount has decreased.
I cannot access my account.+
Confirm that you are using the correct credentials issued at registration. If you have forgotten your credentials, use the credential recovery option on the login page. If recovery does not resolve access, contact support with your organisation name and registered email address.
A step in the tutorial is not producing the stated outcome.+
Re-read the step and confirm that all prior steps were completed in the correct order. Skipping or reordering steps will cause later steps to fail. If all prior steps are confirmed complete and the step still fails, contact support and specify the exact step number, the action taken, and the outcome received.
I want to report a security concern.+
Contact support immediately using the security contact method provided in your onboarding documentation. Do not use the standard support channel for security concerns. Describe what you observed without attempting to investigate or reproduce it.
Question not covered here? This library covers the full scope of HQ OS support. If your matter falls outside it, contact us directly. Our platform operates on a defined service structure — what is offered is what is available.