Common questions, straight answers.

One platform that takes a request from form to signed agreement: forms to capture it, workflows and approvals to process it, documents and e-signature to execute it, and an agreement repository to manage renewals and obligations. It all sits on one transaction record with one audit trail, in Arabic and English.

Organisations in Qatar and the Gulf that run approvals, documents, e-signature and agreements, and need them to work in Arabic and English.

It isn’t bolted on. Forms, documents and signing pages render right-to-left with proper typography, every field holds Arabic and English, and the certificate of completion is bilingual. You can describe a form to the AI in Arabic, English or both.

Instead of showing every question on one long page, the form presents one question at a time. Forms.qa also offers a classic multi-page layout, so you can choose per form.

Every completed submission starts its workflow and becomes a transaction with a reference such as TX-000123. It moves through stages (submitted, approval, document, signature, active, closed) and keeps a timeline of everything that happened.

Twelve installable processes, each combining a form, its documents and its workflow: employee and supplier onboarding, service agreement, job offer, NDA, lease application, official letter, IT incident, hardware request, access request, leave request and expense reimbursement. Install in one step, then edit anything.

Yes. Custom branding, a custom domain and white-label are available.

Yes. API access and webhooks are included, so you can send submissions and events to the systems you already use.

Not today. The API and webhooks let you connect Forms.qa to other systems.

For most documents, no. Signing is built into the workflow: set the signing order, and signers verify with a one-time code sent by email, with no account needed. Signing is included; signing volumes are agreed with your organisation.

Today, each signer opens a secure link and confirms a one-time code sent to their email. SMS codes and Qatar national authentication are planned; national authentication is subject to integration and authorisation.

Each signed PDF is sealed with a tamper-evident PAdES signature and an RFC 3161 timestamp, with a document hash, a full audit trail and a bilingual certificate of completion. For documents with special legal formalities, check with your counsel.

An agreement is created automatically, with a reference such as AG-000001, linked to the counterparty. Expiry reminders go out at 90, 60, 30 and 7 days, and you can set it to renew automatically.

Yes. Import the signed PDF and it joins the same repository, with the same reminders, renewals and obligations.

An agreement can renew automatically. A renewal can re-run the original form’s workflow with the same answers, or create a draft renewal with shifted dates. Each renewal is linked to the one before it.

Recurring or one-off duties on an agreement, such as a yearly insurance certificate or a monthly report. Each occurrence becomes an Inbox task with reminders, and completing it requires uploading evidence.

Only what you ask, and each workspace can switch it off. Questions across your agreements (“which renew this quarter?”) are turned into a search that runs on your own data; only the question goes to the model. Summaries, answers and key-term extraction for one agreement send that document’s text to the AI provider your workspace allows.

No. Extracted key terms are suggestions until a person confirms them, and nothing is written to the record automatically. Answers about an agreement quote the document, and any quote that cannot be found in the text is marked as unverified.

By fixed rules, not model opinion: for example unlimited liability, no liability cap, auto-renewal with under 30 days’ notice, payment terms over 60 days, foreign governing law or no end date.

OpenAI and Groq. Your workspace AI policy decides which of them may be used, and can switch any AI feature off.

A whole form from a prompt, a PDF or a web page, which you can then refine; and a document template from a form’s fields.

Not yet. Scanned PDFs without a text layer cannot be read by the AI today.

Yes. Data is encrypted in transit between the browser and our servers, and at rest while it is stored. A signable DPA is available with your agreement.

Export, correction and erasure are supported, so you can respond when a person asks about their data. For workspace-wide requests, write to hello@forms.qa.

Each workspace runs in its own PostgreSQL schema rather than in shared tables. Actions are recorded in an audit log, and roles with fine-grained permissions control who sees what.

Not yet. Both are on our roadmap.

Not yet. SSO is planned.

Forms.qa is sold to organisations under an agreement. Pricing is set per organisation, based on your processes, volumes and requirements. Book a demo to discuss it.

Yes. Book a demo and we will walk you through your process; we can then set up a workspace for your team to try it.

Yes. Signing is built into the workflow, and signing volumes are part of your agreement.

As many as your agreement covers. Roles and fine-grained permissions control who can design, operate, approve, view or audit; team size is part of your agreement.

Yes. A signable DPA comes with your agreement.

Book a demo. We walk through your process, then scope pricing, onboarding and support for your organisation.