For a manager of a company with field crews
What is happening in the company right now, on one screen. Tasks from your phone, and you see who picked each one up.
You see how things stand, assign tasks and know who picked them up and when they were done. From the office or from your phone, over a secure channel.
The example below is a service company with field crews. The company is fictional and all figures are illustrative. For your business the screen is built around your own indicators.
everyone sees the same data, each their own part
channel · HTTPS
Four things the system does
See.
How things stand now: requests, sites, crews, the most urgent addresses. The same content on the large office screen and on the phone.
Assign.
Who, what to do, by when. The assignee is notified at once.
Track.
Who picked it up, who finished, what is overdue. The system raises the most urgent items itself, in the order you set.
Protected.
Apps by role, sign-in with a personal code. Everyone sees only their own part. The server and the data are yours.
One task from start to finish
Three screens: the manager sees, the manager assigns, the assignee acts.
Site at 12 Sadova St
Site supervisor · crew 2
Go out, restore, report the status
by 18:00
Deadline: by 18:00 · 1 h 57 min left
If nobody reacts, the system escalates on its own
You set the events, the recipients and the deadlines. The example is illustrative.
| Event | Who is notified | Time to react | If nobody reacts |
|---|---|---|---|
| Emergency request with no assignee | dispatcher, site supervisor | 15 min | head of division |
| Client has waited for a reply for over a day | account manager | 2 h | head of department, then the director |
| Crew did not submit the daily report | crew leader | by 10:00 | site supervisor |
Tracking of tasks
| Responsible | Tasks | Done on time | Overdue |
|---|---|---|---|
| Site supervisors | 14 | 11 | 2 |
| Account managers | 6 | 5 | 1 |
| Dispatchers | 4 | 4 | 0 |
When there is no signal
The assignee's app keeps data without a connection and sends it as soon as the network is back. The server sits in a data centre with backup power. The system can be linked to messengers and to the accounting software you already have.
How I launch it
Review.
Which questions you ask every day. I build the main screen around them.
One loop.
The manager's screen and an app for one unit. You see the first result on your own data.
Tasks and the escalation order.
Who gets notified and what happens if nobody reacts.
Expansion.
New units, roles and data sources, once the first loop has taken root.
A similar system already runs at a housing management company in Kyiv: residents' requests, web offices for the services and a phone app. See it in my work.
What it costs
$900 – $1,100 a month while the build and launch last
What is included.
The manager's screen, an app for one unit, tasks with deadline tracking and the order in which the system raises overdue items.
What is separate.
New units and a link to accounting: after the first loop, under a separate estimate.
What happens after handover.
The system is yours: code, server, data. Support is at your request.
How this differs from an off-the-shelf service.
This is not a service you rent. The system sits on your server, fits your roles and your order of work, and stays with you.
I name the exact amount after the review: it depends on the number of roles and data sources.
Start with an intro call
First an intro call: half an hour, free. I tell you plainly whether it is worth doing and what price range to expect.
Then, if it makes sense, a review of your task. After it you have a written goal and an estimate, even if you do not go on working with me. I name the price of the review at the intro call, before you decide anything.
+380 67 623 41 70 · realup111@gmail.com
I reply myself, usually the same day.