Questions, answered

Click Get started, then use Proto to configure Construction Punch List for your business. Pilot one active project and one work package, then rehearse a finding through sign-off, task invoicing and payment receipt.

Create a punch item under the relevant work package, add a clear description and reported date, and assign the responsible team member. Attach a site photo to the same record when it helps the reviewer.

Yes. Each work package belongs to a project and has a manager, delivery type, dates, contract value and budget hours. Punch items, labor entries, job expenses and tasks can all connect to it.

The approval workflow checks billable intent, hours and the work package. An approvable item becomes Approved and receives a review decision and operation receipt. A failed guard leaves it Submitted with a Failed receipt.

A record attachment holds the file URL, kind, uploader and parent record reference. Check that the parent points to the punch item the inspector will review.

Labor entries and job expenses keep their person, package, amount or hours, and status. The submitted lists help the responsible manager inspect those records before acting on package totals.

An Approved task needs an amount and work package. The task invoice action then moves it to Invoiced and records an operation receipt. If either check fails, it stays Approved and has a Failed receipt.

Yes. Payment records carry due date and settlement status. The overdue or disputed list shows cases for collection follow-up, linked to their task.

Manual use follows the platform’s published policy. Agent work, imports and integrations use metered credits, and implementation scope is agreed separately. See pricing.