👀What the Respondent Sees at Their End

We recommend you send a collection to a colleague first so you know what to expect. However, here's what the collection experience looks like to them.

Flat Structure

When you're designing your collection, you may have used packs to group documents together or put rules around how many documents are needed, "collect any two of these four types".

Your respondent doesn't see this "tree of nested packs" but instead a single list of all the documents and forms they need to send. We try to collect your preferred documents first.

Once you open the collection, it'll flatten out and you'll see it, more or less, as it appears to your respondent.

If a pack is configured to collect a subset of the documents, i.e. "any two of..." then once the respondent has satisfied this requirement, all the other documents (no longer needed) will vanish.

If the same document type is collected twice, then they will need to send it twice, once on each item, however it is not possible to collect more than one file per item. For example, you cannot collect the front and back photos of a passport within a single passport item. Instead you'd need to create an item for the front and another for the back.

Conditionals

Since documents and packs can be contingent on information in another document, the respondent may find that submitting a document results in many items suddenly vanishing and no longer being needed. The opposite is true, that the submission of a document may "switch on" the need to send a bunch of other information.

Screenshots!

A picture paints a thousands words, so here are some examples:

Collections are flattened

This image shows the respondent's view of a collection with four packs, Proof of Address, UK Right to Work, Company Formation and Company Insurances. It also collects their residential address history and employment reference history, defined in the "root" collection.

See how there no packs to "go into" like when you're configuring the collection and instead the pack name is a label under its name.

An open complex onboarding collection as seen by the respondent.

Further down the page, Zipwire Collect has noticed that the respondent already has a passport in storage and is offering it up with a Send button.

Further down the same collection the Passport item has picked up a passport held in storage.

---

Pack headings and shading

Items within a pack will be preceded by their pack name and description and a block of shading helps visually distinguish the pack.

Taken from the UK Right to Rent built-in template collection, see the shading and pack details

Requestor's view

The following shows the requestor's view of a collection named Proof of Address. In this case a reusable Proof of Address pack was used as a template for the whole collection.

Requestor Upload

Both the respondent and the requestor can pick files to upload. If requestor already has some of the requested files, perhaps in email attachments, they can upload them to keep everything together.

When the collection is opened, Zipwire will look in both the respondent's and the requestor's workplace store to see if a suitable document is already present.

Note that for some items that need a physical inspection, only the requestor can upload the evidence, since the respondent will be expected to post or take the document to the requestor in person.

An open Proof of Address collection as by the requestor with Pick file buttons.

Physically-inspected items

When configuring your collection, you can choose how it should be inspected and Zipwire Collect will guide the respondent appropriately.

Evidence that needs physically checking will not have an option to upload.

Optional items

The following is what an optional item looks like to the respondent. They will usually see a Not applicable button but sometimes it will be labeled Skip.

An optional item with Pick file and Skip buttons

The requestor can make an item optional after the collection has been opened.

Forms

Forms appear slightly different depending on what is being collected - this should give you a feel. The respondent has Add, Remove and Send buttons.

The respondent's view of the address history form

After sending

For the respondent, sent items are removed from the Open view and become visible over on the Done view. To be clear, the same open collection can be visible on both the Open and Done tabs.

The sender's (respondent's) view is pretty boring and simply has a little label on the item to say when it was sent.

Boring little label.

Requestors view of received items

The requestor will clearly see when an item has been sent to them for review. They'll see a set of controls like this. Lovely.

The requestor's view of an item they've been sent, with controls for accepting and rejecting

And there you have it

We'd love your feedback. If you have a good idea for a form, or if you think the experience falls short somehow or could be improved, please reach out.

Thing's we're working on:

• There's currently no viewer for the files you've been sent. You need to download them locally onto your machine to see them properly. Some folks must not store sensitive data on their devices and so this could be a problem for those users.

• New forms. In particular, links to other websites and services. For example, to have the user go to a website to start background checks. This could be a button to open that website which then tracks that they have clicked it.