Which product boundaries should be set for request categories, service targets, and knowledge links?
Cover request categories, users, forms, attachments, priority, routing, queues, owners, service targets, status, communication, approvals, fulfillment, feedback, reporting, and knowledge links. Treat request categories, users, and service targets as one operated product boundary. A credible first release makes knowledge links observable and defines how exceptions involving reporting are recovered.
Best for: Teams planning Request Management Portal that need to agree on request categories, service targets, and knowledge links before detailed scope.
The first release should connect request categories to knowledge links and expose a clear recovery path for exceptions involving reporting.
Good fit / poor fit
Test whether request categories and service targets require an operated product
This topic is specific enough when request categories has durable state, service targets changes that state, and the team can own exceptions around reporting while observing knowledge links.
Good fit when
Request Management Portal needs a durable workflow connecting request categories, service targets, and observable evidence for knowledge links.
People in the process participant role need a repeatable path from forms through service targets.
The business operator must govern users and intervene when exceptions involve reporting.
Progress can be observed through knowledge links, not merely visits or screen activity.
Choose a narrower model when
An existing tool or simple information surface can already handle request categories without owning its lifecycle.
users does not need separate permissions, history, or accountable state.
No operated workflow must connect forms to service targets.
The team cannot yet name who resolves exceptions around reporting or what evidence is needed for knowledge links.
End-to-end workflow
Trace request categories through service targets and evidence for knowledge links
Use one representative Request Management Portal journey. Keep users, exceptions around reporting, and manual operator work visible so the release boundary reflects the real product rather than an idealized happy path.
1
Frame Forms
Process participant
A person in the process participant role enters with forms and enough context to begin working with request categories.
Business operator
The business operator function defines eligibility, ownership, and the initial state for request categories.
Boundary question
Who may begin with forms, and what makes request categories ready?
2
Establish Users
Process participant
A person in the process participant role creates, selects, or confirms users before progressing.
Business operator
The business operator function validates permissions, quality, and lifecycle rules around users.
Boundary question
Which version of users is authoritative, and which changes need history or review?
3
Operate Service targets
Process participant
A person in the process participant role moves through service targets with visible state, next actions, and feedback.
Business operator
The business operator function observes status, stalled work, and interventions that cannot be safely automated.
Boundary question
Which state changes prove progress through service targets, and where does status branch?
4
Handle Reporting exceptions
Process participant
A person in the process participant role receives a clear recovery path when an exception involving reporting interrupts the expected journey.
Business operator
The business operator function resolves the exception, records the result, and captures evidence for knowledge links.
Boundary question
Who owns exceptions around reporting, and what evidence is needed for knowledge links?
First-release boundary
Scope the smallest release that makes knowledge links observable
The first release of Request Management Portal should connect forms to knowledge links before expanding every variant of communication, integration, automation, or reporting need.
Prove in the first release
Name one primary process participant segment and the exact role of request categories in its journey.
Model the minimum state and permissions needed for users and forms.
Implement one complete path through service targets, including the essential branch around status.
Give the business operator a practical way to detect, inspect, and recover exceptions involving reporting.
Capture evidence of knowledge links so the team can continue, narrow, or revise the product boundary.
Hold until evidence justifies it
Additional audiences, variants, and advanced permissions around request categories and users.
Automation, integrations, and optimization for communication before the core workflow is reliable.
Sophisticated reporting or personalization beyond the evidence needed to verify knowledge links.
Decisions that materially change effort
The number of roles and permission boundaries controlling request categories and users.
Lifecycle branches, approvals, reversals, and recovery paths across service targets and status.
Operational exposure when exceptions involving reporting occur repeatedly or at scale.
External systems that create, change, or depend on forms or communication.
Audit, accessibility, availability, localization, and support expectations attached to knowledge links.
Trust, exceptions, and operations
Assign ownership for service targets, exceptions around reporting, and knowledge links
The interface for Request Management Portal is only the visible layer. The operating model must also govern request categories, keep users trustworthy, and make recovery from exceptions involving reporting practical.
Ownership of Request categories
The business operator function needs explicit rules for creating, changing, and retiring request categories while keeping users consistent.
Who creates or approves request categories, and which roles may change it?
What happens when request categories and users disagree?
Which changes need history, notification, approval, export, or deletion controls?
Control of Service targets
Every important transition through service targets needs a visible owner, especially where status changes the normal path.
Which states make progress through service targets visible to each role?
Where can status be automated safely, and where is review required?
How is duplicated, abandoned, or contradictory work returned to a valid state?
Recovery for Reporting exceptions
A credible release makes exceptions involving reporting visible, gives the business operator a workable response, and preserves evidence for knowledge links.
What can the process participant do when an exception involving reporting occurs without contacting support?
Which evidence does the operator need to investigate and resolve exceptions around reporting?
Which signal demonstrates knowledge links without relying on vanity metrics?
Useful next steps
Turn the planning boundary into an evidence-backed first release
For Request Management Portal, use the Custom Web Application guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.
Plan people or organizations, intake forms, eligibility or triage, cases, stages, assignments, activities, appointments, documents, communications, tasks, outcomes, privacy, and supervisory oversight.
A complete catalog brief with room for deeper research
This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.
This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.