Context
ScopeStack captures view, send, acceptance, reminder, and audit data, but it does not yet present analytics that help teams understand document performance and bottlenecks.
Goal
Add document analytics and reporting views for operational visibility.
Scope
- Dashboard/reporting for:
- Sent documents.
- Viewed vs not viewed.
- Time to first view.
- Time to acceptance.
- Acceptance rate.
- Revision/requested changes rate.
- Decline rate.
- Stale documents awaiting action.
- Reminder effectiveness.
- Template performance.
- Add per-document engagement summary.
- Add template-level performance metrics.
- Support date-range filtering.
UX Notes
- Keep it operational and scannable.
- Avoid flashy vanity charts. Focus on actionable bottlenecks.
- Highlight stale documents and next actions.
Data/Architecture Notes
- Existing
DocumentRecipient, Acceptance, AuditLog, and document statuses may be enough for v1.
- Consider reusable reporting helpers rather than embedding complex queries in pages.
- Date filtering should be URL-backed.
Acceptance Criteria
- Users can view key document workflow metrics for a date range.
- Users can identify stale sent documents quickly.
- Users can see per-template acceptance/revision performance.
- Per-document page shows first viewed, last viewed/reminded, and time-to-acceptance summary.
- Tests cover metric calculation helpers.
Dependencies
- No hard dependency, but recipient routing and completion certificate data will improve analytics quality.
Priority
P1/P2. Useful for teams once document volume grows.
Context
ScopeStack captures view, send, acceptance, reminder, and audit data, but it does not yet present analytics that help teams understand document performance and bottlenecks.
Goal
Add document analytics and reporting views for operational visibility.
Scope
UX Notes
Data/Architecture Notes
DocumentRecipient,Acceptance,AuditLog, and document statuses may be enough for v1.Acceptance Criteria
Dependencies
Priority
P1/P2. Useful for teams once document volume grows.