Reliable Background Screening - Technical Discovery Call Summary

Date: March 6, 2026
Participants: Larry, Devon, Alan, Amanda, Kate, Schuyler, Rudy, Brett
Primary Focus: Chrome Extension Development & Website Security Management

Task Commitments by Person

Larry's Commitments

1. Send step-by-step instructions for Google Developer account setup DONE

(Larry): "I'll just send you step by step instructions. It's not difficult."

Read the Setup Instructions here

2. Review Tazworks API documentation and identify what data access is possible

(Larry): "I'll send you the stuff. And what I'll do is I'll go ahead and to we'll go look at Tazworth. And then there are other places you mentioned that may or may not have APIs that we could talk to."

3. Walk through Reliable's 67 redirect sites to assess security setup
Context: This is a follow-up from the malware incident discussion

(Larry): "Yes, so it would be worth walking through and looking at them all and seeing what are they doing, how are they set up."

Alan/Reliable Team's Commitments

1. Set up Google Developer account (Timeline: Monday afternoon or following Larry's instructions)

(Alan): "So so maybe Brad, if we have any time on Monday, maybe we work with Larry in the late afternoon to set up a Google Developer account."

2. Investigate GoDaddy Hosts subscription for automated malware monitoring
Context: In response to the malware detection issue that occurred

(Alan): "Well, then with that, Rudy, I guess we could look into that."

3. Schedule call with Tazworks IT team (Conditional: if Larry determines more API access is needed)
Timeline: "usually takes about a week" to schedule

(Alan): "And then if you're looking through the code, what TasWorks sent over, and you tell us, hey. Let's have a call with the TasWorks IT team so we can get more access, then let us know, and we'll set that up too. That usually takes about a week."

4. Schuyler to explore Tazworks report launching process with Tazworks representative
Context: Understanding current system before building replacement

(Schuyler): "I could try picking TasWorks Brain, whoever I talked to at TasWorks Live about how we're launching our reports and what ideas they have."

Overview of Discussion

Security Crisis Resolution & Website Infrastructure

The call opened with resolution of a critical malware detection issue. Larry explained that the reliable redirect domain was flagged because it pointed to a site containing actual malware, not because the redirect itself had issues. Google cleared the listing within hours once notified the target site was cleaned. The team discovered they're managing 67 redirect domains, raising questions about security monitoring across all properties. Larry recommended upgrading to GoDaddy's automated malware monitoring ("Hosts") to prevent future incidents, acknowledging this may occasionally remove legitimate code but is preferable to week-long red-screen warnings.

Chrome Extension Architecture Discovery

The core discussion focused on building a Chrome extension to automate Reliable's background screening workflow. Larry emphasized the critical need to map data flow: where each piece of screen data originates, which APIs provide it, and what triggers automated actions like email notifications. The team walked through establishing necessary access: Google Developer account (under Reliable's control, not Larry's), Tazworks API verification, and potentially other third-party API integrations. Larry stressed building foundation architecture that won't require rebuilding in six months.

Process Complexity & System Overhaul Recognition

A significant theme emerged around the current system's excessive complexity and failure points. Larry observed multiple unnecessary steps ("toasting the bread before making the sandwich") creating confusion about where to cut-and-paste data. Schuyler suggested showing Larry the full Tazworks integration might reveal opportunities for "a whole new system." Alan confirmed Tazworks was acquired twice recently, with the new owners stating full integration won't be available until next year—forcing Reliable to build their own solution. The discussion revealed tension between quick Chrome extension delivery and addressing deeper systemic inefficiencies Larry was discovering.

Developer Account Control & Timeline Reality

Larry insisted Reliable establish the Google Developer account under their ownership rather than him controlling it, ensuring they maintain access and control of whatever gets built. He explained the initial Chrome extension approval takes longer ("a few days" for account approval, longer for first extension), but subsequent updates process within an hour. The team discussed using an existing reliable background Gmail account versus creating new credentials, settling on following Larry's forthcoming setup instructions.

Areas of Agreement

1. Automated malware monitoring is better than manual detection

(Larry): "I'd rather go, Okay, you took out good code. Let me put it back in. Then what you just went through for a week of everyone's hitting our site and getting a big, beautiful red screen saying, Don't go here."

(Alan): "Got it. Okay, good."

2. Building on solid foundation is essential even if it delays quick wins

(Larry): "And all I'm trying to do is make sure that that starting piece has a foundation that we don't then tear apart six months ago, which is kind of what Rudy was saying. Yeah. It's like, we build this and throw it all away, why did we build it?"

(Alan): "Right."

3. Reliable must own and control the developer accounts

(Larry): "It's not like you're going to be developing in it, it's just saying this is your account."

(Alan): "Got it."

4. Current process has excessive complexity and failure points

(Larry): "You've got so many failure points in there. Yep. That I just watch and go, poor person that's trying to remember, where do I cut and paste this at?"

(Alan): "As a next step, yeah, I mean, that's why we wanted to show this to you because if we can make it more streamlined and easier for everybody as we get more and more clients using it, it's gonna really help out a lot."

5. Tazworks won't provide integration support anytime soon

(Alan): "when we asked them about a full integration with a client who wanted a full integration, they said, yeah. Probably not till next year. We could even look at it even if we could do something. It's gonna be a full year. We don't have time."

(Schuyler): "They don't have the bandwidth to do, like, anything."

CONFIDENCE-CALIBRATE APPLIED: 92%
High confidence due to clear audio, explicit commitments, and minimal ambiguity. The 8% uncertainty stems from implied vs explicit timelines (e.g., "Monday" suggested but not firmly committed), and one unclear speaker identification ("Not Sure" speaker identity not confirmed).