Capture what your jobs need, then turn it into your own documents

Also in Custom fields & documents

Fieldsets on projects and customers

The roof belongs on the project. How the customer likes to be contacted belongs on the customer.

Build them with Dave

Ask Dave for a fieldset or a document template and he says what he'll change first.

Frequently asked questions

What field types can I use?

Text, long text, email, select, multi-select, yes or no, number, date, web address, upload and user, plus nested fieldsets for grouping. If you need a type that is not there, tell us.

Can custom fields go on customers as well as projects?

Yes. Project fieldsets appear on every project and hold the job's data. Customer fieldsets appear on every customer record and hold what is true of that person on every job.

Can I track permits and inspections with custom fields?

Yes. Add fields for AHJ permit numbers, inspection dates and utility interconnection references to a project fieldset, and they sit on the job where reports and documents can use them.

How do custom field values get onto a document?

Document templates reference custom fields by their identifiers. When you generate a document on a project, Payaca reads the project's fields and custom fields at that moment and writes their values into the document, including multi-select choices and uploaded photos.

Can customers sign the documents?

Yes. Select Require customer signature on the template, then share the document to the customer portal, where any of the customer's contacts with portal access can sign it. You can also capture the signature on site in the mobile app.

Can Agent Dave build fieldsets and templates for me?

Yes. Dave creates and edits custom fields and fieldsets, and creates and edits document templates, working as you and inside your permissions. He says what he is about to change first. Forms that capture data on site are built in the form builder.

Can I rename a field once documents use it?

Yes. The label can change whenever you like. The internal identifier that templates and integrations use is locked once the fieldset is saved, so templates pointing at it keep working.