Product guides, feature references, and developer documentation — from your first facility upload to a fully automated pest management program with API and SSO.
Set up your organization, invite your team, and complete the guided onboarding checklist in under 20 minutes.
After signing up, PestMetry provisions a private workspace scoped to your organization. Add your company name, primary time zone, and default measurement units under Company → Settings. These become the defaults for facilities, schedules, and reports you create later.
Open Company → Users to invite teammates by email. Assign roles — Admin, Manager, Technician, or Viewer — to control what they can see and edit. Role permissions are enforced by row-level security on every table, so a technician in one facility can never accidentally access another.
The Getting Started tab tracks the essential setup tasks: add your first facility, upload a blueprint, place your first pick slot, log a pest incident, and generate a report. Completing the checklist unlocks the full feature set and dashboard analytics.
Every major screen ships with a Take a tour button and read-aloud narration. If you prefer to explore on your own, the tour can be relaunched at any time from the header menu.
Organize every warehouse, cold-storage site, and distribution center in one place with structured metadata.
From Facilities → New facility, enter the site name, address, facility type, square footage, and operating hours. Address autocomplete verifies the location and stores latitude/longitude for future mapping and reporting features.
Each user can be scoped to one or more facilities. Users without access to a facility will not see its incidents, work orders, or reports anywhere in the app — even in global search results.
Admins with access to multiple facilities can filter the dashboard, reports, and analytics by any combination of sites. Use this to compare pest pressure and sanitation performance across a portfolio.
Turn physical blueprints into clean digital layouts, then place pick slots, aisles, zones, and pest devices on the map.
Under Mapping → Digitization, upload a PDF, JPG, or PNG of your facility blueprint. PestMetry auto-processes the image — deskewing, cleaning, and rasterizing to a high-resolution digital asset ready for mapping.
Use the mapping toolbar to draw aisles, define pick slots individually or in bulk with the multi-picker, and group locations into zones. Naming conventions and slot numbering can be automated using the slot-numbering helper.
Every pick slot, aisle, or zone on your map can be linked to work orders, pest incidents, cleaning records, and inspection findings. This turns the map into a live, filterable view of operational activity.
Toggle Forecast in the map editor to highlight the areas most likely to see the next pest incident. PestMetry weights recent activity, measures the interval between past incidents, and returns a 0–100 risk score with a probability, confidence level, and expected time window for each area. Set the horizon between 7 and 60 days, then click any ranked area to focus it on the map.
The time scrubber lets you replay activity across a date range — watching incidents cluster, resolutions land, and cleaning coverage expand. Use it during audits, root-cause reviews, and monthly leadership readouts.
Read predicted pest hotspots on your facility map — risk score, probability, confidence, and expected time window — and turn them into scheduled work.
Forecasts are decision support, not a guarantee. They describe how likely activity is to recur based on your own recorded history — always confirm with a physical inspection before closing or reprioritizing work.
Open Mapping → your facility, then click Forecast in the map toolbar. PestMetry loads up to 180 days of incident history for that facility and scores every mapped zone, room, rack row, and pick slot. Predicted areas are painted with a translucent risk wash, outlined with a dashed halo, and labeled with a rank badge; the ranked list opens in the Forecast panel beside the map.
The horizon control sets how far ahead the model looks. Short horizons (7–14 days) are best for weekly routing and this week's inspection list. Longer horizons (30–60 days) are better for planning treatments, deep cleans, staffing, and audit preparation. Changing the horizon re-scores every area instantly — probabilities and time windows update together.
Each area receives a 0–100 score built from recency-weighted incident pressure: a sighting last week counts far more than one last quarter, and severity and volume both raise the score. Use 70–100 as act now, 40–69 as watch and verify on your next pass, and 0–39 as monitor on your normal cadence. Scores are relative within a facility, so compare areas inside a site rather than across sites.
Probability is the modeled chance of at least one new incident in that area within your selected horizon. Confidence tells you how much history supports that number: High means many, well-spaced incidents; Medium means a usable but thinner record; Low means too few data points to rely on. A high probability with Low confidence is a prompt to inspect and gather data — not yet a reason to reallocate budget.
The window (for example "Expected Aug 18 – Aug 25") is derived from the average interval between past incidents in the area plus how much that interval varies. A tight window means a steady, predictable recurrence pattern you can schedule against precisely. A wide window means irregular history — schedule your inspection near the start of the window and re-check the forecast afterward.
Click any ranked area to focus it on the blueprint and review the incidents driving its score. From there, raise a work order, add a sanitation task, or schedule an inspection inside the expected window. After the work is verified, reopen Forecast — a falling score and widening window are evidence the corrective action is holding, which is exactly the narrative auditors ask for.
Forecasts are decision support, not a guarantee, and they only reflect what your team has recorded. Keep incident logging consistent and location-accurate: unmapped or mislocated incidents cannot contribute to any area's score. Brand-new facilities will show mostly Low confidence until roughly 60–90 days of history accumulates.
Log sightings, evidence, and damage; assign corrective actions; maintain full incident history for your records.
From Pest → New incident, capture the pest type, activity level, evidence photos, affected locations, and any product impact. Attach the incident to specific slots or zones on the facility map for spatial analysis.
Every incident supports linked corrective actions with owner, due date, and completion notes. Resolutions capture what was done, by whom, and when — building a traceable chain of evidence you can present during customer, third-party, or regulatory reviews.
Filter incidents by pest type, location, activity level, and date range. Combine with the facility map to identify hotspots, seasonal patterns, and repeat offenders.
Log cleaning tasks, define recurring schedules, and correlate sanitation performance with pest activity.
Cleaning records capture what was cleaned, by whom, the method, and the outcome. Link records to slots, aisles, or zones on the map to visualize sanitation coverage in the same view as pest activity.
The sanitation calendar supports daily, weekly, and monthly recurrences with owner rotations. Overdue tasks surface in the notification panel and the Getting Started widget.
Analytics highlight zones where sanitation frequency lags and pest incidents rise. Use this to redirect labor to the highest-impact areas.
Create, assign, and verify corrective actions across teams, with completion evidence and printable summaries.
Create work orders manually or from a pest incident, inspection finding, or overdue cleaning. Assign to a user or role, set priority and due date, and attach photos or documents.
Assignees complete work orders with notes and completion photos. Managers verify and close, or reject with feedback. Every state change is timestamped and attributable.
Individual work orders can be printed for on-floor use. Bulk export to CSV for external reporting or audit deliverables.
Track traps, monitoring stations, and control devices — service history, inspections, and captures per device.
Add traps, glueboards, insect light traps, and rodent stations to the facility map. Each device carries a unique ID, install date, and service schedule.
Log each service visit — captures observed, condition, replacements, and notes. History is retained indefinitely and exposed in device-level and program-level reports.
Filter devices by service status to prepare for third-party audits. Overdue devices flag automatically in the dashboard and notification panel.
Generate structured reports, schedule recurring email delivery, and export raw data for third-party analysis.
From Reports → New, pick a template (pest activity, sanitation performance, work-order completion, device servicing), scope by facility and date range, and generate. Reports render as branded PDFs with linked CSV data.
Professional and Enterprise plans can schedule any report daily, weekly, or monthly to a list of recipients. Deliveries are logged in Reports → Schedules with status, timestamps, and downloadable copies.
Every table view supports CSV export of the current filter. Enterprise plans also expose full data through the public REST API for BI tools like Snowflake, BigQuery, and Power BI.
Stay ahead of overdue tasks, upcoming inspections, and critical incidents with in-app and email alerts.
PestMetry sends notifications for new assignments, overdue work orders and cleanings, high-severity incidents, and scheduled report deliveries. Each category can be toggled per user under Profile → Notifications.
The sanitation and inspection calendar shows every scheduled task in weekly or monthly view. Drag to reschedule, click to reassign.
Manage users, group them into teams, and control access with role-based permissions.
Admin, Manager, Technician, and Viewer roles map to sensible default permissions. Custom permission overrides are available on the Company → Users screen for edge cases.
Group users into teams (e.g., Sanitation, QA, Third-party PCO) to assign work orders and route notifications at the team level.
Every create, update, and delete is attributed to a user and timestamped. Admins can export a full activity log for security reviews.
Read and write incidents, cleanings, work orders, facilities, and pick slots through a token-authenticated REST API.
Enterprise admins can create API keys under Company → API keys. Each key is shown once at creation — store it in your secrets manager. Keys are scoped to your organization and can be revoked at any time.
Send your key as a bearer token: Authorization: Bearer pk_live_… — over HTTPS only. Requests are rate-limited to 1,000 per hour per key on a sliding window.
Available endpoints include GET/POST /v1/incidents, GET/POST /v1/cleanings, GET/PATCH /v1/work-orders, GET /v1/facilities, and GET /v1/pick-slots. Full request and response schemas are documented at /docs/api.
Receive real-time notifications for incidents, cleanings, and work-order lifecycle events with HMAC-signed payloads.
Under Company → Webhooks, add a URL and select the events you want to receive: incident.created, incident.resolved, cleaning.logged, work_order.assigned, work_order.completed.
Every delivery includes an X-PestMetry-Signature header containing a timestamp and HMAC-SHA256 signature of the payload, computed with your endpoint's signing secret. Verify before trusting the payload.
Failed deliveries are retried with exponential backoff up to five attempts. Every delivery — successful or failed — appears in the Webhooks log with status code, response time, and a resend button.
Send any report to any inbox on a recurring cadence — with branded PDF and CSV attachments.
From any generated report, click Schedule delivery. Pick recipients, cadence (daily, weekly on a chosen day, or monthly on the 1st), delivery time, and time zone.
Reports → Schedules lists every schedule with next-run time, last-run status, and pause/resume/delete controls.
Every send writes to the delivery audit log — message ID, recipient status, and any errors — so you always have a delivery paper trail.
Enforce single sign-on for your entire organization with your identity provider of choice.
Under Company → SSO, provide your IdP metadata URL and the email domains you want to enforce SSO for. PestMetry issues the ACS URL and Entity ID for your IdP admin to complete the trust.
Any SAML 2.0 IdP is supported — Okta, Azure AD / Entra ID, Google Workspace (SAML), OneLogin, JumpCloud, Ping, and more.
Users entering an email at a configured domain are redirected to your IdP automatically. Password sign-in is disabled for enforced domains.
Manage your subscription, seats, invoices, and payment method from a single billing hub.
Starter, Professional, and Enterprise plans differ in facility count, user seats, report scheduling, API access, SSO, and support SLAs. Full comparison lives on the pricing page.
Upgrades take effect immediately with prorated billing. Downgrades apply at the end of the current period. Add or remove seats at any time.
All invoices are available under Billing → Invoices as downloadable PDFs. Update payment method, billing email, and tax IDs on the same screen.
Encryption, tenant isolation, and access control — how we protect your data.
Every table is protected by row-level security scoped to your organization ID. No query — from the app, API, or database — can return another tenant's data.
The application and its APIs are served exclusively over HTTPS/TLS. Databases, storage, and backups are operated by our managed hosting providers — see the Subprocessors page for the current list and their published security documentation.
Review our Privacy Policy, Terms of Service, DPA, Subprocessors, and Acceptable Use Policy under the Legal menu in the footer.
Can't find what you need in the docs? Support engineers respond within one business day — and same-day for Enterprise plans.
