UX/UI Design · Byggföretagen · Senior UX/UI design and design system
One reporting flow that makes complex rules easier to navigate
Byggföretagen’s time and payroll reporting was spread across several systems. For administrators working with multiple companies and collective agreements, it was difficult to know where to report different information and which rules applied.
My assignment was to design one shared service, Lösen, where users could start with what they needed to report rather than having to understand how the systems and agreements were organised.
As the sole UX/UI designer, I owned the design work from interviews and workshops to user-tested flows, completed interfaces for desktop and mobile, and a shared design system. I worked closely with the business and developers to create an experience that could accommodate complex rules without making them unnecessarily difficult for users.
- My role
- Sole designer, senior UX/UI
- Year
- 2025
- Industry
- Trade association
- Company
- Byggföretagen
- Scope
- 3 months
- Platform
- Web, desktop and mobile
The short version
The problem
Time and payroll reporting took place across several systems with different interfaces and ways of working. People responsible for multiple companies or collective agreements had to work out where information belonged and how to report it.
The service needed to work for both occasional users and experienced administrators, while still supporting all the necessary rules and requirements.
What I did
As the sole UX/UI designer, I led the design work and conducted interviews, workshops, user journey mapping and usability testing.
Based on these insights, I designed one reporting flow where users start with their task, reuse information from previous months and encounter relevant rules when they need them.
I was responsible for information architecture, interaction design, all desktop and mobile screens, and the design system, working closely with the business and developers.
What it led to
I delivered a user-tested design for a shared reporting service supporting multiple companies and collective agreements. It covered the full journey, from choosing a reporting month to submitting, reviewing and amending a report.
Lösen has since launched. I had left the assignment by then, but the feedback I’ve received on the user flows has been very positive, with reporting described as easier. I don’t have measured outcomes to report.
My responsibilities as the sole UX/UI designer
Research and workshops
I planned and ran interviews, workshops and user journey mapping with administrators and managers from member organisations.
Information architecture
I organised the service around reporting tasks instead of the previous systems.
Interaction design
I designed the full journey, including different collective agreements, recurring reporting and exceptional cases.
Desktop and mobile UI
I created every screen in Figma and adapted tables, forms and report overviews for mobile.
Design system
I owned colours, typography, components and interaction states, with accessibility considered throughout.
Usability testing and collaboration
I tested the flows with users, brought the feedback together and worked closely with the business and developers.
Where we started
Time and payroll reporting was spread across several systems with overlapping functions, different interfaces and ways of working.
For people reporting across multiple companies and collective agreements, it was difficult to know where to submit different information. Users had to understand how the systems were organised before they could get on with their work.
The lack of overview created uncertainty, increased the risk of mistakes and made people dependent on instructions and support.
Understanding how reporting worked in practice
I planned and ran interviews and workshops with administrators, administration managers and technical managers from Byggföretagen’s member organisations.
We mapped how people worked, what they needed to report and where they encountered problems. I brought the findings together and used them to guide the design.
One important insight was that users thought about what they needed to report, rather than which system or collective agreement an employee belonged to.
That became a deciding factor in how I organised the new service.
Two different needs in one flow
The service had to work for people with different levels of experience.
Someone who reports occasionally needs to understand what to do, which information is required and how to move forward.
An experienced administrator reporting for several companies needs to work quickly, reuse previous information and handle exceptions without unnecessary steps.
At the same time, reporting must follow the rules of each collective agreement.
The design challenge
The task wasn’t to remove the complexity of the business, but to decide how users would encounter it.
I chose to organise the service around the reporting task, introducing rules and specific choices only when they became relevant.
That gave us the foundation for one reporting flow that could support different companies, agreements and user groups.
Organising the complexity
Based on the interviews and workshops, I made three overarching design decisions that shaped the new service.
They addressed how users would find the right starting point, when rules would appear and how one way of working could support different companies and collective agreements.
- Organise around the task, not the systemsUsers thought about what they needed to report, rather than which system or collective agreement the information belonged to.
I therefore organised the service around the reporting task. Users start with the relevant month and what needs to be done. Companies, agreements and rules are handled within the same flow. - Introduce rules when they’re relevantDifferent collective agreements require different information. Showing every possible option from the start would make an already complex task harder to navigate.
I chose to reveal relevant rules and fields based on the choices users make.
For example, when adding a new employee, the user selects the collective agreement first. The service then presents the information required for that agreement. - One way of working across companies and agreementsPeople reporting for several companies previously had to switch between systems and learn different processes.
I designed one reporting flow with consistent navigation, steps and core interactions. Differences between agreements are handled within the flow rather than through separate interfaces.
This gives users a familiar way of working even when they report for another company or collective agreement.
Turning the principles into a working flow
These three decisions became the foundation for the rest of the design.
Users should be able to start with what needs reporting, get guidance when specific rules become relevant and recognise the process from one month to the next.
The next step was to design how that would work in practice, from the homepage to a submitted report.
From reporting month to submitted report
Every month brings the same task: work out what needs reporting, enter the information and check that everything looks right before sending it.
I designed one connected flow from the homepage to submission, with ways to review and amend reports afterwards.
The end-to-end flow
The flow shows how the reporter, Lösen and Byggföretagen interact across eight steps.
The reporter starts with the relevant month, chooses manual entry or a file upload, completes the information and submits the report. Lösen brings in previous data and helps highlight anything worth checking.
Once the report has been received, the reporter can return to review or amend the submitted information.
- ReporterOpens LösenThe start page shows the month that needs reporting, with one button.
- ReporterChooses the methodA file from the payroll system or manual, with one line on when each fits.
- LösenBrings in last monthEmployees with agreement, job code and workplace. A file is validated instead.
- ReporterEnters hours and payStraight in the list. A new employee starts with the agreement.
- LösenChecks gentlyAnything unusual is listed with a way to fix it. Nothing blocks sending.
- ReporterSends the reportA confirmation shows what was sent and until when it can be changed.
- ByggföretagenReceives the reportThe month’s working time and pay arrive in one format, whatever the company or agreement.
- ReporterFollows upSent reports with key figures, a search for one person across months, and editing and sending again.
In the flow I designedOutside the flow I designed
I designed the reporter’s journey and the Lösen interface. Step 7, where Byggföretagen receives the report, sits outside the flow I designed.
Reporting a month
Following up on submitted reports
Other ways to work in the service
Report using a file
Instead of entering data manually, users can upload a file from their payroll system. Lösen validates the file and explains if it can’t be read.
Amend a submitted report
A report can be reopened, corrected and submitted again while amendments are still allowed.
Find companies, reports and help
The navigation brings together the user’s companies, previous reports and support. Guides are also available directly within the service.
The decisions behind the flow
Designing the reporting experience meant balancing two needs throughout: making routine work fast while giving users support when something was different.
Many of the most important decisions weren’t about adding features. They were about deciding what should appear, when and how much guidance was needed.
Make routine work straightforward
- Start with what needs doingThe homepage puts the month that needs reporting ahead of other choices. Only once the month is selected do users need to decide between a file upload and manual entry.
- Reuse information that’s already thereFor most administrators, many of the same employees return month after month. Their previous information can be brought in rather than re-entered.
- Fast entry for routine tasks, more room for exceptionsHours and pay can be entered directly in the list, with Enter moving to the next row.
Adding an employee, recording overtime or allowances, or handling multiple workplaces opens a more detailed form. Exceptions don’t need to occupy space in the routine flow.
Help people check without getting in their way
- Warn, don’t blockA large change from last month might indicate a typing mistake, but it could also be correct – for example, because of a bonus or time off.
I chose to highlight unusual values and bring them together before submission, with a way to return and make corrections. Users can still submit the report when the information is right. - Provide safety nets rather than more warningsA removed employee can be restored with Undo. The interface shows when information was last saved, and nothing is submitted until the user explicitly chooses to send the report.
That gives users control without adding another confirmation to every action.
Make reports easier to understand and follow up
- Show the date, not the calculationThe interface displays the exact amendment deadline, so users don’t have to calculate it themselves.
- Show the change alongside the numberA total becomes more useful when compared with the previous month. I displayed both the amount and the difference, helping users spot something worth checking.
- Describe exactly what changedWhen someone amends a report, the history records the specific change, such as “Erik Lind: pay 36,200 → 30,000 SEK”. That makes it easier to answer questions later.
- Make missing months visibleAn unreported month also appears in the report overview, with a way to complete it. Otherwise, a gap can easily go unnoticed.
- Use everyday languageI chose labels equivalent to Sent rather than Submitted documentation, and Edit report rather than Amend submitted documentation.
It’s a small change in wording, but an important part of making a rule-driven service easier to understand.
An interface for desktop and mobile
Lösen needs to display a lot of information at once: employees, hours, pay, collective agreements, changes and report statuses.
I wanted a calm interface where important information could stand out without everything competing for attention.
A visual hierarchy that helps people work
- Give colour a clear purposeWhite is the default for content surfaces. Amber highlights information worth checking, mint green indicates completion and dark teal is used for navigation.
I reduced the number of tinted surfaces as the design evolved. Using colour more selectively made it easier to distinguish what needed attention. - One primary action per viewThe main action uses a filled green button. Secondary actions are outlined or displayed as text with an icon.
The same hierarchy carries through the reporting journey. - Make figures and dates easy to readAmounts use spaces between thousands, such as 38 450 kr. Figures align in columns, and units appear beside the input values.
Dates use readable formats such as 14 Oct or 1–31 Oct 2026, rather than technical date strings. - Use consistent patterns for status and changeLabels for statuses, collective agreements and Last used share the same shape.
Changes are communicated through figures, text and symbols, not colour alone. Locked reports also include a lock icon.
Visible, usable interactions
I designed states for focus, hover, errors, disabled and selected.
Keyboard use was part of the design. Enter moves between fields in the employee list, and Escape closes dialogs. An expanded report has a clear visual indicator.
Together with strong contrast, understandable error messages and consistent navigation, these decisions were intended to support users with different levels of digital experience.
The same work, presented differently on mobile
I wanted to keep the reporting journey consistent on mobile without squeezing desktop tables onto a smaller screen.
- OverviewThe current month’s status and reporting action come first. Previous reports appear as cards.
- ReportingEach employee gets a card with fields for hours and pay. The progress indicator and submit action remain at the bottom of the screen.
- Submitted reportsKey figures appear in pairs. A sort menu replaces the table’s column headings, while unusual values and employee details remain available for review.
The content and tasks stay the same, but the presentation responds to how people use the service on a phone.
Design system and outcome
A design system for the whole service
I created a lightweight design system for Lösen, with shared colours, typography and components across the reporting experience.
As the work progressed, I also refined the visual language: fewer tinted surfaces, a consistent label style and clearer rules for when each colour should be used.
This helped keep the interface coherent as the flows expanded.
Colour
Each colour has a purpose: dark teal for navigation, green for primary actions, pale green for completed states and amber for information worth checking.
I defined colour values and usage rules to keep these meanings consistent throughout the service.
- NavigationDark teal
#253B44 - PrimaryMain buttons
#61D29B - Primary tintDone and labels
#E6F7F1 - AttentionThings to check
#FFF8EC / #8A5200 - SurfaceDialogs and panels
#F4F9FC - NeutralTiles and group rows
#F5F5F5 - FocusFocus ring and selected
#1F7A55 - TextOn white
#1A1A1A
Typography
I used Open Sans with a compact type scale for headings, body text, field labels and key figures.
Amounts and other values use tabular numerals so they line up for comparison.
- Rapportera arbetad tid och utbetald lön
- Rapportera arbetad tid och utbetald lön
- Rapportera arbetad tid och utbetald lön
- Rapportera arbetad tid och utbetald lön
- 136 850 kr
- Kan ändras t.o.m. 13 nov
Reusable components
The interface follows Material UI’s component patterns, allowing developers to build on the technical foundation they already had.
What I delivered
During my three-month assignment, I was the sole UX/UI designer responsible for research, interviews, workshops, user journeys, concepts, interaction design, usability testing and all desktop and mobile interfaces.
I delivered the design for one connected reporting journey, from choosing a reporting month through submission, follow-up and amending a report.
After launch
Lösen has since launched.
I’ve received very positive feedback on the user flows, including that reporting feels easier. However, I don’t have metrics showing how reporting time, errors or support needs have changed.
What I can show is the delivered design, the user-tested flows and the decisions behind them.
What I took with me
This project showed me how important it is to distinguish between the complexity of the business and the complexity users actually need to encounter.
The collective agreements and rules must remain. But people don’t need to see everything at once or understand how the systems behind the service are organised.
I also took away how much small design decisions matter in recurring work.
Using Enter to move to the next row. Seeing a change compared with the previous month. Knowing exactly how long a report can be amended. Being able to undo a mistake.
None of these is particularly big on its own. Together, though, they shape what working in the service feels like, month after month.
For me, this was a clear example of why information architecture, interaction design and visual design need to evolve together.