<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Konstantin Poplevin</title>
    <description>The latest articles on DEV Community by Konstantin Poplevin (@konstantin_poplevin_9a539).</description>
    <link>https://dev.to/konstantin_poplevin_9a539</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4252938%2Fd38b2c55-d294-404c-b081-365bfedd2b28.jpg</url>
      <title>DEV Community: Konstantin Poplevin</title>
      <link>https://dev.to/konstantin_poplevin_9a539</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/konstantin_poplevin_9a539"/>
    <language>en</language>
    <item>
      <title>A simple change-order process for fixed-fee web projects</title>
      <dc:creator>Konstantin Poplevin</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:31:29 +0000</pubDate>
      <link>https://dev.to/konstantin_poplevin_9a539/a-simple-change-order-process-for-fixed-fee-web-projects-2pcn</link>
      <guid>https://dev.to/konstantin_poplevin_9a539/a-simple-change-order-process-for-fixed-fee-web-projects-2pcn</guid>
      <description>&lt;h1&gt;
  
  
  A simple change-order process for fixed-fee web projects
&lt;/h1&gt;

&lt;p&gt;Scope creep rarely arrives as a big new project. It arrives as “can you also…” after the scope was agreed.&lt;/p&gt;

&lt;p&gt;You say yes to avoid friction. Then the extra work accumulates, the deadline stays fixed, and the project becomes less profitable with every “quick” request.&lt;/p&gt;

&lt;p&gt;I kept seeing the same pattern in freelance threads: the change order is supposed to go out, but it never does. The relationship pressure wins, the work gets done anyway, and the loss only shows up at project close.&lt;/p&gt;

&lt;p&gt;Here is the process that keeps coming up as the one that actually works.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Write down what “done” means before the project starts
&lt;/h2&gt;

&lt;p&gt;A change order only works if there is a written scope to compare it against. The proposal does not need to be long, but it needs to be countable.&lt;/p&gt;

&lt;p&gt;At minimum, write down:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the deliverables, in countable terms;&lt;/li&gt;
&lt;li&gt;what is explicitly &lt;strong&gt;not&lt;/strong&gt; included;&lt;/li&gt;
&lt;li&gt;the number of revision rounds;&lt;/li&gt;
&lt;li&gt;who provides assets, access, and decisions;&lt;/li&gt;
&lt;li&gt;how new requests are handled.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;“Five pages, responsive build, contact form, two revision rounds, one training call” is countable. “A professional website” is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. When the request arrives, do not answer yes on the spot
&lt;/h2&gt;

&lt;p&gt;The most useful sentence is some version of:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Let me check how that fits the current scope and come back with the price and timeline impact.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This buys you time, signals that the request is being taken seriously, and avoids the trap of saying yes before you know what it costs.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Price the change, not the relationship
&lt;/h2&gt;

&lt;p&gt;A change order does not have to be a legal document. It needs four things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;what is being added;&lt;/li&gt;
&lt;li&gt;the additional hours or fixed fee;&lt;/li&gt;
&lt;li&gt;the timeline impact;&lt;/li&gt;
&lt;li&gt;a written approval.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Options are useful. You can offer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;approve the change at $X and the new date;&lt;/li&gt;
&lt;li&gt;defer it to a later phase;&lt;/li&gt;
&lt;li&gt;cancel it and keep the original scope.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That gives the client a decision instead of a surprise.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Get written approval before starting
&lt;/h2&gt;

&lt;p&gt;“Sounds good” in a call is not approval. A reply that says “approved, go ahead” is.&lt;/p&gt;

&lt;p&gt;If the client will not put it in writing, that is information about the project, not a reason to start the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Log it and invoice it
&lt;/h2&gt;

&lt;p&gt;A simple log with date, request, hours/fee, approval status, and invoice status is enough. The point is not bureaucracy. The point is that at the end of the project you can answer: what changed, what was approved, and what was billed?&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked example
&lt;/h2&gt;

&lt;p&gt;A five-page website project is fixed at &lt;strong&gt;$4,800&lt;/strong&gt;, with a 50% deposit and 50% on acceptance. The timeline is four weeks.&lt;/p&gt;

&lt;p&gt;In week three, the client writes:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“The new hygienist starts in January. Can you also add online booking and a sixth service page? It should be quick because you already have the design.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This sounds small, but it adds an integration, a page, testing, and coordination with a third-party vendor.&lt;/p&gt;

&lt;p&gt;The response:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Thanks for the update. The booking integration and sixth page are outside the five-page scope we signed, so I want to handle them properly rather than quietly absorbing the work. I can add them as a change order: integration and page build, 9 hours at $75/hour = &lt;strong&gt;$675&lt;/strong&gt;, plus a five-business-day timeline shift. The new delivery date would be &lt;strong&gt;December 12&lt;/strong&gt;. If that works, reply with approval and I’ll schedule it.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The client approves. The revised total is &lt;strong&gt;$5,475&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The important part is not the exact numbers. It is that the client got a clear choice before the work started, and the freelancer got a written record.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to put in the proposal
&lt;/h2&gt;

&lt;p&gt;A useful scope section has five parts:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Deliverables&lt;/strong&gt; — files, pages, features, formats.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Acceptance criteria&lt;/strong&gt; — how the client will know it is done.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not included&lt;/strong&gt; — the things people assume are included.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Client responsibilities&lt;/strong&gt; — feedback deadlines, access, decision-maker.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Change control&lt;/strong&gt; — any request outside the scope goes through a change order.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The “not included” section is the one that saves the most arguments. It is also the one most proposals skip.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five red flags
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;“Can you also…” arrives after the scope was agreed.&lt;/li&gt;
&lt;li&gt;The request is called “small” but nobody can estimate the time.&lt;/li&gt;
&lt;li&gt;The direction changes, not just the wording.&lt;/li&gt;
&lt;li&gt;Feedback is verbal and never written down.&lt;/li&gt;
&lt;li&gt;The deadline stays fixed while the scope grows.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If two or more are true, write the change order before starting.&lt;/p&gt;

&lt;h2&gt;
  
  
  What not to do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Do not silently absorb repeated extra work.&lt;/li&gt;
&lt;li&gt;Do not send a surprise invoice after the work is finished.&lt;/li&gt;
&lt;li&gt;Do not promise an outcome you cannot control.&lt;/li&gt;
&lt;li&gt;Do not treat a template as legal advice.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Honest limitations
&lt;/h2&gt;

&lt;p&gt;This is a practical process, not legal, tax, or financial advice. Adapt the documents to your contract and jurisdiction. A template cannot guarantee that a client will behave well; it can only make the agreement easier to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you want the editable version
&lt;/h2&gt;

&lt;p&gt;I packaged the proposal, change-order form, XLSX log, client scripts, and worked example into a 19-file kit for solo web developers:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://poplevin.gumroad.com/l/scopeguard-freelance-proposal-kit?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=scopeguard_launch" rel="noopener noreferrer"&gt;ScopeGuard: Freelance Proposal &amp;amp; Change-Order Template Pack&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It is $12, one ZIP, no subscription. The process above is free to use whether you buy it or not.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I used AI assistance to draft and format this article and the templates; I reviewed and edited them before publication. Not legal advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>webdev</category>
      <category>career</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
