Confluence Requirement Yogi: System versus Engineering group requirement control

[Mark Schroeder]

We are looking for a work flow solution to our situation and would like to know how others may have solved it.

We are trying to solve our use case where we have a Systems Group and an Engineering group.  Systems writes the requirements while interacting with the Engineering group and, at present, releases a version controlled Word Document.  The Engineering group uses Python  to extract the requirements from the Word Document to make an Excel spreadsheet.  The Engineering group currently modifies the Python generated Excel spreadsheet with additional columns such as: which module (circuit board) in the unit each requirement impacts, responsible engineer, method of verification, etc. (10 columns in total).  Then the spreadsheet is imported with Requirements Yogi and Module Specifications are made by RY Reports and careful filter selections.  It works very nice.

GOAL:  Systems is now exploring the benefits of using Confluence to make the Systems specifications and what the ramification, and ground rules would need to be. 

1. Systems does NOT want all the other Engineering columns in the Systems specification, or if the solution remains spreadsheet based any potential Systems Controlled Spreadsheet
2. Systems cannot allow Engineering to have write access to the Systems Specification, or the Systems controlled Spreadsheet to add its own columns
3. Systems is considering a switch to a Confluence Page format where the background and explanation verbiage is on the page in the same manner as the Word Document yet the Requirements are simply reports from a Systems controlled Spreadsheet.  Such that explanation verbiage is controlled on the Confluence pages, but the requirements are in the version controlled spreadsheet imported upon release.
4. Systems does not want to "yank the chain" of Engineering as they work out future potential requirements with the customer. 

So for example if we were to use a master Confluence Page instead of the spreadsheet for requirements definition then, as Systems grappled with getting the requirements correct from the customer, Engineering would see every detail change and may start changing the design for a wording that may never be. 

QUESTIONS:  

Is there a way for Systems to maintain control of the registered requirements and still allow Engineering to add their per requirement information as they flow it to the team?

If Systems did allow Engineering to modify the Confluence Requirement page, is there a way to lock the Systems controlled columns?

Is there a better way to do this whole thing while maintaining the separate control?