Best practices for organizing requirements in large projects

[helengrace]

Hello everyone,

I would like to know how other teams organize and structure requirements in large or long-term projects inside Squash TM.
When the number of requirements grows, it sometimes becomes difficult to maintain a clear hierarchy and avoid duplicated or overlapping requirements. We are currentlySprunki Retake testing different approaches using folders, tags and links between requirements.
Do you have any recommendations or best practices for:

naming conventions,
requirement hierarchy,
traceability management,
or version handling?

I would be interested to hear how other teams manage this efficiently in real projects.