Non billable hour tracking in Jobber (time clock workarounds)
I use Jobber and am finding the Time Clock feature too limited for my needs. While I don’t plan on switching from Jobber any time soon, I wanted to reach out to the community to see what others have done in this situation. I can’t imagine I’m the only one facing this issue. My main concern is that the "General" time clock category hides too much information. Having only the options for clocking "Job Time" or "General" time leaves a lot of room for error, in my opinion. For example, when a team member has a slow day and completes various "overhead" or "non-billable" tasks, it all gets lumped under "General" time. For our company, these tasks include picking up chemicals from a supplier, fixing a headlight on a truck, delivering door hangers, etc. Relying on team members to make their own notes after the fact or expecting an admin to remember these details later feels unsustainable. If we see that a team member has clocked 5 hours on a job and 3 hours under "General" time, it could easily be mistaken for them simply forgetting to clock out for the day. My team is small, but I imagine this issue is even more pronounced in larger teams. Can anyone suggest workarounds or solutions they’ve found? Maybe I need to put more focus on verifying these manual adjustments, but that feels quite labor-intensive. Thanks!
Managing Fill in Jobs
Hi Community! One challenge we face is keeping track of fill in jobs or jobs that need a follow up visit but dont know exactly when it will happen. Having one central location or a way to keep track of all of these for easy reference would be key. We try to use the job status' as much as possible but turns out this does not always work. The work around we have done is creating a new customer named "Fill In" then created a new job titled "Fill In Jobs List". Now techs or **bleep** can add a new line item with scope of work, estimated duration and job number. Each new line item represents a separate fill in job. This puts all our fill ins in one location and we can reference it then direct to the job number in Jobber for scheduling. This works but don't feel its scalable. Curious what others have been doing for this! Thanks, Carson
