Ease of Use

1. All screens (data entry, reporting, etc) should be intuitive and easy to use. 
2. Major data fields (e.g. Name, Event, etc) should be a hyper-link to the detailed information screen.
3. The data field labels should be user-definable so that we can apply our own language for event and ministry descriptors.
4. The system should resemble a typical Microsoft application with standard and custom toolbars, copy/paste/edit functionality, etc.  It should be easy to navigate between functions (such as using a standard navigation bar on every page).
5. There needs to be a simple “Read Only” version (no login required) for the pastors, receptionist, and other staff who do not manage the data.  We are particularly eager for a mobile computing solution for those who carry iPhones and other data enabled cell phones.
6. It should be easy to filter views of the database into a short, manageable list.

Reporting Tools

1. The system should be able to produce dashboard type metrics and reports that we can use to measure our ministry progress (e.g. # of Small Groups, # of Volunteers, # of Leaders, etc.)
2. There should be a robust suite of reporting tools that can access all data fields (giving, event participation, membership in groups or teams, etc)
3. We should be able to quickly produce new reports, or lists of people that meet criteria that we choose, and they should be easily printed or imported into an EXCEL or WORD document.
4. Reports should be customizable by any user, so that we can explore new ideas and concepts without requiring a software development project.
5. The system should provide tools to quickly and easily manipulate groups of people.

Open Architecture

1. The system should be built on open-architecture, industry standard tools which have readily available software licenses.
2. The system should be easily linked to our web site to serve the congregation for event registration, group and team registration, online giving, and member access for editing personal information.
3. Should co-exist with PC and Apple/Mac environments using a web browser.

Security

1. We should be able to easily control which users have access to different areas in the database.  This includes the ability to control who can read, write, and delete data from the system.

People Management

1. The system should have well defined and easy to use processes for managing family records, contact information, and basic life events. 
2. The system should have the ability to generate customizable tasks based on specified metrics
3. There should be on-click view of “everything we know about a person”. 
4. The system should support our Small Group Management process
5. The system should support our Volunteer Management process by:

Event Registration

1. The system should have a robust on-line event invitation, registration, and check-in process.
2. The registration system should have the capability to respond when one person registers more than one person or families, and to report the total number of event attendees
3. The system should be able to identify the difference between adults, teens, and children
4. The registration system should be able to handle the option of registering children (by age and number) for childcare at an event
5. The system should be able to identify special needs (food allergies, handicap seating, etc.)

Check-in

1. The check-in system should be web based and have the ability to integrate between multiple campuses.  Kids should be able to check into any campus they attend without having to re-register.
2. Families should have the ability to check in at one kiosk for all their children.
3. Check-in should be user-friendly with the ability to have assisted check-in or self check-in kiosks.
4. Check-in should also include ability to check in volunteers.
5. Check-in should have the ability to assign kids to specific classrooms or small group leaders.
6. Check-in should also have the ability to load balance classrooms and small groups.

Contributions

1. The system should be able to handle contribution data entry, batch posting, reconciling deposits, statements and reporting.
2. The system should have online payment and merchant accounts for multiple purposes (tithe, building fund, benevolence, mission trips, CD/DVD/T-shirt sales, etc)
3. The system should have check scanning and image storage capability
4. The system should be able to handle a large volume of transactions in a short period of time.  We expect to be able to process 12 deposits with 2,000 transactions in about 2 hours.
5. The system should provide the ability for each person in the church to access their own giving information and download their own statements.