Home / Trust
Trust & honest limitsWe say what it does — and what it doesn’t.
Software for the field should be plain about its limits. Here is where TrueSite draws each line.
Plain limits
Where each feature stops.
| Feature | What it does | What it does not claim |
|---|---|---|
| Bend & fill results | Layout aids that help you plan and check work. | Code compliance. Every result asks for qualified review. |
| E-signing | Records an invited customer’s signature on a proposal snapshot. | Independent identity verification. It proves mailbox access. |
| Payroll | Groundwork for a provider gateway and an ADP adapter. | Live payroll processing. |
| Solar System Passport | A property-centered, permission-aware record. | Government adoption, title authority, or legal proof of ownership. |
| Canvassing | Self-reported visit records with server-stamped time and user. | Proof of physical attendance. |
| GPS arrival | Measures device location against an office-confirmed point. | Proof that work was performed. |
| Proposals | Itemized USD proposals with revisions and PDF export. | Financing, rebates, or tax-credit calculations. |
| Monitoring | Normalizes what supported providers report. | A guarantee of production or a replacement for provider portals. |
| Plan sets | Stores and shares plan sets you upload from your design tool. | A built-in system designer. |
How records are protected
Built so mistakes are hard to make.
Isolation
Company-scoped records
Inventory, sales, and proposals live in company-scoped collections. Reads enforce company boundaries.
Server-side writes
Transactions, not trust
Sensitive changes — stock, sales tasks, proposals — run through validated server-side transactions, not direct client writes.
Retry-safe
Idempotent by design
Stock-changing actions carry idempotency keys so a retry is recognized instead of double-counted.
See TrueSite running on a real job.
Tell us about your operation and we will walk you through the modules that fit — using your own workflow, not a canned script.