Portal Worx Logo

Everything the record needs, on the project it belongs to.

Sign-off is the reason to start. The workspace behind it is the reason the record's still there, at the right version, when someone asks.

Sign-off

They open a link, approve and sign. That's the whole loop.

Pick a document, name the person, send. Whoever has to approve it opens the page wherever they are, reads the file, and approves or rejects it with a signature. No account, nothing to install.

  • Request sign-off from any document row, with the file already attached
  • The page shows the drawing, quote or variation itself, not a summary of it
  • Approve, reject, comment, or mark a spot on the page and say what's wrong
  • A drawn signature and a typed name, on any phone or laptop
  • Ask for a one-time emailed code before signing when you want a second check
  • Send several files in one request and get one answer per file
The request summarised, and the new version compared

On the request's AI insights tab, one press says where it stands and one press says what the new version changed since the one they rejected. The comparison shows on the client's link too.

Sign-off, in detail →
The whole loop: the request sent from one dialog, the email in the client's inbox, the client approving and signing with no account, and the Approvals Centre showing it settled
The whole loop: the request sent from one dialog, the email in the client's inbox, the client approving and signing with no account, and the Approvals Centre showing it settled
The same page on a phone: the drawing, Approve and Reject, and no login
The record

What comes back is evidence, not a notification.

Every answer is written into a PDF with the original file inside it. It names who signed and where from, the time, the exact file they saw, and the version they signed.

  • The file's SHA-256 fingerprint is on the record. Change a single byte of the file afterwards and it no longer matches, so the file is tamper-evident
  • A mark on a drawing comes back as a crop of that spot beside the comment
  • The version they signed is named, so the wrong one can't be argued in later
  • Download the record any time from the request, or from the Approvals Centre
See a real record, annotated →
Page one of a real approval record: Approved, who answered, when, from where, the signature, the verified address, the version and the fingerprint of the file
The corridor lighting layout with a green Approved stamp across its corner
Chasing

It chases them. You don't.

Switch reminders on when you send a request and they'll hear from you on day 3, day 7, then every 3 days until they answer. It stops when they do, or when you stop it.

  • Normal or gentle schedule, per request
  • Stops on an answer, when the link expires, when you stop it, or when they opt out
  • The Approvals Centre groups every request by who owes the next move
  • Every email the workspace sent is listed with whether it landed, and one click sends it again
Chasing, in detail →
The Approvals Centre: every request grouped by whether it's with them, with you or settled
Sharing without accounts

Send anything by one link. Not only what needs signing.

A document, a photo, a report, or a whole category or folder, opened by whoever holds the link, with no account. A folder link shows what's in the folder now.

  • Works for 90 days, or until you turn it off, for one link or many at once
  • A folder or category link stays current: a file you add appears, a file you remove disappears from every link
  • Add a six-digit PIN when the file deserves a second check
  • See every live link, who made it, how often it was opened and when it expires
Sharing, in detail →
A whole category shared by one link in three clicks: Actions, Share by link, Create link, Copy link
A whole category shared by one link in three clicks: Actions, Share by link, Create link, Copy link
The shared folder on a phone, as the person you sent it to opens it: the files, no account, no app
Temporary access

For the person who needs more than one tap.

A consultant on the project for a fortnight, an inspector for a week: give them chosen projects until a date. They sign in with a code sent to their email, see only those projects, and the access ends by itself.

  • Pick the projects and the end date; nothing else to set up
  • They sign in with an emailed code, no password to make or forget
  • An hourglass and their end date in the team list, so nobody wonders
Temporary access, in detail →
The team list filtered to temporary people, each showing the date their access ends
Versions

The record names the version.

Every upload of a document is a new version, with its history kept. An approval is pinned to the version that was signed, so when version C replaces version B, the sign-off on B stays exactly as it was.

  • Version history on every document, with who uploaded each and when
  • The approval each version carried, side by side
  • Download any earlier version when the argument needs it
What changed, without re-reading the file

When a new version goes out for sign-off, the AI reads both and says what moved. The client sees the same reading on their link.

Versions, in detail →
A spec the client rejected, revised: its versions listed with the approval each carried, and a new version uploaded while the old ones keep theirs
A spec the client rejected, revised: its versions listed with the approval each carried, and a new version uploaded while the old ones keep theirs
Projects

The project behind the record.

A project holds its documents, its photos, its reports, its conversations and its activity, with the people on it and a summary of where it stands. The signed variation sits next to the drawing it changed and the photo that justified it, and you'll still find it in eighteen months.

  • One page per project, with documents, photos, reports, approvals, messages and activity in tabs
  • The people on it on one list, with a consultant's end date beside their name
  • A year of activity: every upload, edit, move, deletion and share, filtered to what each person may see
  • An AI catch-up summary whenever you want one, in its own tab
A catch-up on any project

Ask for a headline, a short summary or a full write-up. It reads only what you're allowed to see, reports rather than advises, and never sees another client's project.

Projects, in detail →
One project's page: its documents, photos, reports, approvals, messages and activity in tabs
Documents

Filed where the next person will look.

