Before accepting a recruiting note integration, test normal use, ambiguous records, missing information, permission failures, retries, and corrections. Define the expected outcome for each case so approval is based on observed behavior rather than a single successful demonstration.
Build a small test pack
| Case | What a pass should establish |
|---|---|
| Normal reviewed screen | Correct note on correct candidate and role |
| Similar candidate names | Ambiguity handled without guessing |
| Missing required value | Visible, understandable exception |
| Restricted destination | Appropriate failure without unintended access |
| Uncertain transfer | Reconciliation before duplicate write |
| Corrected source | Current value identifiable downstream |
Use fictional or explicitly approved test records. The table is a suggested acceptance framework, not a universal technical standard.
Involve the people who use the result
An operations reviewer can inspect mapping and access. A recruiter can judge whether the final note is usable. A team lead can confirm ownership of unresolved tasks. Acceptance should include these practical perspectives rather than ending at an API response.
Fictional failure: the integration writes a complete paragraph to the correct record, but removes the headings that distinguish confirmed facts from open questions. Technically the transfer succeeded; operationally the output needs improvement.
Record actual results
For each case, keep the date, configuration version, observed result, evidence location, and unresolved issue. Mark blocked tests as blocked. Do not label an untested case “pass” because a vendor says it should work.
Prioritize failures that could misstate candidate information or expose it to the wrong audience. Cosmetic formatting issues and incorrect record matching do not carry the same consequence.
Define the rollout decision
Agree which failures prevent rollout, which have an accepted manual workaround, and who owns remaining work. Re-test relevant cases after configuration changes. Keep the acceptance pack small enough to repeat when the mapping or destination changes.
The integration checklist is the buying-stage overview; this plan turns the chosen scope into observable tests. Recruit Recap's ATS integrations are scoped on demand. Use the plan to verify that scope and keep any unverified capability out of internal promises and client-facing marketing.