As the spec writing process starts to gather steam, routine check-ins and reviews need to occur to ensure accuracy, and more importantly, capture any missed issues or conflicts/confusions with other members of cross-disciplinary team, particuarly QA or Development.
The reviews are not a time to go through word by word every single line or what’s written, nor is it a time for “committee writing”–simply unproductive! Instead, the weekly reviews should be a time to identify major issues that cropped up during the writing, gaps/deltas, and potential conflicts with what’s been prototyped vs. developed or tested. High level issues should be surfaced and debated, not tactical tweaks.
Before the weekly reviews, the spec writer should be in constant touch with the designers and QA, having a tight feedback loop on getting inputs, making sure changes to the design are communicated, etc.