Why Source Availability and Turnaround Times Can Vary

Overview #

Verification is dependent on source availability, channel performance, manual processing, data quality, integration rules, maintenance windows, regulatory limits and the completeness of the submitted request.

Why it matters #

Clear expectations reduce frustration. Not every check that appears simple to the requester is simple at the source or legally available in real time.

How to think about it #

• Automated checks may fail if a source is unavailable or if input data is incomplete.
• Manual checks may require documents, fingerprints, payment confirmations, agency review or official processing.
• Batch checks may return dashboards and reports rather than individual instant responses.
• Some sources have scope limits: they verify only certain record types or dates.

Common examples #

• A certificate issued recently may not yet be available through a verification channel.
• A criminal record-related check may require official processing time.
• A company search may need disambiguation where many names are similar.
• A credit bureau result may depend on the bureau’s latest contributor updates.

Responsible use reminders #

• Publish realistic turnaround expectations.
• Use statuses such as submitted, pending, completed, failed, disputed and escalated.
• Do not blame the user before checking data quality and source status.

Public knowledge note: This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation’s own compliance review, regulator guidance, or contractual obligations.