Skip to main content

How to choose the right starting point for Analytics

This guide helps you decide which Ontology data to configure first so you can start using Analytics (and later Agentic) without waiting for every optional entity.

T
Written by Tyrone Marhguy

Prerequisites

Ontology is required. If Ontology is not set up, Analytics and Agentic are not available.

Prefer using the Integrations engine to clean, transform, and load Ontology data. File templates are available if you must load CSVs instead.

Required vs optional

Ontology distinguishes required (minimum to start basic Analytics and Agentic) from optional entities.

  • Start with what your business needs now. If you only need analytics on employees (headcount, salary, status), configure the employee and event data required for that—you are not blocked from starting.

  • Add talent acquisition later. Candidates, applications, requisitions, and related statuses unlock insights such as applications per requisition, hire rates, and time from candidate to employee. Connect that data when talent acquisition becomes a goal.

  • Add pay statements when you need actual spend. Use them when paper salary is not enough and you need real payments out the door for budgeting and workforce planning.

When required entities are configured, Ontology indicates you can start using Analytics / Agentic.

Example starting paths

Employee population analytics first

Typical questions: active headcount, headcount by employee type, average salary by age band or department.

Focus on employee records plus the events (position, status, compensation) that support employment snapshots and those calculations.

Talent acquisition analytics next

Typical questions: applications per requisition, quality vs fill rate, time from candidate to employee, time spent in each application status.

Add candidates, applications, application statuses, requisitions, and requisition statuses, and ensure candidate↔employee linking (candidate ID or email).

Compensation reality checks

Typical questions: expected payroll cost vs actual paid, impact of unpaid leave, monthly spend trends for next year’s budget.

Add pay statements when the organization allows Aragorn to read them.

After Ontology is ready

  1. Open Analytics → Manage Analytics (admin area where calculations and visuals are built).

  2. Build stories and place them on boards.

See What is Analytics? for the Manage Analytics workspace.

Did this answer your question?