I&#x27;m in a regulated industry, and we&#x27;d be considered a &quot;very small entity&quot;.  What we&#x27;re doing is likely overkill for you, but how we go about things might be of interest.<p>We develop under a spiral process and requirements are right at the threshold of when we&#x27;re going under design control.  We start out in Emacs org-mode.  I developed a custom template and scripts that tries, to the best of my ability, to corral people into following ISO 29148.  The engineering team uses a table view to track the requirements while we&#x27;re collecting them, and there is a script to export into a pretty LaTeX document for stakeholders to view and redline.  We keep the requirements in org-mode while we&#x27;re collecting them because plain text is easy (and nice) to deal with for revision control.  Everything is maintained in Fossil while it&#x27;s in this state.  Once we&#x27;ve ready to lock the requirements under design controls, we export into Excel via CSV for V&amp;V.  Under design controls, paper hardcopies become the authoritative record; doing things electronically is too expensive for us.<p>It&#x27;d be neat to one day be fully electronic throughout the process…  I could easily see many groups being able to keep things fully electronic, and org-mode is a nice foundation to build a system on top of: it&#x27;s just structured enough, but at the end of the day it&#x27;s human-readable text.  Heinlein said &quot;once you&#x27;re in low Earth orbit you&#x27;re halfway to anywhere&quot;, I say, &quot;once you&#x27;re in org-mode, you&#x27;re half way to anywhere&quot;.