How do I turn a meeting transcript into requirements?

How to do it

1. 1

   Separate needs from noise

   Mark every sentence that says what the system or the team must do. Opinions, status updates and side stories are not requirements.

2. 2

   Write one sentence per requirement

   Use the ISO/IEC/IEEE 29148 shape: <actor> shall <capability> <condition>. If a sentence needs an 'and', it is two requirements.

3. 3

   Number and prioritise

   Give each one a stable identifier (REQ-001) and a priority. The identifier never changes, even when the text is revised.

4. 4

   Keep the source line

   Store who said it, in which meeting, at which minute. Without that link, nobody can audit the requirement later.

5. 5

   Flag contradictions and open questions

   Two people asking for opposite things is not a requirement, it is an open question that needs a decision.

Good to know

• A requirement is testable when you can write a pass/fail check for it.
• ISO/IEC/IEEE 29148 is the standard that defines the wording and attributes of a requirement.
• Segua.ai keeps a revision history per requirement, so an edit never erases the earlier version.
• Every generated line is labelled as AI output and has to be confirmed by a person.

Related questions

Can I do this without a transcript?

Yes. You can paste notes or upload a document instead; the same extraction runs on any text.

What happens to requirements that already exist?

They are extended, not duplicated. Segua.ai proposes a change you can accept or reject; nothing is overwritten silently.

Which languages are supported?

The transcription detects the language automatically, including a switch mid-meeting, and documents can be written in English, Italian, Spanish, French or German.

Other answers