Skip to main content
Procurement CompassClear plans. Stronger business cases.
Getting started

Step-by-step guide · 6 minute read

Manage the policy library

Upload a source, verify extracted text and control which version is active.

For document administrators, workspace administrators

Before you start

Your account needs Administer shared procurement documents permission. Obtain a source approved for Destination Ontario and its verification URL and dates. This guide uses a fictional workshop brief; it is not a policy source.

Our example is Visitor research workshops, a fictional purchase by Strategy and Insights, estimated at CAD 18,000 and needed by December 18, 2026. It is a training example, not a policy determination.

Upload an inactive version

  1. Open Administration, then Documents, and select Upload document.
  2. Enter a stable Document key. Reuse the same key when replacing an existing document; select Upload new version from its document record.
  3. Choose a searchable PDF or UTF-8 text file, up to 20 MB, 300 pages and 2 MB of extracted text. Scanned PDFs need OCR first.
  4. Enter the Document title, HTTPS Source document URL, Reference type, Effective date or applicability dates and Retrieved date.
  5. The organisation context is fixed to Destination Ontario as a provincial agency. Enter the First scope/context page. Select Upload and review text. The new version is inactive.

Review before activation

  1. Compare extracted pages to the original. Check that tables, numbers, headings and dates are readable and accurate.
  2. Verify the source details, relevance to Destination Ontario and first scope/context page. Resolve extraction problems before using the document.
  3. When the version is approved for staff use, select its activation action and read the availability confirmation before submitting.
  4. For a replacement under the same key, confirm that the intended version is active. Earlier versions remain in history.

Remember: The first scope/context page is prioritised; earlier cover and contents pages are excluded from search.

Retire and replace deliberately

Retire a version when it should no longer be used for new evidence selection. Review the availability confirmation before submitting. Existing requests retain the source versions already saved with them. Replacing a document does not update those requests or their AI policy checks.

Screen example

Administrator view · fictional purchase

Document upload fields containing a fictional workshop planning brief, before submission.
Training example only. The fictional brief was not uploaded or activated. The example.invalid URL is a placeholder, not an operational source. Open full-size screenshot (new tab)
  1. The Document key groups versions. Reuse it when replacing a document.
  2. Choose the correct Reference type and supply a genuine HTTPS verification URL for operational documents.
  3. Record applicability dates and review relevance to Destination Ontario before activation.
  4. Upload and review text creates an inactive version. Review the extraction before activating it.

This screenshot was captured using administrator access. The default example follows your access for shared tasks; guides for another role show that role’s example. Choosing another example changes only the illustration. Requesters work on their own requests; reviewers can work on all requests but need requester access to create one. Controls also depend on the request’s status. On smaller screens, controls may move below the draft or into the Menu.

What success looks like

The intended approved version appears as active in document administration and is available in Destination Ontario’s policy library.

Common questions

The upload contains no usable text.

Use a searchable source or perform OCR before uploading. Check extraction again before activation.

The file version already exists.

Review the existing version under the same key instead of creating a duplicate. Activate it only after the normal content review.

Content owner: Policy library team
Last verified against the interface:

Instructions describe the app’s workflow. Procurement applicability and formal approvals remain with your responsible staff.