Real Estate Auction Portal

This project was awarded to mobiletech1604 for $1000.28 USD.

Get free quotes for a project like this
Employer working
Awarded to:
Project Budget
$30 - $5000 USD
Total Bids
Project Description

The Auction Portal is a data warehouse that will maintain, update, and store a list of foreclosure auction properties and their attributes. The list is imported from a foreclosure data website in a CSV file that is uploaded to the portal by an administrator. The portal will have a Trustee Query Engine that continuously pings appropriate designated trustee websites to determine the current status of a property.

Each specific property will have its own record in the portal. Within this record, many data points will be entered and edited by multiple parties.

The Auction Portal will be a web-based application accessible via common web browsers.

## Deliverables

Auction Portal

The Auction Portal is a data warehouse that will maintain, update, and store a list of foreclosure auction properties and their attributes. The list is imported from Foreclosure Radar in a CSV file that is uploaded to the portal by an administrator. It will have a Trustee Query Engine that continuously pings appropriate designated websites to determine the current status of a property.

Each specific property will have its own record in the portal. Within this record, many data points will be entered and edited by multiple parties.

The portal will check the Trustee website for each active property to update the status of that property in the portal. The Trustee website will display that date, time, opening bid and location of the property's auction. If an auction is cancelled, it is marked as inactive in the portal. If the auction date is postponed, the portal will update itself with the new auction date. For completed auctions the trustee will display highest bid and if the property was sold to a 3rd party or to the bank. Once the property's auction results are displayed no further updates from the trustee are needed. Auctioned property data will be stored in the portal for historical data reporting.

**Property Attributes / Foreclosure Radar Data Imported to Portal**

| ForeclosureType












OwnerState | OwnerZip












LotSize | EstimatedValue












WinningBid | EstimatedLoanPosition


LoanDocNum LoanAmount










loan3LoanAmount |

In addition to these initial data points for each property, the administrator or users of the portal will be able to add / edit data into the following fields **User Entered Data Fields**. Each time an entry to these fields is made, it needs to be stored in the database by the user entering the data and date / time of the data entry. We may have multiple entries in each field - we must keep record of each entry by username and date / time. For example, if a driver enters a repair estimate for a property, and the auction gets postponed, the admin will be able to see that prior entry and compare with the most recent estimate. There will be rules and alerts programmed into the portal to alert the admin of changes in some of these fields (this will be explained later).

**User Entered Data Fields**

| Upload Photos
Repair Estimate
Occupancy (Vacant/Owner/Tenant/)
Condition Commentary
Driver Notes
Administrator Notes | Block (Permanent Pass) / Accept

Temporary Pass
Property Resale Value

Realtor Notes

Rental Value

Lien Position
Title Notes | Driver Notes
Other Liens
Name Run

Alta's Bid Max | Title Files to Upload
Active BK Judgments
Active BK Date
Monthly Utilities |

**Trustee Query Engine**

The portal will have a Trustee Query Engine that will go out to the Trustee's website for each property to confirm / update the auction status of the property. The engine can determine which website to go to by the Trustee phone number (TrusteePhone). In the administrator panel we will need to be able to tie a specific phone number to a particular Trustee website. The engine will need to be programmed for each Trustee website so it knows how to read the website's results and update the Portal. Some of the Trustee websites require a login, and some will require Captcha. The portal will be able to use one of the Captcha services to automatically enter the Captcha code so that the Trustee Query Engine can run automatically.

As Trustee websites will change from time to time, we will require a programmer who can provide maintenance to update the engine to "re-learn" a Trustee's website when their format has changed.

The Trustee website will give the auction place, auction time, auction status, and opening bid for a property. The Trustee may also display Winning Bid and Sold To (bank or 3rd party) for completed auctions. The administrator will have the ability to change the trustee for a property, which in turn will tell the Trustee Query Engine which Trustee website it should be checking for a status update.

One of the main functions of the Trustee Query Engine is to automatically update the status of hundreds of properties going to auction that day, the next day or days. This saves us time from having to check it manually. Another feature is that this will update the **Driver Interface** and remove inactive auction properties from the Driver Interface saving the driver time. The Driver Interface will be discussed in more detail later.

