Intake that starts real work

Anyone, anonymously

No sign-in, no email. For feedback, tip-offs and anything where asking who you are would stop people answering.

Anyone, with an email

Captures an address so the submitter can be told what happened, without needing an account.

Signed in

Any Qik Office account — used when the response has to be attributable outside your own company.

Employees of this office

The default for internal processes: everybody in the company can fill it, nobody outside can, and the submitter is known.

In their own Forms list

Every employee has a Forms app of their own. Forms from processes that cover them appear there, grouped by process — no room membership needed.

Across the whole company

A suggestion box or an IT ticket is listed for everybody, whatever department they sit in.

Inside the room

Team-internal forms stay where the team works, visible to the room’s members as they always were.

On a public link

Vendor onboarding, job applications, customer requests — shareable anywhere, with your branding and your domain.

Only from a case

A “revise your request” form is never listed anywhere. It reaches exactly one person, for exactly one case, and stops working after.

Wherever you drop the link

In a chat message, an email signature, an intranet page, a QR code on a noticeboard — it is a URL like any other.

It becomes a row

Typed, validated and visible in the table — with attachments stored against it and the submitter recorded.

It opens a case

If the form starts a process, the case is created and the first approver is notified in the same moment.

It reports back

The person who submitted it sees the step it is on and who it is waiting for, from their own submissions list.

It can come back

If changes are requested, the same form returns to them prefilled with what they wrote — and the answer updates the original record rather than creating a second one.

Nobody should type the same thing twice

• Read a submission back as its form

  Open any submitted record in the shape the person filled it in — the fastest way for a reviewer to understand what was actually asked for.

• Revise without forking

  A revision edits the record it came from. One request, one row, one history — never two half-finished copies.

• Fields that fill themselves

  A person column can be set from whoever is signed in, so an employee never types their own name, department or manager.

• The agent can fill one too

  A decision recorded in minutes, or a sentence typed in chat, can open the right form already populated for a person to confirm.

Submissions land inside your office

Not in a third-party form service that then has to be connected back. The row is in your room from the first second.

Results obey table permissions

Who can read the responses is the room’s existing permission model — there is no second, parallel way to grant access.

Attachments are first class

Receipts, CVs, photographs and documents upload straight onto the record and count toward your office storage like anything else.

Your domain, your branding

Forms can be served under your own domain with your own identity, so the person filling one never leaves your brand.

One form, several steps

The same form can be the way a process starts and the way it is revised — the link says which case and which step it belongs to.

The submitter is kept informed

Acknowledgements, decisions and outcomes reach them by email and notification, whether or not they have an account.

Replace the form that emails a mailbox

Every company has one: a request form that lands in a shared inbox, where somebody copies it into a spreadsheet and chases an approval by hand. Show us yours and we will show you what happens when the form is the start of the process.