What Should Be Included in an Estimate? The Complete Checklist
A solid estimate doesn't require guesswork about what to put in it. This checklist covers every element worth including, organized by priority — from the non-negotiables through to the professional details that separate a strong document from an average one.
Use this as an audit for your existing estimates or a reference when building your first template.
Essential Elements (Non-Negotiable)
These items must appear in every estimate you send. Omitting any of them creates confusion, slows approvals, or opens disputes.
Your Business Information
What to include:
- Full legal name or business name
- Mailing address (or city/state at minimum)
- Phone number
- Email address
- Website URL
- Logo (if you have one)
Why it matters: The client needs to know who sent this document. If you're operating as a registered business, use your business name. If you're a sole proprietor under your own name, your name and contact details are sufficient. A logo signals that you operate like a business, even if you're a solo freelancer.
Client Information
What to include:
- Client's full name or contact person name
- Company name (if applicable)
- Client's billing address
- Client's email address
Why it matters: Incorrect client information creates immediate doubt — if you got the name wrong, what else did you get wrong? Match the contact details to the person who will approve the estimate and process payment. For larger companies, this is often someone in Accounts Payable, not the person you spoke with.
Estimate Number
What to include:
- A unique reference number (e.g., EST-2026-0042)
Why it matters: The estimate number is your filing system. When a client emails to say "we want to move forward," you need to know which estimate they're referencing. It also carries through to your invoice, making the paper trail clean.
Issue Date
What to include:
- The date the estimate was created and sent
Why it matters: The issue date anchors everything else — it's the starting point for your validity period and your follow-up timeline.
Line Items
What to include for each line:
- Description of the deliverable or service
- Quantity or estimated hours
- Unit rate
- Line total
Why it matters: This is the core of the estimate. Vague descriptions ("design services — $4,000") force clients to guess what they're paying for and invite negotiation. Specific, itemized descriptions justify your price and demonstrate that you've thought through the project.
Subtotal, Taxes, and Total
What to include:
- Subtotal before tax
- Tax rate and amount (if applicable)
- Any discounts (shown explicitly)
- Grand total
Why it matters: Show your math. Even if tax is zero, include the line to make clear you've considered it. Discounts should be explicit — don't just reduce the total and expect the client to notice.
Scope of Work Description
What to include:
- A brief paragraph or bullet list describing what the project covers
- Explicit list of exclusions (what's NOT included)
Why it matters: The scope description gives context to your line items. Exclusions are equally important — clients regularly assume that adjacent services are included unless you specifically say otherwise. A contractor who doesn't list "painting" as excluded may end up in a dispute when the client expected a painted room.
Validity Period
What to include:
- An expiration date ("This estimate is valid for 30 days from issue date")
Why it matters: Estimates are based on your current availability, material costs, and rates. Without a validity period, a client can accept a 6-month-old estimate when your pricing has changed, or during a period when you're fully committed elsewhere. Most freelancers use 15–30 days. Contractors dealing with material costs sometimes use 7–10 days.
Payment Terms
What to include:
- When payment is due (net-30, 50% upfront/50% on delivery, milestone-based)
- Accepted payment methods
- Late payment policy (optional but recommended)
Why it matters: Ambiguous payment terms are the number one source of freelance payment disputes. Spell out exactly when you expect to be paid and how. If you charge late fees, say so here — not after a payment is overdue.
Recommended Additions
These aren't strictly required, but they improve approval rates and prevent common problems.
Estimated Project Timeline
What to include:
- Project start date (or "upon receipt of deposit")
- Key milestones or phases
- Estimated delivery date
Why it matters: Clients are almost always asking "when will this be done?" Include a timeline and you remove one more question from their approval process. Be honest about your availability — overpromising a timeline is one of the fastest ways to damage a client relationship.
Revision Policy
What to include:
- Number of revision rounds included for each deliverable
- What constitutes a revision vs. a scope change
- Rate for additional revisions
Why it matters: Undefined revision expectations are the single biggest source of scope creep. "Unlimited revisions" sounds generous until you're doing your eighth round on a logo. "Two rounds of revisions per deliverable, additional rounds at $X/hr" is clear, fair, and protects your time.
Assumptions and Dependencies
What to include:
- Materials, access, or information you need from the client before you can start
- Any assumptions baked into your pricing (e.g., "assumes client provides finalized copy")
Why it matters: If your estimate is contingent on receiving something from the client, that dependency needs to be explicit. A developer who assumes the client will provide finalized content needs to say so — if the content isn't ready, the timeline slips and your price may change.
Project Contact Information
What to include:
- Who the client should reach out to with questions or approvals
- Preferred method of communication during the project
Why it matters: On larger or longer projects, having a named point of contact removes friction from the approval process and the working relationship.
Signature or Approval Field
What to include:
- A signature line (for printed/PDF estimates)
- Or an online approval mechanism (for digital delivery)
Why it matters: An unsigned estimate is just a document. Getting a signature — even digital — creates a record of agreement and signals to the client that this is a real commitment, not a casual discussion.
Optional Professional Touches
These elements aren't expected in most estimates, but they elevate the document and reinforce your professionalism.
Brief Project Summary
A one or two sentence plain-language summary of what you'll be doing, written for the client, before you get into line items. Example: "This estimate covers the design and development of a new 6-page website for [Client Company]. The site will be built on WordPress, mobile-responsive, and editable by your team without developer support."
This serves as a quick sanity check for the client and makes the line items easier to understand in context.
Testimonials or Portfolio Links
Including a brief "why us" section or links to relevant past work is appropriate for estimates sent to clients you haven't worked with before. Keep it brief — one sentence plus a link is enough. This is not a sales brochure; it's a document that happens to include a confidence signal.
Terms and Conditions Reference
For larger projects, including a reference to your full T&C document (linked or attached) signals that you operate with professional standards. For smaller projects, the payment terms and revision policy embedded in the estimate are usually sufficient.
Tiered Options
Presenting two or three versions of the scope (Basic / Recommended / Premium) gives the client a choice rather than a binary decision. This often increases approval rates and your average project value. See the tiered pricing section in How to Write an Estimate for how to structure this effectively.
What NOT to Include in an Estimate
Personal apologies for your pricing
Never write things like "I know this might be more than you expected" or "I'm happy to adjust if this doesn't fit your budget." These phrases signal insecurity and invite negotiation. Stand behind your numbers.
Overly technical jargon
Clients don't need to know which specific library you're using or which proprietary method you follow. Describe deliverables in plain language that a non-expert can understand and approve.
Vague "miscellaneous" line items
"Miscellaneous — $500" raises immediate questions. If there's a cost, name it. If you're uncertain about a specific cost, estimate a range with a note explaining what it depends on.
Verbal commitments not in the document
If you've promised something in conversation, it needs to be in the estimate. Verbal agreements disappear; written documents don't.
Future projects or add-ons pushed into the current estimate
Keep the estimate focused on the current scope. Mentioning future potential work in the estimate itself looks like upselling before the client has even said yes. Keep future opportunities for after project kickoff.
Quick Reference Checklist
Essential:
- Your business name, contact details, and logo
- Client name and billing information
- Unique estimate number
- Issue date
- Line items with descriptions, quantities, rates, and line totals
- Subtotal, tax, and total
- Scope description and explicit exclusions
- Validity period
- Payment terms
Recommended:
- Project timeline
- Revision policy
- Assumptions and client dependencies
- Signature or approval field
Optional professional touches:
- Brief project summary
- Portfolio link or relevant case study reference
- Tiered pricing options
- Terms and conditions reference
Related Guides
- How to Write an Estimate: The Definitive Guide — The full process from scope to delivery
- Freelance Estimate Examples: Real Templates You Can Use Today — See how these elements appear in real estimates across five freelance categories
Ready to create professional estimates?
Generate polished, client-ready estimates in minutes with EstimateForge.
Create Free Estimate