BlueprintOpen Blueprint
  1. Start here
  2. Navigate Blueprint
  3. Find opportunities
  4. Build responses
  5. Build tender offers
  6. Reuse knowledge
  7. Run sourcing events
  8. Evaluate and award
  9. Govern orders
  10. Administer the platform
  11. Trust and AI controls
  12. Feature directory
  13. Access and support

Blueprint product guide

Use Blueprint to discover work, turn tender packages into governed responses and offers, run sourcing events, compare bids, approve awards, and manage the resulting order. Every AI-assisted value keeps its source; people confirm the decisions that bind the company.

RespondFind tenders, build responses, and price offers.ProcurePublish RFPs, evaluate bids, and govern orders.AdministerConfigure people, knowledge, models, and access.

Start here

Blueprint has two product modes. Respond is for teams pursuing and answering buyer requests. Procure is for teams issuing RFPs and choosing suppliers. An organization may have either mode or both; the switcher changes the work shown without creating a second account.

The operating rule

AI extracts, drafts, and recommends. People verify evidence, accept commercial commitments, approve publication, and decide awards.

Navigate Blueprint

Dashboard

The command centre opens on the work: a one-line greeting with how many pursuits or events are waiting and the next deadline, the most urgent decision, live figures for active responses or events, pipeline or committed value, and new matches or bids, then a work queue grouped by kind of work or by stage. On phones it becomes a stack of light cards.

Global search

Search responses, RFPs, Library entries, and questions from the top bar. Use the quick-action command palette for common navigation.

Notifications

Receive approval requests, decisions, and workflow updates. Organization branding identifies the tenant; Bloomteq remains the platform provider.

Organizations and branches

Switch organizations when authorized. Super admins can open any active organization through clearly labeled platform access without becoming a customer member. Branch visibility keeps private work scoped while allowing intentional company-wide sharing.

Bloomteq © 2026 · BlueprintBack to the guide

Find opportunities worth pursuing

Opportunities brings official public tender notices into one queue. Blueprint normalizes different markets, applies your company profile, and explains the fit instead of hiding the decision in an AI score.

  • Configure fit: add capability tags, interests, markets, languages, classifications, delivery locations, and commercial limits. Discovery is profile-aware: notices that match your capabilities or classification codes are kept even when they fall outside a source’s most recent window.
  • Control sources: enable only connectors with a reliable path to the authoritative package. Store authorized access details where supported, or require manual upload.
  • Review the evidence: inspect title, buyer, dates, value, classification, source links, and the reasons behind the match.
  • Make a governed decision: watch, pursue, record no-bid with a rationale, or dismiss. Pursuit creates one source-backed response workspace.
  • Acquire the package: each opportunity states its package route up front: auto fetch, authenticated, manual, or notice only. Fetch public documents where permitted, or skip the fetch when you already hold the files. A notice alone is retained for audit but does not become drafting evidence.

Build RFP and RFI responses

Response workspaces carry an incoming request from source package to approved delivery. RFPs use a brief-and-proposal workflow; RFIs use a question work queue. Both support multiple documents, assignments, collaboration, evidence, revision history, and governed delivery.

  1. Start the responseUpload every RFP or RFI file together. PDF, Word, Excel, text, images, and ZIP packages are supported, subject to the configured file limits.
  2. Review the analysisBlueprint processes the documents in the background, preserves each source, extracts the request, and highlights missing or ambiguous information.
  3. Coordinate the responseAssign owners and due dates, use the engagement plan, discuss work in the response chat, and keep branch or company visibility explicit.
  4. Draft and verifyFor an RFP, review the brief and mandatory requirements, ask the package questions, then build the delivery approach and executive summary from your approved company narrative, with AI as an optional pass. For an RFI, work question by question, retrieve approved Library evidence, draft grounded answers, and sign them off; the same company narrative builds an optional executive summary and delivery approach for the front of the response.
  5. Deliver in the right formatWrite answers back into a mapped buyer workbook where supported, or generate a branded Word or Excel response. Delivery approval remains a human gate.

The response record is a stack of four stages: setup, source material, build, and review. Each stage is a disclosure whose folded header states its live state in words, the stage holding the next action opens by default, and your open or closed choices are remembered. The buyer RFP record uses the same stages.

Buyer-format delivery

When the buyer supplies an Excel questionnaire, confirm the detected layout before writing answers back. Blueprint preserves formulas, validation lists, protected cells, macros, and untouched workbook content.

Turn a tender into a viable offer

