Skip to content

Procurement

Procurement helps your organization review public buying requests, called notices. A notice can contain separate lots. EosHQ collects public notices centrally, then assesses them separately against each customer's business and monitor requirements. Your company's decisions and private documents are not shared with other customers.

Before you start

You need an active Procurement license assigned to you in the current organization. Your administrator must enable Procurement processing in Settings. Check the organization name before working. A Procurement-only license includes access to procurement-linked Opportunities inside this module.

Step 1: Describe your business

Open Sales > About your business. Review and publish your products, services and markets. Be specific about what you sell: a Salesforce software product and Salesforce consulting are different offerings. The website URL uses the same value as Settings.

Step 2: Choose sources

Open Sources and coverage or US states. Turn on Monitoring for each source your organization wants, enter the additional monitor requirements, and click Save. US states share one requirements description. State sites that cannot currently be monitored are omitted; the page explains that technical limitations prevent their inclusion. Use the request form to request another state, city or agency.

There is no Check every setting. EosHQ collects public sources daily, with bounded continuation while more pages remain. A source's last successful page is not proof that its entire history has been collected. Check its coverage and error information. Older notices may still be arriving during the initial scan. Technical or source limits can delay collection.

Step 3: Receive assessments

New and changed notices are queued automatically for enabled organizations. You do not need to press a button each day. Assess latest queues a check of the current shared catalogue against your saved settings. It does not download a separate source copy or finish all AI work immediately.

Use the Notices list to review Relevant notices. Other views show Needs verification, Excluded and Processing records. Needs verification means the available evidence cannot support a confident decision. It is different from a poor fit. Missing content or attachments may explain this status. Monitor run reports show pending work and failures.

Step 4: Review a notice

Click a row or open it with the keyboard. AI Assessment opens first. Original Text shows the available source content. Related Documents contains assessment evidence, translations and available public attachments. Check source links and deadlines before acting. Fit is a recommendation, not proof of eligibility.

Click a column heading to sort. Choose the number of rows per page. The search icon reveals additional filters. Dates without times use DD-MMM-YYYY; date-times use your display settings.

If any organization finds a public notice relevant, or supporting documents may resolve uncertainty, EosHQ queues public attachment retrieval. Original public files are downloaded once and reused. Assessments are refined as new content becomes available. Some attachments require supplier access or cannot be downloaded or read; the module shows those limitations.

You can press Get attachments even on an excluded notice. It queues available public documents and subsequent reassessment. It does not bypass supplier sign-in. The original notice remains authoritative. Translate notice creates a saved translation into your organization's configured language; review AI-generated translations against the original.

Step 5: Record your decision

Mark reviewing means someone is reviewing the notice. Dismiss records that you do not intend to pursue it. Restore to New resets the review status; it does not undo a pursuit or change the fit assessment. You can dismiss individual lots.

Pursue opens a confirmation form. Confirm the buyer, territory, selected lots, owner and first action. The default owner is you. On confirmation EosHQ creates an Opportunity and first Activity, reusing an existing pursuit of the same buying process. It does not submit a bid or contact the buyer. Known source facts are included; unknown forecast values remain blank. Review and update the linked Opportunity in Related Documents, including with a Procurement-only subscription.

Step 6: Choose your email updates

In Sources and coverage, choose When assessment finishes, Daily digest or Off, then save your personal email preference. Active licensed users receive their own organization's results. Reports distinguish relevant notices, excluded notices, uncertainty and failures. A source scan and an organization assessment are different operations; an assessment-complete email is not a promise of complete worldwide coverage.

Stop processing and retain records

An administrator can disable company Procurement processing in Settings. This stops your company's automatic assessment and notifications. Public collection can continue for other customers. Saved company records remain available for review.

EosHQ never automatically deletes organization records. Shared public notices, saved versions and collected public attachments are retained in the historical archive for future customer assessments, including after their submission deadlines. Historical fit reports stay private to the organisation that requested them.

Delete is a separate, explicit user action for an unpursued notice. It removes your organization's item and its deletable private evidence, while preserving an audit entry. It does not delete other organizations' data or the shared catalogue. Pursued records are protected.

Chat and Agents

You can list, read, assess, translate, request attachments, record decisions, pursue and review/update a linked Opportunity through Chat or Agents with the same permissions as the web app. Configuration changes, including business descriptions, source switches and email preferences, are available only in the web app.

Troubleshooting

  • No Relevant notices: check that processing and the desired sources are enabled and your business profile is published. Check Processing and Needs verification before concluding there are no opportunities.

  • Collection is partial: more source pages or historical windows remain. The monitor saves its place and continues within its limits.

  • Assessment stays pending: processing capacity, daily allowances, retries or attachment retrieval may be delaying it. Check the report before pressing Assess latest again.

  • A document is unavailable: open its official source. Do not assume an incomplete notice proves fit or eligibility.

  • No email: check your personal preference, active license, organization processing switch and whether assessment has finished. Delivery failures are recorded for support.

