How to Automate RBT and BCBA Credential Verification

If you are reading this, chances are you or your team are spending way too much time on RBT and BCBA credential verification.

Every new hire brings another round of registry checks, portal logins, and document chasing. You’re copying the same details between systems and tracking renewal dates in spreadsheets. As the roster grows, keeping each provider’s record current takes more of your team’s day.

We built Skyvern to reduce that repetitive browser work (I'm Skyvern's CEO). It can enter approved verification results, upload supporting documents, and update provider records, giving your team more time to resolve missing information and keep onboarding moving.

In this article, you’ll learn what to verify, how the 2026 RBT changes affect your records, and how to build a credential verification workflow with Skyvern.

What you need to verify for an RBT or BCBA

Verifying RBT and BCBA credentials depends on the provider’s role, where they practice, and the payers involved. The table below shows what to check, which sources to use, and what to record.

Check	Source	What to record
BACB certification	BACB Certificant Registry or appropriate verification report	Matched identity, certification type, observed status, and reportable actions
State license or registration, where applicable	Relevant state regulator	Credential number, status, dates, and any restrictions shown
RBT supervision and assessment requirements	Supervisor credentials and the practice's supporting records	Assigned supervisor, applicable qualifications, and required documentation
CAQH profile, where needed	Provider's authorized portal access	Profile completeness, current documents, and attestation due date
NPI information, where needed	NPPES	NPI, identity, taxonomy, and practice information
Payer participation	Payer records and confirmation documents	Enrollment status, effective dates, and applicable providers and locations

These distinctions also matter in a broader healthcare credentialing workflow.

How to verify BACB certification

The BACB Certificant Registry supports searches by certification number or general search criteria. Prefer the certification number when available, then confirm that the returned identity matches the person in your records.

Review the certification type, current status, and any reportable disciplinary actions. Record the source and retrieval time alongside the result. BACB says its registry is updated daily, so retain the date of the check when sharing the evidence.

If information conflicts with an onboarding document, assign the discrepancy to a reviewer. A failed search needs investigation before anyone draws a conclusion about the person's certification.

What the 2026 RBT changes mean for your records

The RBT transition changes the dates and documents a practice needs to track:

• Existing RBTs complete their 2026 recertification with the Recertification Competency Assessment. After that recertification, they move to a two-year cycle and must complete 12 professional development units (PDUs) before the following recertification.
• People first certified in 2026 begin with a two-year cycle and the 12-PDU requirement.

For example, an existing RBT who recertified on March 1, 2026, would next recertify on March 1, 2028. Their 2026 assessment and subsequent PDU evidence belong to different stages of the record. BACB's 2026 transition guide also explains the separate treatment of voluntary inactive status.

BCBAs follow different maintenance requirements: 32 continuing education units (CEUs) per two-year cycle, including four in ethics and three in supervision for supervisors. Use the current BCBA handbook when defining those checks.

Where an RBT assessment is required, verify the responsible assessor's qualifications. Eligible BCBAs and BCaBAs must meet BACB's specified requirements, including the eight-hour supervision training.

Where browser automation fits

Browser automation is good for repetitive credentialing tasks that happen inside websites: entering provider details, uploading documents, downloading available records, and updating your practice management system. It’s especially useful when those systems don’t offer an API or a direct integration.

For example, after your team verifies a BCBA’s certification, Skyvern can open the matching provider record, enter the result, attach the supporting document, and confirm the update was saved. Your team spends less time copying information between systems and more time resolving missing documents or conflicting records.

Skyvern brings three core advantages:

• Layout changes don’t have to break the workflow. Skyvern reads the page and identifies fields by their meaning, so it can adapt when buttons move or forms change.
• It scales easily. Run multiple provider workflows in parallel as your roster grows, reducing the manual work required for each additional record.
• It adapts to different portals without rewriting the automation. Reuse the same instructions for similar tasks, and let Skyvern work out how to navigate each portal and complete the steps.

How to build the workflow with Skyvern

Start with one process your team already understands. For example, consider a practice onboarding a BCBA and an RBT. A credentialing specialist completes the BACB source checks. Skyvern then transfers the approved results into the practice's web application and handles other portal tasks for which access is permitted.

1. Prepare the provider record

