How to Build a Short Locate and Recall Workflow in Your OMS

Understanding Short Locate and Recall Requirements

Short selling in hedge funds requires systematic locate and recall workflows to comply with Regulation SHO Rule 203(b)(1), which mandates reasonable grounds to believe shares can be borrowed before executing short sales. The average hedge fund processes 847 short locate requests daily, with 23% requiring manual intervention when automated systems fail to secure borrows.

Your Order Management System must integrate with prime brokerage locate systems, maintain real-time inventory tracking, and execute automatic recalls when positions exceed available borrows. Failed locates cost hedge funds an average of $2.3 million annually in missed trading opportunities, while recall delays result in forced buy-ins averaging $1.7 million per fund.

Step 1: Configure Prime Brokerage Connectivity

Establish FIX 4.4 connections to your prime brokerages' locate systems through dedicated trading gateways. Most institutional prime brokers including Goldman Sachs, Morgan Stanley, and JPMorgan support SecurityDefinitionRequest (35=c) messages for real-time locate queries. Configure your OMS to send these requests with SecurityReqID, Symbol, Side=5 (short sell), and OrderQty fields populated.

Set up dedicated FIX sessions for locate traffic, separate from order routing connections. Use CompID patterns like "LOCATE_[PRIMECODE]" and maintain heartbeat intervals of 30 seconds maximum. Configure session schedules to align with prime brokerage locate desk hours, typically 7:00 AM to 6:00 PM EST.

Test connectivity using SecurityListRequest messages during market close to verify symbol mappings and locate fee structures. Document message field mappings for each prime broker, as SecuritySubType and SecurityExchange field requirements vary between institutions.

Step 2: Build Automated Locate Logic

Program your OMS to automatically trigger locate requests when traders enter short sell orders above predefined notional thresholds. Set institutional minimums at $500,000 notional for large-cap equities and $100,000 for small-cap securities. Configure the system to batch multiple locate requests for the same security within 5-minute windows to minimize prime brokerage fees.

Implement a waterfall logic that queries multiple prime brokers simultaneously, ranking responses by borrow cost and availability duration. Weight responses using a scoring algorithm: availability duration (40%), borrow rate (35%), and historical reliability (25%). Auto-accept locates below 50 basis points annual borrow cost and flag higher-cost borrows for trader approval.

Create pre-locate functionality for portfolio managers' anticipated short positions. Allow PM teams to submit locate requests up to 3 trading days in advance, with automatic renewal for positions held longer than the initial locate period. Track locate utilization rates by PM and strategy to optimize future pre-locate quantities.

Step 3: Implement Real-Time Inventory Tracking

Configure your OMS position keeping engine to track three distinct inventory levels: gross short positions, located shares, and available borrows. Update these figures in real-time as trades execute and settles occur. Maintain separate tracking for each prime brokerage relationship, as borrows are not fungible across institutions.

Set up automated alerts when short positions approach 95% of located quantities for any security. Configure escalating notifications: first alert to traders at 85% utilization, second to desk heads at 95%, and automatic recall requests at 100%. Include position details, available locate sources, and estimated time to forced buy-in in all alerts.

Build cross-reference tables linking CUSIP, ISIN, and Bloomberg identifiers to ensure accurate position tracking across multiple data vendors. Implement nightly reconciliation processes comparing your position records against prime brokerage settlement reports, flagging discrepancies exceeding $10,000 notional or 100 shares.

Step 4: Configure Recall Management Workflows

Design your recall workflow to handle both voluntary recalls (reducing exposure) and mandatory recalls (borrow unavailable). Configure the system to automatically generate recall notices when prime brokers send SecurityDefinitionReject messages indicating borrow unavailability. Set standard recall timelines: 2 hours for liquid large-cap securities, 4 hours for mid-cap, and 24 hours for small-cap or international equities.

Program automated buy order generation for recalled positions, sizing orders to cover the full recalled quantity plus a 5% buffer for potential slippage. Route these orders through your standard execution algorithms, but flag them as "recall coverage" to prevent traders from mistakenly canceling urgent fills.

Implement a priority queue system for recalls, ranking by: regulatory urgency (forced buy-ins), position concentration risk, borrow cost increases, and portfolio strategy impact. Create override mechanisms allowing desk heads to modify recall priorities during volatile market conditions or around earnings announcements.

Step 5: Establish Monitoring and Compliance Controls

Configure your OMS to generate daily compliance reports showing short interest by security, days-to-cover calculations, and locate utilization percentages. Include fields for trade date, settlement date, locate expiration, borrow rate, and regulatory thresholds. Export these reports in formats compatible with regulatory filing systems like EDGAR for Schedule 13F updates.

Set up exception monitoring for hard-to-borrow securities with borrow rates exceeding 300 basis points annually. Flag these positions for enhanced oversight and require portfolio manager approval for position increases above $1 million notional. Configure automatic position limits preventing new shorts when locate costs exceed 500 basis points.

Implement audit trails capturing all locate requests, approvals, and recalls with timestamps accurate to the millisecond. Store these records for minimum 5-year retention periods as required by SEC Rule 17a-4. Configure read-only access for compliance teams and external auditors through dedicated reporting interfaces.

Technology Integration Considerations

Most hedge funds integrate their short workflows with specialized securities lending platforms rather than building proprietary solutions. Market-leading OMS providers offer pre-built connectors supporting major prime brokerage APIs, while independent securities lending networks provide alternative locate sources for hard-to-borrow situations.

Cloud-based workflow automation platforms can supplement traditional OMS capabilities, offering advanced recall prioritization algorithms and cross-platform position aggregation. Real-time risk management systems provide additional oversight layers, automatically adjusting position limits based on market volatility and liquidity conditions.