Platform

Build

Connect & extend

Govern & run

Government
EnterprisePricing
Resources

Live sessions

Platform · Documents

Permits, letters, and reports, produced from the record.

Generate PDF, Word, and Excel documents from your data, sign them, send them, and keep them under the same permissions as everything else. And the documents people send in become data.

Illustration of documents generated from one building permit application, BP-2041, for Dana Whitfield at 14 Elm Street. From the same record come the signed permit certificate as a PDF with a QR code, an approval letter as a Word document, and a row in a spreadsheet of permits issued.

Produce

Documents come from the data, not from copy and paste.

A document is another view of the record. The record already holds every name, address, fee, and date. A template puts them on the page, the same way every time, for every application.

  • PDF.

    Permits, certificates, and notices, laid out once as a template and filled with each record’s data, in any paper size.

  • Word.

    Letters and contracts that start from your own Word templates, keeping your letterhead, styles, headers, and footers.

  • Excel and CSV.

    Reports and exports from any list or database query, up to a million rows.

  • QR codes and barcodes.

    Printed on a permit, a badge, or a notice, so anyone can scan their way back to the record.

Tables come from the record’s related data, so a permit lists every condition attached to it and an invoice lists every fee.

Assemble

One package, from many parts.

A decision rarely goes out as a single page. The letter, the permit, the approved plans, and the standard conditions leave together, as one file, in the right order.

PartComes fromPages

  1. Cover letterGenerated1
  2. Permit certificateGenerated1
  3. Approved site planUploaded by the applicant3
  4. Standard conditionsYour fixed file2

One PDFPermit package BP-2041.pdf · 7 pages

  • Merge.

    Combine generated documents, uploads, and standard files into one PDF, in the order you choose.

  • Extract.

    Pull out the pages you need, like a signature page or a single section, or reorder them into a new file.

  • Overlay.

    Place letterhead on every page, or stamp “DRAFT” across everything but the cover.

Sign

Signed the way each document requires.

An inspection report needs the inspector’s signature on the spot. A permit needs the official’s certificate. A contract may come back signed somewhere else. Signing is a step in the workflow, so a permit isn’t issued until the right people have signed it.

  • Handwritten, on screen.

    Applicants and inspectors sign with a finger, a stylus, a mouse, or a signature pad, and the signature appears in the document.

  • Certificate-based PDF signing.

    Officials sign PDFs with their own signing token and PIN, through a signing app on their computer. The certificate never leaves it.

  • Signed elsewhere.

    Documents signed outside the platform come back as uploads, and the process checks that a signature is present before it moves on.

Deliver

To the people who need them, the moment they’re ready.

A document only matters once it reaches someone. The same workflow that decides a document is ready also delivers it. No one exports, attaches, and sends it by hand.

  • By email.

    Attached to the decision notice, sent through your own mail server, Microsoft 365, or Google Workspace.

  • From the portal.

    Applicants download their own permit. Every download checks permissions first, so no one opens someone else’s.

  • To other systems.

    Returned from an API of your own, uploaded over FTP, or stored in Amazon S3.

  • In bulk, on a schedule.

    One document per record, such as every renewal notice due this month, or a weekly export for the finance team.

Keep

Stored under the same permissions as everything else.

Uploaded plans and issued permits belong to an application. They don’t get permissions of their own. Only the people allowed to see the application can open them.

  • Uploads within limits.

    Applicants attach plans and photos by drag and drop, within the file types and sizes you allow.

  • Private where it matters.

    Secure folders per role or per person, so each applicant opens only their own files.

  • Your storage.

    On your own servers, or in your own Amazon S3 buckets.

  • Searchable inside.

    The words inside PDF, Word, Excel, and PowerPoint files are found by search, within the same permissions.

Read

What comes in becomes data.

Applicants send licenses, spreadsheets, and letters. Instead of someone retyping them, the platform reads them into the record.

PDFContractor license.pdfUploaded by the applicant

Read into the recordTo check

License number
GC-118204
Contractor
Harbor Line Builders
Expires
Mar 31, 2027
  • Spreadsheets into records.

    Excel and CSV files import straight into the database, adding new rows and updating existing ones.

  • The text of every page.

    PDF and Word files give up their text, ready for rules, review, or search.

  • AI that fills in the fields.

    AI reads uploaded PDF and Word files and returns the fields you ask for, ready for staff to check and save.

Documents go out from the record.Documents come back as data.

Your records already know what the document says.Let them write it.

Bring a permit, a letter, or a report your team prepares by hand. Talk to us, and see it generated, signed, and sent from the record.