Work Allocation Process (WAP)

The Work Allocation Process (WAP) is the procedure Canada uses to decide which of several qualified contractors receives a request to perform a task under a multi-contractor contract. It applies where more than one contract has been awarded and individual tasks are assigned later through task authorizations. The process identifies a contractor, generally according to stated ranking or allocation rules, and sends that contractor the task request.

The term appears in task-authorization contracting. It sits alongside related concepts such as the Task Authorization (TA) process, Statements of Work (SOWs), ranked contractors and the right of first refusal. A Government of Canada challenge-based solicitation for IaaS and Native PaaS uses WAP as the heading of section 6.5 and refers to it in section 6.4 as the mechanism for selecting one of two contractors to receive a task request.

How the WAP selects a contractor

In the IaaS and Native PaaS solicitation, the contracts were established with task authorizations. The solicitation states that when more than one contract is awarded, one contractor will be invited to sign a task authorization in accordance with the WAP. The contractor identified by the WAP is the one that receives the request to perform the task.

The WAP therefore works as a gatekeeper between contract award and actual work. Winning a place on a multi-contractor contract does not by itself guarantee any task. The work reaches a contractor only when the WAP points to it and a task authorization is issued.

Second-ranked contractors and the 48-hour right of first refusal

Ranking is central to how requests move. In the IaaS and Native PaaS solicitation, if the contractor identified by the WAP confirms in writing that it cannot perform the task, the request is forwarded to the contractor ranked second.

A separate procurement for VIA HFR follows a similar logic. Under that services solicitation, VIA HFR requests services through Statements of Work from the highest-ranked qualified proponent in each stream, on a right-of-first-refusal basis. If that proponent cannot confirm capacity within 48 hours, the request moves to the next-ranked qualified proponent.

• The highest-ranked qualified contractor or proponent is asked first.
• A written confirmation that it cannot perform sends the request down the ranking.
• In the VIA HFR model, silence past 48 hours has the same effect as a lack of confirmed capacity.

Declaring unavailability under the WAP

A contractor can step out of the rotation temporarily. In the IaaS and Native PaaS solicitation, a contractor may notify the Technical Authority and the Contracting Authority in writing that it is unavailable for additional tasks because of previous task authorizations. No further request is sent to that contractor until it confirms that it is available again.

This gives contractors a formal way to manage workload without breaching the contract. It also puts the responsibility on the contractor to tell Canada when its capacity changes, in writing and to the correct authorities.

Starting work only after an authorized task authorization

Selection through the WAP is not permission to begin. The solicitation requires the contractor to receive an authorized task authorization before starting work. Work performed before an authorized TA is received is at the contractor's own risk, which means Canada has no obligation to pay for it.

What the WAP means for suppliers bidding on Canadian public contracts

If a solicitation will result in more than one contract, read the sections on task authorization and work allocation before you price or position your bid. Your ranking or place in the allocation rules determines how often task requests reach you.

• Monitor the channels named in the contract and respond to task requests promptly.
• Confirm capacity, or the lack of it, in writing when asked. In the VIA HFR model, the window is 48 hours.
• Notify the Technical Authority and Contracting Authority in writing if existing commitments mean you cannot take more tasks.
• Do not start work until you hold an authorized task authorization.

Each solicitation sets its own allocation rules, so check the specific wording in every bid document rather than assuming one model applies everywhere. Additional guidance on federal procurement practice is published in the Supply Manual annexes on CanadaBuys.