Tagging jobs increases the power of the dashboard search, making jobs easier to find, and they help you communicate important information with your surveying team.
Tags are fully customisable, and you can use any naming convention. But with the freedom to create any tags you want, it's essential to follow some tried-and-tested tag naming practices. In this article, I'll explain some basic tips to follow when creating and naming tags.
Before we look at some detailed examples, here are some basic pointers of good and bad Tag names.
These Tag names are good as they provide some extra information about the job and they're easily re-usable for different jobs.
These Tag names are poor because either: 1) The same information is already available on the job, so they don't add anything new, or 2) They're too specific to a job and can't be re-used.
If you have a high workload or time-sensitive jobs, you can use Tags to help your team schedule their workload in a sensible order, ensuring they complete high-priority jobs first.
Priority level:
Tagging jobs with their priority level can help you decide which ones to schedule first. Here are some examples:
Urgent jobs:
Another approach, rather than giving jobs a priority level, is to simply Tag the urgent jobs for attention.
On-hold jobs:
You can use Tags to indicate that the job is on-hold, perhaps if it's awaiting input from the client.
When you have a large team, each with different skills, qualifications, and geographical locations, Tags can help you to match jobs to the best person.
Qualifications required:
Tagging jobs with the required qualifications ensures you don’t send an unqualified person to the site. e.g.
Branch / Department:
Do you have staff located in different parts of the country? You could Tag jobs with the relevant branch or office if you have a distributed workforce like this.
You can use Tags to communicate extra information about the job to your team. Here are some examples:
Survey type:
Property type:
Access issues:
You can use Tags to indicate whether a site needs revisiting. You can also use Tags to monitor actions like auditing and resurveys, which you may be required to track for compliance reasons.
Revisits:
Auditing:
Resurveys:
UKAS-accredited companies must re-survey 4% of properties over the year. In this case, it’s helpful to Tag jobs as ‘re-surveyed’ and then run a query to see which jobs have (or have not) been re-surveyed.
Although Flow isn’t designed for billing, storing some basic information about the billing state against the job may be helpful.
Quoting:
Invoicing:
.png)