Categories you name, every upload a new version, a comment thread and a reminder on each file, and a PDF that opens in the browser for the client checking a drawing. Nothing has to be downloaded to be checked.

  • Categories you name, per project, uploaded singly or in bulk
  • Every upload is a new version, with its history kept and the approval each one carried
  • Comments with mentions and a reminder on any document
  • A category can be restricted to a few staff and one named client while the rest of the project doesn't move
Category names from what the project is

Tell it the industry and how you file, and it suggests the categories for the project, created in one go, so the filing makes sense from day one.

Documents, in detail →
A project's documents filed in named categories, each row with its version, comments and actions
Photos

Photos in folders, by stage.

Folders you name, one per stage, with a cover, captions and full-screen viewing. The whole folder downloads as a zip, goes into the report, or reaches the client by one link that shows what's in it now.

  • Folders per stage, captioned, opened full screen, downloaded as a zip
  • A folder's audience is its own, so the client sees progress and not the quote
  • Share a folder by one link: a photo you add appears, one you remove disappears from every link at once
  • The photos that matter go into the site report, beside the checks
Folder names for the stages of a project

The same suggestion for photo folders: the stages a project like this goes through, named and created in one go.

Photos, in detail →
The photo folders of one project, the Progress folder opened, one photo with who took it and when
The photo folders of one project, the Progress folder opened, one photo with who took it and when
Threads and messages

The conversation, next to the thing it's about.

A thread per project, so a conversation only reaches the people on that project. Direct messages with anyone on your projects, your client included. Comments on the document, the photo or the report itself, with a mention when you need someone.

  • A thread per project, open only to the people on it, live, with reactions and read state
  • Direct messages with anyone on your projects, guests included, with edit
  • Comments on documents, photos and reports, with replies and @mentions
  • A mention is the notification. Nobody gets emailed about a thread they didn't ask about
Messages, in detail →
A project thread: the people on the project talking about it, with the files beside them
Reports and templates

Reports worth handing to a client.

Build the form once as a template or start from one of 33 in the library, fill it in on site, sign it on screen, and export a PDF with your logo on it.

  • Eleven block types: text, numbers, dates, choices, checklists, ratings, progress, tables, photo galleries, signatures and locations
  • 33 ready-made site, safety and handover records: site diary, snagging list, handover checklist, RAMS, toolbox talk and the rest
  • Show, hide or require a section based on the answers given
  • Draft, then complete; the full edit history on any completed report

Exporting a PDF and sharing a report by email are on Professional and Business. A report is shared, never sent for signature.

A template from a sentence

Describe the form you need and it drafts the template, sections and required fields included. Describe what should change in one you have and it edits it. You check it and keep what's right.

Reports, in detail →
A site inspection filled in from the template: the particulars, progress, a line on what moved, and two photos going in
A site inspection filled in from the template: the particulars, progress, a line on what moved, and two photos going in
The template builder: a section with a required date and a location, each with its own display logic
Page one of the exported inspection report, with the company logo and the first photos
Access control

They see their project. Not your business.

Every category, folder, report and thread carries its own audience: your team on one side, the named people outside it on the other. A guest starts with nothing and gains only what you give them.

  • Four roles, from full control down to guest
  • Restrict a category to four staff and one named client, and the rest of the project doesn't move
  • Guests never see your other projects, your other clients, or each other
  • Tune what each role can do, per workspace

Editing the permission matrix is on Professional and Business. Every plan gets the four roles and their defaults.

Who sees what, in detail →
The same project twice: every category for the team, and only the shared ones for a guest architect
The team list with each person's role, including a guest who sees one project only
AI

AI that reads the project, and stops there.

Ask any project for a plain-language catch-up: progress against the dates, what moved, what's flagged. It's built only from what you can see, and it reports rather than advises.

  • A summary in four lengths, from a headline to a detailed write-up, downloadable as a PDF
  • Draft a report template from a sentence, or describe what should change in one you have
  • Suggested category and folder names when you set a project up
  • Ask Scout, a help assistant that answers only from our own guides, free

Every plan includes a monthly bundle of credits. A summary costs one, two for detailed. Template drafting is on Professional and Business. Top-up packs from £7.

AI, in detail →
A plain-language summary of where a project stands, generated on the AI Insights tab

We prove the email address was theirs. We don't pretend to check their passport.

What the signature proves

Ask for it on a request and, before they sign, we email them a one-time code they have to type in. That proves whoever signed had that inbox in front of them at that moment, and it's written on the record. It isn't an identity check.

If your document needs a verified identity, a property transfer, a deed, anything that calls for a qualified electronic signature, you need a notary, not us.

Not built, so nothing above should make you think it is:

  • sign-off on a report (documents are approved, reports are shared)
  • approvals on images
  • more than one approver on a request
  • delegating an approval to someone else
  • a public API
  • search across the whole workspace
  • integrations with accounting, estimating or other tools
  • drawing on photos
  • two-factor sign-in for workspace users
  • working fully offline on a phone
  • Word or Excel files as the thing being approved (PDF, images and plain text are)
  • a custom domain on the pages people outside your team open

Send the first one today.

Free for 14 days, no card. Approvals and share links aren't counted on any plan.