YOUR OBJECTIVE COMES FIRST
Define the scope in its operating context.
Connect employer needs with a practical workforce plan.
New Mexico's target industries include aerospace, intelligent manufacturing, cybersecurity and value-added agriculture. This is economic context, not evidence of an agency requirement or a public-sector engagement. For a proposed initiative involving technical request qualification, first identify the authorized process owner and the decision the initiative is meant to support. A private-sector operating example can inform questions, but it does not establish procurement eligibility, agency demand or suitability for a government deployment.
New Mexico Economic Development Department: Target Industries ↗01Employer requirements stated precisely
Work with the initiative owner to distinguish roles, skills, work arrangements and evidence employers need to assess. Separate immediate job requirements from capabilities that can be developed. Use participating employer input rather than presenting every industry interest as a confirmed vacancy. For a discussion about technical request qualification, an approved discovery brief should identify affected systems, part references and attached specifications. Confirm which information may be used and where a coordinator establishes the intended work before a specialist commits engineering time. These are questions to assess with the initiative owner, not an assertion that this workflow exists at a particular agency.
02Employer evidence behind a capability requirement
A participating employer can explain a representative workstream rather than only requesting a job title. One scoping example is: Extract an affected system, part or project reference from approved request channels and show any missing information. Keep source files and messages attached to the draft. Route ambiguous requests to a coordinator who can confirm the intended work before a task reaches engineering or operations. Ask which responsibilities need an employee, which can be learned and who will assess capability. The example is not evidence of a state shortage, an open vacancy or a promise of placement.
03A practical boundary between program partners
A related task can reveal different training and operating responsibilities: Compare proposed order references, dates and quantities with the project's approved records. Flag duplicate attachments and incompatible item references. The workflow should distinguish document completeness from technical acceptance, leaving product and quality judgments with the qualified people who own them. Employer managers define job requirements and hiring decisions. Program owners control eligibility and reporting, while training or delivery partners contribute within an agreed scope. Document those boundaries before referrals begin.
04Measures with clear definitions
Agree what is being counted and who can verify it: employer requirements, referrals, completed learning, interviews or hiring outcomes are different events. Report the evidence available and the observation period. Participation does not by itself establish placement or economic impact.
