Hi Peter,
It doesn't have this built-in, but the concept of approval is flexible. Extensions can mark changes as being approved, and if your repository's hooks are checking the approval state of the review request before letting the change in (or, client-side, if rbt land is being used), then changes will be blocked from landing if the custom approval logic doesn't allow it.
An extension could map files to groups and require that each group has a user that has given a Ship It before a change is approved to land. That'd be one option. Custom UI could also be added for marking that you've signed off on a file, though this would be a bit more extensive in terms of what the extension would need to do.
This also just depends on the types of changes being made there. We find that in an ideal situation, changes would be broken up by area of responsibility so that each team has a smaller piece of code to read, each of which would be able to land separately, pieced together by the Depends On field. This doesn't always work for all types of changes or products, though.
Christian