What the software actually needs to do
Electronic signature software sits between the final draft of a document and the records an organisation keeps afterwards. A useful evaluation therefore starts with the whole workflow, not the appearance of a signature alone. The sender needs to prepare the right file, address it to the right people, identify each required action and understand when the process is complete.
Orbis Sign starts with a supported PDF. An account holder can place signature, initials, date, text, number, name, email and checkbox fields on its pages and assign them to recipients. Required fields help prevent a recipient from knowingly completing their step while an assigned answer remains blank. They do not check whether the underlying terms are correct or whether an answer is commercially sensible.
Recipients follow a document-specific invitation in a browser and do not need their own Orbis Sign account. This makes the product relevant where an organisation controls preparation but sends documents to customers, candidates, suppliers or other external parties.
Follow one document from preparation to completion
- Prepare: upload the final supported PDF, add recipients, position fields and check page placement.
- Route: use sequential signing when one person should act before another, or parallel signing when order is unnecessary.
- Invite: send each recipient a unique link through the configured delivery method. Check contact details before dispatch.
- Review: use draft, pending and completed states, recorded activity and manual reminders to manage follow-up.
- Retain: access the completed PDF and separate completion or activity record, then apply your own retention policy.
Delivery, open and click information depends on events reported by the relevant provider or system. It does not prove that a named individual personally read and understood every page. Treat statuses as workflow signals rather than a substitute for judgement.
Capabilities to test during a vendor evaluation
Document preparation
Use representative PDFs, including longer agreements and files produced by your normal office software. Check page rendering, field placement, required-field behaviour and the completed output. Orbis Sign is a signing workflow, not an anonymous PDF annotation tool, and the current workflow begins with PDF rather than an editable Word file.
Recipients and signing order
Test the experience from the recipient’s perspective on the devices your counterparties use. Confirm how corrections, declined requests and expired invitations are handled operationally. Where authority matters, establish that before sending; possession of an invitation link is not universal proof of identity or authority.
Team access and reuse
Workspace roles help restrict application actions, while shared templates can preserve repeatable field layouts and branding can be configured for the workspace. Customers remain responsible for memberships, roles, recipient selection and their wider access policies.
Records and export
Ask what is recorded, what is provider-reported, and which record is separate from the PDF. In Orbis Sign, selected consent, workflow, signing and provider events can be available alongside the completed document. Coverage varies; reported browser or network data does not capture every interaction or independently establish identity.
Browser and device considerations
Orbis Sign provides a browser-based recipient experience with responsive layouts; recipients are not asked to install a separate signing application. Browser-based does not mean every device, browser extension, accessibility setup or unusual PDF will behave identically. A sensible rollout tests current browsers and managed devices used by the organisation and by typical recipients.
Also consider the surrounding journey: whether invitations are recognisable, whether recipients can reach support, and whether a small screen gives enough context to review the document before signing. For the product sequence, see how Orbis Sign works; for the PDF-specific process, read signing a PDF online.
Security questions should be specific
Avoid treating a badge or a broad “secure” claim as the answer. Evaluate how invitations are generated and expire, whether additional recipient checks can be configured, how application roles work, what event evidence exists, and how completed files are downloaded. Ask separately about production hosting, encryption, backups, supplier arrangements, incident response, retention and deletion.
Source review identifies controls including random document links with expiry, optional OTP gates, workspace roles and completion hashing when completed PDF bytes are available. These controls reduce risk; they do not prove production configuration, certify the service, guarantee storage protection or make an online system absolutely secure. Read the current security overview and conduct your own due diligence.
Benefits that depend on good process
A structured online workflow can remove printing and scanning steps, make assigned fields visible, preserve a consistent route and give colleagues a shared status view. Templates may reduce repeated field setup. Those are practical capabilities, not a promise that every agreement will finish faster or without mistakes.
Benefits are strongest when the organisation also controls document versions, verifies recipient details, defines signing authority, reviews exceptions and downloads the records it needs. The current offer is £8.99 per month and includes up to 500 documents for signature each month; review the details on the pricing page.
Common evaluation questions
Do recipients need accounts?
No. Standard recipients use the invitation for the document in a browser.
Can several people sign?
Yes. Fields can be assigned to multiple recipients and routing can be sequential or parallel.
Does the software prove identity?
No single standard workflow proves identity in every context. Contact-channel access, optional checks and recorded evidence must be assessed against transaction risk.
Is every document suitable?
No. Witnessing, deeds, regulated transactions, filing rules or agreed contractual formalities may require a different process or specialist advice.
This is general practical information, not legal advice. Electronic execution is not suitable for every document. Check the law, agreed formalities and your organisation’s requirements for the transaction.