52X CONSULTING ●

Architecture / child reference / WF-001 Rev A

AS IS.
The workflow we start from.

Primary reference for assumptions about manual candidate intake-to-Loxo transfer. Use this baseline to frame discovery, compare options and evaluate the optimized workflow by project close.

MODELED BASELINE / AWAITING RECRUITER VALIDATION

This drawing records the workflow discussed with the project lead. It is not an audited observation of 52X’s operations. Confirm steps, tools, variations and timing with recruiters before treating assumptions as established facts.

01 / Shop drawing

Manual transfer, operation by operation.

Open full-size drawing ↗Download SVGRead the text equivalent ↓
Workflow WF-001: intake packet passes through seven manual recruiter operations into Loxo; exceptions return for resolution. Full step-by-step text follows.
WF-001 / Rev A / October 20, 2026 / Not to scale. Scope: manual per-record transfer; CSV-assisted and automated routes require separate validation.
Accessible text equivalent / seven operations
  1. Find the person. Search Loxo identifiers, inspect matches and resolve ambiguous duplicates.
  2. Check the intake. Compare answers, resume, portfolio and existing values; resolve conflicts and stale information.
  3. Enter the baseline. Create or edit contact, role, employer and location fields.
  4. Translate matching signals. Choose agreed fields, categories and tags for architecture experience and preferences.
  5. Handle documents. Download and attach files; check versions and evidence references.
  6. Route the candidate. Assign owner, lists, jobs and appropriate workflow stage.
  7. Verify completion. Check values, files and routing; record unresolved exceptions.

Duplicate, missing, conflicting or unmapped information triggers an exception loop. Hold affected updates, resolve with the candidate or recruiter and recheck before completion.

02 / Assumptions anchored to the baseline

Hypotheses to test.
Not facts to inherit.

Baseline operationWorking assumptionEvidence to collect
Find + checkIdentity ambiguity and conflicting sources consume recruiter effort.Observed search steps, duplicate cases, conflict frequency and resolution time.
Enter + translateRepeated entry and inconsistent mapping create avoidable work.Fields retyped, category decisions, screen switches and corrections.
Documents + routingFile handling and associations add work beyond field transfer.Download/upload actions, missing documents, wrong versions and routing errors.
Verify + exceptionsReview of proposed values and exceptions could improve handoff quality.Review time, missed issues, completeness and operator acceptance.

No time saving, error reduction or placement uplift has been measured. Validate whether each step exists and how Loxo’s current features already support it.

03 / Project evaluation

Observe → design → compare.

Establish AS IS

Observe representative cases with recruiters. Record actual tools, sequence, handling time, retyping, switches, corrections and exceptions.

Test improvements

Compare manual, CSV-assisted and tested integration routes. Include evidence, proposed-value review, attachments and ownership.

Evaluate by close

Compare net recruiter effort and handoff completeness. Agree outcomes with 52X and document remaining gaps.

Optimization direction: let recruiters review proposed changes and exceptions with evidence, rather than reconstructing the candidate record. Implementation and targets remain to be agreed after validation.

Return to Loxo handoff architecture →