Raffles Consulting Services
Control EDGE solution package licences by reconciling users, quantities, implementation periods, training, identifiers and accepted deployment evidence.
EDGE solution package licences should reflect the applicant’s real deployment, not a quantity selected only to fit a vendor bundle or grant forecast. Enterprise Singapore’s current FAQ says package components may vary with staff size, implementation period and training needs. It also treats a software licence number, user ID or user email as a possible unique identifier. The company therefore needs one quantity record from application through claim.
Fix the EDGE solution package licences baseline
List the functions, named user groups, locations, expected usage and implementation period. Separate active users, occasional users, administrators, service accounts and training access. Use the current EDGE FAQ to identify the package-builder variables and the unique-identifier requirement, then compare the selected activity page and vendor package.
Reconcile the proposed quantity with payroll, organisation records and the process being changed. A higher headcount does not automatically justify a licence for every employee, while shared credentials can weaken security and the claim trail. Record the quantity method and the person who approved it.
Match commercial terms to supported deployment
Break the quotation into licence type, quantity, price, subscription period, implementation, migration, integration, training and optional support. Identify auto-renewal, minimum-user and overage terms. The EDGE activity directory should be used to confirm the selected route; the supplier’s package name does not control eligibility.
Freeze the package reference and quotation used for the application. If users, dates or components change, preserve both versions and test whether the approved scope still fits before commitment. Do not hide an unsupported add-on inside an average per-user price.
Prove licences, acceptance and continued use
At implementation, export the licence assignment, unique identifiers, activation dates and administrator record. Sample users against approved roles and test the functions tied to the project outcome. Record unused, duplicate and reassigned licences and the reason for each exception.
At claim closeout, match the Letter of Offer, invoice, full payment, deployed quantity, accepted functions and identifiers. Keep personal data proportionate and access-controlled. Schedule a later utilisation review so management can distinguish grant closeout from ongoing licence-value management.
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 package-reference 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
- User groups mapped
- Package variables recorded
- Quotation components separated
- Unique identifiers preserved
- Deployed quantity reconciled
EDGE solution package licences are controlled when the quantity method, commercial package, deployed users, unique identifiers and accepted functions can be reconciled without shared credentials or unsupported components.