Manitoba Provincial Nominee Program Code of Conduct
What the Manitoba Provincial Nominee Program Code of Conduct is and when it applies
Why the Code of Conduct matters for applicants and representatives
A clear Code protects applicants, preserves program integrity, and reduces risk of refusal or compliance sanctions by documenting responsibilities, fee arrangements, and acceptable practices for recruitment and representation in Manitoba PNP processes.
Who completes and signs the Code of Conduct
This document is completed by parties directly involved in a nomination: the applicant, any authorized immigration representative, and the employer or designated third party providing support.
- Prospective nominees or primary applicants — confirm facts, disclosures, and consent to representation.
- Employers or local sponsors — attest to recruitment practices, job offer legitimacy, and fee arrangements.
- Authorized representatives or agents — declare adherence to professional conduct and client fee disclosure.
Step-by-step: completing the Code of Conduct correctly
-
01Gather documents: Collect passport, job offer, and representation agreement before starting.
-
02Enter names and dates: Populate legal names and MM/DD/YYYY effective date fields.
-
03Disclose conflicts: Describe any referral fees or affiliations clearly.
-
04Sign and retain: All parties sign, date, and keep copies for recordkeeping.
Routing and submission: how the completed Code moves through the process
-
Applicant retention: Applicant keeps a signed copy for audit and future reference.
-
Representative copy: Representative retains one signed copy and prepares province submission materials.
-
Employer record: Employer stores the signed Code to evidence recruitment and offer legitimacy.
-
Submission with MPNP: Include the Code as part of the nomination package or provide when requested by MPNP.
Configuring a digital workflow for the Code of Conduct
| Field | Configuration |
|---|---|
| Authentication method | Email link | SMS code | ID verification |
| Signing order | Sequential or parallel signer flow |
| Audit capture | IP, timestamp, and action logs retained |
| Document retention | Export signed PDF with certificate |
Technical considerations for electronic completion and eSubmission
Choose a platform that records signer attribution, stores an immutable audit trail, and supports standard PDF output for provincial review.
- Authentication: Email plus optional SMS or ID verification
- File formats: PDF/A or standard signed PDF
- Integrations: Cloud storage and CRM sync
Ensure the chosen system preserves signing metadata and allows export of a verification certificate to attach to the nomination or produce on request.
Consequences of an incomplete or incorrect Code of Conduct
Common preparation pitfalls to avoid
- Leaving signer names or dates blank causes immediate administrative requests and can delay the nomination package.
- Using informal initials instead of full signatures generates questions about intent and may be rejected by reviewing officers.
- Failing to disclose referral fees or recruitment charges can be interpreted as conflict of interest and trigger sanctions.
- Submitting inconsistent employer or job details between the Code and the job offer invites verification and possible refusal.
Timing considerations and expected checkpoints
Submission timing:
Provide the signed Code with the initial MPNP nomination or upon request.
Response windows:
Be prepared to produce supporting documentation within provincial follow-up timelines.
Record retention:
Keep signed copies for the entire active nomination period.
Employer audits:
Province may review employer documentation during compliance checks.
Amendments:
Revised Codes should be re-signed and dated by all parties.
Common eSignature vendor pricing and capabilities to consider
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes (Premium tier) | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes (BAA) | Yes (BAA) | No | No |
Real-world examples of Code use and outcomes
Optica Ventures (COO)
Optica used a standardized Code to centralize representation records and reduce back-and-forth with candidates.
- The interface simplified signature collection.
- As a result, their team retained consistent documentation for every nominee and reduced document-related inquiries during provincial verification.
Martin Properties (Founder)
Martin Properties shifted to digital Codes for all sponsored hires to ensure traceable consent and fee disclosures.
- Mobile signing allowed field approvals.
- This change ensured compliance when remote offers were made and provided auditable records for employer files and provincial reviews.
Practical tips for accurate, defensible completion
Frequently asked questions about signing and using the Code of Conduct
-
Can this Code be signed electronically?
Yes. Electronic signatures that demonstrate intent, consent, attribution, and retention are generally valid under ESIGN and UETA, provided consumer-facing disclosures are given when required.
-
Is notarization ever required?
Not typically for the Code itself, but certain supporting affidavits or powers of attorney may require notarization or remote online notarization depending on jurisdiction.
-
What if names do not match?
Mismatched names between the Code and identity documents can prompt verification requests. Correct and re-sign documents where necessary to avoid processing delays.
-
How do I revoke or update a signed Code?
Revisions require a signed amendment or a new signed Code by all parties, with the effective date and record of prior versions retained for auditability.
-
How long should I keep signed copies?
Keep signed Codes for the active nomination period and at least three years afterward; retain healthcare-related records for six years when PHI is involved.
-
What authentication strength is recommended?
Use at minimum email plus access code; for higher-assurance cases, add ID verification or multi-factor authentication to strengthen signer attribution.