Every job tracked, every visit on one calendar.

Accepted estimates become jobs. Track each one by phase, and keep your appointments and Google Calendar events on one calendar.

Tracked by phase.

Each job shows its current phase, so you know where it stands without a phone call.

One calendar, with Google.

Your appointments and your Google Calendar events on one calendar, filtered by person or status.

The schedule lives in three places.

A whiteboard, a group text, and someone's head. They disagree by 9am. Nobody's sure which jobs are underway, which are on hold, or what's already on the Google Calendar, so the office spends the day on the phone finding out.

The old way
JAGALX
A whiteboard only the office can see
Every job's phase at a glance
Jobs retyped from the estimate
Jobs created from accepted estimates
No idea which jobs are on hold
Scheduled, in progress, and on hold, on one board
Two calendars that never agree
One calendar, with your Google events on it

Questions the trades ask.

A job shouldn't start as a blank form. It starts as the estimate the customer already accepted, and the calendar sits next to the Google Calendar your team already lives in. That's the whole design.

How jobs & calendar is built
Does it work with Google Calendar?

Yes. Your Google Calendar events show on the JAGALX calendar next to your appointments, marked Google, with a link to open each one in Google.

Can I see one person's schedule?

Yes. Filter the calendar by assignee, and by status: booked, rescheduled, completed, cancelled, or no show.

How do jobs get onto the board?

Jobs are created from accepted estimates, so the customer and address come with them. No retyping.

Can I see where a job stands without calling anyone?

Yes. Every job shows its current phase, and the board groups jobs as scheduled, in progress, or on hold. The Today screen lists active jobs too.

How does this connect to estimating and analytics?

Jobs start as accepted estimates, and completed jobs count toward contract value and margin in Analytics.

The rest of the system.

Every part shares one workspace. The call becomes the estimate becomes the job, with nothing retyped in between.