# Synthetic prototype brief

Everything below is fictional.

## Problem

Employees cannot tell whether an IT request is waiting for them, assigned to support, or already resolved. They send follow-up messages because the current portal exposes ticket numbers but not useful status.

## Intended user

An employee checking a laptop, access, or software request.

## Main task

Find a request and understand the next action in less than thirty seconds.

## Prototype scope

- Search by fictional request number
- Show plain-language status
- Show who acts next
- Show the expected next update
- Offer a button to add a comment

## Constraints

- Use fictional requests only
- Do not connect to a real service desk
- Label the page as a prototype
- One HTML file with no installation
- The add-comment button may display a confirmation but must not save or send anything

## Example requests

| Request | Topic | Status | Next action | Expected update |
| --- | --- | --- | --- | --- |
| REQ-1042 | Laptop replacement | Waiting for employee | Confirm delivery address | Today |
| REQ-1088 | Analytics access | With support | Support is reviewing group membership | Tomorrow |
| REQ-1103 | Design software | Resolved | Restart the device and test | Complete |