The Tender-to-Offer workspace connects the buyer’s cited request to the supplier’s reusable commercial structure. The same engine supports products, parts, professional services, subscriptions, bundles, one-off charges, and mixed offers without making AI the pricing authority.

  1. Confirm the buyer requestBlueprint turns ready source documents into cited request lines, quantities, requirements, dates, terms, and required files. A person confirms the snapshot before pricing starts.
  2. Attach a price listChoose a published price list containing products, parts, services, subscriptions, bundles, charges, rates, rules, and reusable evidence.
  3. Resolve mappingsReview suggested matches, then explicitly map, configure, substitute, include, exclude, or leave each buyer line unresolved. No mandatory line is allowed to disappear.
  4. Calculate the offerBuild one or more scenarios using fixed, unit, tiered, recurring, usage, resource, milestone, cost-plus, or included pricing. Calculations use confirmed inputs and retain a readable trace.
  5. Approve and packageTechnical approval confirms scope and evidence; commercial approval confirms price and terms; final sign-off pins the exact versions before buyer-format and branded packages are exported.

Price lists

Admins manage reusable price lists under Admin → Price lists. Models belong to the organization: each tenant keeps its own published models and its own default, and nothing is shared between organizations. The picker leads with the organization’s existing structures, which can be copied into a new draft, and folds the generic starters away; software starters appear only for organizations whose profile sells software. A model can be built manually or staged from PDF, Word, Excel, CSV, text, or image rate cards. Imported values keep source evidence and remain unverified until a person reviews the item, unit, pricing method, and sell price. Internal cost is optional unless the organization enables margin governance.

Amendments and scenarios

Each scenario pins exact request and model versions. An amended tender creates a new request snapshot, identifies affected work, and invalidates only the decisions, approvals, and artifacts that depend on a change.

Reuse and govern response knowledge

Response Library

Store approved reusable answers and the company narrative (company overview, delivery approach, differentiators, certifications, references, key people, executive summary opener), search by meaning or keyword, trace each answer to its source, and see when it was last verified and reused.

Review and history

Assign reviewers, retain immutable prior versions, renew review dates, and surface conflicts rather than silently choosing between contradictory answers.

Duplicate review

Resolve exact and high-similarity entries by keeping, merging, or dismissing a pair while preserving the governance record.

Response desk

Work the operational queue for overdue tasks, deadlines within seven days, low-confidence answers, and stale high-use Library content.

Run a governed sourcing event

The buyer workflow separates authoring, publication, sealed collection, evaluation, and award so a convenient interface cannot bypass the underlying approval rules.

  1. Author the RFPCreate the business context, requirements, response instructions, evaluation criteria, weighting, dates, and supporting documents on the full authoring page.
  2. Approve and publishNamed approvers clear the publishing gate. Blueprint then opens the sourcing event and creates a tokenized vendor submission link.
  3. Collect sealed bidsVendors review the request and submit without a platform account. Offers remain sealed until the governed opening step.
  4. Compare and scoreBlueprint aligns submitted offers, exposes source evidence, calculates the configured score, and lets committee members record independent scores and notes.
  5. Sign off the awardA person selects the vendor and records the rationale. Named award approvers clear the final gate before a purchase order is created.

Evaluate offers and decide the award

The Workspace aligns every opened offer against the published criteria. Desktop uses a detailed comparison ledger; mobile uses stacked vendor comparisons so the same evidence remains reachable without editing a wide table.

Scoring balance

The automated score comes from the category evaluation model in Admin → Procurement setup. It is one ledger: every scored attribute has a weight in percent, the column must add up to 100%, and a Rebalance action scales the weights proportionally. Catalog attributes and company-specific attributes matched from SLA or compliance text join the same ledger, each with its evidence source and, for numeric SLAs, whether higher or lower is better. There is no separate set of scoring sliders.

  • Filter and rank offers while keeping the automated score separate from committee judgment.
  • Open any extracted value to inspect its document source, confidence, and review state.
  • Review incomplete offers and prepare vendor clarification drafts without sending them automatically.
  • Confirm or correct flagged fields, rescore from the current rules, and record committee scores and notes.
  • Select a vendor only after required evidence is reviewed, then route the award to named approvers.

Govern the order after award

Orders preserve the handoff from the approved bid to delivery. The orders book opens with the open commitment, orders by stage, and the next delivery or the count past due, then one row per purchase order with its stage rail, next step, delivery date, owner, and value. A single order shows the next step with an inline note field and, for closing, an explicit reconciliation confirmation, beside a timeline of who recorded each milestone. The order retains its source RFP, approved supplier, value, line items, and audit trail.

Administer the platform

People and roles

Invite members, assign roles and home branches, remove access, and keep approval authority separate from daily operation.

Branding and documents

Set the organization identity, logo, contact details, document theme, and notification branding used on new outputs.

Integrations

Connect approved collaboration, CRM, SharePoint, and opportunity-source services. Enterprise identity, OCR, and storage remain deployment-managed adapters.

