Skip to content
Content SnareHelp centre

Request statuses

Quick answer

A Published request is live, and your client can open it and fill it in. Once you mark it Complete, your client can no longer open it. Only Published requests count toward your plan's active request limit, and completing or archiving one frees its slot.

Every request is in one of six states, and its status tells you where it's up to and whether it's using up your plan's active request allowance. Your status filter also shows Waiting, which is covered further down.

The six statuses

Status What it means
Draft You're still building it. Your client can't see it yet.
Published It's live. Your client can open the link and fill it in.
Complete You've marked it done. Your client can no longer open it.
Expired You set it to close on its due date, and that time has passed. Your client can no longer open it.
Scheduled Set to publish itself at a date and time you choose.
Archived Filed out of the way and locked until you restore it.

The difference between Published and Complete

A Published request is live. Your client can open the link, work through it, and send their answers back. Marking a request Complete tells Content Snare you're finished with it, and from that point your client can't open it any more.

Only mark a request Complete once you've finished collecting. If you've turned on downloads for completed requests, your client keeps a link to download their answers until it expires, but they still can't reopen the request to change anything. There's more on that in whether clients can view or download a completed request.

Which requests count toward your plan limit

Only Published requests count toward your plan's active request limit. "Active" isn't a status you set. An active request is one that's published.

Because of that, the moment you complete or archive a request, its slot opens back up and you can publish another. Draft, Scheduled, Complete, Expired, and Archived requests don't use a slot. If you're at your limit, see what to do when you've hit your active request limit, and plans and limits for the number on your plan.

Scheduled requests

A Scheduled request is one you've set to publish itself at a date and time you pick. Until that time your client can't see it, and it doesn't use a plan slot. When the scheduled time arrives, it publishes on its own and becomes a live, Published request.

Expired requests

If you turn on Close client access after the due date for a request, your client loses access on the due date, at the time of day you published the request, in your organization's time zone. The request then shows as Expired.

Your client can no longer open or download an expired request, and it stops using a plan slot. Your team can still open it and see everything your client sent.

To reopen an expired request, publish it again with a new due date. It counts toward your plan limit again, so you need a free slot. The steps are in request expiry.

Archiving a request

Archiving is for a request you're done with and want off your list. It no longer appears on your main requests list and is locked. While a request is archived, no one on your team can approve answers, mark fields done, or add or edit its questions, and your client can't open it either.

Completed requests stay on your main list. To pick an archived request back up, restore it first.

Waiting means answers are ready for you

Waiting is an option in your status filter, and it sits on top of Published rather than replacing it. A published request shows as Waiting once your client has submitted answers you haven't approved or sent back yet, the request owner gets a notification, and the request is highlighted on your dashboard. It's still published underneath, so it still uses a plan slot. Your clients never see it.

You choose what puts a request into Waiting, and an administrator can change it from one answer arriving to all required answers or every answer. Review and approve answers has the setting and the three choices. A request stays in Waiting until your team has approved or sent back every answer that came in. If it expires first, it shows as Expired, and the answers are still there for you to review.

Answer status is separate from request status

As your client submits answers and you review, approve, or send them back for changes, the request itself stays Published unless it expires along the way. Once you've reviewed the last of them, the request moves out of Waiting.