THE EXEDRA GATE PLATFORM
A private workspace connects invited people, the checks required of them, exact document versions and their recorded responses. When a question comes later, the team can trace the process rather than reconstruct it from separate tools.
Give the person managing the work a clear view of responsibilities, outstanding documents and responses.
Connect a recorded action to its participant and document version, so a later review does not begin with a search across disconnected tools.
Capabilities and evidence fields depend on the configured workflow. The examples below explain the operating model; they are not a guarantee of legal compliance or a production screenshot.
ILLUSTRATIVE SUPPLIER AGREEMENT, FROM INVITATION TO FOLLOW-UP
An agreement cannot progress while the team is unclear who must respond.
Invite the supplier representative and assign the commercial and compliance reviewers. Connect the required verification steps to this engagement.
One engagement shows the participants, roles and outstanding checks.The supplier sends a revised delivery clause while an earlier draft is still circulating.
Link the review request to supply agreement v3 and retain its relationship to the previous version.
Everyone knows which document the request concerns.The commercial reviewer needs a supporting document before recommending approval.
Keep that request, its source document and the responsible colleague together. A human reviewer assesses the response.
The missing information has an owner and a visible next step.The agreed terms are ready for the named signatory.
Send the defined version through the configured signing process. The signatory can review and respond from a phone.
The recorded signature refers to the participant and exact document version.A later review asks which terms were signed and when.
Retrieve the supported signing events, document references and evidence export. Its manifest defines the included files and verification material.
The review starts with an inspectable record, not a search through attachments.A renewal or delivery question arrives after the original employee changes roles.
Connect the continuing obligation and the next request to the agreement. Assign the colleague now responsible.
The working context survives the handover.WHAT BELONGS IN THE EVIDENCE
A SHA-256 hash is a digital fingerprint of the exact file. Supported openings, acknowledgements and signatures can be recorded with the account, time and document version involved. The exported manifest identifies which files and events are included, with signatures and independent timestamps where required.
Invited participants have roles and permissions. Depending on the workflow, identity checks (KYC), organisation checks (KYB), PEP screening and questionnaires are linked to the engagement. A check's status is recorded separately from the human decision; an invitation alone does not mean a participant has passed every check.
A document open records access, not proof that a person read or understood every word. Technical context such as IP address or browser/device information is collected only where the workflow permits it; it does not identify a physical device with certainty. Review the actual export and its coverage. Integrity verification detects changes to protected content, not whether its statements are true or legally sufficient.
PARTICIPATION WITHOUT THE PAPER CHASE
The operator coordinates the project on the dashboard. Participants review the relevant document and complete the required response from their phone.
Try the signing demonstrationVERIFICATION WITH CONTEXT
The configured process brings together the participant, required checks, exact document version, response and permitted technical context. A drawn mark or a press-and-hold gesture alone does not establish identity.
Review the controlsAFTER THE DEAL
Handover, changed instructions, updated disclosures and periodic reviews belong to the same relationship. Plan who owns the next request, what must be shared and whether an explicit response is required.
YOUR OPERATING MODEL
No. The same operating model applies to document-heavy, multi-party work in different industries. The published Basic and Team plans currently retain capital-raising entitlements. Other workflows and enterprise requirements are scoped in a consultation.
No. Participation and access follow the roles, permissions and checks required for the engagement. A private workspace is not permission to share every document with every participant.
No. Evidence integrity, factual accuracy and legal sufficiency are different questions. The platform supports a reviewable record; qualified people assess its meaning and sufficiency.
No. Exedra Gate supplies technology. Funds remain with the parties and their appointed providers. Human reviewers retain responsibility for compliance decisions.
In a free consultation, we will map the participants, document handoffs and review points with you, then clarify fit, configuration and next steps. No purchase is required.