I'm in a regulated industry, and we'd be considered a "very small entity". What we're doing is likely overkill for you, but how we go about things might be of

I'm in a regulated industry, and we'd be considered a "very small entity". What we're doing is likely overkill for you, but how we go about things might be of interest. We develop under a spiral process and requirements are right at the threshold of when we'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'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're collecting them because plain text is easy (and nice) to deal with for revision control. Everything is maintained in Fossil while it's in this state. Once we've ready to lock the requirements under design controls, we export into Excel via CSV for V&V. Under design controls, paper hardcopies become the authoritative record; doing things electronically is too expensive for us. It'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's just structured enough, but at the end of the day it's human-readable text. Heinlein said "once you're in low Earth orbit you're halfway to anywhere", I say, "once you're in org-mode, you're half way to anywhere".