EDGE main contact: protect claim reminder continuity

The EDGE main contact is a control point, not just an email field. Enterprise Singapore says reminder emails are sent to the main contact before the claim due date. If that person leaves or the mailbox is not monitored, the company can miss an important warning even when the project work is complete.

Record the contact and the deadline together

Create one project record showing the main contact, authorised submitter, project owner, finance owner, project end date and claim due date. Keep the accepted Letter of Offer and portal readback with it. The person named as main contact should know what messages to expect and where the evidence file is kept.

The current EDGE FAQ states that multiple reminder emails will be sent to the main contact before the claim due date expires. These emails help, but they do not transfer responsibility from the company. Maintain an internal calendar that does not depend on a single inbox.

Use a role mailbox carefully

A monitored business mailbox can improve continuity, provided the portal permits it and the company controls access. Assign named owners, review membership quarterly and remove departed staff promptly. Do not use a shared password. Access should follow the company’s supported identity and security process.

Where an individual email must be used, add a second internal diary and a documented handover route. Forwarding alone is fragile because security controls, account closure or leave may stop delivery. The project record should remain usable without opening the former employee’s mailbox.

Plan for staff changes

Add grant records to the company’s leaver checklist. Before the last day, identify every active application and approved project owned by that person. Confirm the new operational contact, outstanding deliverables, vendor issues, payments and dates. Preserve business records through the approved repository, not a private device.

Treat extended leave, illness and role transfer the same way. A contact can be unavailable without leaving. Name a deputy who understands the file and knows when to escalate. The deputy should not use another person’s login or submit a claim without proper authority.

Separate contact from submission authority

The main contact may receive messages while an authorised employee submits through the official route. Record both roles. Confirm current portal permissions before the intended filing day. Never share Corppass credentials or ask a consultant to act through an employee’s identity.

Run a readiness check at least one month before the due date. Verify that the correct people can see the project, the company details remain current and the evidence file can be reviewed. The EDGE application receipt guide explains how to preserve the original submission receipt without exposing credentials.

Build a three-date diary

Track project end, internal evidence freeze and claim due date. The evidence freeze should leave time for missing invoices, payment proof, deliverable acceptance and any required audit work. Add reminders at intervals that suit the project rather than copying a generic schedule.

Record the source of every date. A vendor plan, internal timetable and Letter of Offer may show different dates for different purposes. The official project and claim dates control the grant file. If the company needs more time, use the proper request route before expiry and do not present a request as approval.

Reconcile the handover

The outgoing and incoming owners should review the approved scope, amounts, vendor, deliverables, payments, changes, risks and open questions. Use a short checklist and attach links to the records. Both should confirm what remains incomplete. The handover is not finished merely because a folder changed owner.

Ask finance to confirm unpaid invoices and procurement to confirm open orders. Ask the project team to confirm final acceptance. The EDGE final-claim closeout guide provides the broader closeout sequence. This contact-control article focuses on keeping responsibility and reminders attached to a real person throughout that sequence.

Respond to a missing reminder

If an expected reminder does not arrive, check the official project record and contact route. Do not infer that the deadline moved or that the project disappeared. Preserve screenshots or acknowledgements through approved means and ask Enterprise Singapore when the portal record is unclear.

A reminder is evidence of communication, not proof that a claim was submitted. Completion requires an official submission receipt and later outcome readback. Keep each state separate so a quiet inbox does not create either false confidence or an unnecessary duplicate action.

Contact continuity is inexpensive to design and costly to improvise. One current owner, one deputy, one official date record and one usable evidence folder give the company a reliable path from approval to claim.

Create a contact continuity record

Maintain a one-page record showing the portal main contact, business email, mobile number, job role, deputy, Corppass access status and last verification date. Add the project end date and expected claim window. Review the record at approval, project midpoint, one month before completion and whenever a staff member gives notice. A calendar reminder owned by finance or operations should supplement, not replace, the portal contact.

Use a role mailbox where the organisation can control access, but keep the named person current where the portal requires one. Do not share personal login credentials. The deputy should know where the approval letter, variation records, invoices, payment proofs, deliverables and outcome evidence are stored. Test that the mailbox can receive messages and that spam controls do not divert programme notifications.

Practise the handover before a real departure

Run a short handover exercise. Ask the deputy to identify the grant reference, current milestone, approved scope, next deadline, outstanding evidence and authorised portal user. Record any gap and fix it. Where the main contact has already left, check the portal and official correspondence before assuming that reminders or deadlines moved with the employee.

At project close, reconcile the latest approved variation, final deliverables, paid costs and outcome report before opening the claim. Preserve acknowledgements and official status readbacks. If the system is quiet or a submission times out, check the current record before trying again. This operating discipline prevents duplicate submissions and makes the company less dependent on a single person’s inbox.