Skip to content

Know what matters across your business.

When performance changes, the explanation rarely lives in one report. HQ helps teams frame an operating question, inspect related evidence and review the next decision.

Ri’SERVE’s Operating Intelligence application.

SIGNAL → EVIDENCE → OWNER REVIEW
Selected signal
operating question
HQ investigation
Source evidence
source evidence
HQ investigation
HQ investigation
proposal for reviewPossible; subject to review
Owner review
An operating question connects source evidence to a proposal for a named owner.
Read diagram details
  • Selected signal: Selected location
  • HQ investigation: Context to inspect
  • Source evidence: References retained
  • Owner review: Decision stays here
  • Selected signal connects to HQ investigation: operating question
  • Source evidence connects to HQ investigation: source evidence
  • HQ investigation connects to Owner review: proposal for review (possible, subject to review)

A change at one outlet.
Where would you look next?

Imagine repeat visits changing at Outlet A. HQ’s investigation model connects the question to comparable locations, surrounding evidence and a named reviewer.

Guided operating example · Outlet A

Four steps, at your pace

HQ / MULTI-OUTLET JOURNEY
Feedback + visits
observed at
Outlet A
A location signal leads to comparison, evidence and owner review.
Read diagram details
  • Outlet A: Repeat-visit signal
  • Feedback + visits: Source references
  • Feedback + visits connects to Outlet A: observed at

Step 1 of 4

Notice one outlet exception

A change in repeat visits starts an investigation at Outlet A. Inspect its period, location and underlying visit records.

What to check
Example: Outlet A · repeat-visit signal · source period to confirm.
What this establishes
Keep the signal attached to a named location.

Have an operating question of your own?

Book a walkthrough

Trace a supply exception beyond the warehouse.

Location performance and supply-chain exceptions need different evidence. HQ’s application model is horizontal; the operating context is specific.

EXPLAINER · 4 STEPS

Skip explainer
HQ / SOURCE-TO-SALE JOURNEY
One exception, one traceable starting point.
Source / typed relationship Possible / requires review

From a batch exception to an approval boundary.

  1. STEP 01

    Identify the delayed batch

    Start with a batch exception. Keep the batch identity explicit so later relationships can be checked against the same record.

    Batch B-17

    Schedule delay

    One exception, one traceable starting point.

    Read diagram details
    • Batch B-17: Schedule delay

    Evidence to inspectBatch B-17 · schedule exception · source period.

  2. STEP 02

    Connect inventory and order evidence

    A linked order is potentially exposed to the delay. The relationship warrants investigation; it does not prove that delivery will be missed.

    ERP / MES record
    source reference
    Batch B-17
    Batch B-17
    allocated to
    Warehouse
    Warehouse
    may affectPossible; subject to review
    Linked orders
    Shipment
    linked delivery
    Linked orders

    Distinguish a known link from a possible impact.

    Read diagram details
    • Batch B-17: Schedule delay
    • ERP / MES record: Source + timestamp
    • Warehouse: Stock / allocation
    • Shipment: Delivery relationship
    • Linked orders: Potential exposure
    • ERP / MES record connects to Batch B-17: source reference
    • Batch B-17 connects to Warehouse: allocated to
    • Warehouse connects to Linked orders: may affect (possible, subject to review)
    • Shipment connects to Linked orders: linked delivery

    Evidence to inspectSolid: source relationship. Dashed: possible downstream impact.

  3. STEP 03

    Compare response options

    Compare replenishment, partial allocation and rescheduling against the exposed orders. Inspect available stock, lead times and delivery commitments before selecting an option.

    Batch B-17
    allocated to
    Warehouse
    Warehouse
    may affectPossible; subject to review
    Linked orders
    Linked orders
    proposed responsePossible; subject to review
    Decision owner

    Each option needs evidence about feasibility and timing.

    Read diagram details
    • Batch B-17: Schedule delay
    • Warehouse: Stock / allocation
    • Linked orders: Potential exposure
    • Decision owner: Review required
    • Batch B-17 connects to Warehouse: allocated to
    • Warehouse connects to Linked orders: may affect (possible, subject to review)
    • Linked orders connects to Decision owner: proposed response (possible, subject to review)

    Evidence to inspectAvailable stock, replacement lead time and order commitments.

  4. STEP 04

    Record the owner’s review

    The operations owner reviews the preferred option, its evidence and unresolved questions, then decides which next step to take forward.

    Batch B-17
    allocated to
    Warehouse
    Warehouse
    may affectPossible; subject to review
    Linked orders
    Shipment
    options for reviewPossible; subject to review
    Decision owner

    A review decision names an owner and a next step.

    Read diagram details
    • Batch B-17: Schedule delay
    • Warehouse: Stock / allocation
    • Linked orders: Potential exposure
    • Shipment: Delivery relationship
    • Decision owner: Review required
    • Batch B-17 connects to Warehouse: allocated to
    • Warehouse connects to Linked orders: may affect (possible, subject to review)
    • Shipment connects to Decision owner: options for review (possible, subject to review)

    Evidence to inspectReviewer, selected option, remaining questions and follow-up date.

