Issue RFT, RFP & RFQ Packages. One Auditable Record.
Compose a complete tender package once — title, scope, closing date, cover letter, recipients, documentation and submittal criteria — then track every response, addendum and submission in a single controlled record alongside project correspondence.
Why Email + Spreadsheets Is Not Enough
Scattered invitations, missing attachments and untracked responses create commercial risk. Methvin turns the same process into a single, owned, auditable tender package.
- Email invitations sent individually
- Attachments missing or outdated
- Who has opened the package?
- Chase responses in separate threads
- Addendum buried in inbox
- “Which version of the drawings?”
- Reconstruct the record for audit
Deterministic Control Over Every Package
Four capabilities that turn unstructured tendering into a contractually sound, auditable procurement record.
Four-Step Package Wizard
Compose once: Package Details (title, RFT/RFP/RFQ type, closing date, cover letter), Recipients by trade/company/contact, Attachments, then Submittal Requirements and Requested Documents. Nothing leaves until you click Send.
Defined Submittal Criteria
Pre-set and custom Submittal Requirements (conflict of interest, validity period, inclusive pricing) plus Requested Documents (Schedule of Prices, methodology, programme). Recipients must answer every item before Submit is enabled.
Addenda vs Mail Separation
Formal changes to scope, dates or commercial terms are issued as Addenda and form part of the contractual baseline. Day-to-day clarification travels as Mail — keeping the formal record clean and searchable.
Live Recipient & Submission Tracking
Status moves from Pending → Will Price → Submitted. Progress icons show when a recipient has opened the package and when a formal response has been received. Click through to the submission itself.
Everything Needed for Controlled Tendering
Built for estimators, procurement managers and contracts administrators who need more than an email chain.
Package Types
Request for Tender for formal binding responses, Request for Proposal for methodology plus price, Request for Quotation for defined-scope pricing. Same controlled workflow for all three.
Learn more →Recipient Selection by Trade
Expandable Trade → Company → Contact tree. Select an entire trade or individual contacts. Add missing contacts at the point of composition. Recipients can still be added after issue.
Learn more →Controlled Document Folder
Attach drawings, specifications and schedules from device or the project Files workspace. Each package maintains its own document folder under its mail reference. Download All available for export.
Learn more →Access & Security Controls
Sender-only Access & Security tab. Restrict specific team members from viewing a package while keeping the rest of the project team operational. Clean external records for tenderers.
Learn more →Email vs Generic Tools vs Methvin
The differences that matter when the tender period closes or an audit arrives.
| Capability | Standard Email | Generic PM / Bid Tools | Methvin Publish Tender |
|---|---|---|---|
| Structured package types (RFT / RFP / RFQ) | None | Limited or manual | Native classification at source |
| Mandatory submittal criteria before response | None | Optional forms | Submit blocked until complete |
| Formal addenda vs day-to-day mail | All mixed in threads | Often undifferentiated | Separated contractual baseline |
| Live recipient status (Pending / Will Price / Submitted) | None | Basic open/read flags | Tracked with click-through to response |
| Single auditable package record | Reconstruct from inboxes | Fragmented across modules | One record with full history |
| Integration with project correspondence | Separate silo | Usually separate | Same workspace as RFI & Mail |
Built for Packages That Cannot Afford Ambiguity
Trade packages, formal tenders and quotations generate commercial commitments. Only a structured system turns volume into control and a defensible record.
- Four-step wizard enforces complete package definition before issue
- Recipients answer every Submittal Requirement and Requested Document before Submit is enabled
- Addenda update the contractual baseline; Mail handles routine clarification
- Live status tracking from Pending through Will Price to Submitted
- Documents held in a controlled package folder with version visibility
- Full package history retained alongside project RFIs and correspondence
From Composition to Submittal
A single controlled path for both the issuing team and the receiving tenderers.
Compose
Define package details, select recipients by trade tree, attach documentation, set Submittal Requirements and Requested Documents. Wizard saves progress between steps.
Issue
Send once. Every selected recipient receives the same cover letter, attachments and criteria. Package opens under its mail reference on both sender and recipient sides.
Track & Amend
Monitor status and progress icons. Issue formal Addenda when scope or dates change. Use Mail for clarification. Restrict access where required.
Receive Responses
Recipients answer criteria, attach priced schedules and supporting documents, then Submit. Sender sees green progress and can open the full submission immediately.
Trusted by Construction Professionals
Estimators, procurement managers and contracts teams rely on Methvin for controlled, auditable tender packages.
Every package now has a clear closing date, defined criteria and a live view of who has opened and who has submitted. We no longer reconstruct the tender record from Outlook.
Separating formal addenda from day-to-day mail has cleaned up our contractual baseline. When a dispute arises we can produce the exact package history in minutes.
The requirement that tenderers answer every criterion before Submit is enabled has improved the quality and completeness of responses we receive.
Common Questions
Everything you need to know before moving tender packages out of email.
Can I edit a package after it has been sent?
Yes. Open the sent package and use Edit on Contract Information, or the controls on Submission Criteria and Documents. Changes to the record do not automatically notify existing recipients — issue an Addendum when the change must reach them.
Can I add recipients after the package has been issued?
Yes. Open the Trades panel from the Recipients & Submissions tab and select the additional company or contact. This is independent of the Mail tab, which is used for correspondence with parties already on the package.
What is the difference between Submit, Intend to Respond and Decline?
Intend to Respond signals that the recipient will price the work and moves status from Pending to Will Price. Submit sends the completed response and is only enabled once every Submittal Requirement and Requested Document has been answered. Decline notifies the sender that no response will be made.
Why can’t a recipient click Submit?
Submit remains disabled until every item on the Submission Criteria tab has an answer (Yes / No / N/A). Open that tab and complete any unanswered requirements or requested documents.
How do Addenda differ from Mail?
Addenda are formal, structured changes to scope, timeline or commercial terms and form part of the contractual baseline. Mail is for day-to-day clarification and coordination; it does not alter the contract documents.
Do all recipients receive the same package content?
Yes. Every recipient added in the composition step (or later) receives the same cover letter, attachments, Submittal Requirements and Requested Documents.
Stop Managing Tenders in Scattered Email Threads
Move from fragmented invitations and untracked responses to a single, owned, auditable package record with defined criteria, formal addenda and live submission tracking.
No credit card required · Cancel anytime · Global support