1. SMART Doc® 3.0 E-Signature Data Points

2. Request Level Signers’ data – Common name container? – Type of signature (either per signer or for all of them) – Email address – Invitation text (inviting the signer to go the signing room) Who to notify after the signing event is completed – Carbon copy – eMCIT has a message Place/Location where the ceremony will occur Sequence of signers (for the entire set of documents) Other loan data information Documents to be signed Electronic/paper signing indicator Opt-out/opt-in If we have a use case for two views, what happens with the signature relationships? Modifications: Lender void documents previously sent and send a new set of documents (eMCit?)

3. Document Level Audit trail of the signing Data collection at signing time – Use the document as UI? – Define form fields for data collection? – The signer should be able to change his/hers own information – Assign signer to form field (many to one) – Affidavit (I represent so and so person) Is this pre-populated in the document? Is this part of the signature appearance Need to appear in the audit trail – Fields to be populated by the notary (legal requirements, – Strike-out “he/she/them” / circle / fill-out

4. Signature Placeholder Level Signer name, and its relationship with the transaction signer name (Same signer may sign with diff names on different documents (legal names vs. nick names)) XY location of the signature placeholders (possibly multiple placeholders for the same signer/document) Initials vs full signatures indicator Optional indicator Execution information (hash, date, type) Notary?