SHEYU.AI舍予基业
Products/SHEYU AIBID
SHEYU AIBID · Bid Writing

AI reads the 100-page tender. One person can write the bid.

A 105-page tender document yields 180 requirements in 130 seconds, each with its page reference. Evidence comes from your own library, drafts are built by volume, and 17 rules check the result.

TENDER RESPONSEVol. I

Contents

  1. 1.1Tender intake✓
  2. 1.2Requirement list✓
  3. 1.3Company library✓
  4. 1.4Response matrix✓
  5. 2.1Global fact sheet✓
  6. 2.2Outline & sections✓
  7. 2.3Pricing✓
  8. 2.4Required forms✓
  9. 3.1Compliance self-check✓
  10. 3.2Mock evaluation✓
  11. 3.3Version compare✓
  12. 3.4Export & submission✓
CHECKED
130 sto parse a 105-page tender (measured)
180requirements extracted from one document
17compliance rules checked automatically
5volumes: qualification, commercial, technical, pricing, forms
AIBID · How it works

Five stages from tender document to submission.

  1. 01

    Read

    Turn a hundred-plus pages into one list.

  2. 02

    Reconcile

    Find evidence that backs each requirement.

  3. 03

    Draft

    Write by volume and section, with marked citations.

  4. 04

    Check

    Run the rules and a mock evaluation first.

  5. 05

    Deliver

    Export by volume only once everything is filled in.

No invented facts

Where there is no evidence, it leaves a gap.

Track records, staff and certificate numbers can only cite entries that exist in your library, and each citation carries an evidence marker. Anything missing is written as [to be supplied].

Every citation marked [evidence]
Missing facts become [to be supplied] placeholders
Export stays locked until placeholders are cleared
Starred requirements must all be answered before export
AIBID · Core capabilities

Read the tender into a list you can answer.

01

Page-by-page reading

docx and pdf, page by page. Scanned pages go through OCR.

02

Sourced requirement list

Every item records its page and clause number. Starred items are flagged automatically.

03

Response matrix with evidence

Requirement × response × evidence × section, reconciled in one table.

04

Drafting by volume and section

Volumes follow the tender's own wording. Citations carry markers.

05

Self-check and mock evaluation

17 rules graded red, yellow, green or grey. Each leaf scoring item is estimated.

06

Re-bids change only the differences

Derive from the previous version and rewrite only the sections that changed.

07

Ask AIBID

A side panel answers questions from the matrix, library and chapters only. If the library lacks it, it says so.

AIBID · Feature map

Twelve modules across the five stages.

01

Tender intake

docx/pdf parsing page by page, OCR for scans, tables and contents restored, per-page coverage visible.

02

Requirement list

Nine requirement types, page references, star flags, manual additions and confirmation.

03

Company library

One library per bidding entity: licences, certificates, finance and social insurance, track record, staff. Expiry warnings; finance hidden from staff.

04

Response matrix

Status, evidence and target section per item; prefill from the library with certificate validity checks.

05

Global fact sheet

Delivery time, warranty, response time and team commitments confirmed once; contradictions across sections flagged red.

06

Outline & sections

Volumes by the tender's wording, chapters by topic, section drafting and rewriting, owners and sign-off.

07

Pricing

Itemised price table, totals and RMB amounts in Chinese words generated, three linked price entries, cost-floor and ceiling warnings.

08

Required forms

Detects the forms the tender requires, refills them from extracted fields, marks seal positions.

09

Compliance self-check

17 rules in four grades, placeholder list, leftover checks, export blockers listed one by one.

10

Mock evaluation

Leaf scoring items estimated with lost-point notes; price score computed.

11

Version compare

Changes from addenda and clarifications; re-bid item pairing; only changed sections rewritten.

12

Export & submission

Export docx by volume, locked until blockers are cleared, submission checklist and seal-page reminders.

Requirement list

Every requirement, with the page it came from.

Each item carries its page, clause number and original wording. A page heat map shows which pages yielded nothing, so a person can check them.

Requirement list
  • Nine requirement types, from qualification to pricing and forms
  • Items under 90% confidence must be confirmed by a person
  • Scanned pages go through OCR; table parameters flagged for checking
  • Manual additions and deletions, logged
  • Starred items: zero misses, confirmed page by page
Who does what

Built for a small team, or one person wearing every hat.

Bid owner

