Questions, answered

Click Get started, then use Proto to configure Field Installation PSA for your business. Begin with one organization, an active site, a named installation manager and a representative engagement. Rehearse a work order submission and a milestone invoice before adding more locations.

It holds the site, owning organization, manager, installation type, contract value, budget hours, dates and delivery status. Linked field work and milestones let the team inspect progress against that baseline.

Yes. Each installation engagement links to a site, so the site remains the shared location while each engagement keeps its own contract and delivery history.

The configured check approves a billable line with hours and an installation engagement. It records a review decision and operation receipt. A line that fails the check stays Submitted with a Failed receipt for correction.

Technician hours link a work date, hours, technician, site and installation. Travel and expenses carry a date, category, amount and installation link, with a receipt URL when applicable. Managers review their submitted statuses separately.

The Installation Manager reviews the submitted deliverable and amount, then records the Approved status. The Billing Coordinator handles the subsequent invoice action.

An approved milestone with no amount or no installation engagement stays Approved and receives a Failed operation receipt. Correct the record and review the result of the next invoice action.

A payment record links to a milestone and carries its amount, invoice number, due date and status. When it is marked Received, the payment receipt workflow records the app operation. Reconcile that record with the outside collection source.

Use the Installation Margin Desk to compare contract value, delivered and billed amounts, and cost signals. Open the installation record behind a signal to inspect its work and milestone sources.

Record attachments can link contracts, statements of work, receipts, deliverables, change orders and screenshots to supported records. Agree where the files are stored and how their links will remain available.