Contracting • NDA/MSA/SOW/DPA • procurement-safe • RID continuity

Contracting Notes

A procurement-oriented overview of contracting lanes and workflow. Final obligations are governed by the executed agreement. Public intake remains non-confidential.

Request ID —Include RID in legal/procurement subject lines.
Open Status Back to Procurement
Public boundary: do not submit secrets, credentials, customer content, or regulated personal data on public pages/forms. NDA and secure sharing options are used when required by buyer policy and scope.

Common contracting lanes

Choose the lane that matches buyer policy; keep scope and acceptance explicit.

NDA (when required)

Used when buyer policy requires confidentiality prior to sharing non-public information.

  • Recommended before sharing sensitive internal materials.
  • Does not start work by itself; work starts under SOW (or package acceptance path).

MSA + SOW (enterprise default)

Master agreement for general terms plus a Statement of Work for scope, deliverables, milestones, and acceptance criteria.

  • SOW defines: deliverables, schedule, acceptance checks, exclusions, buyer responsibilities.
  • Best fit for PO workflows and vendor onboarding.

SOW-only (when MSA is not required)

For buyers that prefer a single document, scope and acceptance can be contained in the SOW.

  • Still requires explicit: deliverables, acceptance, pricing, payment terms, change control.
  • Procurement pack + RID recommended for routing and traceability.

DPA / privacy review (when applicable)

Where scope involves processing buyer personal data (if any), DPA and privacy review can be supported as required by policy.

  • DPA scope is engagement-specific (data types, purpose, retention, security measures).
  • Preferred posture is minimisation; avoid unnecessary personal data in the first place.

High-level posture: Security & privacy summary.

Procurement workflow (recommended)

A practical sequence that reduces back-and-forth and keeps routing clean.

Step 1 — Select package and lane

Step 2 — Route contracting documents (if required)

Step 3 — Kickoff and controlled information sharing

  • Kickoff is email-first by default; calls can be scheduled if policy requires.
  • Secure sharing options (if needed) are confirmed after kickoff under executed terms.
  • Delivery remains anchored to written scope + acceptance criteria.
What should procurement send first?
Buyer policy requirements (invoice/PO/vendor onboarding), preferred contracting lane (MSA+SOW vs SOW-only), required timelines, and any mandatory vendor questionnaire. Avoid sending secrets via public channels.
How are changes handled?
Scope is fixed per package/SOW. Changes require explicit approval (and may require an amended SOW or additional fee), to prevent delivery ambiguity and procurement surprises.

Commercial notes (high-level)

Procurement-safe defaults; final terms confirmed in writing.

Defaults

  • Currency: CAD (unless agreed otherwise in writing).
  • Payment: invoice/PO supported for procurement workflows; card optional via Sales lane.
  • Acceptance: defined per package/SOW with measurable checks and artefact delivery criteria.
This page is informational and does not constitute a binding offer. Binding terms exist only in the executed agreement and SOW (or confirmed package acceptance).