Decides whether to bid and signs off what leaves the office.

  • Reads the feasibility check before any writing
  • Approves each volume for export
  • Sees prices, cost floor and past winning prices
  • Clears starred items the dashboard assigns
Writer (staff)

Does the day-to-day work on requirements, evidence and chapters.

  • Confirms low-confidence requirements
  • Links evidence in the response matrix
  • Drafts and edits chapters
  • Prices, cost floor and finance records are hidden
Document keeper

Keeps the company library complete and in date.

  • Uploads licences, certificates, track record and staff files
  • Gets the certificate-expiry items on the dashboard
  • Fills gaps the matrix reports
Commercial lead

Handles the money side of submission.

  • Gets bid-deposit deadline items on the dashboard
  • Checks deposit amount, form and timing (rule 7)
What it takes off your desk

Bid writing, from one person's craft to a pipeline.

Before
With SHEYU AIBID
Finding requirements
Reading a hundred-plus pages to find every requirement.
A requirement list in 130 seconds.
Know-how
Keeping a dedicated bid writer on staff.
The rules live in the system, not in someone's memory.
Checking for gaps
Checking page by page for anything left unanswered.
Missing items are listed automatically.
Winning odds
Guessing from experience whether the bid can win.
Each scoring item is estimated, with where points are lost.
Global fact sheet

One delivery time. One warranty. Across every chapter.

Chapters are drafted in parallel and cannot see each other. Commitments such as delivery time, warranty and response time are confirmed once and fed to every chapter; contradictions are flagged red.

Facts only from the tender text, the library or manual entry
Values the model proposes must match the source word for word
Only confirmed facts reach the writer
Rule 17 checks the whole text against them
Compliance self-check

17 rules before anything leaves.

Each rule is graded red, yellow, green or grey, and the rule set follows the procurement method. 13 rules come from Article 51 of the Regulations on the Implementation of the Bidding Law and Article 63 of Ministry of Finance Decree 87.

17
  1. 01Signature and seal checklist
  2. 02Joint-bid agreement for consortia
  3. 03Qualification evidence in date
  4. 04One price, in three places, words match figures
  5. 05Price within ceiling; below-cost warning
  6. 06Every starred requirement answered
  7. 07Deposit amount, form and timing
  8. 08No conditions the purchaser cannot accept
  9. 09Bid validity period long enough
  10. 10Volumes in the order the tender sets
  11. 11Copies, binding, fonts and margins
  12. 12Project name, number and purchaser consistent
  13. 13Date logic: signing, track record, certificates
  14. 14Contents and page numbers match
  15. 15Technical deviation table complete
  16. 16Staff and track-record counts met
  17. 17One commitment value across the text
Deadlines first

Bidding runs on a countdown.

The dashboard sorts projects by submission deadline and lists what still blocks each one. A daily check adds the things that cannot be undone once the time passes.

Deadlines first
  1. 01Submission deadline close, with starred items or red checks open✓
  2. 02Bid deposit due and not marked paid✓
  3. 03Certificates expiring before a project's submission date✓
  4. 04Starred items untouched for days after parsing✓
  5. 05Possible re-tenders spotted in LEIDA: same purchaser, similar title, service period ending✓
AIBID · Full specification

Everything SHEYU AIBID does today.

Each line is on the live site or in the shipped workbench.

Tender intake

  • docx and pdf, read page by page
  • No page limit
  • Scanned pages via OCR
  • Tables and contents restored
  • Per-page coverage heat map
  • .doc files: save as docx first
  • Addenda and clarifications uploaded as new versions

Requirement list

  • Nine requirement types
  • Page, clause number and original wording per item
  • Starred substantive items flagged
  • Under 90% confidence: manual confirmation
  • Manual additions
  • Feasibility check before writing: qualification rate, gaps, estimated score

Company library

  • One library per bidding entity
  • Licences, certificates, finance and social insurance, track record, staff
  • Upload scans, photos or PDFs up to 50MB
  • OCR extracts the fields
  • Expiry warnings
  • Finance records visible to the owner only
  • Originals bound into the bid's attachments at export

Response & drafting

  • Response matrix: status, evidence, target section per item
  • Prefill from the library, checking certificate validity against the deadline
  • Volumes named in the tender's own words
  • Chapters by topic, drafted section by section
  • Citations marked [evidence] and [requirement]
  • Missing facts left as [to be supplied]
  • Evidence IDs the model invents become placeholders
  • Past bids as reference for similar chapters
  • Global fact sheet shared by all chapters

