Safety-critical systems need a lot of work and expertise to determine they are safe before being deployed into the public domain. Therefore, the safety case of these systems must be robust and comprehensible. This paper presents a potential solution to verifying safety-critical systems at the requirements stage of the project lifecycle by checking for loops within system requirements in the reasoning and totalization of a system specification. By undertaking these checks at an earlier stage in the project lifecycle both time and money can be saved.