The problem: In the middle of a project, a security fix turns out to be needed. It is not in the contract, and the project has no people or money left for it. The project team says, “It is not in scope.” Security says, “But it is a real risk.”
Words used here: scope is the list of what the project has agreed to deliver. A change request is a formal ask to change the scope, the price, or the date. A baseline is the standard set of security work that every project includes.
Think of a smoke alarm that was not in the quote
A builder gives a family a price for a house: walls, roof, doors. After the contract is signed, the family says, “We need smoke alarms.” The builder says, “They were not in the quote.” Nobody doubts that smoke alarms are needed. The only question is who pays, and nobody has asked it yet.
What it looks like at work
A project is halfway through. A security review finds that a feature stores client files in a way that anyone with the link can open. Fixing it needs about two weeks of work. The contract says nothing about this, the team is fully booked, and the budget is spent. The project manager says, “It is not in scope.” Security says, “We cannot ship this.”
- 1ContractScope and price are fixed
- 2Need appearsA security fix is needed mid-project
- 3Project team“Not in scope, no people left.”
- 4Security“The risk is real.”
- 5ResultThe fix waits, or is done unpaid
Both sides are half right. The project manager is right that scope and price were agreed, and that the team has no spare room. Security is right that the weakness is real. What is missing is a way to decide whose cost it is, and a name for the kind of fix it is.
You will notice it when:
- Security fixes are found after the contract is signed.
- “Not in scope” is the end of the talk.
- Nobody has priced the fix.
- The team does the work quietly, in extra hours, and does not tell anyone.
- The same missing item appears in project after project.
What exactly needs fixing
The first fix is not the technical work. It is deciding what kind of fix this is, and who pays. This card shows the whole problem on one page:
A needed security fix has no scope, no people, and no budget in the project.
The contract scope, the project plan, and the change request process.
The weakness ships, or the team does the work unpaid and falls behind.
- Unpaid extra work
- Weak delivery
- Missed date
- Client dispute
- 1Sort the fix
- 2Price it clearly
- 3Add to the baseline
Delivery and sales heads
The next contract draft
A blank copy of this card is in the Tools section.
Why it happens
- Security was not in the estimate. The price was set without it.
- Contracts list features, not protection. So protection looks like an extra.
- Everyone assumes “secure” is included. The client assumes it, and the team assumes it was priced.
- There is no standard security line in the contract. So each case is a new argument.
- Raising a change request feels hard. Teams avoid it.
- Nobody tells the difference between a basic need and an extra. So everything becomes a fight.
What happens if you ignore it
Either the weakness ships, or the team pays for it without anyone noticing.
- The weakness goes live, and the client or an attacker finds it.
- The team does unpaid work, falls behind, and loses trust in security.
- The cost of the fix grows when it is found after go-live.
- A dispute with the client starts, and nobody has anything in writing.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely. It happens in most projects with a fixed price. |
| Worst case? | A weak product ships, or the team burns out paying for the fix. |
| What does it cost? | Unpaid time, a missed date, or a client dispute. |
| What if we wait? | The fix costs more, and the dispute gets bigger. |
| What does the fix cost? | A line in every estimate, and one short talk per case. |
How to fix it, step by step
Sort the fix first. Then decide who pays, with a name and a date.
- Sort the fix into one of three kinds. A: it is part of the baseline that every project carries. B: it is real extra work for this client. C: it cannot be paid now, so it needs a stop-gap and a later fix.
- For kind A, absorb it. If the baseline was missing from the estimate, this is our cost. Learn from it for the next estimate.
- For kind B, raise a change request. One page: what, why, price, and date. The client can say yes, say no, or accept the risk in writing.
- For kind C, agree a stop-gap. Protect the weak part now, set a date for the real fix, and have the owner sign.
- Price it in days, not in words. “Two weeks of two people” is easier to decide on than “a big fix.”
- Do not hide the work. If the team does it quietly, nobody learns that it was missing.
- Add the baseline to every estimate and contract from now on. A named line, so security is never an extra.
- Look back at the last few projects. Which fixes were kind A? Put them into the baseline.
The picture shows the three kinds. Naming the kind first makes the talk about money shorter.
Who to bring in: The head of delivery, the sales or account lead (who owns the contract), the project manager, the lead developer, and security.
Tools and templates
Sorting the fix
| Question | If yes, it is… |
|---|---|
| Does every project of this type need it? | A: baseline, we carry the cost |
| Is it a new need of this client that was not known? | B: change request |
| Is it a real need but cannot be paid or built now? | C: stop-gap, then a planned fix |
A baseline line for every estimate (example)
| Item | What it covers |
|---|---|
| Security baseline | Safe login, safe storage, a basic security check before go-live |
| Security review | A short design review and a final check |
| Fix time | A small reserve for fixing findings |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the project manager
Subject: A security fix that is not in the plan
Hi [name]. Our review found a problem that needs a fix before go-live: client files can be opened by anyone with the link. It is not in the scope, so I would like to decide with you what kind of fix it is. I will bring a rough size in days, and three options: we carry it, we raise a change request, or we use a stop-gap now and fix it later. Could we meet for 20 minutes today?
Field tip
Do not argue about whether it is in scope. Ask, “Which kind of fix is this, and who signs for the cost?”
Words used in this chapter
- Scope: the list of what the project has agreed to deliver.
- Change request: a formal ask to change the scope, price, or date.
- Baseline: the standard security work every project includes.
- Stop-gap: a temporary protection until the real fix is done.
- Estimate: the price and time given to a client before work starts.