Locate the work.
A deliverable register sits alongside progress, decisions, team and activity.
Consulting client workspace / Interface design
The work under review.
The work under review.
The version in question.
A consulting workspace that connects engagement progress, document review, revision history and milestones.
We designed Morrow around the work a consulting team shares with its client. The overview shows the engagement; the document screen gives a particular deliverable space for review and discussion.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Professional services
- DESIGN FOCUS
- Deliverables, revisions and review decisions
01 / THE CHALLENGEA progress summary
A progress summary
cannot explain a decision.
We needed to distinguish work completed from work still waiting for review.
An engagement contains several kinds of information: deliverables, deadlines, responsibilities and feedback on specific versions. We separated them into four screens while keeping the engagement navigation consistent.
The overview gives the client a starting point. From there, a reviewer can open a deliverable, inspect its revision history or look at the milestone schedule without searching a single crowded dashboard.
02 / THE STRUCTUREOne engagement.
One engagement.
Four useful views.
We built each screen around a different level of detail.
Read in context.
The blueprint preview, discussion and review checklist share a document screen.
See what changed.
Three retained versions include text comparisons and dated review history.
Understand dependencies.
An eight-week schedule shows ownership, checkpoints and a blocking dependency.
03 / DOCUMENT REVIEWKeep the discussion
Keep the discussion
beside the deliverable.
We gave the blueprint a designed preview rather than reducing it to a filename and download button. The document, annotations and review checklist can be examined in the same workspace.
Version-specific discussion makes the object of a review explicit. The revision screen then supplies the history: which version came before, what text changed and when the review happened.
04 / ENGAGEMENT PROGRESSProgress at a glance.
Progress at a glance.
Dependencies in detail.
The overview shows 67% progress against eight completed items out of twelve. We kept the underlying register visible so the percentage has a count behind it.
The milestone view answers a different question. It shows the sequence of work, its owners and a blocking dependency. A percentage alone cannot explain why a particular checkpoint is waiting.
05 / THE DELIVERYA workspace for review,
A workspace for review,
with the history attached.
We used an aubergine navigation rail and quiet work surfaces to keep the application structured while leaving the documents readable.
From engagement to document.
The overview and review screen serve different reading tasks.
Retained revisions.
Earlier versions remain available alongside meaningful text comparisons.
Visible dependencies.
The schedule gives checkpoints and blockers their own view.
DELIVERED SCOPE
Self-initiated portfolio project: four front-end screens with authored engagement, document and review data. Morrow and the client identities are illustrative. This is not a deployed client portal; authentication, permissions, durable approvals and document storage are outside this build.
06 / ON SCREENA closer look.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
4 views Select any view to explore
How does your client
review the work?
We design client workspaces around your deliverables, review responsibilities and approval process.