Case Management Solution

This project will consist of only the back-end programming. A user-interface will be provided. here is a description of the company: The company is involved with financial planning. They provide specialty services to 3rd party clients as a means of “private label”. Basically, a financial firm would approach them to handle a special service for one of their clients, The company would then perform this service as if they were the firm that hired them. Sort of like an outsource for financial firms (but not really). The software we’ve proposed for them is to manage all their clients, contacts, 3rd party contacts, and so on… all members of the company should be able to carry on a conversation on any topic or sub-topic, for any case… Hopefully the outline below will clarify. Objective: A single web-based solution to manage all case related material, tailored to the company’s business model: • establish the progress stage of any and all cases • manage contacts, clients, advisors, institutions on one central platform • communicate with other company employees efficiently and from anywhere In the world on specific and/or general topics through discussion posts • eliminate the need to cross-reference client names, case numbers, agents etc. • have all your information easily sorted, searched, and printed Features: manage any number of cases with each cases holding: • a single or several clients (with individual/personal info) • a reference to an advisor (with individual/firm info) • store dates for the following: o client info submitted o presentation target o delivered to advisor o client response required o client decision • Proposal details: o Loan amount o Reference to Lender (with individual info) o Reference to Insurer (with individual info) o Policy face amount o Initial Deposit o Annual Deposit o Proposal Delivered by (company employee) • Each case will be equipped with a Modification Request Chart that will store the following: o Client-request description o Date of request o Date that the modification is provided o Reference to discussion for this request ** • And finally, a Client Decision (Y/N) manage all aspects of 3rd party involvement: Insurance for each case, client: • Date submitted • Expected EC Commission • 3rd party Agent name • settled manage all aspects of the lending process for each case, client: • loan amount • lender • submitted date • approved date • accepted by client date manage all clients/contacts/advisors/lenders: • name • profession (accountant, lawyer…) • address, phone, cell, fax etc. • firm name • reference to discussion for each contact/client/advisor ** ** Discussion notes: Any and all aspects of the system can carry a conversation among company employees. Discussion notes can then be viewed and sorted either by case, client, contact, or topic. For example, case specific notes will hold the following: • each note will stem from a root topic such as: o commission o medical o financial o lending o closing o general • a reference to the case • date and stamp of the post • the posted note • a post heading • the user that posted the note (i.e. Tom) Another note holder will focus on contacts such as Lenders and Insurers. This will be non-case specific: • each note will stem from a root topic such as: o insurer o lender o advisor • the name of the contact • the posted note • a post heading • (optional - case reference) • posted date and stamp • user Client modification requests will also reference a note holder. Each request note will contain: • case reference • client reference • request reference • posted note • post heading • posted date and stamp • user Admin and security features: Access to the system will be of a secure nature. Each user will be equipped with a username and password. 2 levels of access will grant most users the ability to add and modify content on the system, with a special level of entry for admin users that can: • add and modify content just as regular users • add new contacts (i.e. lenders/insurers) • delete or modify posted notes • create and manage system users