Demo or small Incoming/Outgoing mailing system needed asap

Here is the translation of the project I should come up with in less than a week. Its a basic incoming/outgoing sorting system, with probably involves 2 databases in total. "Incoming/Outgoing Mailing management" Eveytime the Protocol Dept. employee gets an incoming document, he digitizes it (scanning it or sth like that) and he imports it to the system. During this procedure, the digitized document gets a unique id number (AES for incoming, AEX for outgoing) randomly created. Furthermore, the same employee registers/fills a few more data on the document (ie. date of receipt, senders info, a few content-relative keywords, etc). All these data are saved (including aex and response date -HAA-, which are still blank, as no response is sent back). Every morning, the Process Dept. employee seeks for pending incoming documents (ie. docs without aex number- not yet answered). When he finds one, he reads the scanned image of it, and imports a new empty responsive document to the system (which gets an AEX, cause its outgoing). Furthermore, the same employee registers/fills a few more data on the document (ie. senders info etc). All these data, along with the response date which is still blank and the relative's document AES, are saved separately, while the relative incoming documents are updated with the new AEX. A pending incoming document could be updated (with replacement of the scanned image, for example), till the DATE OF RESPONSE (HAA) is registered, and the responsive document is finalised. Every morning the protocol employee seeks and finds finalised responsive documents, which are written in response to the incoming ones. When he finds one, he "marks" which results in an update to the HAA field of the incoming document, prints it and mails it to the sender of the incoming document. I am to present this software next week, so short delivery times will be appreciated. Furthermore, since I am a cs student working part-time, I would pick the winning offer giving extra attention to the budget matter. You dont have to make it work exactly this way, make all the assumptions necessary, this is just the general idea. You can code it in every way you want, everything will do, though i would prefer it uploaded somewhere online (i will provide the server) and operated through a browser. Finally, a brief user manual with screenshots and 3-4 uml diagrams is necessary upon delivery.