Like me, Matus Goljer (fuco1) is a heavy user of Org-capture. I’ve got 11 templates that cover all sorts of events that I want to capture. Goljer has a similar number of templates but his taxonomy is much richer than mine. I’m generally content to file the note at the end of one of my agenda files and the templates take care of that automatically. Goljer has more target files and headings within those files that are possible targets for the notes. As a hypothetical example, consider a TODO note. It may be associated with one of his projects and within that project it may be concerned with some task and within that task, some subtask and so on. That makes putting the note in the proper place difficult and, as Goljer says, it’s not always obvious at capture time what the proper place is.
To solve that problem, Goljer’s templates dump many of his captures into a holding file that he can come back to later to refile the notes. The problem is that having so many possible targets—Goljer says the number can grow into the tens of thousands—makes refiling very slow.
As I’ve written before, Goljer is an expert at identifying and eliminating friction in his workflow. He eliminates this particular friction by temporarily restricting the number of targets. He’s got a clever scheme for doing that and ties everything together with a hydra that makes refiling entries in the holding file easy. Take a look at his post for the details. If you have a complicated taxonomy like Goljer’s, you may want to adopt or adapt his system.