Template · ProcurementUpdated October 17, 2026

EDC quote request template: the details vendors need to give a real price

A vague request gets a vague quote and a surprise invoice. This template gives you a structured block to paste into an RFQ, covering study parameters, modules, change orders, fees and exit terms, plus a note on how to compare the replies.

  • Copy-paste RFQ block
  • Fees and change-order terms
  • Exit and data export

Free sandbox · No credit card · 21 CFR Part 11 aligned

RFQ completeness · demo request

Sections filled

7 of 9

Open fields

4

  • Study parameters and phasePhase 2, 120 participants
  • Visits, forms and repeating sections9 visits, 24 forms
  • Users, roles and sites6 sites, 30 users
  • Modules: eConsent, ePRO, randomization
  • Change-order termsAdd rate card request
  • Hosting and validation fees
  • Close-out and data export on exitOften omitted
Demo request. Omitted lines become surprise invoices.

What this template is for

  • A quote can only be as precise as the request. Vendors price what you tell them; what you leave out becomes an assumption in their favour or a change order later.
  • Ask for line items, not a total. A total hides which parts are licence, build, hosting, validation, support and change.
  • Put the exit in the first request. Data export format, audit trail export and any fee for leaving are far easier to agree before you sign.
  • Ask each vendor to price the same scenario. Give study parameters and an enrolment curve so the replies can be compared on one basis.
  • This is the short RFQ. For a full vendor evaluation with scoring, use the EDC RFP template.

How to use it

Use the template in four moves

First, fill in the study parameters from your protocol synopsis; the numbers need not be final, but should be your best estimate and marked as such. Second, send the same block to every vendor on your shortlist, and ask for the reply in the same section order. Third, require line-item pricing, with the assumptions each vendor made written next to the number. Fourth, normalise: convert every reply to total cost over your scenario, including likely changes, before comparing.

The template is deliberately neutral. It suits quotes for full-service builds and for self-serve platforms alike, which is where the two models diverge: a full-service reply should have a build fee and a change-order rate card, while a self-serve reply should have a subscription structure and say plainly what the vendor does and does not do. For the model choice, see self-serve vs full-service EDC.

The template

Paste-ready request, section by section

Copy the left column into your RFQ and complete the brackets. The right column explains why each line is there.

Paste into your RFQWhy it matters
1. Study: [title], phase [1/2/3], design [open label/blinded/randomised], countries [list], planned start [date], enrolment period [months], follow-up per participant [months].Drives months live and participant-months, the base of most pricing.
2. Participants: planned [N], screen failure rate [%], expected dropouts [%]. State whether screened-but-not-enrolled participants count as billable.Defines who is billed and from when.
3. Sites and users: [N] sites, [N] total users, of which [N] are read-only monitors or auditors. Roles required: [PI, coordinator, monitor, data manager, statistician, unblinded].Some vendors price per site or per seat; roles also affect blinding set-up.
4. Build scope: [N] visits, [N] unique forms, approx. [N] fields, [N] repeating sections (e.g. adverse events, medications, labs), [N] edit checks, [N] calculated fields. Attach the schedule of assessments.The basis for any build fee or service hours.
5. Modules: EDC; eConsent [yes/no]; ePRO or diaries [yes/no, schedule]; randomisation [simple/stratified/blinded]; drug supply [yes/no]; eTMF [yes/no]; CTMS [yes/no]; integrations [list, e.g. lab or device feed].Modules are often separate licences or add-ons; list each so none is omitted.
6. Data standards and outputs: export formats [CSV/Excel/SAS/SDTM], Define-XML [yes/no], interim exports [N], database lock [date].Confirms outputs are included, not billed per export.
7. Validation and compliance: Part 11 controls, audit trail export, vendor validation documentation, support for sponsor audit, hosting region [EU/US].Validation packs, audit support and region choice may carry fees.
8. Change control: provide your rate card for changes before and after go-live, turnaround times, who validates a change, and whether amendments are included up to [N].The largest source of cost growth after signing.
9. Support and training: channels, hours, response times, onboarding, training sessions included, named contact.Support tiers are often priced separately.
10. Fees: list separately setup, licence/subscription, per-participant, per-site, per-user, hosting, validation, storage, extra environments, interim analyses, archive. State all minimum terms and escalators.Forces line items rather than a lump sum.
11. Close-out: database lock support, final export with codebook and audit trail, archive period and fee, certified copies, return or deletion of data on exit.Exit costs are often missing from the first quote.
12. Contract: term, notice period, auto-renewal, termination for convenience, data ownership, subcontractors, breach notification.Terms affect cost more than a small price difference.

Adapt the brackets to your protocol. Add anything your sponsor or funder requires, such as a vendor security questionnaire.

Copyable block

Plain-text version for an email or portal

Use this compact block when a vendor portal or email will not take a table. Replace every bracket.

Copy from here

