Skip to content

Custom workflows

If you do it twice,
it can be a workflow.

Eight workflows have pages of their own. Hundreds more were built for one team's specific job — the staff report that eats a Friday, the fee calculation nobody has time to double-check, the owner update rebuilt from scratch notes every single Monday.

What teams automate

Pick anything off this list.
Or something that isn't on it.

101 of them, numbered. If yours isn't here, it's number 102.

01RFI responses, drafted and cited
02Comment letters from review notes
03Submittal review against the spec section
04Notices of violation from field photos
05Sprinkler plan review
06Comment letter response matrices
07Permit application completeness screening
08Punch lists from site photos
09Due-diligence zoning reports
10QA/QC drawing review before you submit
11Re-submittal delta review — what actually changed
12Fire alarm submittal review
13Occupant load and egress width checks
14Daily reports into a weekly owner update
15Accessibility (CBC 11B) compliance passes
16Applicant emails, answered from the file
17Structural calculation package QA
18Feasibility studies — what can this parcel hold
19Submittal registers built from the specs
20Conditions of approval, tracked to closeout
21Hazmat inventory statement reviews
22Multi-discipline comment consolidation
23Drawing-to-spec cross-checks
24Change order backup, assembled
25Code determination memos
26Inspection reports written from voice notes
27Emergency access and turnaround checks
28Deferred submittal tracking
29Basis-of-design narratives
30Zoning and setback consistency checks
31Entitlement risk memos
32Bid scope gap analysis
33Title 24 energy documentation checks
34Fire flow and hydrant spacing checks
35ADU and state housing law screening
36Door and hardware schedule checks
37Stormwater management plan screening
38Pay application backup checks
39Hearing staff reports, drafted
40High-piled storage permit reviews
41Spec sections drafted from product selections
42Valuation and fee calculation checks
43Truss and joist submittal reviews
44Subcontractor scope sheets
45Permit timeline forecasts by jurisdiction
46Certificate of occupancy checklists
47Evacuation and life-safety plan reviews
48Plumbing fixture count calculations
49Construction observation reports
50Lien waiver tracking
51Public records requests, answered from the archive
52Sheet index and drawing set completeness
53Annual operational permit renewals
54Geotech report digests into foundation notes
55Certified payroll and prevailing wage checks
56Short-term rental compliance checks
57Design review board packages
58Impact fee estimates
59Grading and drainage plan screening
60Special event permit reviews
61Window and glazing schedules vs the energy calcs
62Incident reports from field notes
63Business license review against zoning
64Seismic anchorage checklists
65Warranty claim letters
66Historic district design review summaries
67Weed abatement notice campaigns
68Room data sheets from the program
69Utility will-serve letter requests
70Expired-permit follow-up letters
71Panel schedule and load calc sanity checks
72Material substitution requests
73Solar permit fast-track eligibility screening
74Fire pump and standpipe plan checks
75Finish schedule consistency checks
76Schedule delay narratives with backup
77EV charger permit screening
78Value engineering option comparisons
79ADA path-of-travel narratives
80Floodplain development permit checks
81Toolbox talks into OSHA-ready safety logs
82Kitchen hood suppression submittal checks
83Consultant coordination logs
84Encroachment permit reviews
85Preconstruction bid clarifications
86CEQA document summaries
87Right-of-way permit intake
88Mechanical load calc sanity checks
89Permit set vs bid set delta reports
90Stop-work order documentation
91Closeout packages: O&M, warranties, as-builts
92Tenant improvement pre-checks
93Plan review consistency QA across reviewers
94Smoke control rational analysis reviews
95Meeting minutes into tracked action items
96Buyout comparison sheets
97Code cycle diffs — what changed on adoption
98Owner status rollups across projects
99Appeal and determination write-ups
100Transmittals and cover letters
101Permit condition compliance matrices

None of these are products we sell separately. They're the same platform, configured against a different task — which is why a new one takes days rather than a procurement cycle.

The shape underneath

Notes in. Finished document out.

Every workflow on this page decomposes the same way, whether it has a page of its own or was built last month for one team. Read the inputs, split the work, check it against the code and your own files, recombine it into one document — then stop, and wait for a person. The last step is never automated.

Fig. 01 — Any document, from your notes

Your notes, your template, your finished document

  1. Take the instructions the way you'd say them out loud

  2. Pull the context: files, findings, photos, past decisions

  3. Learn the format from documents you've already approved

  4. Research whatever the document has to stand on

  5. Write the draft, section by section

  6. Check it against itself for gaps and contradictions

  7. You edit, approve and send

Want the same thing with a specific job in it? See RFIs & submittals, inspection reports or plan review.

Why it's a workflow, not a prompt

Repetitive work should stop costing you a person.

A prompt gets you one answer, once, if the right person is sitting there to write it. A workflow is the same job made permanent.

01

They run in parallel

A workflow isn't one agent working down a list. It's the work split into pieces that run at once — 40 comments, 214 sheets, six products in a submittal — then recombined into one document. Volume stops being the reason something takes a week.

02

They run while you sleep

Work arrives on its own schedule. A workflow can trigger on a new submittal, a nightly queue, or a webhook from the system you already use, and have the draft waiting when someone sits down. Nobody has to be at a keyboard for the work to move.

03

They run your way

Your template, your letterhead, your local amendments, the phrasing your team has approved a hundred times. A workflow is configured from documents you've already signed off on — not a generic model guessing at your format.

How one gets built

Bring the task. Bring three examples.

We build workflows from the documents you've already produced, not from a requirements document.

  1. Show us the job

    Walk through it once the way you'd train a new hire. What comes in, what you check, what you send out.

  2. Hand over your examples

    Three finished documents you'd be happy to see again. That's where the format, tone and standards come from.

  3. Run it on a live one

    Your next real submittal, side by side with how you'd have done it. You keep whichever one is better.

Looking for the workflows with published numbers? See the workflow index →

Name the task your team dreads.

If it's repetitive and documented, it's a candidate. Bring one to a demo and we'll show it running on your own files.