Build a quotation request form in Tally

Outcome and scope

Collect the specifications a print or creative business needs before preparing a quotation. The form receives a request; it does not promise a final price. Let applicants mark genuinely undecided requirements, while distinguishing those from missing mandatory information. The output should help a reviewer decide what can be quoted and what needs a follow-up question.

Order questions around what an applicant can answer. Offer a consult option for specialist specifications while keeping essential quantity and timing fields clear.

Prepare the fields and destination

Prepare these fields: Request ID, project type, quantity, dimensions, material, desired deadline, undecided requirements, attachment reference and reply address. Keep source values separate from a reviewer’s confirmed values, and do not reuse an existing column for a different meaning. Create the first record with practice identifiers in a destination whose read and edit access matches the intended staff roles. Inspect the saved result from that role before using live information.

Distinguish a visual reference from print-ready production data. Receiving a file does not establish permission to use its contents, and attachment access needs an explicit internal owner.

Build the workflow in order

Start with project type and show only relevant specification questions through conditional logic. A booklet may need page count, while a single sheet needs dimensions. Keep common contact fields together. Test changing an earlier answer so a hidden mandatory question does not block submission, and give a concise example beside unfamiliar terminology.

State the unit for quantity and ask whether a deadline means dispatch or arrival. Request attachments only when they help the estimate and state accepted formats and size conditions. Submitted designs may contain private information, so restrict access to the responses and any file links used by the review team.

Review submitted specifications and maintain a separate operational state for quotable, follow-up needed or declined requests. An acknowledgment should confirm receipt and explain the next contact route. It should not state that the requested deadline or an estimated amount has already been accepted by the supplier.

Work through a small example

Test a request for one hundred folded A4 booklets. Check finished size, page-count meaning, paper choice and delivery-date interpretation. Choose a consult-the-supplier option for paper and ensure that uncertainty remains visible. A reviewer should be able to prepare a targeted follow-up using the submission, without guessing what the applicant meant.

Handle changes during operation

Preserve the submitted specification separately from the reviewer’s confirmed one. Link a quote version to the response ID so a later clarification changes the correct project rather than another request from the same company.

Estimate cost and usage

Select a Tally plan after checking the exact question, branching, attachment and notification requirements. Separate branding preferences from the functions needed to receive a usable request. External storage or integration services can add costs. Start with the required specification fields and include the reviewer’s follow-up workload instead of assuming the form subscription covers the complete quotation process.

Investigate failures

When specifications are incomplete, inspect branching and examples before adding more mandatory questions. A large required text box does not guarantee useful detail. After editing the form, preserve the mapping to earlier responses so an integration does not silently write a new meaning into an old management column.

Review before release

Before release, test a normal record, one missing a required value, a repeated identifier and an edited record. Use request id to trace the saved result back to the source. The acceptance condition is: A reviewer must be able to distinguish usable specifications from explicit uncertainties. Record the expected result before testing, compare it with the actual saved state, and resolve unexplained differences before increasing the scope.

• Build a Tally contact form
• Conditional questions in Tally
• Collect file submissions with Tally