Please quote the following EDC study. Reply with line-item pricing and list every assumption beside the number.

  • Study: [title], phase [ ], design [ ], countries [ ], enrolment [ ] months, follow-up [ ] months, start [date]
  • Participants: [N] planned, [N]% screen failure, [N]% dropout; confirm when a participant becomes billable
  • Sites and users: [N] sites, [N] users, roles [ ], blinded or unblinded roles [ ]
  • Build: [N] visits, [N] forms, [N] repeating sections, [N] edit checks; schedule of assessments attached
  • Modules: EDC, eConsent [y/n], ePRO [y/n], randomisation [type], drug supply [y/n], eTMF [y/n], CTMS [y/n], integrations [ ]
  • Outputs: [CSV/Excel/SAS/SDTM + Define-XML], [N] interim exports, lock date [ ]
  • Compliance: Part 11 controls, audit trail export, validation documentation, hosting region [ ]
  • Change control: send rate card, turnaround, and amendment allowance for pre- and post-go-live changes
  • Fees: itemise setup, subscription, per-participant, per-site, per-user, hosting, validation, storage, support, archive
  • Close-out: final export, codebook, audit trail, archive period and fee, data return or deletion on exit
  • Contract: term, notice, renewal, termination, data ownership, subprocessors
  • Please also state what is not included in this quote.

Get a reference price before the quotes arrive

Build the study in the free sandbox and read the published rates on the pricing page. You will know what a reasonable reply looks like. No credit card, pay only once you go live.

Compare against a free build

How Capture answers

Where Capture's published terms line up with each section

Capture publishes its price structure, so most of the template can be answered from the pricing page and the product pages. Where the site does not publish a figure, it says so instead of guessing.

  • Fees: Core is $1,000 per month including one live study, plus $50 per participant per month; extra live studies are $1,000 per month. Full Platform is $5,000 per month per live study plus $30 per participant per month. Enterprise is custom.
  • Setup: the pricing page lists study setup by the Capture team at $0, and the free sandbox lets your team build and test before any fee starts.
  • Billing start: the study fee starts when the first participant is screened. Rates are lower above 100 participants, but those rates are not published; ask for them in writing.
  • Modules: EDC, ePRO and eConsent are in Core; eTMF, CTMS, stratified and blinded randomisation and drug supply are in Full Platform.
  • Outputs: CSV or Excel with a data dictionary, and SDTM datasets as SAS XPT with Define-XML. The audit trail is exportable.
  • Hosting: EU (Frankfurt) or US (N. Virginia).
  • Not published, so ask: the volume rate above 100 participants, exact support terms, and contract and notice terms.
Open the pricing page
Worked line items · Core · demo study
Line itemBasisQtyUnitTotal
Core subscription (1 live study)months live7$1,000$7,000
Per-participant feeparticipant-months180$50$9,000
Study setup by the Capture teamone-off1$0$0
ePRO and eConsent modulesincluded in Core1$0$0
Direct costs$16,000
Total$16,000
List-rate arithmetic for 60 participants over 7 months live. Not a quote.

Reading the replies

Normalise every quote to one scenario

Copy this into a spreadsheet and fill one column per vendor.

LineVendor AVendor BVendor C
Setup or build fee
Subscription or licence (months live x rate)
Per-participant charges (participant-months x rate)
Per-site, per-user and module charges
Hosting, storage, validation, extra environments
Expected change orders (your estimate x rate card)
Support and training
Close-out, archive and export
Total over scenario
Assumptions the vendor made

Compare the total, then the assumptions. A low total with five assumptions in the vendor's favour is not a low price.

Red flags

Reply patterns to challenge

A reply with a single lump sum and no assumptions has not answered the request. A reply that omits change orders probably has a rate card you have not seen. A quote that prices "standard" validation but leaves your sponsor audit out is only half priced. A contract with a long minimum term and an auto-renewal, combined with no export clause, makes leaving expensive. Read more on these patterns in hidden EDC fees, and compare structures in the EDC pricing guide.

For sizing your own scenario, use the worksheets for 100 participants, 500 participants or 1,000 participants, and the per-patient pricing guide.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

What should an EDC quote request include?

Study phase and design, enrolment and follow-up length, participants, sites and users, forms and visits, modules needed, outputs, validation and hosting needs, change-control terms, close-out and exit requirements. The template on this page covers each.

What is the difference between an RFQ and an RFP for EDC?

An RFQ asks for a price on a defined scope. An RFP also asks vendors to propose approaches and answer capability questions, with scoring. This page is the RFQ; see the EDC RFP template for the longer evaluation.

Why ask for change-order terms in the first request?

Amendments are the usual source of cost growth after signing. A rate card and turnaround time up front lets you model them before you choose a vendor.

What fees are commonly left out of EDC quotes?

Hosting, validation documentation, extra environments, interim exports, sponsor audit support, archive and data export on exit. List each in the request so the vendor has to answer.

Does Capture charge a setup fee?

The pricing page lists study setup by the Capture team at $0 on Core. It shows no per-site fee or per-seat licence. Confirm the terms for your tier in writing.

Are Capture's rates published?

Core and Full Platform list rates are on the pricing page. Rates above 100 participants are lower but not published, and Enterprise is custom.

How many vendors should I send the quote request to?

Three to five is usually enough to compare structures without drowning in replies. Send the identical block to each.

Benchmark your quotes against a published price list

Build in the free sandbox with every feature, then compare. No credit card, and you pay only once you go live.

Compare against a free build