How to build any hiring report in minutes using AI

Getting useful data out of your hiring process has always been harder than it should be. You know the question you want answered. But getting from that question to a useful answer means knowing which data to pull, which filters to set, and how to get it into a format that means something to whoever asked.

In episode six of the Pinpoint How-To Series, we walked through how to use AI Hiring Copilot and Pinpoint's MCP to answer hiring questions in plain language, build dashboards without touching a single filter, and connect your hiring data to the rest of your stack. This article covers the key ideas from the session, along with the exact prompts we used so you can try them yourself.

Context matters

AI can only surface data that exists in Pinpoint. If a field hasn't been filled in, a stage hasn't been recorded, or a source wasn't captured when the application came in, it won't appear in the report. That's not a limitation of the AI. It's a reminder that good reporting starts with good data. What goes in is what comes out.

If you want to go deeper on building the foundations that make this work, Episode 4 of the Pinpoint How-To Series covers exactly that.

Two tools, two use cases

Before getting into examples, it helps to understand which tool to reach for.

Pinpoint's MCP connects your AI assistant, like Claude, to your Pinpoint data. It's designed for quick, specific questions where you need a direct answer fast. The answer comes back in Claude, ready to copy, paste, or drop into a doc or email. It can also connect to data that lives outside Pinpoint, like a Google Doc with your hiring targets or a planning tool, which makes it useful for anything that crosses systems.

AI Hiring Copilot lives inside Pinpoint, so there's nothing extra to set up (beyond enabling it). It's better suited to building something that stays in Pinpoint: a dashboard you can come back to, a view you can share with your leadership team. Because it was built specifically for hiring, it understands recruiting context, which means you can give it a fairly vague prompt and still get a useful result.

Simple rule: Both are great for getting quick answers to questions. MCP for cross-system questions. Copilot for building dashboards inside Pinpoint.

Quick answers to three core hiring reporting question

These three came up most in the report submissions from episode attendees. All of them can be answered instantly using both Copilot and in Claude with the Pinpoint MCP connected.

1. Where are candidates coming from?

Most hiring teams track applications by source but rarely see which sources produce actual hires, not just volume.

Why this matters: Budget follows outcomes, not volume. Knowing which channels convert is where the real sourcing decisions get made. This report gives you that in seconds.

Try it yourself

"What are our top sources of hire over the last 6 months?"

2. Where are candidates dropping out?

Understanding your funnel means looking at closed roles, not just whatever's active right now.

Why this matters: Active pipeline views only show where things are, not where they went. A funnel built on closed roles shows you the real drop-off points: where candidates are consistently being lost, whether that's at screening, interview, or offer stage. That's where process improvements actually live.

Try it yourself

"Show me the conversion rate of candidates from application through to hire across all closed roles."

3. How fast are we hiring?

Time to hire and time to fill are the numbers leadership asks for most, and the hardest to pull without going through multiple filters.

Why this matters: This is the report that tells you whether hiring is running on schedule or quietly falling behind somewhere. By department, you can see exactly which teams are on track and which are slowing down, without a single filter to set.

Try it yourself

"What is our average time to hire and time to fill, broken down by department?"

Building a hiring health dashboard in Copilot

For a broader view of your hiring operation, AI Hiring Copilot is the better tool, particularly when you want to build something that lives in Pinpoint and can be accessed by your team anytime.

This is where Copilot's recruiting-specific context really shows. You can give it a fairly vague prompt and it figures out what to build. Here's the one we used in the session:

Try it yourself

"I've been asked by the board to show our overall hiring health and identify anything that's slowing down our hiring. Can you help me build a dashboard for this?"

Copilot comes back with suggestions for what to include and asks about timeframes and filters. Respond with something like "last 6 months, broken down monthly" and it builds from there.

The result is a dashboard inside Pinpoint covering hiring health, time to fill by team, pipeline conversion, and recruiter performance, all in one view. You didn't need to specify any of that. You just needed to know the question you were trying to answer.

Why this matters: A report you have to rebuild from scratch every month is a report that doesn't always get built. A dashboard inside Pinpoint that stays updated means your leadership team can see the answer anytime, not just when someone had time to pull it.

What becomes possible when you connect out

The MCP's real strength shows when you connect Pinpoint to other tools in your stack. For example:

Comparing actuals against targets

If your annual hiring plan lives in a Google Doc or a planning tool, you can connect that to Claude via MCP and ask: "Where are we against our hiring plan for this quarter?" Claude looks at your Pinpoint data and your planning document at the same time. Pinpoint doesn't know your targets on its own. Connected to the doc where they live, it does.

Scheduled reporting to Slack

You can set up a scheduled Slack notification powered by live Pinpoint data. Every Monday morning: "You've hired 17 of your 20 target hires this quarter. Three roles are currently behind plan." No manual report. No dashboard to log into. The answer arrives on a schedule, without you doing anything to trigger it.

Key takeaways

• Data quality is everything. AI can only surface what exists in Pinpoint. The more complete your data, the more useful your reporting. That's a process problem, not a tech one.
• MCP and Copilot serve different jobs. MCP for quick answers and cross-system questions. Copilot for building dashboards inside Pinpoint that your team can come back to. And since Copilot is built with hiring context, you don't need a detailed prompt, it already understands your recruiting workflow.
• You don't need to know how to build a report. You need to know the question. Describe it in plain language and let the tool figure out the structure.

What to do this week

1. Get connected. Follow these steps to set up Pinpoint's MCP and enable AI Hiring Copilot.
2. Try one prompt. Ask "What's my average time to hire this quarter?" or "Which sources produced the most hires in the last 6 months?" One question, one answer, see what it saves you.
3. Build a dashboard in Copilot. Ask it to show your hiring health for the last three months using the prompt above. See what it builds.
4. Think about your targets. Where does your hiring plan live? Getting that document into the MCP conversation is where the most powerful reporting workflows start. Your CSM can help you set it up.