TES Submission Day: The File Is Sent: Now What Should Your Team Record?

Hook caption: You clicked “submit.” The deadline is met. But can your team prove exactly what was sent, who approved it, and what happens next? Here is the post-submission record every South Africa Trusted Employer Scheme team should control.

The South Africa Trusted Employer Scheme Phase II expression-of-interest deadline is 4 September 2026.

By then, your organisation should have selected one pathway, completed the required information, attached the supporting records and submitted through the relevant online process. The official invitation is available through the South African Government notice.

But submission day is not the end of the workflow.

It is the moment your team moves from preparation control to record control.

The EOI has been sent. The next question is simple:

If someone asks your team three weeks from now, “What exactly did we submit?”, can you answer without searching through email threads, downloads, screenshots and spreadsheets?

If the answer is uncertain, the file is not finished.

The old way: submission without control

Many teams treat the submission confirmation as the complete record.

That creates problems quickly.

: The final document version is unclear.
: Different people retain different copies.
: Internal approval is buried in an email chain.
: No one knows who owns follow-up communication.
: A portal reference is saved on one person’s laptop.
: The organisation cannot easily reconstruct what it represented.
: Future visa and workforce processes begin without a reliable foundation.

This is not only disorganised. It creates unnecessary compliance risk.

A Trusted Employer Scheme application is built around an organisation’s profile, operations, workforce, compliance position and strategic value. The submitted record therefore matters beyond the deadline.

The new way is controlled, centralised and auditable.

• One final submitted version.
• One proof-of-submission record.
• One approval trail.
• One responsible owner.
• One communication log.
• One controlled record of representations.

That is the difference between sending a file and managing a case.

1. Preserve the final submitted version

The first record should answer:

What exact version did the organisation submit?

Do not rely on a working draft. Do not assume the last file in the shared folder is the submitted file. Do not leave the answer inside the memory of the person who clicked the button.

Create a final submission record containing:

: The completed EOI or submission form.
: Every attachment uploaded with it.
: The selected TES Phase II pathway.
: The scoring calculation or internal assessment used.
: The date and time of submission.
: The name and role of the submitting person.
: A clear version number or finalisation date.
: Any declaration or confirmation accepted during submission.

The record should be locked against accidental editing.

If a correction is needed later, create a new version. Do not overwrite the original. The purpose is to preserve the historical record of what was represented at the deadline.

This matters because post-submission discussions may refer to details that are easy to forget. A controlled copy prevents uncertainty.

Summary: Preserve the submitted file as evidence, not as an editable working document. That means less admin later and more control now.

2. Store proof that the submission was made

A completed file does not prove that it reached the relevant portal.

Your team should retain every available confirmation record.

This may include:

• A portal confirmation page.
• A submission reference number.
• A confirmation email.
• A downloaded receipt or generated PDF.
• A timestamped screenshot, where appropriate.
• The name of the account or authorised user that submitted it.
• The portal or channel used.
• A note confirming whether all attachments were accepted.

Save the proof inside the case record. Do not leave it in a personal inbox.

Use a consistent naming format. For example:

TES_PhaseII_EOI_SubmissionProof_EmployerName_2026-09-04

If the portal produces no formal receipt, record that fact. Keep the available evidence and note the submission steps completed by the authorised user.

The objective is not to manufacture certainty. It is to document the facts accurately.

Avoid statements such as “TES approval secured” or “fast-track access confirmed.” Submission starts an assessment. It does not guarantee membership, approval, visa outcomes or processing timelines.

Use precise status language:

: EOI submitted.
: Awaiting assessment.
: Awaiting further communication.
: Additional information requested.
: Outcome received.
: Further action required.

Clear language protects internal teams from making assumptions.

3. Record internal approvals

A submission can be technically complete but internally unclear.

Who authorised the final representation?

For a corporate employer, the EOI may involve information from human resources, finance, legal, compliance, operations and executive leadership. Different teams may have supplied different parts of the evidence.

After submission, record:

: The final internal approver.
: The date approval was given.
: The scope of the approval.
: Any conditions or reservations.
: The person responsible for confirming factual information.
: The legal or immigration provider involved, where applicable.
: Any information that still requires validation or updating.

This does not replace legal or immigration advice. It creates an internal governance record around the information supplied.

The approval record should answer:

Did the right people review the final version before it was sent?

If your selected immigration practitioner, attorney or mobility provider prepared or reviewed the submission, record their role. E-Migration Assist is designed to support employers and their chosen professional providers with structured case-management infrastructure. It is not a replacement for the advice or professional responsibility of those providers.

That distinction is important.

The system should make collaboration clearer, not blur accountability.

4. Assign one responsible owner

“Everyone is monitoring the application” usually means no one owns the next step.

Assign a primary owner immediately after submission.

That owner may be an internal global mobility manager, HR leader, compliance officer or designated contact working with the organisation’s selected immigration provider.

