We are aiming for the following, but will accept anything that covers most of what we need:

1) A page/entry for each organisation that contains lists of the services that organisation is providing.

2) A page/entry for each service (cross-linked to any organisations responsible for it and any events relating to the service), ideally that can be time limited - e.g. I have a project that will be running from April to Oct, it will be taking referrals from Feb until Sep and I need it to appear in search results during that time only.  It should then automatically appear in some sort of archive, but shouldn't appear in current search results for services with open referrals.  Most services will be run by one organisation but some may be run by partnerships or consortia.  One person will take responsibility for maintaining the entry.

3) A diary of one-off events (cross-linked to the organisation and a service, if applicable).  Events might be truly one-off in which case they may not be linked to a service, just the organisation, or they might be part of a wider service.  Most events will be run by one organisation but some may be run by partnerships or consortia.  One person will take responsibility for maintaining the entry.  The events should be searchable.

4) A diary of regular activities (cross-linked to the organisation and a service, if applicable).  The diary should be searchable.

5) Rich text and image handling for any of the pages listed above - ideally with small thumbnails generated for the aggregation (see 6)

6) Some sort of aggregation of news from services on a front page - hopefully automatically generated, but with priority given to items approved by an administrator of the system.  Probably three aggregations - latest service updates, latest activity updates and upcoming events.

7) A facility to automatically email maintainers when their services are expiring or have not been updated for six months (configurable - we may want to change to three months or a year) and to unpublish them if the maintainer does not take action.  They should stay in the archive or an "inactive" section for a year or so, then go offline but stay on the server so the maintainer can revive them or an administrator can choose to delete them later.

8) A search / list facility that defaults to current events, services and activities but has an advanced search where you can: 
select just from the archives, just current, or both; 
select just events, just services, just activities, or any combination; 
limit to a particular organisation; 
limit to a particular type or combination of types, e.g. learning / work / recreation / sports / etc.

9) Simple user interface for org/service/event/activity maintainers, who will not be particularly proficient in IT - no HTML but BBcode or similar might be okay - as long as uploading and including images work.  Ideally, rich text editing with image handling.

10) All of the above should be able to be indexed by search engines.  SEO would be ideal, but not altogether important.