Procurement setup

Set the scoring balance per RFP category: which attributes are scored, from which evidence, and what share of the score each carries. Add company-specific attributes and see them land in the ledger before saving.

Price lists

Publish versioned supplier catalogues, rate books, pricing rules, evidence, and commercial policies for reuse across responses. Every model is scoped to the organization that owns it.

Tenant management

Super admins create each isolated customer tenant, appoint its first owner, choose Respond, Procure, or both, and suspend or reactivate access without deleting the customer record. The organization switcher opens any active tenant in an audited platform context; it does not create a membership.

Roles and access

Access levelPurpose
OwnerControls the organization, membership, branches, settings, and operational work.
AdminManages people and configuration and can operate the organization’s enabled product areas.
OperatorRuns daily sourcing, response, document, drafting, and analysis work without gaining approval authority.
ApproverReviews evidence and records governed response, publishing, commercial, or award decisions.
ViewerReads records available to their organization and branch without changing them.
Super adminA separate platform capability. It controls which Blueprint products each organization receives; it does not replace the person’s organization role.

Understand trust, evidence, and AI controls

Provenance
Extracted values retain the source document, location, confidence, extractor identity, review state, and original value when corrected.
Human authority
AI may extract, summarize, draft, and recommend. It cannot approve publication, invent a commercial fact, confirm equivalence, accept a contract, decide an award, or submit on a person’s behalf.
Deterministic calculation
Scores and prices are reproduced from pinned inputs and explicit rules. AI output is not used as an untraceable calculator.
Audit trail
Important actions are tenant-scoped, append-only, and hash-chained so silent history changes are detectable.
Isolation
Data access is session-driven, tenant-scoped, branch-aware, and enforced on the server. Protected internal costs are hidden from roles without commercial authority.
Recovery
Background document and AI jobs are retryable. Missing files, uncertain extraction, stale amendments, and unsupported content remain visible rather than completing silently.

Feature directory

Use this directory to find every primary product surface and understand why it exists.

FeatureWhereWhat it does
DashboardOverviewSwitch between Procure and Respond, read the command centre’s live figures, and open the next work that needs attention.
InsightsOverviewReview response, procurement, branch, deadline, and knowledge-governance trends.
OpportunitiesRespondDiscover public tenders, filter by explainable fit, and record watching, pursue, no-bid, or dismissed decisions.
Company profileOpportunities → ProfileSet capabilities, interests, markets, languages, classifications, value ranges, and delivery constraints used by opportunity matching.
Source settingsOpportunities → SourcesEnable supported markets and choose public, manual, licensed, or authenticated package access without treating a notice as the full RFP.
ResponsesRespondCreate multi-document RFP or RFI workspaces, analyze source files, coordinate people, draft, approve, and deliver responses.
Source documentsResponseSee processing status, retry failed work, inspect original files, and download the authoritative package.
Response LibraryRespondSearch, review, version, reuse, verify, and de-duplicate approved response knowledge with provenance and review dates.
Response deskRespondFocus on overdue tasks, upcoming deadlines, low-confidence answers, and Library entries needing review.
Offering ModelsAdmin → RespondCreate the organization’s reusable products, parts, services, subscriptions, bundles, charges, rates, costs, rules, and evidence; copy an existing structure or import rate cards for human verification.
Procurement setupAdmin → ProcureSet the per-category scoring balance: scored attributes, their evidence, and weights that add up to 100%.
Tender-to-OfferResponse → Build tender offerConfirm the buyer request, map supplier components, calculate scenarios, govern approvals, and generate submission packages.
RFPsProcureCreate, approve, publish, archive, restore, and manage sourcing events through their full lifecycle.
Vendor portalPublished RFPGive each invited vendor a tokenized link to review the request and submit a sealed offer without an account.
WorkspaceProcureOpen bids, compare normalized values, inspect evidence, resolve clarifications, verify fields, score, and award.
Vendor DocumentsProcureRetain submitted vendor files and their processing records.
OrdersProcureRead the orders book, then govern issue, supplier acknowledgement, receipt, and closeout on each purchase order with inline notes.
ActivityRecordsReview the ordered, hash-chained record of important actions and decisions.
Organization SettingsAdminManage profile, account, team, roles, customer-managed branches, branding, document templates, and integrations.
Tenant managementSuper adminCreate isolated customer tenants, appoint the first owner, choose the modules each tenant can use, and suspend or reactivate a tenant while preserving its record.

Access and support

Your organization administrator grants access and assigns the role and branch matching your work. If you already have an account, sign in to Blueprint. If a feature is missing, first confirm the organization has the module for it switched on and that your role is authorized for that action.

For account, integration, or workflow support, contact your organization’s Blueprint administrator.