It is an unfortunate incidence of home ownership that some type of casualty or property loss is likely to eventually occur, necessitating that the home owner become involved with his insurance company to make a claim and see to having his property repaired/renewed. While some small number of home owners are savvy, or become savvy through repeated unhappy experience, most are ignorant of the process including knowing the full extent of their rights under their insurance policy.
The statistics concerning these claims are surprisingly enormous. For example, there are typically 7 million claims made annually against homeowners policies by individual homeowners for casualty losses not involved in major catastrophes. In satisfaction of these claims, approximately $43 billion is annually paid. That averages to a little more than $6,000 per claim, not including amounts not reimbursed due to deductibles, denied coverage, etc. For these smaller types of claims, a homeowner will typically rely on his insurance agent, friends, or others generally not familiar with the claims process for help in filling out the necessary forms, etc. in order to obtain reimbursement for his loss. In some states, public adjusters are available for hire by a home owner and many of these adjusters are very helpful in obtaining the full benefits allotted under the insurance policy. However, the cost for these adjusters generally prices them out of consideration for hire by a homeowner for a smaller claim, such as the typical claim identified above. Additionally, due to a homeowners naiveté, even for those claims which would justify use of a public adjuster a homeowner forgoes such assistance. For these and other reasons, a typical homeowner may well experience frustration in negotiating through the claims process and end up with a final adjustment or claim satisfaction which is not satisfactory in that his property would not be returned to an “as new” condition, and possibly even short of what he would legally be entitled to under the terms of his policy. It must be remembered that a homeowner is left to negotiate with a claims adjuster who has as his job, the task of negotiating with homeowner after homeowner, on a daily basis, their claims. In essence, the amateur homeowner is dealing with the professional claims adjuster. And, although the homeowner is the insurance company's customer, the insurance company is motivated to do the minimum, and spend the minimum, to satisfy each claim. After all, the insurance company is in business to make money for their shareholders so their motivation is to not help but instead oppose a claimant's request for assistance as to the true range of benefit for claims.
To address these unsolved needs and to remedy those and other shortcomings in the prior art, the inventors herein have designed and developed an on-line, real-time, property and casualty loss estimation system and method for using same to assist an uninitiated homeowner or other property owner in estimating his true loss due to any casualty, while at the same time producing a proof of loss estimate/affidavit for submittal to the insurance company as supporting evidence for his claim. The preferred embodiment of the invention is embodied in a web server, or internet portal, comprising of a computer program that displays a series of interactive web pages presented in a logical set of ordered inquiries, which allows the homeowner, upon accessing the web site and qualifying himself to use the service, to enter the data requested as needed to describe his loss in terms convertible by the computer ultimately into a damage estimate. The initial qualifying portion of the program is preferably gathering identifying data from the user, validating his permission to use the program such as by requiring payment through a credit card or entering data establishing his right to use under a pre-qualified arrangement, and then allowing further access to the program. Once validated, the user is then presented with a series of web pages presenting questions requiring answers before successive web pages are displayed.
There are a number of particularly unique features embodied in the preferred embodiment. For example, one such feature is that the program identifies “matching” issues which go beyond what a typical homeowner would be familiar with. To be more specific, a loss may occur in which a carpet is damaged and needs replacing. In that instance, the homeowner may be offered a replacement for only that portion of his carpet that has been damaged, matched as best as can be matched with the undamaged portion. However, in most instances, worn or faded carpet, even after only a year or two of usage, is virtually impossible to be matched and while the “matched” carpet may not be unsightly, the finished result is not equivalent to the finished and fully matching carpet prior to the loss. Many insurance policies in these “matching” situations provide that the policyholder's property is to be renewed or restored to its original condition and that has generally been interpreted to include in this example replacement of all of the carpet with new carpet. The preferred embodiment includes logic that guides the user into providing information concerning matching situations, gathers data relating to those matching elements, and produces loss estimates detailing these matching elements for inclusion in the loss estimate. Matching issues can come up with respect to surface finishes such as carpeting, painting, wallpaper; construction materials such as roof tiles, brick or brick veneer, siding such as aluminum siding, flooring materials such as hardwood flooring; and other elements subject to loss or damage such as might be covered by a homeowner's or other casualty loss policy such as appliances, etc.
Another unique feature includes providing an estimate not only based on the current cost of construction, but also the cost as necessary to upgrade the damaged or related element to present building code, based on the location where the property is. While some repairs would necessarily require compliance with the new code, others would desirably be upgraded to new code and in those instances it is doubtful that an insurance company would voluntarily offer to foot the expenses to upgrade to code. This increased expense would be automatically included in a loss estimate and presented to the insurance company in a claim, and ordinarily approved for payment.
Yet another particularly unique feature includes providing cost estimates which include ancillary costs and other incidentals which, surprisingly, are many times forgotten but which eventually have to be paid by the homeowner in order to get the work completed. Examples include sales tax, permitting costs incurred when obtaining work permits from a local or municipal authority, etc. These costs are necessary to the homeowner being made whole and are properly reimbursable by the insurance company and in most instances are fully included in the coverage. These costs are automatically added to the loss estimate.
The preferred embodiment of the present invention is preferably implemented on a computer, connected to the internet through a web portal for wide access, and user friendly through the use of a question and answer format which guides a user through the process of inputting all the necessary information required to calculate a loss estimate and produce a proof of loss for submittal to the insurance company. The loss estimate includes a series of attachments, forming a schedule which itemizes the necessary tasks to achieve a “renewal” of the property. This schedule is detailed and in a form that is virtually self explanatory to the insurance company to provide a comprehensive backup for the claim. The preferred embodiment utilizes a program written in HTML which accesses a modular database, with the database being readily customized to provide accurate costing information to the construction industry by zip code. That includes labor costs, materials, local practices, etc. Furthermore, the database may be readily updated in recognition of rising prices in times of duress or shortage, as prices can swiftly change should large scale devastation occur in a local area. Other less time sensitive changes are also readily implemented, such as labor union contract negotiations raising labor rates, etc.
Yet another aspect of the preferred embodiment is the modular construct of the cost information within the database. Various common tasks, such as replacing an interior door, involve a number of sub-tasks such as removing the old door, sizing the new door, replacing the door hardware, applying a matching finish to the new door, etc. Each of these sub-tasks themselves involve a corresponding set of sub-tasks, and in some instances different trades such as a carpenter and painter for applying a matching finish. The data base is designed and constructed to allow these sub-tasks to be accumulated and added together to arrive at the finished estimate. This degree of granularity allows for precision in not only maintaining the database, but also provides credence to the estimate that makes it difficult for an insurance company to rebut. This greatly increases the persuasiveness of the proof of loss and likelihood that an insurance settlement will more likely cover the true expenses to return the property to an “as new” or “renewed” condition.
In many instances, the user will be in possession of an insurance company estimate before he makes use of the invention. In those many instances, the user will have the additional advantage of using the estimate as a road map to further help guide him through the process. However, it is also true that in many instances the insurance company estimate will have missing tasks, missing collateral issues such as the matching issues and also code upgrade issues. Thus, the experience with the limited trial uses of the invention has demonstrated a dramatic difference between the calculate loss and the insurance estimate. One such example is that a roof damage was estimated at approximately $1700, the proof of loss estimate obtained through use of the invention was approximately $60,000, and the final settlement paid by the insurance company was approximately $48,000, demonstrating the power and effectiveness of the present invention.
While the principal advantages and features of the preferred embodiment have been described above, a more thorough understanding of the invention may be attained by referring to the drawings and detailed description which follow.
a-2d are a set of diagrams depicting in a logical flow the data entry aspect of the invention;
a-5b are a set of diagrams depicting the use case for simple content management;
a-7b are a set of diagrams depicting the use case for calculation of the loss, generating a loss estimate, and matching; and
a-8c are a set of diagrams depicting a use case for system administration.
The logical flow of the programming is illustrated in the form of the preferred embodiment, and as exemplified in a series of functional diagrams forming the figures. When coupled with the database description attached hereto as Exhibit A, and considered along with the balance of the specification, one of ordinary skill could readily program a computer without undue experimentation to perform the functional operations described herein. As such, this disclosure is to be considered as illustrative of the preferred embodiment, and not limiting.
As shown in the diagram of
As shown in the diagram of
As further shown in the diagram of
The functionality depicted in
As shown in
a-5b depict the administrator's access and management of the content, both for individual users and enterprise users, and for home pages and other page content. Also, depicted is the functionality allowing users and customers to browse and access entry level page displays.
a-7b depict the functionality for a customer to consult, enter data, generate a loss estimate including attending to matching issues, and generate a conclusive report. This feature allows a user to view but not change a claim once started but not yet finished.
a-8c depict administrator functionality to update information, such as cost data (use case 23, 49), geographic information (use case 31), costing rules (use case 26, 21), and other similar kinds of logical routines to assemble and calculate costs.
Attached hereto as Exhibit A is an eighteen page layout, with the pages being assembled six across in three separate rows to go from page 1 to page 18, of the database architecture accessed by the program to obtain information as necessary to perform. Layout as follows:
In general, the architecture is set up in two halves, with the left half storing data relating to setting up the claim including the user entry of data, and the right half providing the data and storage relating to manipulating the data to generate the cost information needed to generate the proof of loss. While the inventors have adopted this particular database architecture, it would be understood by one of ordinary skill in the art that other architectures could be used and that successful operation of the program is not dependent on the particular architecture utilized.
Referring now to Exhibit B attached, a selection of various web page printouts are provided to illustrate the displays presently designed for presentation to a user as he accesses the web site, web portal, or otherwise uses the invention. The first page is a home page asking for the user to register or sign in. The second page is an information page describing the operation of the program and the various opportunities to proceed. Page 3 is an acknowledgement page that signals to a user that they have become qualified to start a claim. Page 4 illustrates the terms of use agreement and asks for acceptance before continuing. Page 5 is a questionnaire asking for insurance company information. Page 6 asks for the insured's (user's) information. Page 7 asks for credit card payment. Page 8 displays the claim number assigned to the user's claim for tracking purposes. Page 9 begins the inquiries asking for information relating to the insurance company loss estimate. Page 10 continues that inquiry, asking about which structures have experienced loss as reflected on the insurance company loss estimate. Page 11 continues asking about the insurance company loss estimate, with room details. Page 12 continues that inquiry, asking about detached structures. Page 13 continues by asking for confirmation of data entered from the insurance company loss estimate. Page 14 begins asking for data entry by the user to supplement the insurance company estimate, asking first for the user to select which of several rooms previously identified that the user wishes to enter data for. Page 15 asks the user to identify the ceiling shape for the room chosen. Page 16 asks the user to provide room dimensions and to identify elements contained within the room such as base molding, doors, windows, etc. Page 17 continues by asking for information relating to cabinetry that may have been contained in the room. It is noted that a running total of the loss estimate is displayed along the lower part of this and subsequent pages, with the program calculating this as the user enters data reflective of damage to the structure. Page 18 then asks for further detailed information for those room elements specified to be in the room previously. Such as the size of a window, etc. Page 19 summarizes the data entered so far for that room, and asks for the user to enter data from the insurance company loss estimate for repairs/renewal of that room. Page 20 asks for floor detail information and notably further asks the user if the floor has a finish match to the walls, carpet or floor in any other room. As the user is usually familiar with his house, he would know if a finish extends from one room to another, for example from a kitchen floor to a hall adjacent the kitchen. This entry triggers the matching issue, as described herein. Page 21 asks for information on the matching issue, asking the user to specify the room that has the selected matching finish. Page 22 asks for details relating to a wall, and asks if there is a wall having more than one type of finish. Page 23 asks for room details relating to a wall, such as the finish, matching finish issues, light switches, electrical outlets, etc. Page 24 asks for additional information relating to any room having a matching issue, in this example a common room which could be a hall. Page 25 asks for information relating to the ceiling in the room, and the presence of lights, outlets, etc. Page 26 asks detail information relating to any appliances included in the insurance company estimate. Page 27 asks the user to identify the appliances. Page 28 asks information relating to another room, such as a closet. Page 29 then is a room summary, summarizing data entered by the user and the calculation backing up the room total loss estimate displayed on this same page. Page 30 asks for detail about a garage door, to be added to the claim. By now, the user has gone through all the rooms in which there has been damage, rooms into which finishes extend to create matching issues, and this page 31 asks the user if he is ready to view the conclusive report or the proof of loss. The next twelve pages are printouts of an estimate that summarizes and supports the calculated loss estimate based upon the insurance company estimate as augmented by data entered by the user and as augmented by the program due to matching issues, etc. The last page in this Exhibit B is a “Sworn Statement in Proof of Loss” affidavit which is filled out and prepared for signature by the insured, printed out from the program, and which confirms the loss estimate. In sum, the invention thus produces not only a convenient affidavit for submission to the insurance company but also a detailed estimate calculating the cost to repair/renew the property and return it to its pre-loss condition.
Exhibit B is merely illustrative of the many various web page displays which are produced by the invention, and the invention should not be considered as being limited by particular graphics, arrangement, layout or other artistic representation used in these displays. Furthermore, for purposes of illustration, dummy data was used and entered for what would be a limited claim, and the full scope and capability of the invention has not thus been fully demonstrated. The invention should only be considered as limited by the legal scope of the claims appended hereto and their legal equivalents, For example, the present invention has been disclosed in terms of a residential property, but with minor programming and database changes could be adapted for use for commercial buildings, multi-family housing, etc. The present invention could also be made available in CD or DVD format, or otherwise distributed for use on a local computer/printer. Yet other changes would be apparent to those of skill in the art, using the present disclosure to guide them.