Review and sign-off of survey deliverables
A client organisation opens a delivered survey in its own browser, reviews the published layers, measures against them and downloads the files, and can record a dated acceptance the sending firm sees. GISweaver has no approval workflow and no signature step: what it gives you instead is a record of what was delivered, what was downloaded and what the client said about it.
What the client can do in the browser
Nothing is installed. The client signs in to its own organisation, opens the delivery and reads the release as a map, on the same web application the surveyor uses.
- Turn each delivered layer on and off, and change its opacity, colour and line thickness while reading it.
- Measure distance, area and a point’s coordinates against the delivered geometry.
- Search inside the release for a feature, and read a feature’s own attributes.
- Download the delivered files, as one archive or one file at a time, with each file’s size and SHA-256 checksum shown beside it.
That is the whole tool set a delivery carries, and it is fixed: the sending firm does not choose it, and the elevation tools are not part of it. They need an elevation surface, and no format GISweaver accepts today produces one.
Recording an acceptance, and what it does not do
A client reading a delivery has two controls beside it: Accept and Decline. Either one is recorded with its date in both organisations’ activity records, and the sending firm is told by email and in the product.
Accepting is optional and it is not a gate. The files can be downloaded before it, after it, and whether or not it ever happens — a client who simply downloads the survey and says nothing has taken the delivery in full, and the receipt below is written all the same.
Declining is recorded the same way and asks for no reason. There is no field for one, so whatever the client wants to say about the survey is said outside GISweaver.
The sending firm is told that the receiving organisation accepted, and never which person there pressed it. One acceptance is recorded per delivery, and it names an organisation.
The record of what was delivered
When the server has recorded a completed download of every file in the delivery, a receipt is written and kept by both organisations. It names the two organisations, the release with its publication date and its checksum, and every file with its size and SHA-256 checksum — enough for somebody who has the saved files to check them, years later, without asking either party.
It carries a signature where the deployment holds a signing key, and the delivery screen says whether this one does. The canonical bytes the signature covers are kept beside it, so the check can be repeated outside GISweaver.
It is a record of a transfer and not an approval. It names no person, it says nothing about whether the survey is correct or fit for the client’s purpose, and it does not confirm that the files saved on somebody’s disk are usable — check those against the manifest.
What GISweaver does not call sign-off
Said plainly, because a firm choosing software for an approval process needs to know before it starts rather than after:
- There is no approval workflow. No stages, no reviewer assignment, no queue of surveys awaiting somebody’s decision, and no per-file or partial acceptance.
- There is no signature and no signed certificate of acceptance. The acceptance is a dated organisation-level record; the signature GISweaver does hold is on the transfer receipt above.
- A receiving organisation cannot write comments, mark-ups or annotations back through GISweaver. Comments, mentions and the work layer belong to a project and stay inside the organisation that owns it, and a delivery gives the client a release to read rather than a project to write in.
If your contract needs a signed acceptance, sign it in your own document and quote the release, its publication date and its checksum. That is what the receipt is evidence for, and it is stronger evidence than a tick inside somebody’s software.
When the survey changes after review
The release the client reviewed is unchanged and unchangeable, so a correction is a new release that supersedes it and a new delivery. Which version a client reviewed and downloaded stays answerable afterwards, which is the practical reason releases are frozen at all.
The step-by-step instructions
The documentation walks a member of the receiving organisation through finding a delivery, opening it, downloading the files and reading the receipt, with the screens as they appear.
DocumentationQuestions firms ask about this
- Does GISweaver have a sign-off or approval step?
- Not as a workflow. A client can record a dated acceptance that both organisations see, and it changes nothing about access: the files are downloadable before it and without it. There are no approval stages and no signature step.
- Can a client reject a survey and send comments back?
- A client can decline a delivery, and the decline is recorded on both sides with its date. It carries no reason field, and a receiving organisation cannot write comments or mark-ups back through GISweaver, so the reasons are given outside it.
- What proof do we have that the client received the survey?
- A receipt, written once the server has recorded a completed download of every file. It names both organisations, the release with its publication date and checksum, and each file with its size and SHA-256 checksum, and both organisations keep a copy.
- Does the record say who reviewed and accepted it?
- No. Acceptance is recorded against the receiving organisation, and the receipt names the two organisations and no person. The receiving organisation’s own activity records show which of its members acted; the sending firm is not told.
- Can several people in the client’s team review it before accepting?
- Anybody in the receiving organisation whose role lets them receive deliveries can open, review and download it, and any one of them can record the acceptance. There is no reviewer assignment and no multi-person approval.
Ready to look at the product?
The plans page lists what each plan includes and what it costs. If you would rather ask a person first, the support page is the way to reach one.