User Manual
How to read DemandIntel
DemandIntel is built as a public live hub plus public workspaces. This guide explains what each product is for, how to read the shared signal language, and how Live, Flow, Hospitality, and Inbound fit together.
1. Public DemandIntel homepage
The public homepage is the fast-answer layer. It is built for quick city checks: whether Singapore feels smooth, busy, or painful right now, and what is likely driving that pressure across traffic, airport movement, cruise activity, and event pull.
2. Flow
Flow is the movement-intelligence workspace for near-term direction. It helps users read where pressure is now, where it may shift next, what friction can bend the pattern, and how activity, traffic, weather, and timing fit together.
3. Hospitality
Hospitality is the forward-looking workspace for hotels, serviced apartments, retail, F&B businesses, and revenue-facing teams. It is designed to show demand build, compression signals, calendar watch days, and the commercial pressure likely to matter over the next several days.
4. Inbound
Inbound is the scenario and same-day incoming-build workspace. It is used when a directional estimate is more useful than a live city snapshot, especially around flights, cruises, visitor pressure, and broader arrival-linked demand patterns.
5. Live, modelled, and reference layers
Across the public hub and the workspaces, DemandIntel mixes three kinds of inputs. Live layers come directly from active feeds when available. Modelled layers turn multiple inputs into a directional estimate. Reference layers give useful context, but are not meant to be treated as a live operational trigger.
6. Activity, friction, and timing language
DemandIntel uses simple decision wording on purpose. Activity describes how busy an area feels. Friction describes what can slow, redirect, or separate movement. Timing labels such as Now, Watch next, or Next block show whether the current pattern is holding or a stronger window may form shortly after.
7. Pulse, score help, and plain-English guidance
Pulse is the quick explainer layer. It summarizes what the current situation means in one human-readable note. Score explanations such as 70/100 are there to show that the system blends activity, friction, alerts, timing, and access context instead of relying on one signal alone.
8. Source freshness and status
Live data status panels explain whether a source is current, delayed, or temporarily unavailable. This matters because some answers are based on active feed timing, while others are based on more stable modelled or reference layers.
9. About, Short Reads, Privacy, and Contact
The About page explains the product family. Singapore Short Reads is the public editorial layer for explaining what city signals mean. Privacy covers site data handling, and Contact is the main path for bad data, partnerships, requests, or commercial enquiries.
Need help or spotted something off?
If you spot bad data, want a new zone tracked, notice timing that looks wrong, or want to discuss partnerships, ads, or integrations, contact [email protected].