Basically, I am building a system to support my business.
I am in the business of protecting engagements and verbal contracts between two parties. When one party wishes to get into an engagement or verbal contract with the next party, they would normally query to see the portfolio or profile of the other party Which they want to get into engagement with.
Based on what they see in the portfolio, they will then decide if they want to be in an engagement with the party.
I want a database built to register these parties with ID numbers with the key information needed by anyone querying them to know about their background and history in honoured engagements and contracts. Eg
Name ,income base value, how many contracts they have ongoing, how many are completed and fully honoured, how much they currently owe according to all live contracts, as a percentage of their income base value , employed or unemployed, stock on loan, etc
The point is to build enough information about each parties dealings over time to help others who make enquiries to decide if they want to get into an engagement or contract with them or not.
Naturally there will be different levels of query: basic, important, deep restricting how much information is made available based on the query level and the person being queried must approve first. Either by text or phone or via app
Secondly, interface to handle this electronically. The interface that queries or loads information on the database must be such that it can operate from phones by directly going to the website and specifically to the information held about the party who’s card was scanned by barcode or near field technology. It must also work seamlessly in places where the Internet is not of best quality. But without approval (one time code sent via text and email ) the query will not be successful
