Short, practical pieces for teams planning a portal or workflow tool. Filter by topic.
intake
Why your intake form is the most important screen
The intake form decides the quality of every brief that follows. Ask for the deliverable type first, then show only the questions that type needs. Make deadline and approver mandatory. Offer examples beside the field, not in a help page. A form that takes four minutes but prevents a day of clarification emails is a good trade.
approvals
Approval routes: sequential, parallel or by exception
Sequential routes are clear but slow. Parallel routes are faster but can produce contradictory feedback. Approval by exception, where a reviewer only acts if they object within a window, works for low-risk items. Most teams need a mix, decided by deliverable type and risk, and the rule should be visible to the requester.
accounts
Single sign-on for customers: when it is worth it
SSO is worth it when your customers are large organisations with their own identity providers and many users. For small customers, email-based login with optional multi-factor authentication is simpler. Design the account model so SSO can be added per organisation later.
intake
Writing status labels people understand
Statuses are written for the customer, not the team. In review means nothing to someone outside; Waiting for your approval says what to do. Keep to six or fewer customer-facing statuses and map your internal ones to them.
assets
Stopping old files from circulating
Old logos spread because the old file is easier to find. A library should show only the current version by default, label superseded files clearly and give download links that always point to the latest approved version.
planning
What to prepare before talking to any portal builder
Collect ten real requests, the current list of statuses, the names of the systems involved and who decides on scope. That is enough for a productive first conversation with us or anyone else.
accounts
Accessibility is part of the brief
Customers include people using screen readers, keyboard only or zoom. Building to WCAG 2.2 AA from the first prototype costs far less than retrofitting. Ask any supplier how they test it.
Cookies and storage
This site uses no analytics or advertising cookies. One essential browser entry remembers this choice. Optional storage is not used before you accept, and is cleared if you reject.