Why are similar locations diverging?

Review comparable periods, service mix, repeat visits and staffing context. Differences suggest questions to investigate, not an automatic explanation.

Explore the multi-location example

What could a batch exception affect?

Trace supplier records, stock movements and downstream order references to identify the evidence an operations owner needs.

Explore Source-to-Sale context

Start with one
operational problem.

The HQ Value Sprint

A scoped evaluation of how HQ could help your team investigate one measurable operating challenge. Begin with discovery, then agree the evidence, capabilities and evaluation criteria in writing.

  1. Choose one question

    Agree the operating problem, the decision owner and what a useful evaluation would establish.

  2. Check the evidence

    Review candidate records, definitions, access permissions and integration feasibility together.

  3. Evaluate the agreed scope

    Inspect the agreed capabilities against that question. Keep data gaps and limitations visible.

  4. Review the findings

    Review written findings, unresolved gaps and an expand or no-go recommendation against the agreed criteria.

What we scope together

Candidate inputs
Relevant records or exports, location definitions, source periods and an agreed access route.
Your team
An accountable sponsor, a source-system contact and authorized access to the agreed data.
Written deliverables
A question and success criteria, a feasibility assessment, evaluation findings and a next-step recommendation, as agreed in the proposal.

Agree the work before it begins.

Set the fees, duration, sources, refresh needs and responsibilities in writing, alongside the question and success criteria.

Scoped proposal following discovery.

Discuss an HQ Value Sprint

Scope the evidence before the connection.

Start with the records you already have.

Transaction history, location definitions, staffing context and authorized feedback may help frame an investigation. The question determines the useful evidence.

Assess the connection method, field coverage, mapping and refresh cadence for each source with its technical owner.

Review data readinessRead common data questions

The application is horizontal. The context is specific.

Motif is the Graph Compiler foundation. Domain packs supply business meaning; HQ is the application for working with that context.

THREE-PART MODEL / MOTIF
Source record
identifies
Business identity
Business identity
domain semantics
Selected context
Sources, domain meaning and application context form a shared operating picture.
Read diagram details
  • Source record: ERP / CRM / POS
  • Business identity: References linked
  • Selected context: Meaning + evidence
  • Source record connects to Business identity: identifies
  • Business identity connects to Selected context: domain semantics

Source identities, typed relationships and evidence connect the compiler foundation to an application’s operating question.

Read the Motif overviewExplore domain packsReview HQ pricing options

Make the deployment boundaries explicit.

Production and staging hosting

HQ production and staging are hosted in AWS us-east-1 (Northern Virginia, United States).

Agree the boundaries before rollout.

Review source permissions, data handling, operating responsibilities and the approval boundary for any supported action.

Review security and deployment

Bring one question. Find a useful first scope.

Tell us what changed, which systems hold the records and who owns the next decision. Bring one question to a walkthrough, or send your requirements for an initial reply.