If the Trustee Query Engine can not get results for a specific property, it will list the reason for that property (unable to connect, connection refused, unable to parse data, etc.) and a timestamp. For a successful query, the portal will timestamp the latest data so we know how fresh it is. We will want to be able to sort our auctions for that day a number of ways. We will want to be able to sort them by failed queries so that we can manually run them and enter the auction data. The system must allow the administrator to manually assign trustee sites to properties via dropdown window.

The Trustee Query Engine must not try to ping all properties at once. The engine must have an interval between queries to the same site so that it does not get blocked by that website. Some randomization of intervals, varying browser descriptions and language types can be used to make each query appear unique. The engine should rotate queries between the various Trustee web sites to further extend the amount of time between queries to the same Trustee website.

**Admin Interface - Add / Edit / Delete Users**

The Admin Interface for User Administration will give the administrator permission to add, edit or delete a user. The Admin panel will have these components:

**User Profile**

- These fields include the user's name, contact information, and login information.

**Geographic Permissions**

- These settings decide which properties a user can see. A property only needs to match one field in order to be viewable to the user. Access All Areas Override will give that user access to all properties.

**User / Admin Data Fields**

Permissions - This is a series of check boxes, one for each **User / Admin Data Field**. If the box is checked, the user will have the ability to enter data for that field. If it is not checked, he will not be able to see that field or add / edit data to that field. If a box is checked here, it will display on the user's report.

**Report Permissions**

- This is a series of check boxes for each **Property Attribute**. If checked, this field will display in their user's report. By default, the auction date and street address must always show in all reports for all users.

**Driver Interface**

- This is a check box that will give the user access to the Driver Interface for their selected properties.


- This is a check box that gives this user most administrator privileges. This user will be able to add / edit / delete other non-administrators. This also gives the user access edit the **Administrator Red Flag Rules** (described below).

**Cashier Check Logging**

- This is a check box that gives the user access to logging their inventory of Cashier's Checks in the system and applying them to a property purchased at auction. Unused Cashier Checks can be marked as "Returned To Bank" or "Other". If they enter "Other" - they can type in a note about the status of that check.

| **User Profile:**

First Name

Last Name

Cell Phone

SMS Alerts Y/N | **Geographic Permission:**

Zip Codes

Access All Areas Override Y/N |

**Daily Auction List**

The User or Administrator can view a list of auction properties for a particular day. From this list they can edit / add data in the fields that they have permission to see. They can also BLOCK or ACCEPT a property. A BLOCK means that we will never buy this property for some reason. If it comes up in the auction file again, it will be marked as "BLOCKED". Only Administrators can UNBLOCK a property.

**Driver Interface**

The day before an auction, a Driver will drive to each property to evaluate it and enter data into the Alta Auction Portal. The **Driver Interface** gives the user a logical driving order of their properties based upon their current location.

Before a driver goes to their next property, they will click on that property and the Portal will check to see if that property's auction status is still active or postponed. If a property has been postponed, the system prompts the driver to skip that property and go to the next active property in the driving list. A property can also become inactive by it being marked as a temporary pass or a permanent pass by another user or administrator.


If the owner address and property address do not match, the system will list the Occupancy as Tenant. If the owner address is a PO Box but it is in the same city as the property address, the Occupancy will be listed as Owner.

Only an Administrator can unblock a property.

If a driver marks a property as Vacant (Occupancy), that action can override all other Occupancy entries. If a property is marked as Owner (Occupancy), the Administrator can override entry.

Many more rules will be created during the development and testing of the portal.

**Red Flag Alerts to Administrators**

* If a property goes from Vacant to Owner or Tenant Occupancy.
* If a Repair Estimate changes by more than 15% since the last Repair Estimate.
* Any Lien Position or Other Liens changes.
* NOA changes.

**V2 - Future Features**

These are features and components that we will add in Version 2 of the Alta Auction Portal.

* Renovation Worksheet
* Rental Model Pricing
* Flip Model Pricing
* Track Properties Sold To 3rd
* Track Properties Sold to Bank
* Automatic Download of Auction Properties from Foreclosure Radar.

Looking to make some money?

  • Set your budget and the timeframe
  • Outline your proposal
  • Get paid for your work

Hire Freelancers who also bid on this project

    • Forbes
    • The New York Times
    • Time
    • Wall Street Journal
    • Times Online