Schedule Job to Start at Different Steps
A schedule has no dependencies on a job. In fact, a schedule is a shared resource which can be used by several jobs.
There's no such thing as a &quot;local&quot; schedule. There's nothing stopping you, of course, from having only one job using a schedule.
I.e., there is no place in the Agent architecture for a schedule to kick off a certain job step.
So, yes, you are limited to having a schedule starting the job at the step defined in the job.
The way I read your scenario, there is nothing in common between the steps except that they share the same subsystem of your application (or however you would phrase it). I'd love for agent to have some namespace/folder functionality for jobs, but no. IMO, the closest you can come is to have a healthy naming standard for your jobs, using some prefix in the job name to identify which system each set of jobs belong to. And, of course, comments inside the job.