EDGE sustainable product development: prove advancement

EDGE sustainable product development is intended for more than a routine upgrade with environmental language added later. The current activity expects sustainability-related technological or functional advancement, a competitive response to a market gap, growth from existing capabilities and tangible prototype or small-batch work. The evidence plan should test each of those points before the company commits to a vendor.

Describe the current product and the proposed advancement

Record the existing commercial product or service, customer problem, performance baseline and present market alternatives. State the proposed change in measurable terms, such as durability, energy use, material recovery or a third party’s sustainability outcome. The current activity page distinguishes genuine advancement from routine replacement, standard implementation and incremental upgrades.

Explain why the project builds on existing operations rather than creating the company’s first product. Where an existing company is making its first sustainability pivot, identify the capabilities it already owns and what is genuinely new. Keep unsupported capital expenditure outside Singapore and other excluded costs visible.

Turn sustainability claims into tests

For each proposed benefit, record the baseline, unit, test condition, data source, owner and acceptance threshold. Include failure cases and trade-offs. A lighter product may use more energy, or a reusable design may require a return system. Management needs the net operating proposition, not an isolated favourable measure.

Preserve test protocols, raw results and design changes. Label estimates and user feedback separately from verified performance. If carbon data is used, record the boundary and method. Do not publish an environmental claim that the project evidence cannot support.

Connect prototype work to market validation

Plan actual prototype or small-batch production, with versions, bills of material, manufacturing changes and acceptance decisions. Strategy work can lead into development but should not replace it. Obtain user validation from the intended segment and record negative findings as well as favourable ones.

Link the market viability report, roadmap, commercialisation plan and intellectual-property review to specific management decisions. State what will be protected, licensed or disclosed. Forecast one-year revenue, cost savings and qualifying jobs from explicit assumptions rather than treating them as grant promises.

Close the project with a reproducible development record

Reconcile the approved deliverables with prototypes, test results, user evidence, manufacturing refinements, invoices and full payment. Explain why a version was accepted or rejected. Keep later production expansion separate from the supported development phase unless the Letter of Offer says otherwise.

Turn the decision into a controlled file

Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.

Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.

Review before commitment and again before closeout

Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.

Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.

Handle exceptions without rewriting history

Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.

If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.

Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.

Verify the final outcome independently

Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.

Use the EDGE projected resource gains guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.

Practical review checklist

• Existing product baseline recorded
• Advancement measured
• Prototype work versioned
• User validation retained
• Commercial decision approved

The project is defensible when the company can show a real baseline, material advancement, tested sustainability value, tangible development work and a commercially owned decision about what to launch next.