Document expiration & signer portal

summary

Starting at the beginning

I started at Stavvy as the first in house designer and 18th employee. The original standalone eSign functionality was one of my first bigger projects. Banks and vendor companies mainly use stavvy's platform for their life cycle of loan origination - from uploading documents to closing on a home. At the time you could only access the ability to sign document through digital signing meetings which was causing frustrations for those who didn't aim to complete their closing digitally. We implemented a basic flow that would allow users to name a document packet, upload their documents, assign signers, place annotation fields, and send these to their signers to sign in our existing portal.

Due to a majority of customers being in the mortgage lending field, this later led to requests for more customization on when users would be able to see and sign these documents.

The problem

Lender and vendor companies want more control over when users can sign their documents

Users wanted more customization not only when creating their packets but also within the signer portal. The current signer portal was outdated, built without the ability to preview a document before signing, and lacked a clear step by step flow to guide the user both through a regular eSign experience and also when going through the steps to complete a mortgage closing.

THE GOAL

Designing a more intuitive experience

Based of the list of user requirements, we came up with 2 main goals.
• Add signing window and preview options to documents
• Redesign the signer portal and streamline the signers process

Since I would be updating eSign packets in the signer portal, I also had to make sure these changes would work for meetings as well.

THE PROCESS

Competitive research

While splitting the project into two parts, I conducted audits on other platforms such as docu-sign, panda docs, hello sign, sign now, adobe sign, trello, and qualia.

User flows

Mapping out all avenues

After collecting competitive research, I created preliminary flows for how to set packet expiration, what happens when documents expire, how users will receive documents that have a time box, and if individual document expiration is needed in the future.

ITERATING

Visual Iterations

I went through multiple iterations, conversations, and testing. Some changes came about due to development constraints such as removing the idea of a pizza tracker.

Setting expiration

I went through many routes with settings expirations from hiding the ability set expiration behind a button to allowing a user to set individual expiration on each document. These options were too hidden and required too many clicks for the user when only one setting option was being added but were good potential explorations for the future.

Signer portal cards

I experimented with many different card and wording iterations. Users preferred the versions that had very clear wording on what the current step is and what the next steps would be and our lender customers requested listing out which items users needed before joining a meeting so they knew what to prepare for their next steps after they are done signing documents.

Checking in with stakeholders