Atelier web
Centralise requests.Coordinate the work.
A shared workspace for receiving internal requests, assigning them and finding related documents. This fictional case illustrates the workflows and design choices of a business tool.
- Client
- Atelier — fictional company
- Industry
- Business services
- Year
- 2026
- Expertise
- Web application
The starting point
Context and challenges
In this scenario, teams receive requests by email, track progress in a spreadsheet and keep supporting documents in separate folders. Reconstructing the context of a task requires switching between tools.
The team needs a shared entry point: record a request, identify its owner, track its status and find its documents. The workflow must work for both the people submitting requests and those handling them.
Let every team member know what to handle, who owns it and where to find the information.
Our contribution
Our solution
The project brings request intake and tracking together in a web application. Each request has a record: description, owner, deadline, status and related documents.
The overview shows team priorities. The detail view helps prepare the next action without searching through multiple conversations.
What was delivered
- A request board with status and owner filters
- One record per request: context, deadline and related documents
- A shared schedule to prepare upcoming workshops
- A mobile journey for viewing and submitting requests
Request tracking
A visible owner and status for each task.
Documents in context
Useful documents attached to the relevant request.
Mobile access
View requests and progress on your phone.
The product in use
From request to action
A request starts with context and a priority. The team then appoints an owner, prepares documents and organises the next step. The record preserves these references as the work progresses.
The mobile version follows the same journey: view your requests, check their status and open the relevant information.
Intended benefits
What the project should improve
Find the context and documents in a single record.
Identify the owner and progress of each request.
Share the same priorities across the team.
These benefits are goals for the demonstration scenario. Time savings and adoption would be measured after a real launch.
Fictional demonstration case. No real client outcomes are claimed.Let’s discuss your project