Reliable & Tazworks Integration Planning Call

Meeting Notes from 5 February 2026
Alan, Kate, Rudy, Larry

TASK COMMITMENTS BY PERSON

Alan:

• Will send Tazworks API documentation to Larry for review

(Alan): "I have to send you the Tazworks API just so you can take a look at it. So I'll get that document over to you."

• Will verify QuickApp Pro API access availability for static link functionality

(Alan): "Rudy, I'll check on that to make sure that we can get the API for the plus for that static link."

• Will compile and send system requirements and feature specifications

(Alan): "And then we'll come up with some ideas of what we would like to see and then send it to you."

• Will provide CareerPlug page screenshots for integration planning

(Alan): "And let and let's get Larry screenshots of what that page is."

Larry:

• Will create detailed integration mockup showing placement and functionality

(Larry): "what I would do next, obviously, I'll dig in, look at pages, look at stuff, and then I'll do a mock up, which will literally be like what you just saw. It's a screenshot of them and me saying we'll put this here, we'll do this there."

• Will provide cost estimate after reviewing API and requirements

(Larry): "And once we agree that that's what you want, then I will tell you what it's gonna cost because I'll know."

Kate:

• Will coordinate with Brad regarding QuickApp Pro API access

(Kate): "Alan, I'll talk to Brad. We'll talk about that. We'll get that done."

• Will maintain demo CareerPlug account access for development testing

(Kate): "I have a demo account." [Referenced for continued access during development]

OVERVIEW OF DISCUSSION

Chrome Extension Integration Architecture: Detailed discussion of replacing current HireLink system with custom Chrome extension that integrates CareerPlug candidate management with Tazworks background check processing, emphasizing side panel approach over popup windows for better user experience.

Branded Link vs Manual Process Requirements: Key technical challenge identified around implementing static branded links for background checks rather than manual data entry, requiring seamless integration between CareerPlug candidate data and Tazworks processing workflows.

Status Tracking and Visual Integration: Requirement for simplified status updates (3-4 states maximum) and real-time status display directly on CareerPlug candidate pages, eliminating need for separate status checking workflows.

Technical Feasibility and Timeline Discussion: Larry's assessment of under 8 hours development time based on existing Chrome extension architecture, with emphasis on candidate identification/tracking as primary technical challenge.

System Integration Pain Points: Discussion of current HireLink limitations including inability to handle driver's license uploads, social media searches, and proper branded link integration, driving need for custom solution.

AREAS OF AGREEMENT

Side Panel Integration Approach: All participants agreed on Larry's side panel recommendation over popup windows for better user experience.

(Alan): "Got it. So your Applet would not put a button over here. It would put that side panel. So when you clicked on it, it would open up."

Simplified Status Updates: Consensus on reducing status complexity to 3-4 essential states.

(Alan): "Really, these three are the most important, processing, pending, and completed."

Static Branded Link Solution: Agreement that static link integration is optimal solution for their workflow requirements.

(Kate): "Yeah. That would be cool because it then it would have if it had the status link in there, then now that just solves everything."

Development Timeline Expectations: All parties accepted Larry's 8-hour development estimate as reasonable.

(Larry): "Time wise to build what you want, less than eight hours."
(Kate): "That that's not the made up one. Are you sure?"
PROTOCOL MARKERS APPLIED:
• QUOTE-ANCHOR-VERIFY APPLIED: All commitments anchored with contextual direct quotes
• COMMITMENT-ISOLATE APPLIED: Separated actionable deliverables from technical architecture discussion
• INTENT-TONE-FILTER APPLIED: Demo account setup treated as ongoing resource, not one-time task
• AGREEMENT-DETECT APPLIED: Agreement points supported by respondent confirmation quotes
• THEME-CLUSTER APPLIED: Technical integration themes organized by system component
CONFIDENCE-CALIBRATE APPLIED: 90% completeness confidence. Full transcript with clear technical requirements discussion. Primary uncertainty around QuickApp Pro API access pending Brad's confirmation, which affects branded link implementation approach.