Business application2026-08-16
A work order from request intake to a completed visit
The office opens a work order and assigns a team. Field staff update the job, while administration manages customers, expenses, invoices and reports in the same system.
- Client
- Private client (name is not published)
- Type
- Field service application
- Users
- Administration, teams and field staff
- Scope
- Orders, customers, teams, shifts, expenses, invoices and reports
- Status
- Active private application
- Technology
- PHP 8.3 · MariaDB · PDF
Problem and context
Work orders and teams
A request becomes a work order with the customer, location, appointment and status. Administration assigns a technician or team and sees recent orders and current employee status on the dashboard.
Work on a phone
On a phone, field staff open assigned orders and record the progress of a visit. Shift controls and live connection status support daily work outside the office without separate manual records.
Expenses, invoices and reports
Expenses are grouped by category and period, while invoices have their own payment records. Reports can be reviewed monthly, yearly, by technician or by team.
Outcome
Privacy in the public presentation
Public images use an isolated copy of the interface with test customers, addresses, staff, work orders and amounts. No active service data was copied into the portfolio.
Gallery
A closer look at the project.

FAQ
Frequently asked questions
Does it work on a phone?
Yes. The field view is designed for short phone interactions, while the dispatcher receives a broader overview.
Which records does the demonstrated product connect?
Work orders, customers, teams, users, shifts, expenses, invoices and reports.
Do public images contain data from the active service?
No. They use test people, addresses, work orders and amounts in an isolated interface copy.
Next step
Have a project that needs to work better?
Send me your goal and current situation. I will reply with a concrete scope proposal.
Start a project