This page goes deeper than the condensed features page. It explains the current workflow, role boundaries, approval steps, and export trail without turning into route-by-route help.
The core workflow starts before field work, continues through capture and review, and stays retrievable after completion.
Set up the log with the client, site, planned assignee, product, and timing before work begins.
Review EPA registration context, lifecycle status, and product restrictions before crews move forward.
Record weather, timing, rates, signatures, and notes while the job is actually happening.
Owners and managers can review records, approve start where required, and move completed work through final approval.
Completed records remain available for PDF export, lookup, and audit follow-up.
SprayLedger uses reusable workspace, client, and site data so the next record starts from trusted details instead of repeated typing.
Client records keep the contact and delivery context tied to future logs.
Site records keep the field location and site context ready for the next job.
Once setup is in place, crews can start new logs from known client and site data instead of rebuilding basics each time.
The public story should stay simple: roles separate responsibility boundaries without publishing the full internal permission model.
Oversees company-level setup, role control, and the broadest record-management responsibilities.
Handles day-to-day record review, approvals, and team workflows. Billing access can be granted separately.
Creates and completes field records without taking over review or workspace administration.
Has read-only visibility into records without edit or approval authority.
SprayLedger separates preparation, review, and completed history so active approval work does not get mixed into archive lookup.
Prepared logs can be sent into review instead of being treated as finished immediately.
When start approval is part of the workflow, managers can approve records before field work begins.
Completed work can move through final approval and then stay visible in history for later retrieval.
Export and history claims should stay precise. The product supports PDF output and a traceable record trail, not automatic regulator submission.
Completed records can be exported as PDF when a client, manager, or inspector needs the file.
The export path includes the core record details, signatures, and workflow context needed for review.
Approvals, updates, and status changes remain available for later lookup and audit follow-up.
EPA product lookup is part of the workflow context. It helps teams review product status before field work, but SprayLedger is not the source of record for EPA data itself.
Teams can use EPA lookup to confirm registration details and key product context before the job moves forward.
EPA product context belongs near prep and review so crews are not guessing later.
If the workflow matches how your team prepares, reviews, and retrieves records, the next step is pricing and plan fit.