52X Candidate Intake.
High-Level Data Architecture.
Architecture recruiting. Less candidate effort. Richer matching intelligence. A shared model to shape with 52X.
Download the landscape PDF ↗What Loxo can store is not what 52X should ask candidates to manually enter.
Start before the form.
Choose a stage to explore its purpose, data and discovery questions. Pre-intake emails and marketing can lead through the website or directly to a dedicated intake URL.
Ask for intent.
Reuse the evidence.
Filter by a likely acquisition source. Many datasets use multiple sources; these are initial mapping hypotheses, not confirmed Loxo field definitions.
A record. A match.
Project Architect
8 years of experience
Design-led architecture firm
Cultural + civic projects
Design through construction
$120K+ / Bay Area hybrid
Will not relocate
Fictional architecture candidate. Compensation is illustrative, not a market benchmark.
The baseline is a starting point.
Define the signals that change a placement decision. Decide which extend Loxo and which belong in a separate 52X matching model.
Baseline Schema →
What the current system knows. Confirm native fields, custom fields and configuration.
Matching Schema →
What makes someone matchable for an architecture role, firm and project context.
Acquisition Schema
Where each field comes from, how certain it is and who verifies it.
Open Ruben’s intake question + sequence studio →
Working space / 52X-defined signals
Add discussion ideas and assign a likely source. These are browser-local working notes; they do not update Loxo or the shared project record. Export to bring decisions back into Obsidian.
Week 1 / field-mapping dimensions
Loxo field / 52X extension → business value → source → ask / extract / enrich / generate → required / optional → confidence → operator verification.
Understand what already connects.
Map
Tools and manual steps accessing Loxo data. Read paths, transformations, write-back and ownership.
Assess
Existing matching and insight capabilities. Gaps, duplicate effort and constraints.
Decide
What to reuse, configure, connect or extend to improve recruiter, candidate and client outcomes.
Explore service opportunities
Compare Clay, Make, Retool and Textkernel: connection evidence, problems, recruiter impact, cost drivers and editable scenarios.
Open the interactive service explorer →Clay has a documented Loxo connector. Make and Retool are custom API routes to validate. A Loxo integration for Textkernel remains unverified.
Discovery deliverable: current-state system map + capability/gap assessment + recommended path.
What should this intelligence become?
Potential forms, not committed deliverables. Explore audience → decision → format → destination. Outputs require approved data, evidence and operator review.
The workflow our assumptions start from.
Seven manual recruiter operations, from identity search through verification, plus the exception loop. This baseline will be validated with 52X and considered for optimization by project close.
Explore the AS IS workflow drawing →
Modeled baseline awaiting recruiter observation. Assumptions and impact estimates remain hypotheses until validated.
A clean datasheet.
A verified database handoff.
Produce a reviewed candidate datasheet alongside a destination-mapped CSV or tested API payload. Keep resume and portfolio attachments in a separate verified document workflow. The review sheet alone is not a database import.
01 / Prepare
Identity + contact, professional baseline, candidate intent, architecture evidence and routing. Confirm actual native/custom destinations and required fields in 52X’s account.
02 / Review + transfer
Resolve duplicates and conflicts. Operator approves create/update, mapping and documents. Use native Record Field forms, mapped CSV or a tested API/connector route.
03 / Reconcile
Check destination values, attachments, ownership and job/list association. Capture the Loxo record ID, errors and reviewer signoff.
Candidate intake versus client intake
Candidate applications collect name, email, phone and resume. Additional required questions are configurable. Client intake is a company + contact, with a separate Job/search brief when needed. Job setup includes role title, hiring company, location and visibility, plus account-specific validations. Jobs are not imported through standard CSV.
CSV handoff requirements and account validation
Map each column to one destination. Choose Candidate or Contact type; job/list association is optional. Pilot 5–10 entries before larger batches. The reviewed guide does not establish one universal required-field schema. Confirm 52X field types, required values and update behavior before production use. Standalone Loxo Forms do not accept file uploads.
Official references: CSV import · Applications · Forms · Job setup · Jobs FAQ
Researched October 20, 2026. Proposed 52X handoff design; account-specific mapping is not yet validated. No production import performed.
Turn the map into decisions.
Acquisition
Website → Intake Opportunity Map: entry paths, friction, technical constraints, context and instrumentation.
Data
Agree baseline, matching and acquisition schemas. Confirm 52X-specific signals and storage.
Systems
Inventory Loxo access and existing middle layers. Assess reuse before selecting services.
Evidence
Define operator validation, candidate/client usefulness and measured recruiter impact.
Working architecture, October 20, 2026. Not a verified export of 52X's Loxo configuration. This site is a presentation and planning tool, with no live integrations.