Pricing & forms

  • Itemised price table
  • Totals and RMB amounts in Chinese words computed by the program
  • Bid letter, opening summary and itemised table kept in step
  • Ceiling check and cost-floor warning
  • Detects required forms: bid letter, authorisation, opening summary, deviation tables, SME declaration
  • Fields filled from project, entity, price and matrix
  • Seal positions marked

Checks & evaluation

  • 17 rules, graded red, yellow, green or grey
  • Rule set follows the procurement method
  • Leftover check for old names, numbers, years and purchasers
  • Leaf scoring items estimated as a range, with reasons and fixes
  • Price score by the Decree 87 Article 55 formula, computed by the program
  • Lowest-price method: compliance checklist instead of a score
  • Points lost last time flagged first

Versions & re-bids

  • Item-level comparison, not full-text diff
  • Addenda: what was added, removed or changed
  • Re-bid: derive chapters from the previous project
  • Project name, number, purchaser and dates replaced
  • Affected chapters marked rewrite or proofread
  • Library changes since the last bid listed
  • Split a tender into lots as separate projects
  • Record score and rank after bid opening

Export & delivery

  • docx per volume; PDF for final layout
  • Export locked while blockers remain
  • Owner approval per volume
  • Printable delivery sheet: copies, binding, sealing, place and deadline
  • Seal and signature checklist
  • Download log for every file
  • Mark as submitted, then await bid opening
Bids are rarely lost on the proposal. They are lost on one missed requirement.
Works with LEIDA Tender Radar

The radar finds the tender. SHEYU AIBID starts the bid.

On a notice page in LEIDA, one click on "AI write bid" creates the project. Purchaser, title and attachments come across; public attachments are fetched automatically, and you are asked to upload any it cannot reach.

Project created from the notice
Purchaser, title and attachments carried over
Requirements parsed on arrival
Price reference from the same purchaser's award notices in LEIDA

Supported and handled

Open tenderCompetitive consultationCompetitive negotiationdocxpdfScanned pagesBid letterAuthorisation letterOpening summaryItemised price tableTechnical deviation tableCommercial deviation tableSME declarationAddendaClarificationsLotsConsortium bidsRe-bidsOpen tenderCompetitive consultationCompetitive negotiationdocxpdfScanned pagesBid letterAuthorisation letterOpening summaryItemised price tableTechnical deviation tableCommercial deviation tableSME declarationAddendaClarificationsLotsConsortium bidsRe-bids
Open tenderCompetitive consultationCompetitive negotiationdocxpdfScanned pagesBid letterAuthorisation letterOpening summaryItemised price tableTechnical deviation tableCommercial deviation tableSME declarationAddendaClarificationsLotsConsortium bidsRe-bidsOpen tenderCompetitive consultationCompetitive negotiationdocxpdfScanned pagesBid letterAuthorisation letterOpening summaryItemised price tableTechnical deviation tableCommercial deviation tableSME declarationAddendaClarificationsLotsConsortium bidsRe-bids
FAQ

Questions about AIBID

What is a starred requirement?

A substantive requirement in a Chinese tender document, usually marked ★. Leaving one unanswered gets the bid rejected, so AIBID flags them automatically and blocks export until each has a response.

Which procurement methods does it support?

Open tender, competitive consultation and competitive negotiation.

Where do the 130-second and 180-requirement figures come from?

A measured run on a real, publicly issued 105-page tender document.

Will it write content it cannot back up?

No. Track records, staff and certificate numbers only cite what is in your library. Anything missing is left as a placeholder.

What do I need to prepare?

Your company library: licences, certificates, track record and staff. A complete bid depends on those being uploaded.

Does it submit the bid electronically?

No. Encrypted bids are generated by the trading platform's own client; AIBID exports docx and PDF to import there, or to print, seal and deliver by hand. Once submitted, you mark it and the project waits for bid opening.

Can staff see our prices?

No. Staff do not see prices, the cost floor, past winning prices or finance records. Volume approval and export belong to the bid owner.

Does the mock evaluation predict whether we win?

No. It looks for weak spots: each leaf scoring item gets an estimated range with reasons. The price score is computed by formula, not by the model.