A client portal exposes information and actions outside the organisation. An internal portal supports the people handling that work. Both can be useful, but their first-version priorities are different.
Inspect the request behind the screen
Choose a recurring client request and follow it from submission to response. If staff cannot agree on its status or ownership, publishing a status page will not resolve the underlying uncertainty.
An internal view can first establish who acts next, what information is missing and which status is safe to share. A client view becomes valuable when it gives the client a reliable action or answer.
Start externally when intake is the bottleneck
If staff already handle the process consistently but clients send incomplete or scattered information, structured external intake may be the best first step. Ask only for information the receiving team uses and provide a way to correct a submission.
Keep internal notes and client-visible messages distinct. A comment intended for a reviewer should not become public just because both interfaces use the same record.
Avoid two disconnected versions of the truth
Whichever portal comes first, use stable record identity and explicit visibility rules. Test a change in status, a withdrawn request and a corrected attachment from both roles' perspectives.
The first release should complete one interaction. See requirements for an operations portal before turning that interaction into a catalogue of screens.