EDGE project changes after approval: know the boundary

EDGE project changes need a documented decision before the team alters a contract, supplier or deliverable. Current programme guidance allows only limited change requests for projects approved under EDGE. Treating every operational variation as a routine amendment can leave the actual project outside the accepted Letter of Offer.

Start with the accepted Letter of Offer

Create a one-page control record from the accepted Letter of Offer: applicant, activity, vendor, approved scope, cost categories, project start and end dates, claim due date and deliverables. Attach the accepted version and name one employee who owns alignment. Project staff should use this record instead of an application draft or vendor presentation.

Record the current state at every steering meeting. If the project still matches, say so. If a variance appears, describe it without prematurely calling it minor. A difference in brand name may hide a different contracting entity, and a small feature request may change the technical objective or evidence required at claim.

Know the permitted request types

The current EDGE FAQ states that, from 1 November 2026, the change-request function is limited to the project end date and claim due date. Requests remain subject to approval. A company should therefore prepare the reason, revised date, project status, remaining work and impact before submitting either request.

Do not assume that asking for more time changes the approved scope or revives an expired obligation. Submit while the project remains within the applicable period and retain the official response. Until approval is confirmed, manage the project against the existing date and avoid presenting the requested extension as already granted.

Pause vendor substitutions

The same FAQ says the vendor cannot be changed after approval. If a vendor cannot deliver, becomes unsuitable or asks another entity to invoice, pause new commitments and obtain current official guidance. A replacement invoice should never be uploaded under the approved vendor merely because the commercial outcome seems similar.

Document the trigger, amounts already paid, work completed, assets or source files available and contractual recovery options. Check relationships between the applicant, original vendor and proposed replacement. The EDGE unrelated-vendor guide explains the separate declaration review that should remain current.

Distinguish delivery detail from scope change

Some implementation choices may sit within the approved outcome, while others change the business need or activity. Compare the proposed change with the application objective, approved deliverables, vendor quotation and assessment basis. Ask whether a reviewer would still recognise the same project. If not, do not rely on an internal label such as enhancement or configuration.

Examples requiring careful review include moving from one product to another, replacing a consulting workstream, removing a market, changing an equipment deployment location or converting a prototype project into ordinary software implementation. Record the facts and question sent through the official channel. Keep the response with the decision.

Use termination deliberately

Where the company has a different need, the FAQ directs it to terminate and submit a new application. Termination is not an administrative shortcut. Management should understand the effect on approved support, annual grant cap, sunk costs, contracts and project timing before authorising it.

The FAQ also explains that grant cap drawn down on approval is returned to the grant year in which the project was originally approved when a project ends with no claims. Confirm the actual portal and official outcome for the company’s case. Do not forecast restored capacity until the termination is processed and visible.

Control supplier and finance actions

Procurement should flag any revised quotation, payee or contract. Finance should flag invoices that do not match the approved schedule. The project manager should flag missing deliverables and dates. Route all three to the same change owner so a commercial response is not implemented before its grant consequence is understood.

Do not backdate a purchase order, relabel an invoice or ask a vendor to reproduce an old quotation. If an ordinary business cost is no longer supportable, record it outside the claim. Transparent treatment protects the wider project better than trying to make changed facts resemble the original submission.

Maintain a concise change chronology

For each issue, record discovery date, source, approved baseline, proposed action, money at risk, official question, response, management decision and implementation date. Link documents instead of copying sensitive or inconsistent versions into several folders. A clean chronology helps a new reviewer understand why the company acted.

Pair the chronology with the EDGE application evidence handover. A date request, vendor failure and scope change have different routes, yet all require evidence before action. The register should make those distinctions visible rather than reducing every issue to open or closed.

Review before claim preparation

Before engaging the auditor or finalising the claim, compare the delivered project with the accepted Letter of Offer and every approved date request. Check the vendor identity, deliverables, invoices, payment evidence and applicant eligibility. Resolve variances before the claim is assembled because an audit cannot turn an unapproved change into an approved one.

If uncertainty remains, state it and seek official clarification. Keep the company’s commercial decision separate from the grant outcome. Management may decide to continue a useful project without support, but the claim must still contain only the approved, eligible and accurately evidenced part.

A disciplined change record gives management an early choice: continue within the accepted project, request a permitted date change, terminate and reapply, or proceed without assuming support. That choice is far safer before the next contract or payment is released.