A governed advisory workflow for the pre-procurement stage

Procurement risk starts before procurement is engaged.

GC Procurement Advisor helps Government of Canada business and IT teams arrive at procurement, legal, security, privacy, and accessibility reviews better prepared — with structured analysis, visible unknowns, and a record of how they got there.


The problem

Where the file starts to drift.

In the Government of Canada, the highest-risk procurement moves often happen before procurement is formally engaged. Business areas and IT teams are still shaping the requirement, exploring solutions, and forming assumptions. By the time the file reaches the contracting authority, certain decisions have already been made — sometimes without the analysis the file will later be expected to defend.

This is where the patterns flagged in reports from the Office of the Procurement Ombud, the Office of the Auditor General, and departmental internal audit functions tend to originate:

  • Unclear business needs and shifting scope
  • Requirements unduly shaped by a particular solution
  • Weak documentation of options considered
  • Incomplete threshold analysis and missed policy overlays
  • Premature assumptions about the right procurement vehicle

GC Procurement Advisor exists to give these teams a more disciplined starting point — before formal procurement, legal, security, privacy, and accessibility reviews begin.


What it does

A structured advisory workflow for early-stage thinking.

The user describes an emerging requirement in plain language. The application then works through the considerations that shape a procurement file:

Threshold analysis and value framing
The total estimated requirement, including foreseeable expansions, is examined against contract-value thresholds that drive trade-agreement coverage and competition obligations.
Trade agreement coverage
Coverage under CFTA, CETA, CPTPP, WTO-GPA, and the bilateral free trade agreements is evaluated against commodity classification and entity coverage.
Competition method
Competitive and non-competitive paths, and any proposed GCR Section 6 exception, are tested against the encoded rules before the file is brought forward.
Procurement vehicle mapping
Mandatory PSPC instruments — SaaSSA, SLSA, TBIPS, ProServices, NMSO — are mapped against the commodity and value envelope.
Policy overlays and governance triggers
Security, privacy, accessibility, official languages, Indigenous procurement, Buy Canadian, and other governance considerations are surfaced based on the requirement profile.

Assumptions, unknowns, and issues requiring confirmation stay visible throughout. The user leaves with a structured record of the analysis — what was considered, what was assumed, and what still needs an authoritative answer — that can be brought into the next conversation with procurement, contracting, legal, security, privacy, or accessibility advisors.

This is preparation support. It does not replace procurement officers, contracting authorities, legal counsel, security or privacy advisors, accessibility specialists, or any formal departmental approval.


How it differs

Not ChatGPT plus documents. Not a generic RAG agent.

“The compliance logic follows the structure of Government of Canada procurement rules, not the structure of a language model.”

GC Procurement Advisor is not built on document retrieval and prompt engineering. The rule layer is deterministic: thresholds, trade-agreement coverage, vehicle eligibility, and governance triggers are resolved against an encoded model of GC procurement policy — not inferred by an AI from training data.

The AI layer explains the result, asks better scoping questions, and translates complexity into plain language. It does not define compliance paths, override the rule engine, or silently fill in missing facts.

Where a fact is missing, the system surfaces it as an open assumption or open question rather than guessing. Gaps stay visible and travel with the file into the next review.

What makes it different

Built for procurement risk control, not generic productivity.

Rule-based compliance logic

The compliance layer is deterministic. The AI layer explains the result; it does not produce it.

Visible unknowns

The system does not silently fill in missing facts. Gaps are surfaced to the user and travel with the file.

Built inside the GC operating context

Designed by a consultant with 25+ years in Government of Canada procurement reform and transformation — not retrofitted from a generic AI product.

Designed to support auditability

Every session produces a structured record of the analysis performed, the assumptions made, and the unknowns flagged.


Security & deployment

Hosted in Canada. Designed to support a Protected B conversation.

GC Procurement Advisor is hosted on Google Cloud in Montréal, with operational data held in Canada. The deployment separates operational records — sessions, audit logs, and decisions — from the policy data the application reasons over. The policy layer is identity-free by design.

Control selection has been informed by ITSG-33 and is designed to support Protected B Medium Medium alignment, subject to departmental Security Assessment and Authorization. The current posture supports discovery, demonstration, and unclassified advisory use.


Provider

Built by someone who understands the GC machinery.

GC Procurement Advisor was architected by Daniel Fallon, a senior management consultant with 25+ years leading Government of Canada procurement, IT modernization, and enterprise transformation initiatives — typically reporting at the DG and ADM level. Selected engagements include:

  • Transformation planning and procurement strategy for the Canada.ca Managed Web Service
  • Enterprise professional services procurements at ESDC
  • Advisory work on DND’s ACCORD procurement reform initiative
  • Chief Negotiator for Newfoundland and Labrador on the Canadian Internal Trade Agreement

Former contributor to TBS policy on project management. Holds a Government of Canada Secret clearance.

Evaluation access

How to evaluate it.

For departmental scans and capability assessments, we suggest a two-step path:

  1. Step 1

    Guided demonstration

    A working session using representative GC procurement scenarios. Scenarios can be aligned to your draft capability requirements or to a specific GC scan your team is preparing for.

  2. Step 2

    Evaluator access (optional)

    Time-limited access to a dedicated assessment environment so your team can run its own scenarios under controlled conditions.