# ATS integrations: working checklist

Companion to https://lunaprompts.com/blog/ats-assessment-integration-guide

LunaPrompts Editorial. Original illustrative exercise.

## Define the workflow

- Role or campaign:
- Owner:
- Decision this workflow should support:
- Candidate instructions and support route:

## Worked example: Trace an assessment round trip

Use a test candidate and a non-production hiring workflow approved by your team. Create the assessment invitation from the relevant ATS application. Verify the selected assessment, the candidate-facing message, and where progress appears.

Complete the task and inspect the return path. Does the right application receive the result? Can the authorized interviewer open the detailed report? Is the visible state distinguishable from a candidate who has only started? Record the exact behavior for your system rather than assuming another ATS works the same way.

Then exercise one exception that matters to your process. Cancel an assessment, check how a resend is handled, or review what happens if the same person has another application. Document the owner and recovery procedure. These checks prevent a recruiter from discovering an ambiguous state during a live campaign.

For Greenhouse, use the vendor’s documented LunaPrompts assessment-stage workflow as the starting point. For Ashby, confirm the enabled actions and result access for your account. For Workday or another enterprise system, establish the supported connection and scope before planning rollout. A logo list cannot substitute for that agreement.

## Review checklist

- [ ] Identity: Candidate and application association
  Evidence or open question:
- [ ] Actions: Select, invite, cancel, and supported retries
  Evidence or open question:
- [ ] Results: States, score fields, and report access
  Evidence or open question:
- [ ] Operations: Errors, ownership, and recovery
  Evidence or open question:

## Working session

Run one invitation-to-report round trip and one exception in a test workflow. Record the observed behavior in the downloadable acceptance checklist.

## Avoid this mistake

Do not assume all connectors are equivalent or describe an unverified system as a native integration. Publish and evaluate the scope actually supported.

## Record the next step

- Observed evidence:
- What remains uncertain:
- Person responsible:
- Next action and date:

Keep candidate examples anonymous when sharing this worksheet.