You've asked what you want, but not why you want it. I am guessing that this is a preconception that you think it needs to complete in order to be successful. Time Machine isn't just a standard "backup job" that will create individual backups that depend on the success of each backup, it's more a permanent process.
Effectively each time you change a file, whether by addition or alteration of the contents or metadata, it gets added to the list of files that need to be backed up. The list grows and grows all the time, and it's built into the actions of the filesystem that whenever it makes a change, it also adds the file to the list. Every hour (or whatever you have set if you are using a non-standard config), Time Machine will start at the beginning of this list of changes, and start to plough through them and copy the changes to the backup disk. At the end of the process, when there are no more files to include in the backup, it stops.
But there is no need to wait for it to stop. If you have say 100 files in the queue, and it only processes 45.5 of them when you shut the machine down, the completed files are removed from the list only after Time Machine confirms they were completely backed up -- any partly-completed files will not be flagged as complete. Then, next time you boot up, wait another hour, the process will start again. You will have the 55 files that were not transferred last time at the front of the queue, followed by any other changes that have been made in the first place.
So, in summary, unlike a traditional backup which requires completion to ensure validity, the Time Machine backup is an ongoing process that can be interrupted at any time, and you do not have to wait for it to finish before shutting down. Indeed, if you are doing something disk intensive, feel free to temporarily turn Time Machine off or interrupt a backup that is in progress while you do stuff, then when you turn it back on it will just pick up where it left off.