Give each person a stable internal ID. Add their name, role, certification number, relevant jurisdictions, and the checks assigned by your credentialing team.

Keep source results separate from submitted information. A certification number supplied on an onboarding form is an input. The matched status retrieved from an authoritative source is a verification result.

Resolve missing identifiers before a run starts. If two people share a name, the workflow needs enough information to distinguish them.

2. Define the evidence and access method

For each check, specify the source, how the result will be obtained, and what evidence the team will accept. One step may use an official data file, another may require staff verification, and another may use an authorized browser session.

Define completion in terms of the saved result. Opening a record or reaching a search page does not establish that verification is complete. The workflow should return the matched identity, observed information, retrieval time, and evidence reference.

3. Configure portal access

Set up the account and permissions appropriate to the task. Use managed credentials for supported logins and configure the portal's actual MFA process. Our guide to authentication in Skyvern explains the available approaches.

Test access before connecting the full workflow. Establish what happens when a session expires or a verification code is unavailable. Include downloaded documents and run recordings in the practice's access and retention rules.

4. Transfer approved data and validate the result

Use the provider record and supplied evidence to drive the portal task. For an internal record update, the instruction might be:

Open the provider record matching the supplied internal ID. Enter the approved verification result and attach its supporting document. Confirm that the displayed provider ID and certification number match the supplied values before saving. Return the saved record reference. Stop for review if an identifier differs or required information is missing.

This applies the same principles used when filling forms with Skyvern: supply the information, describe the intended outcome, and check that the destination contains the correct values.

Developer teams can define a structured output schema for the fields their system needs. Validate returned identifiers against the input record before accepting the result.

5.Log and assign exceptions

Keep enough context for another person to understand what happened. An illustrative record might look like this:

Field	Example
Internal provider ID	DEMO-BCBA-01, a fictional record
Source	BACB verification completed by credentialing staff
Checked at	October 7, 2026, 10:15 UTC
Observed certification status	Active
Evidence	Reference to the saved verification document
Other required checks	State and payer checks pending
Next action	Assigned to the credentialing coordinator

Keep the outcome of the automation separate from the observed credential status. Similarly, a missing field should remain unknown until resolved.

Assign each exception an owner and a specific action. "Confirm certification number with provider" is more useful than "verification failed."

6. Schedule follow-up from the actual requirements

Track certification deadlines, assessment requirements, supervision records, and payer follow-up separately. Use the applicable source rules and the practice's review policy to set the schedule.

Include changes that should trigger a new check, such as a provider working in another jurisdiction or joining another practice location. Preserve earlier verification results so staff can reconstruct the history.

For requested letters, track the request and receipt as separate events. A payment confirmation establishes that the request was paid. The verification document still needs to arrive and be matched to the correct record.

Start with one workflow and measure the result

I recommend beginning with a recurring task that has clean inputs and an obvious completion point. Transferring reviewed verification evidence into a provider record is easier to evaluate than an entire onboarding process spanning several organizations.

Have an experienced staff member review the pilot's outputs. Measure:

• Staff minutes per completed, usable record, including review time.
• The proportion of records needing correction or additional information.
• Incomplete runs and the reasons they stopped.
• Time spent resolving exceptions.
• Whether staff can retrieve the supporting evidence when asked.

Include a missing identifier, an unavailable document, and an unexpected portal response in your evaluation. Those cases reveal whether the workflow makes unfinished work visible.

Measure internal processing time separately from payer turnaround. Automation can reduce your team's preparation and follow-up work, while payer decisions remain an external dependency.

Once the first process produces dependable records, expand to the next recurring task. Try Skyvern with a workflow your credentialing team can inspect and measure.

Frequently asked questions

Does active BACB certification mean a provider is enrolled with a payer?

No. Certification is one part of the record. Confirm payer participation and the applicable effective dates, providers, and locations through the payer's process before treating enrollment as complete.

Can a public registry check establish that all PDUs or supervision requirements are complete?

Use the public registry for the certification information it reports. Maintain the supporting training and supervision records required by the practice and BACB separately. The RBT handbook explains the maintenance and documentation requirements.

What should happen when a search returns no match?

Check the identifier and spelling, confirm the appropriate source, and assign unresolved cases to a reviewer. Record the unsuccessful check. Keep the provider's certification status unresolved until the team has sufficient evidence to establish it.