The job record is the center of Easy Install Solar CRM. It stores scope, status, dates, notes, attachments, assignments, communication context, job-level messaging, financial linkage, and audit-style history that helps admins understand what changed and who changed it.
Build clean jobs from the start
When creating a job, treat it as a long-lived operational file, not a throwaway task. Use clear titles, accurate due dates, meaningful notes, custom fields where needed, and enough detail that the next person can act without a back-and-forth call.
The job form supports attachments, custom fields, reminders, recurring settings, and direct linkage to the larger operational workflow. The more disciplined the initial record is, the more useful dashboards, AI, reports, and reminders become later.
- Use due dates consistently because they feed reminders, AI answers, and planning views.
- Put urgent context in the job notes so it stays attached to the record.
- Use attachments for photos, documents, and proof-of-work rather than leaving them in side channels.
Use the single job page as your control room
The single job view is designed to be more than a read-only page. It shows operational context, attachments, logs, and threaded communication. Admins can inspect the job log to see who updated the job, uploaded files, or changed state over time.
If your team experiences follow-up issues, the job log is one of the best places to start. It helps distinguish whether the problem came from data entry, missed communication, or a timing gap in execution.
Calendar and map views are for coordination, not just display
The calendar helps teams understand work over time, including recurring patterns and schedule movement. For eligible roles, jobs can be rescheduled by drag-and-drop, and clicking a calendar item can open job detail context and a direct path to the full job page.
The map view helps coordinators understand geographic workload and dispatch patterns. If you manage crews across locations, use map view to spot clustering, travel inefficiency, or route overloads more quickly.
Attachments and image galleries should support trust
Attachments are not just file storage. They provide proof, clarity, and continuity. The CRM supports cleaner image viewing, uploader metadata, and richer context on job attachments so teams can understand what was uploaded, by whom, and when.
A good practice is to standardize attachment use: before photos, after photos, documents, signed forms, and exception notes. That consistency makes job review and closeout much easier.