Tally review: Build a project brief with only the questions you need

Tally provides conditional logic, calculations and forms under its free tier, subject to fair-use guidelines. It also lists integrations and a choice of paid features for more advanced requirements. This makes it a candidate for a small intake form with conditional questions or calculations. The sections below connect those features with a task you can try using your own material.

What Tally offers—and what remains to check

Review fair use, upload needs, branding and the integration required by your process. Test both branches of every condition and verify where responses arrive. It may not be the right purchase if you have unresolved requirements for handling sensitive information or restricting access to responses.

For this use case, conditional logic matters more than calculations. A useful brief should establish what someone needs, what already exists and what remains undecided. Calculations might be relevant to a separate estimating process, but adding them to an initial enquiry could complicate a task that mainly needs specific answers. Keep the first version focused on collecting scope, rather than trying to automate every decision.

Example: a brief for one email or a short sequence

As a hypothetical example, consider a solo copywriter who accepts either a single promotional email or a short welcome sequence. Both enquiries need a business objective, an intended audience, an offer and a target date. Only the sequence enquiry needs questions about the proposed number of messages and the purpose of each message. Showing those questions to someone requesting one email adds effort without improving that brief.

Sketch the shared questions first, then identify the smallest useful branch. One early question could distinguish a single email from a sequence. Plan each route to collect only the details needed for an initial scoping conversation. Include an answer such as “not sure yet” in your design: uncertainty is valuable information, not a reason to force a client into a category that may be wrong.

Keep questions concrete. Asking what readers should do after receiving the email is more actionable than asking for a broad marketing vision. Ask about existing material without assuming the client has it. Before requesting confidential campaign details, decide whether a general description would be sufficient at this stage. A shorter brief should reduce unnecessary collection as well as unnecessary questions.

Judge the output, not just the form’s length

A form can feel concise yet produce an unusable brief. Your evaluation should therefore end with the answers: can you identify the requested deliverable, the intended audience, the desired action and the unresolved decisions? If a branch removes a question that you immediately need to ask by email, the apparent saving may simply move work into follow-up.

Also check how you will review and use submissions in your chosen workflow. The published product details do not establish specific delivery, export or integration options. Verify the route you actually need rather than assuming it exists. For a solo operator, a straightforward review process may matter more than an elaborate form that requires manual rearranging before every client conversation.

Run a small trial before building a larger intake system

Create fictional briefs for three cases: a specific single-email request, a specific sequence request and an uncertain enquiry. Follow each planned route and inspect the resulting information. Then change an early answer and check whether the later questions and submitted answers remain appropriate. This is a proposed trial, not a report of observed Tally behaviour.

Record every question that needs explanation and every missing detail that prevents scoping. Revise those points before adding more branches. Keep a simple question map alongside the form so future edits do not accidentally separate a necessary question from the people who should answer it. Conditional logic creates a maintenance responsibility: each additional route needs checking when your services change.

When the extra setup is worthwhile

Tally is a plausible fit when your enquiries share a common core but differ in a few predictable ways. If every project needs essentially the same information, a short linear brief may be easier to maintain. Proceed only after checking fair-use conditions, any paid features your design depends on, and appropriate data handling. The action is one working brief with a few tested paths—not a comprehensive intake system.

Strengths

• Collect a brief and show follow-up fields when an answer calls for them.
• Tally provides conditional logic, calculations and forms under its free tier, subject to fair-use guidelines.

Limitations

• Test both branches of every condition and verify where responses arrive.
• Review fair use, upload needs, branding and the integration required by your process.

Before you decide

• Review fair use, upload needs, branding and the integration required by your process.
• Try one representative task with non-sensitive material and inspect the result.
• Test both branches of every condition and verify where responses arrive.
• Confirm the current cost, cancellation terms and any separately billed extras before paying.