What is a Change Order?
One coordinated request. One dispatch. Everything you need us to do, delivered in a single shot, as long as the materials are complete and the work fits your plan’s time budget.
Size is not the limit. Completeness is. A change order can be small or large, including work like building multiple new pages, when it arrives ready to execute.
The short definition
A change order is one coordinated request we execute in a single dispatch with MOG, your AI Site Director, fully loaded on your site.
It is not open-ended hourly billing, and it is not a fee for every short email you send. The expensive unit is the dispatch: spinning MOG up with your full site memory, prior decisions, constraints, and audit trail so work can ship in minutes instead of multi-day tickets.
Your plan gives you a monthly count of change orders and a minute budget per dispatch (for example, up to 30 minutes, 45 minutes, 1 hour, or 2 hours depending on tier). Stay inside both, and you are good.
The one-shot rule
If it arrives complete in one message and can be finished within your plan’s time limit for that dispatch, it is one change order, even when the work itself is large.
One coordinated package
You send a single request (email, portal ticket, or chat) that includes everything we need to execute end-to-end. We run it as one dispatch. When the work fits the minute budget, that is one change order on your monthly allotment.
Including, but not limited to: a message that asks us to create 10 pages, with all necessary emails, information, text, images or image locations, structure, links, and other materials attached or linked so we can build without chasing you for missing pieces.
Piecemeal dispatches
Five separate emails on five different mornings are five change orders, even if each note is tiny, because each one boots a fresh dispatch of the Director with full site context.
Incomplete requests that force a second (or third) round just to collect missing copy, assets, or decisions also burn additional change orders. Batch first; send once when you are ready.
The practical test
- 1. Is it one request? One list, one email, one portal ticket, not a drip of half-finished notes.
- 2. Is it complete? Do we have the copy, assets, links, contacts, and decisions needed to finish without a scavenger hunt?
- 3. Does it fit the time budget? Your plan’s minute cap for that dispatch is the ceiling. If the package is ready and fits, you are good to go.
What one change order can include
Examples only, not an exhaustive list. The rule is completeness + one dispatch + time budget, not a menu of allowed ticket types.
New pages (including many at once)
Create multiple service, location, or content pages in one request when final copy, images, and structure ship with the message.
Copy and messaging updates
Headlines, body text, CTAs, hours, seasonal banners, or site-wide wording shifts batched into one list.
Images and media swaps
Hero images, galleries, team photos, logos, with files uploaded or linked and placement notes included.
Forms and contact details
Field changes, destination emails, phone/NAP updates, and related form copy when specified completely.
Layout and section work
New sections, reordered blocks, nav adjustments, or a package of related layout fixes in one coordinated pass.
Mixed packages
Pages + copy + images + emails in the same request are still one change order if they form one ready-to-run package within the minute cap.
What to include so it stays one shot
The more complete the first message, the further your minute budget goes.
- ✓ Goal in one sentence: what should be true when we finish.
- ✓ Numbered list of work items: pages to create/update, sections to change, links to fix.
- ✓ Final (or near-final) text: headlines, body copy, CTAs, legal blurbs. Drafts are fine if you say what is locked vs open.
- ✓ Images and files: attached, Drive links, or media-library paths, with notes on where each goes.
- ✓ Emails, phones, addresses, form destinations: anything that must be typed exactly right.
- ✓ Structure notes: page order, nav labels, which template/section to mirror if you have a preference.
- ✓ Constraints: hard deadlines, must-not-change items, brand rules, pages to leave alone.
Missing materials do not always block us forever, but chasing them often means another dispatch. When you can, wait until the package is ready, then send once.
Monthly change-order allowances
Count is how many times we spin the Director up. Minutes are the wall-clock ceiling for that dispatch. Full plan details live on Forged Sites.
| Plan | Change orders / mo | Time budget / dispatch |
|---|---|---|
| Forged Lite | Up to 1 | Up to 30 min total |
| Forged Basic | Up to 2 | Up to 30 min total |
| Forged Standard | Up to 3 | Up to 45 min total |
| Forged Professional | Up to 5 | Up to 1 hr total |
| Forged Pro | Up to 10 | Up to 2 hrs total |
Change-order time always includes work with the MOG AI Site Director, so these minute budgets go further than traditional web-design hours.
Worked example: 10 new pages, one change order
This is the shape of a request that stays one dispatch.
You write one email (or one portal ticket) that says: create these 10 pages. You attach or link the final text for each page, the images for each hero and body section, the nav labels, the destination emails for any forms, and a short note on order and which existing page to mirror for layout.
We open one change order, load MOG once on your site, and execute the package. If that full job fits inside your plan’s minute budget for a single dispatch, you have used one of your monthly change orders, not ten.
If instead you send page 1 on Monday, page 2 on Tuesday, and images for page 3 next week, that becomes multiple change orders even though the total work is similar. Same site, same end state, different dispatch cost.
How to submit a change order
Batch your list
Collect every related item and all materials before you hit send.
Send one request
Email us, use your client portal ticket, or message MOG with the full package.
Human review, then live
Material changes still pass a human audit before they ship. You are never talking only to a bot.