See past opportunities with Historical fit

  1. Open Sales, Procurement, then Historical fit.

  2. Check that About your business is published and the sources you need are enabled.

  3. Select New historical search to open the search popup, then choose the publication dates. The default is the past three years; one report can cover up to three years.

  4. Leave “Email me when this report finishes” checked if you want a completion email, then select Run historical search.

  5. Use Refresh runs to update the table. It shows when each run was requested, who requested it, the publication period, status and saved result counts. Click a run to open its results in a large popup. Use Refresh results inside that popup to update it. You can leave the page while processing runs. Only one report runs at a time for your organisation.

  6. Open the report and read Source coverage and limitations. A completed report can still have gaps because collection is incomplete or source documents are unavailable.

  7. Use Results in this run to choose a result category. All results is selected initially; each option shows its saved count. The filter applies only to the open run. If no results have been saved, the filter is hidden and an explanation appears. A run waiting for organization tokens or standard AI capacity shows its retry status; zero results at that stage does not mean no notices fit your company. Click a column title to sort; use Prev, Next and the rows control to browse.

  8. Click a notice to read the saved assessment, supporting quotations and original text. Historical results do not create active notices or Opportunities.

  9. Select Cancel report to stop work while keeping partial results. Your organisation can also pause all Procurement processing with its existing processing switch.

  10. Request a new report after the archive grows or your business description changes. Earlier reports keep their original business profile and conclusions.

The report applies your current capabilities to past public notices. It does not prove that you met every bidding condition at that time or would have won a contract. Closed notices are examples of past demand. Public history is retained centrally for later reuse; your company's assessments remain private. Completion emails include counts and coverage limitations. An email marked “delivery unknown” has not been confirmed by the email provider and is not automatically resent.

Fit corrections and daily results (05-Oct-2026)

A missing platform keyword does not decide relevance. The AI first compares the actual purchased scope with the organization's offerings. A bounded organization-token-funded AI scope screen may reject clear mismatches with exact notice quotations. Ambiguous or plausible scope continues to detailed assessment. Missing notice content has its own Content unavailable category; it is not a completed fit assessment. Potential matches request available public attachments before final batch reporting.

In a notice's AI Assessment tab, use Correct the fit assessment to choose Relevant or Not relevant and supply a reason. Check Use this correction as an example only if future assessments should use it. These examples stay within the organization, never override published requirements, and do not automatically create exclusion rules. Up to 50 examples can be retained; the latest 12 are supplied to each assessment. Review matching examples lets users remove an example without removing the notice's correction. Clear correction and reassess removes that notice's manual override and example. Dismissal, review and pursuit remain workflow decisions and do not train fit.

A manual correction survives later automatic assessment and notice updates until explicitly cleared. Review it when the source changes. Changes and removals are audited. Chat and Agents expose procurement_feedback, procurement_feedback_list and procurement_feedback_forget using the same access checks.

Email defaults to a daily digest; an explicit Immediate or Off preference remains respected. Counts distinguish detailed AI assessments, AI scope evaluations, manual classifications, plausible matches needing verification and content unavailable. Old platform-shortcut results are repaired by an audited requeue, not treated as completed AI assessments. Existing historical reports containing those results are marked superseded and linked to a replacement report where access and processing settings permit. Archive completeness remains separate from report completion.

Product fit and historical demand

The default Potential matches list includes relevant notices and plausible matches whose explicit requirements still need verification. A buyer can match one of your products or services; they do not need to buy everything your company sells. Your monitor instructions remain requirements. For example, a suitable time-tracking purchase may have a potential functional fit while its Salesforce compatibility is unconfirmed. Check the assessment before pursuing it.

Historical reports include awards as evidence of past purchasing demand. An award is not an open invitation to bid. Completed assessments, unavailable content, waiting content and failures have separate counts. Zero matches in an incomplete report does not mean there was no market demand.

Sources display their archive target and collection progress. A completed date scan does not guarantee every historical record is available. Technical limits, source credentials and archive availability still apply. A source rate limit pauses retrieval and preserves pending work. Your organization can stop Procurement processing at any time.

Published contract awards

Open a notice or a Historical fit result to see Published contract awards. Where the public source reports them, this section shows the winning supplier, buyer, contract number, awarded lots, award date, contract-signing date and value. Open Source evidence to inspect the original fields or quoted winner section. A winning tender value is labelled as such.

Public notices and their award information are collected and extracted centrally and reused across licensed organizations. Your company's assessments, notes, decisions and private documents remain private to your organization. Missing information means it was not extracted from the saved source; it does not mean no award occurred. An old award is evidence of past purchasing, not proof of an open tender or a current supplier relationship.

Organization tokens and email preferences (06-Oct-2026)

Procurement has no separate daily assessment quota. Screening, detailed assessments, historical searches and translations use your organization’s existing token allowance. You can see this use in the same usage reports as other AI work. Processing runs in controlled batches with safeguards against repeated or overlapping work. If your allowance is unavailable, work pauses and retries automatically. It does not mark the notice as a failed assessment.

Turning on a source switch displays a top banner explaining that Save is required. After Save, eligible existing and newly collected notices are assessed automatically in batches; Assess latest is optional. A company processing pause remains respected.

My Procurement email updates supports immediate completion reports, daily digest, weekly digest, relevant-notice alerts only, relevant-notice alerts plus weekly digest, and Off. Relevant-notice alerts require a Relevant assessment; Needs verification is not enough. Weekly digests begin seven days after selecting the preference and summarize newly completed batches. If no batches completed, no digest is sent. Combined mode retains alerted results for the weekly summary without resending the immediate alert. Large digests may be sent in bounded parts. Each user’s preference applies within the current organization. Requested historical-report completion emails retain their separate checkbox. Unknown email delivery is not automatically retried.