The case record should include:

• Primary owner.
• Backup owner.
• Provider contact.
• Executive stakeholder.
• Escalation contact.
• Date for the next internal review.
• Responsibility for checking official communications.
• Responsibility for responding to any information request.

The owner does not need to make every decision. The owner needs to coordinate the workflow.

Set a review cadence. For example:

: Confirm submission records are complete.
: Check the official communication channel.
: Review any request for clarification.
: Update the case status.
: Notify relevant internal stakeholders.
: Escalate delays or uncertainties to the selected professional provider.

Avoid using a general inbox as the only control point. A shared inbox can support the process, but it should not replace ownership and decision logging.

Summary: A named owner turns waiting into a managed workflow. That creates less admin and more control.

5. Define expected communications without making assumptions

Your team should know what communication it is monitoring for.

That does not mean predicting an outcome.

It means creating a communication plan that covers:

: Which email addresses or portal accounts may receive updates.
: Who checks those channels.
: How often they are checked.
: How communications will be saved.
: Who must be notified internally.
: Who will coordinate a response.
: What the escalation process is if a request is unclear.
: What to do if no communication is received within the relevant official timeframe.

The post-submission case status should be updated whenever a communication is received.

Record:

• Date received.
• Sender or channel.
• Subject or reference.
• Summary of the communication.
• Action required.
• Action owner.
• Due date.
• Response submitted.
• Supporting documents attached.
• Date the matter was closed.

Do not treat informal commentary, third-party updates or assumptions as an official outcome. Link each status change to its underlying communication or internal note.

A communication log gives your team a clean chronology. It also reduces duplicate responses and missed requests.

6. Maintain a controlled record of what was represented

The most valuable post-submission record is often the simplest:

What did the organisation say about itself?

Create a representation register for material statements made in the EOI.

This may cover:

: Corporate registration and operational presence.
: Workforce composition.
: Local investment.
: Skills development.
: Sector activity.
: Head office or regional operations.
: Financial or strategic information.
: Compliance history.
: Recruitment practices.
: Supporting evidence linked to each statement.

For each material representation, record:

• The statement made.
• The source document.
• The internal owner.
• The date verified.
• Any assumptions or limitations.
• The person or provider who reviewed it.
• Any change that may require attention.

This record becomes valuable if the organisation is asked to clarify its EOI. It also helps ensure that future work permit, critical skills visa or workforce processes remain aligned with the employer’s documented position.

A representation register is not a promise of acceptance. It is a control mechanism for accuracy, consistency and accountability.

Build the post-submission workflow before the outcome

The TES Phase II process may involve assessment and further communication after the 4 September 2026 deadline. Your team should therefore prepare for the next stage without presenting membership as guaranteed.

That means building a workflow for:

1. Submitted record preservation.
2. Proof-of-submission storage.
3. Internal approval logging.
4. Ownership and escalation.
5. Communication monitoring.
6. Information-request handling.
7. Representation verification.
8. Outcome recording.
9. Next-step planning.

This is where immigration case management software becomes useful.

The old way depends on spreadsheets, personal folders and long email chains.

The new way provides:

• Structured case workflows.
• Secure document handling.
• Requirements and evidence checklists.
• Status tracking.
• Activity and decision logging.
• Controlled collaboration with employers and selected legal or immigration providers.
• A single record for the full case lifecycle.

E-Migration Assist provides supportive infrastructure for this workflow. Its professional case-management platform helps firms, employers and mobility teams centralise documents, assign responsibility and track case progress.

Its compliance information also explains the importance of accurate user information, privacy-conscious handling and the fact that government authorities retain responsibility for immigration decisions.

The outcome is not more technology for its own sake.

It is a stronger operating record.

The practical test

Ask your team these five questions after submission:

1. Can we produce the exact final version sent?
2. Can we show proof that it was submitted?
3. Can we identify who approved the final representation?
4. Can we name the person responsible for follow-up?
5. Can we reconstruct every important communication and response?

If any answer is “not immediately,” the post-submission workflow needs structure.

The file is sent. Now preserve the record, control the communication and prepare for the next decision.

More structure. Less admin. More control.

Start your E-Migration Assist assessment and explore a privacy-first case-management foundation for South African immigration workflows.

#SouthAfricaTrustedEmployerScheme #TrustedEmployerScheme #TESPhaseII #ImmigrationCaseManagementSoftware #SouthAfricaImmigration #GlobalMobility #WorkVisaSouthAfrica #CorporateImmigration #ImmigrationTech #LegalTech #E MigrationAssist

This article is provided for general information and workflow-planning purposes. It does not constitute legal or immigration advice and does not guarantee TES membership, visa approval, permit approval or any processing outcome. Requirements and official processes may change. Employers should confirm current information through the relevant official channels and consult their selected qualified legal or immigration provider.