EDGE internationalisation applications: separate activities

EDGE internationalisation applications must be separated by activity when a company pursues several activities in one country. It may apply to multiple markets at the same time, but every application needs its own scope, deliverables and expansion logic. The portfolio should remain coherent even though the submissions are separate.

Define each EDGE internationalisation application's outcome

List market entry setup, staff deployment, promotion, trade fairs and other planned work. Give each activity a distinct outcome, owner, supplier, cost, timeline and evidence. The EDGE FAQ states that a separate application is required for each internationalisation activity within a country.

Use the internationalisation activity directory to confirm the correct route. Do not combine unrelated deliverables to reduce paperwork or split a single indivisible activity merely to create more cap capacity. Record the purpose of each EDGE internationalisation application in the country plan.

Keep the country plan and applications reconciled

Build one market plan showing the commercial sequence and dependencies, then map each application to it. Record shared assumptions only once and make sure figures remain consistent across submissions. Explain when one activity can proceed if another is rejected or delayed.

Track the S$100,000 annual company cap across all EDGE activities. Separate submitted, approved and paid amounts. A concurrent application is not an approval and does not reserve cash or cap automatically.

Prevent duplicated costs and evidence

Assign every quotation, invoice, employee cost and deliverable to one activity unless the official terms allow a supported allocation. Document the basis for shared costs and avoid double support. Keep market, project and activity identifiers on the records.

Use the EDGE annual cap register for portfolio control and the market-entry cornerstone for the wider entry decision.

Test the plan if one application fails

For each proposed activity, write a dependency statement explaining what happens if another activity is delayed, reduced or rejected. A trade fair may still proceed without a later staff deployment, while a market setup may depend on legal or regulatory work first. Update the country cash flow and management approval for each scenario. This makes separate applications operationally meaningful and prevents teams from assuming that one approval confirms the commercial case or eligibility of every other activity in the market plan.

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 market-entry cornerstone 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

• Activities separated
• Country plan reconciled
• Application owners assigned
• Annual cap tracked
• Duplicate costs screened

The expansion file is ready when each activity has a separate truthful application, the country plan remains commercially coherent, and no cost, cap amount or deliverable is counted twice.