71 lines
3.2 KiB
Markdown
71 lines
3.2 KiB
Markdown
# Phase 6: Signing Flow - Context
|
|
|
|
**Gathered:** 2026-03-20
|
|
**Status:** Ready for planning
|
|
|
|
<domain>
|
|
## Phase Boundary
|
|
|
|
Client receives a unique email signing link, opens the prepared PDF in any browser without creating an account, draws or types a signature, and the signed document is stored with a legally defensible audit trail. Email delivery, signing page, canvas capture, token expiry/one-time-use enforcement, and audit logging are all in scope. Secure agent download of signed PDFs is Phase 7.
|
|
|
|
</domain>
|
|
|
|
<decisions>
|
|
## Implementation Decisions
|
|
|
|
### Signing page layout
|
|
- Full document scroll — client scrolls through the entire PDF, reading before signing
|
|
- Signature fields use a glowing/pulsing blue outline to draw attention
|
|
- Sticky progress bar at top or bottom: "1 of 2 signatures complete" with jump-to-next navigation
|
|
- Page header shows: "Teressa Copeland Homes" branding + document title + short instruction ("Please review and sign the document below.")
|
|
|
|
### Signature canvas UX
|
|
- Canvas appears in a modal overlay (not inline) — keeps drawing interaction focused, works well on mobile
|
|
- Modal has three tabs: **Draw** | **Type** | **Use Saved**
|
|
- Draw: freehand canvas
|
|
- Type: client types their name, rendered in a cursive font
|
|
- Use Saved: shows saved signature preview with "Apply" button (tab only appears if a saved sig exists)
|
|
- Clear/Redo available within the modal before confirming
|
|
- After all fields are signed, an explicit **"Submit Signature"** button becomes active (or appears) in the sticky bar — one intentional final action
|
|
|
|
### Email design
|
|
- Branded HTML email (not plain text)
|
|
- Sender: `"Teressa Copeland" <teressa@teressacopelandhomes.com>`
|
|
- Body content: document name, expiry deadline, simple instruction ("No account needed — just click the button below"), prominent "Review & Sign" CTA button
|
|
- Agent notification: Teressa receives an email when a client completes signing (client name, document name, timestamp) — no notification on link open
|
|
|
|
### Post-signing experience
|
|
- Full confirmation page after submit: success checkmark, "You've signed [Document Name]", timestamp, download button for a copy of the signed PDF
|
|
- Clean thank-you only — no agent contact info on the page
|
|
- If a client revisits an already-used signing link: "Already signed" page showing signed date/time + download link for their copy
|
|
- Expired links show a distinct "Link expired" message (separate from already-signed)
|
|
|
|
### Claude's Discretion
|
|
- Exact cursive font for typed signatures
|
|
- Confirmation page visual design/layout details
|
|
- How the one-time download link for the client copy is generated (short-lived token or inline with the confirmation session)
|
|
- Mobile responsiveness specifics for the signing page PDF viewer
|
|
|
|
</decisions>
|
|
|
|
<specifics>
|
|
## Specific Ideas
|
|
|
|
- The modal canvas approach mirrors DocuSign-style tooling — familiar to clients
|
|
- "Submit Signature" should feel like a meaningful, intentional action — not accidental
|
|
- Signed date/time on the "already signed" page gives the client confidence they can reference when it happened
|
|
|
|
</specifics>
|
|
|
|
<deferred>
|
|
## Deferred Ideas
|
|
|
|
- None — discussion stayed within phase scope
|
|
|
|
</deferred>
|
|
|
|
---
|
|
|
|
*Phase: 06-signing-flow*
|
|
*Context gathered: 2026-03-20*
|