Raffles Consulting Services

GIA co-innovation: control partner work packages

Control GIA co-innovation work packages by separating partner eligibility, technical tasks, costs, ownership, market evidence and claim records.

GIA co-innovation work packages should show why two independent partners need each other to develop a new product or solution with market potential. A partner letter and a combined budget do not establish a coherent research and development project. The Singapore applicant needs a clear division of technical work, cost, ownership, decision rights, evidence and commercial follow-through.

Build one bilateral project from two company files

Confirm the Singapore lead applicant, overseas partner, ownership independence, operating status, financial capacity and call-specific eligibility. Describe the customer problem, technical uncertainty, proposed advance and intended market. Keep each company’s application, declarations and authority route separate while reconciling the shared project facts.

Enterprise Singapore’s co-innovation programme page states that Singapore-based companies and overseas partners collaborate on research and development projects for new products or solutions with strong market potential. The GIA overview distinguishes co-innovation from acceleration and other market-access routes.

Assign work, cost and evidence before submission

Create a work-package table with objective, partner, named lead, inputs, method, milestone, acceptance test, cost and evidence. Identify interfaces where one partner depends on the other. Separate Singapore qualifying costs from the overseas partner’s budget and from unsupported commercial activity. Reconcile quotations, salaries and materials to the proposal.

Agree how background intellectual property, project results, confidential information, publication, licences, improvements and commercialisation will be handled. The grant application does not replace a suitable collaboration agreement. Coordinate legal documentation with counsel and keep the technical project file consistent with the signed terms.

Control joint changes and final claims

Set a bilateral change process for schedule, scope, personnel, partner contribution, cost and ownership. A change approved by one company’s management may still affect the other application or call rules. Preserve joint meeting records and obtain required authority decisions before relying on a material change.

At closeout, reconcile each deliverable to test results, partner acceptance, invoices, salary evidence and the market case. The current programme page states that final claims follow achieved deliverables and the Letter of Offer deadline. Keep the partners’ evidence aligned without merging legal entities or duplicating the same cost.

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 Singapore business support decision 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

  • Partner eligibility checked
  • Technical advance defined
  • Work packages separated
  • Ownership terms coordinated
  • Joint changes and claims reconciled

The project is ready when each partner has a distinct, necessary and costed work package, the interfaces and ownership terms are clear, and both sides can reproduce the shared result from their own records.