Admin & dashboards · Design concept
A property administration concept moving from a site overview to maintenance detail and assignment review, with proposed ownership and conflict states.
Design concepts, not client projects. Screens are static mockups; names and data are illustrative.
Keep a maintenance request tied to its site while a coordinator prepares an assignment. The concept separates overall site awareness from the details of one request.
The overview introduces a site-level view of property operations.
Maintenance detail gives one reported issue its own context.
The assignment review provides a separate check before an intended allocation. The concept sends no work order.
A request needs an identifiable site and location. Similar issue descriptions should not make different properties look interchangeable.
Naming a responsible person does not mean a repair is complete. Ownership and request progress need their own labels.
Proposed design specimens. These are static examples, not working controls or a production specification.
Site workspace
#F4F7F8
Navigation & data
#33434E
Assignment actions
#167F81
Clear information. A considered next step.
Use a sans-serif family with stronger request titles and readable location labels. Keep status text explicit rather than reducing it to coloured dots.
Group site information separately from request history. Leave room around assignment controls for reviewing the destination and responsible person.
No open requests
No open maintenance requests match this site and filter.
Assignment ready
Assignment ready to review. The maintenance request is still open.
Request changed
This request was updated. Review the latest details before assigning it.
Assignment identifies responsibility, while status describes progress. A request may have an owner and still need assessment or work. Separate labels avoid implying that allocation itself resolves the issue.
