CriteriaTech
Talk to us

Examples.

Everyday jobs we fix, each shaped to fit your business.

Illustration: an invoice copied between an inbox and a spreadsheet.

Getting a yes or no

Buying a laptop stand
Asked byOffice manager
Approved becauseUnder £100
Time waited4 minutes
Example: small purchases don't sit in an inbox.

For anything that waits in someone’s inbox for a yes.

The problem
Purchases, holiday requests, expenses and new starters get stuck because nobody knows who needs to say yes.
For example
A £40 printer cartridge is approved in minutes, not a week.
How we fix it
Requests go to the right person with reminders. Small ones (say, under £100) are approved on their own.
How we’d know it’s working
How long it takes to get an answer, and how many requests got stuck.

Forms and typing things in

New supplier form
Boxes filled in correctly6 of 7
Needs checkingVAT number
Sent toAccounts
Example: mistakes are caught before they're saved.

For information that is typed in more than once.

The problem
The same details get typed into a form, a spreadsheet and the accounts, and the copies don’t match.
For example
A new supplier’s VAT number looks wrong, so it’s flagged before it reaches the accounts.
How we fix it
One form that checks for mistakes, then sends the details everywhere.
How we’d know it’s working
How much double typing is gone, and how many records needed fixing later.

Reports and documents

Monthly report emails
People to send to4
Delivered3
Trying again1
Example: if one doesn't arrive, it's sent again and you're told.

For paperwork that has to look right and reach the right people.

The problem
Reports are put together by hand, checked by eye and emailed one by one.
For example
The monthly sales report goes to four people. One email bounces, so it’s resent and you’re told.
How we fix it
Filled in from data you already have, with your logo, approved by a person if needed, then sent.
How we’d know it’s working
How quickly reports go out, and how many needed fixing after sending.

Booking jobs and sending staff

Tomorrow's jobs
Jobs booked9
Given to a team member8
Needs you to decide1
Example: only the tricky one comes to you.

For teams who plan work and send people to do it.

The problem
Jobs are planned in one place, done in another and confirmed from memory.
For example
Tomorrow’s nine jobs go to the right phones. The one with a clash comes to you.
How we fix it
Each job reaches the right person, and the office knows when it’s done without a phone call.
How we’d know it’s working
How many jobs are finished the same day, and time spent chasing updates.

Getting apps to talk to each other

This morning's update
Records copied across120
Matched up118
Held for you to check2
Example: anything that doesn't match waits for a person.

For the copying people do between two apps.

The problem
Someone has to copy details from one app into another, because the two don’t link up.
For example
A website booking appears in your customer list and calendar, with no retyping.
How we fix it
Details are typed once and copied everywhere. If something fails to copy, you’re told.
How we’d know it’s working
Hours spent copying between apps, and how many details didn’t match.

On-site checks and inspections

One site visit
Boxes checked22 of 24
Couldn't reach2
Report sent4:05pm
Example: the customer gets their report the same day.

For checks that have to be done in person, point by point.

The problem
Paper checklists can be ticked without actually being next to the thing being checked, and reports get written days later.
For example
A pest-control technician scans 24 rat boxes and records each one. This is the first app we’re building.
How we fix it
Each point has a QR code. Staff scan it with a phone app that works without signal, and the report is built from their answers.
How we’d know it’s working
How many checks were confirmed, and how soon the customer gets their report after the job.

Which job takes too long?

Send opens an email for you to check and send. We’ll tell you honestly if we can help.