I agree with the above that you do not want dependent actions on your NA list if they cannot be done yet.
With the bookmark analogy, it would work like this for some projects: imagine a project with 20 steps. They could be sequential or independent or a mix of both. It doesn't matter. Your project list includes an entry with the project name. Your NA list has step 1 on it. At 8:00 am, you look at your project list, see step 1 ("call Jane" or whatever it is), and you do that action. You are in the flow and then automatically complete steps 2 and 3 before breaking to do something else. Now you refer back to the NA list which has step one crossed off and you write step 4 on the list so you know where to pick back up later when you get back to working on the project.
It is OK to have other independent steps also listed on the NA list if you want to keep multiple parts moving at once, but by following the practice of noting the next action when you finish work on the project, you will always have at least one action for that project on your NA list (possibly one action per moving part of the project). That is what bookmarks the project on your NA list.
Don't think of your NA lists as a precise inventory of actions that you will complete in the coming week. It is just a list of the very next actions on all the projects that you want to advance during the next week. It is possible that every action will be crossed off in a few days and be replaced by other actions.