Skip to content

OTYS Go! Power BI dashboard

We bring together job openings, candidates and placements from OTYS Go! with revenue in one Power BI model. For Olympia, we built a model that matches candidates.

For recruitment agency Olympia, we developed a classification model that matches candidates with job openings

Olympia wants to match candidates with suitable job openings more efficiently and accurately using a data-driven approach. To do this, we developed an automated classification model based on data about candidates and job openings.

Read the case study

Which client and which source actually generate placements for our agency?

OTYS Go! records job openings, candidates and placements, while the accounts record revenue. To see which clients, sources and recruiters generate the margin, bring that data together in a single model.

Book a meeting

From a client vacancy to placement and invoice, all in one view

Discuss your agency figures

Placements by client

Job openings, candidate submissions and placements by client, and the share of job openings you actually fill.

Sources that deliver

Candidates by channel, how many are ultimately placed, and what each channel costs.

Work by recruiter

Open job openings, interviews and placements by recruiter or team, without pulling everything together in Excel at the end of the week.

Candidates and vacancies connected

Just as we brought candidate and vacancy data together in one model for Olympia, we connect them in your dashboard too.

First define what counts as a placement, then build the dashboard

  1. Mapping the setup

    Which statuses, fields and labels you use in OTYS Go!, and how to extract the data.

  2. Validating one label

    The figures for one label or team in the model, compared with what recruiters see in OTYS.

  3. Adding revenue

    All labels, the link to the accounts, access rights for each team and a fixed refresh time.

What’s missing from OTYS’s own reporting?

Talk it through with us

A good fit if

You want to see placements alongside revenue, margin or payroll costs, compare brands or branches, or someone currently puts together a report by hand every week.

Not a good fit if

The reporting in OTYS Go! answers your questions and no one needs revenue or margin alongside it. In that case, a custom model adds little.

What determines the scope

How OTYS is set up in your organisation, how the data can be accessed, which other systems are involved and who manages the model.

Can candidate data go into a dashboard?

Only what’s needed. Counts by source, job opening and client are usually enough, without names or CVs. We’ll agree with your privacy officer who can see more.

Reporting in OTYS, an export or your own model alongside the accounts?

Reporting in OTYS

Choose this if you only need to look at recruitment, such as the Source of Hire report. Everything stays in the system recruiters already use.

An export to Excel

Choose this if you occasionally prepare an overview for senior management. Exporting and updating it each period remains manual work.

Your own model

Choose this if you need to compare placements with revenue and margin. Our advice: define what counts as a placement before you start comparing figures.

We’ve worked with candidate and vacancy data for a staffing agency before

Data Science Lab has built data platforms, models and dashboards since 2016, as a Microsoft Partner and Databricks Partner. For Olympia, we developed a model to match candidates with job openings.

Book an introductory meeting

The figures your leadership team asks for every week are the starting point for our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In our first conversation, we’ll discuss how OTYS is set up in your organisation and which figures you’re missing.

What question about placements and margin would you like answered first?

Tell us which labels you have and which systems you use alongside OTYS Go!. We’ll reply by email or arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Through a connection or export provided by OTYS. We couldn’t find a public description of the OTYS API, so we’ll check with your administrator and OTYS which option is available under your licence. We then set up a data-loading step and build the OTYS Power BI model.

To see where a dashboard starts, read about Power BI dashboards.

OTYS lists recruitment and selection, temporary staffing, secondment and in-house recruitment. This page focuses on agencies that need to see placements alongside revenue and margin by client.

If you use Bullhorn Connexys in an in-house recruitment team, read about the Connexys Power BI dashboard.

Job openings with their client and status; candidates with their source; submissions, interviews and placements with dates. The available fields and statuses depend on how your system is configured.

That’s why we first map out what you use with your administrator.

Placements and vacancy fill rates by client, candidates and placements by source, time from job opening to placement, workload by recruiter, and revenue and margin by placement once accounting data is included.

For revenue by client more generally, read about the sales dashboard.

Yes, if placements can be linked to invoices or payroll data, for example by client and period. How this works in your organisation determines how accurately the margin can be calculated.

We only show what the data can support.

We include only the data needed to answer a question. Counts by source, job opening and client are usually enough, without names, contact details or CVs. Anyone who needs to look at individual candidates does so in OTYS.

We agree access rights and retention periods with your privacy officer.

A dashboard shows what happened; matching requires a model. For Olympia, we developed a classification model to match candidates with suitable job openings. Such a model needs its own agreements on explainability and oversight.

Read more about models under machine learning.

If the reporting in OTYS already answers your questions. Or if statuses and sources aren’t recorded consistently: in that case, data quality is the first step.

We’ll tell you that upfront.