The scenario

A contractor bids on city repair jobs. In four tutorials you build one workspace that reads each Invitation to Bid, answers it with a bid, invoices the finished job, and packs many jobs into one transmittal.

Tutorials
Updated 1 min read

A contractor repairs buildings for a city housing agency. Every job starts with an Invitation to Bid and ends with an invoice. Each job has an E-Number, and that number keeps its paperwork together.

Fig. 01The invitation is read once into the job's case. The bid and the invoice fill from it.

One job is one case

Every document for a job lands in the same case, matched by E-Number, and every template after the first reuses its values.

Fig. 02The case for job EQ28416: four documents, one set of values.

What you build

Four templates in one workspace, one per tutorial.

Fig. 03The four templates this series builds.
  1. Capture an Invitation to Bid: read each invitation into a case, by hand or by automation.
  2. Respond with your bid: fill the bid from the case and email it from Gmail.
  3. Invoice the job: fill the invoice on the same case.
  4. Assemble the transmittal: list many finished jobs on one sheet.

Before you start

  • One of your own Invitations to Bid as a PDF, and your invoice form if you use one. Any form works the same way: swap in your own document and values.
  • The first template works on every plan. Automations, runs on a case, email and batch runs open on Pro (Plans & limits).
Fig. 04Your own invitation PDF becomes the first template.

Next: Capture an Invitation to Bid.

We use cookies to keep you signed in and improve the app. See our Cookie Policy.
Manage preferences