I'm nearly done explaining why apprenticeship is so complicated, I swear! We've talked about the multi stakeholder agreement, the need for apprenticeship regulation, and the apprenticeship jargon. The last piece isn't as universal as some of the above, but it certainly makes apprenticeship in the U.S. more complicated for some organizations. If you operate in a single state, you can stop reading here.
However, if you operate in multiple states, you need to understand that the U.S. apprenticeship system is more of a federal framework with individual state systems (see OA vs SAA). These state-specific systems add a whole 'nother wrinkle if you need to operate in multiple states.
Apprenticeships are a microcosm of many things in the U.S. There's a larger federal umbrella around apprenticeships, but they're really governed by the states. For this reason, we'll just refer to the U.S. apprenticeship system as more of a federal framework. Yes, at a high level, apprenticeships are the same nationwide. You're expected to do on-the-job training with related instruction and a progressive wage schedule based on an apprenticeable occupation. That applies to every state and territory program. How you go about your on-the-job training, who does the training, who is the sponsor, how you register, what you need to do to register, etc. will vary depending on your state. If you operate solely in OA states, you're in luck. The federal framework is the only system you need to know. If you haven't designed your organization along the lines of the ever changing OA vs SAA divide, however, you'll need to contend with multiple systems.
Now, all of the states adhere to roughly the same framework, but they vary slightly with different twists that are only clear once you've run into them. You'll need an LEA in California but no where else. Your program in Maine may not meet the standard in Washington. Things like that.
You may get your apprenticeship program approved in one state if its an SAA even though its not on the apprenticeable occupations list.
What really matters is that, especially if you're dealing with SAA states, they make the call on what's allowed and what's not. That's fine when they're aligned with other states. It becomes just another complication when they're not as now you have different tracking standards, maybe different partners, etc.
One way to navigate this is to develop National Program Standards. There's a whole series of requirements you'll need to meet this standard, but once done, you're covered in all states. The other way to deal with this is to start with the most universal option -- register in your OA state(s), first. It is much easier to register in an SAA state after you've been approved in an OA state, and you can often use the bulk of your work from the OA registration. It's here, however, where you'll find there differences that arise -- prepare for and expect them.
Again, it makes sense why a state would want to run things differently. They have state-specific laws. They have state-specific needs that they're best equipped to understand. For the employer who has to navigate all of this, however, this is starts to beg the question of why?