F.Doc: signing workflows and a clearer status model
F.Doc: signing workflows and a clearer status model

How a three-level state model connected the operator’s overview, an asynchronous signing queue and the document cancellation process.

How a three-level state model connected the operator’s overview, an asynchronous signing queue and the document cancellation process.

How a three-level state model connected the operator’s overview, an asynchronous signing queue and the document cancellation process.

ROLE

Senior Product Designer

TIMELINE

2021—2022

PLATFORMS

Web, Mobile

RESULT

29% fewer status enquiries /
76% of document sets signed

01 THE PROBLEM WITH STATUSES

01 THE PROBLEM WITH STATUSES

“Sent” told us what happened.
Not who we were waiting for

“Sent” told us what happened.
Not who we were waiting for

“Sent” told us what happened.
Not who we were waiting for

Three people are involved in a deal: a customer, a manager and a company director. The existing status model recorded events such as “Documents sent”, but left the operator’s main question unanswered: who is holding things up?

Customers were just as unsure. After signing, they could not tell whether the deal was complete or they still had something to do. Disconnected screens struggled to explain multi-party workflows, driving more questions to support.

02 THE STATE MODEL

02 THE STATE MODEL

Three levels. Each with its own meaning

Three levels. Each with its own meaning

Three levels. Each with its own meaning

One shared status could not explain the whole process. The interface needed three distinct levels: a participant’s action, an individual document’s progress and the status of the full document set.

“Signed by you” could now sit alongside “Awaiting the director’s signature” without contradiction. A shared rules matrix connected state, role, available action and status message, resolving ambiguous behaviour before development began.

03 TWO SIDES OF THE SAME PROCESS

03 TWO SIDES OF THE SAME PROCESS

The operator sees the queue. The customer sees the next step

The operator sees the queue. The customer sees the next step

The operator sees the queue. The customer sees the next step

One screen could not serve both sides equally well. Operators needed to track every participant; customers needed to complete the task in front of them.

The operator view brought together signing order, participant cards and an expandable activity log. The customer view focused on the next relevant action: sign this document, wait for another participant or download the completed set.

One process, two views: the operator manages the queue; the customer sees where their part stands.

04 ACTIONS WITH LASTING CONSEQUENCES

04 ACTIONS WITH LASTING CONSEQUENCES

Cancellation is a process

Cancellation is a process

Cancellation is a process

A signed document cannot simply be erased. Cancelling it requires a separate agreement and another round of signatures.

Two parallel tracks made that distinction visible. The original document set remained active while the cancellation agreement moved through its own signing queue. Each step explained the consequences and recorded the reason for cancellation, helping operators avoid unintended legal consequences.

05 RESEARCH

05 RESEARCH

The hard part was understanding the consequences

The hard part was understanding the consequences

The hard part was understanding the consequences

In a service handling legal documents, a successful click means little if the user misunderstands its consequences.

Two rounds of testing revealed recurring misconceptions: a personal signature was mistaken for a completed deal, and a cancellation request for a cancellation already in effect. The findings led to a clearer separation between personal progress and the status of the full set, with cancellation placed in a distinct warning block.

06 DESIGN SYSTEM

06 DESIGN SYSTEM

State rules, built into the components

State rules, built into the components

State rules, built into the components

To keep behaviour consistent as new document types were added, the state model became part of the design system’s component properties.

Specifications defined required data and combinations that must never occur. The sign button could not be active on a completed set. A failure to send a cancellation agreement could not change the status of the original contract.

07 RESULTS

07 RESULTS

More completed deals.
Less manual checking.
More completed deals.
Less manual checking.
More completed deals.
Less manual checking.

68% → 76%

68% → 76%

68% → 76%

of document sets signed

within 7 days

−29%

−29%

−29%

support enquiries

about document status

22s → 12s

22s → 12s

22s → 12s

time to find the next signer

in the interface

The main outcome was clarity in a complex, asynchronous process. Operators could see where the queue was held up, customers understood the legal consequences of their actions, and new financial products could follow an established set of tested rules.

HAVE A PRODUCT CHALLENGE?

HAVE A PRODUCT CHALLENGE?