The Verbal Change Order: A Walkthrough for Architecture Firms

The original AIA-style owner-architect agreement, with its fee schedule and phase breakdown, is the easy part. Both PandaDoc and Ironclad can hold a standard template, route it for signature, and store the executed copy. This is the stage where the two tools look most alike: a document goes out, a client signs it, and the project starts. The real test comes later, once the project is underway and the scope starts moving.

The base agreement is also where a firm's actual exposure gets set, in the fee schedule's assumptions about site visits, review cycles, and reimbursable expenses. Whichever tool holds the template, that fee schedule is worth reading as closely as the additional-services process it will eventually feed, since a loosely worded base agreement produces more of the add-on requests that follow.

PandaDoc's strength shows up here. A principal who already has a template for additional-services authorizations can generate one from the phone in the parking lot after that call, with the scope description, the fee, and a signature block ready before the meeting ends. The client signs from their inbox that evening. What PandaDoc doesn't do on its own is remind anyone that this authorization needs to exist in the first place; someone still has to remember to draft it before billing for the work.

The template itself is worth getting right once, rather than rebuilding it every time. A good additional-services form names the specific deliverable being added, states whether it's a fixed fee or hourly against a not-to-exceed cap, and spells out how it changes the project schedule. A vague one, "additional lighting design services as requested," creates the same scope ambiguity at the add-on level that a loose base agreement creates at the project level.

Three additional-services authorizations into the project, a fourth request comes in for site visits beyond the number the fee schedule assumed. Ironclad's repository, searchable across every document tied to the project, can answer a question PandaDoc's document builder isn't built to answer on its own: how many site visits has this client already been billed for, and does the fee schedule still cover the ones remaining. For firms running several active projects with the same recurring pattern of add-on requests, that repository view is what keeps additional fees from quietly going unbilled.

The lighting redesign gets built, the fee for it eventually gets invoiced, and the payment arrives about 28.8 days later, roughly the US small-business average¹. None of that delay is unusual. What's worth noticing is how much earlier the invoice could have gone out if the authorization had existed the day the scope actually changed, rather than the week after, once someone remembered to draft it.

Neither tool prevents a principal from saying yes on a call before the paperwork exists; that's a habit, not a software gap. What changes is how long the gap lasts. PandaDoc shortens it by making the authorization fast to generate in the moment. Ironclad shortens the exposure of the ones that were never drafted at all, by making it obvious across the whole project what's been billed, what's been authorized, and where the two don't match.

Small firms with one or two active projects usually have the speed problem: the authorization exists eventually, just later than it should, and PandaDoc's fast template generation closes most of that gap on its own. Firms running six or eight projects at once, each with its own trail of add-on requests, tend to have the visibility problem instead: authorizations exist, scattered across email threads and shared drives, and nobody can say with confidence which ones are still unbilled. That second problem is where Ironclad's project-level repository starts to matter more than how quickly any single document gets generated.

A studio that's growing from the first category into the second usually notices the shift at billing time, when a bookkeeper asks whether a particular round of renderings was ever authorized and nobody can answer without opening three different email threads. That's the moment to move the additional-services trail out of inboxes and into a system that can answer the question directly.

Close the gap between a verbal yes and a signed authorization:

1. Save a standard additional-services form with the scope description and fee fields left blank, ready to fill in.
2. After the call, complete the form and send it for signature within minutes of the verbal approval, before work starts.
3. Log each additional-services request against its project, so extra site visits beyond the fee schedule stay visible.
4. Confirm the signed authorization exists before invoicing, so nobody reconstructs what was agreed at billing time.