If a "section" is what I equate to a work order task then I envision a main form (single job record) with a task/section subform (single record) with navigation because it's the many relationship to the single job, and if necessary, a subform below that if there are multiple child records related to a section/task. I don't think it matters if they're all in the header or not since any form with a multiple record view would be on it's own sub form.
Perhaps the level of detail for the job is greater than what you show later (the part where you mention entering dates), in which case a different view once the job has been entered. If that's not close, I guess I didn't understand your explanation as the description of the process is just a bit vague to me.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.