Delivery settings and what a delivery holds

This page lists the settings of a delivery and what the client receives. It does not repeat the steps.

The hold, and ending the delivery

The hold is the hours your platform has set, such as 1, 24 or 48. The dialog states them beside the checkbox.

If you tick the hold, the files cannot be downloaded until those hours pass.

• During the hold you can end the delivery: select ⋯ on its row on the Access tab, then End delivery, and confirm.
• Deliver now on the same menu ends the hold early.
• Ending it during the hold still works while your organisation is suspended or frozen.

Once the hold has ended, or if you leave it unticked (Delivered at once. You will not be able to end it yourself.), you cannot end the delivery yourself. If you try just as the hold ends, GISweaver says You can no longer end this delivery yourself.

Where your organisation's external sharing policy is on for the project, a delivery is refused. Making an existing delivery longer is refused the same way; ending it, reminding the client and ending its hold still work.

When the hold is set to 0 hours the box is not offered, and the dialog says the client can download the files as soon as you deliver.

How long it stays open

Setting	Value
Access lasts choices	90, 180, 365 or 730 days. 365 is chosen unless you change it.
Making it longer	At no charge, while it is open. See Extend a delivery or remind the client.
Reminders	GISweaver reminds your client 30, 14 and 1 days before access ends.
If files are still undownloaded	A delivery whose files have not all been downloaded when its period ends is closed.

What is delivered

The release's files: the files drawn on the map, and any kept files (PDFs, DWG drawings, photos and any other file) that were ticked into the release. A file whose malware scan has not come back clean is listed but not handed to another organisation. Your client sees the reason beside it and is told to contact you, and the archive they download carries the other files with a list of the ones left out.

Which files a delivery counts

Counts toward the delivery	Does not count
The survey files and the kept files you included.	Map tiles and other generated viewer data. They are kept for viewing and in the archive, but the client does not need to download them to complete the receipt.

The file count and size in the delivery dialog, the Access row and the client's file list all use the same rule. Older signed receipts are unchanged, including any viewer files they counted.

What each status means

The Status of a delivery on the Sent and Received tabs is one of these. The second column reads for the organisation that delivered; the third is what the client does.

Status	What it means	What the client does
Available	The client can download the files until the day under Access ends.	Download them.
Held until \<date>	The hold has not ended; the sender can still end it, and the client can see the file list.	Wait for the date.
Downloaded in full	Every file was downloaded and the receipt was written.	Copy the receipt.
Declined	The client said it does not need the files.	Nothing.
Not downloaded	The period ended before every file was downloaded.	Ask the sender if the files are still needed.
Ended	The sender ended it during its hold.	Ask the sender if the files are still needed.
Revoked	GISweaver support removed the delivery at the sender's request.	Contact the sender or GISweaver support. Files already downloaded are the client's.
Frozen	Downloads are stopped while the sender's organisation is frozen; the period is extended by the length of the freeze.	Wait, or contact the sender.
Access paused by \<organisation>	The sender paused the client in the project.	Contact the sender to resume it.
Files removed	The sender removed the release's files from storage; the receipt stands.	Nothing.
Client organisation closed	The client's organisation closed its account.	Nothing.
Sender organisation closed	The sender's account is closing or closed.	Download the remaining files by the Download by day.

Checking the files and the archive

Under the file list, Check the files are unchanged (for IT staff) opens each file's full checksum and the release's checksum, a 64-character code that names the release exactly. Compare them with what you saved if you need to show that the copy is the one that was sent. The archive's list of files holds the same checksums.

Each file shows its checksum as a short code (the first four and last four characters); select it to copy the whole value.

The archive records the project's coordinate system and the dates the release was created, surveyed, uploaded and published, and the date a later release replaced it, as known when it was delivered. A date that was never recorded stays empty. Later project edits do not change this handover record.

Storage and the receipt

The delivered files stay on your plan and count against your storage until each is deleted permanently. Removing the release's files from storage is possible only once every delivery of that release has ended. Removing a release's files hides them at once. They stay in trash, still counted against your storage, for the days the confirmation shows, and storage is freed when they are erased. The receipt records what the server sent; it does not prove your client kept a usable copy.