A once detected need can lose relevance or change shape. The cooperative should be able to recognize how the needs of the members vary over time. An organizational needs map helps link requests, available services, and problems that do not yet find an answer.
I propose to use simple categories and periodic reviews. Requests must maintain the connection with the activity that generates them. Not all needs have the same frequency: some appear daily, others become important during a season or a transformation of the enterprise.
Let's imagine members opening up new departments at different times. The need for initial care can be intense and temporary. Aggregating all requests without considering this stage could make permanent service with capacity greater than the next demand appear necessary.
The map should include unmet requests and information that is still incomplete. Its function is to orient insights, without promising an answer to every need. Reviewing it over time allows you to design services that are consistent with real conditions and to better explain the priorities of the structure.