Team
Sample price$24per site, per month
For one to three sites getting started.
- Up to 3 sites and 10 people
- Three sources, any type
- Morning digest and CSV export
See late work before your customers do.
Pallwick pulls jobs from the tools your sites already use and shows which ones are slipping, why, and who owns the next step.
Late work is usually found by the customer, not the team.
Most service teams already have the data to spot a slipping job. It is just spread out, and it arrives too late to act on.
- 01
The story is split across four tools
The order system, the helpdesk, a shift sheet and someone's inbox each hold part of a job. Nobody sees all of it at once.
- 02
The report explains last week
The weekly review is good at saying why jobs were missed. By then the customer has already called.
- 03
Nobody owns the next step
A job waiting on a part has no name next to it, so it waits. The delay grows quietly until it becomes a complaint.
How it works
Three steps. Most teams finish the first two in a day, without changing how they book or schedule work.
-
01
Connect what you already use
Point Pallwick at your order export, helpdesk and shift sheet. It reads them; it never writes back.
-
02
Say what late means, per site
Each site and job type gets its own window. A boiler repair and a solar survey are not judged by the same clock.
-
03
Work the list each morning
Every late job gets a cause, a next step and one owner. The list is short because it only holds what needs a person.
What's included
Everything is in every plan. Larger plans add controls that bigger teams need, not features held back.
- Late and at-risk view
- One list across every site, refreshed every five minutes, sorted by how far each job is past its window.
- Cause tags
- A short list your team picks from when a job slips. After a month you know which causes cost the most hours.
- One owner per late job
- Assign a person and a next step. They get a single message, not a stream of alerts.
- Site comparison
- On-time rate, median delay and top causes per site, side by side, so the weekly review starts from the same numbers.
- Morning digest
- An email at a time you choose with yesterday's misses and today's risks. Readable on a phone in a minute.
- Exports
- CSV on demand or on a schedule, so your BI tool or finance team gets the same data you see.
- Roles and audit log
- Site leads see their sites; managers see all. Every assignment and rule change is recorded with who and when.
- Spreadsheets welcome
- If a source is a shared sheet, map its columns once. No rebuild of your process before you start.
How it compares
Three common ways to keep track of late work, compared by approach. We don't name or rate other products; this is about what each route leaves for you to do.
| Question | Spreadsheet and a weekly review | A BI dashboard | Pallwick |
|---|---|---|---|
| Shows late work | Once a week, after the fact | Yes, once someone builds the view | Yes, every five minutes |
| Says why it's late | In the meeting notes, if at all | Only if the cause is already a field | Cause tags your team chooses |
| Names who acts next | No | No | One owner and one next step |
| Setup | None, you have it already | Weeks, usually with an analyst | About a day: connect sources, set rules |
| Custom charts and analysis | Anything, by hand | Its main strength | Not the aim; export to your BI tool |
| What it costs | Staff time each week | Licences plus analyst time | Per site, per month (see pricing) |
Pricing
Priced per site, because that's how the work grows. Every plan includes every feature above.
Operations
Sample price$19per site, per month
For 4 to 40 sites with site leads and managers.
- Unlimited people and sources
- Roles, audit log and single sign-on
- Scheduled exports and an API
Enterprise
Customagreed per contract
For more than 40 sites or strict data rules.
- Choice of data region
- Uptime agreement and named support
- Help mapping older systems
Sample prices for this template. Replace them before you publish. Taxes may apply.
Questions
Anything else: [email protected]
What can Pallwick read from?
CSV and spreadsheet exports, most helpdesk and field-service tools with an API, and a shared sheet. If a tool can export a file on a schedule, Pallwick can read it.
Do we have to change how we book or schedule work?
No. Pallwick only reads. Your team keeps booking and scheduling in the tools they use today.
How does it decide a job is late?
From the rules you set: a window per site and job type, and the point at which a job counts as at risk. You can change a rule at any time; the change is recorded in the audit log.
Who sees what?
Site leads see their own sites. Managers see every site. Admins manage sources, rules and people.
Where is our data stored?
In the region you choose when you sign up. Enterprise plans can pick a specific region and get a data processing agreement.
Can we try it with our own data?
Yes. The trial lasts 14 days, uses your real sources, and needs no card. If you stop, your data is deleted after 30 days.
Find out what's late before nine tomorrow.
A 30-minute call with your own export open. You'll leave knowing whether Pallwick fits, either way.