My translation jobs
A translation and localisation portal is where clients submit jobs with their source files and follow each one to delivery, and the agency hands back translated files on the job that asked for them.
Pattern: RequestsDescribe it to Pory
“We're a translation agency. Clients should submit jobs with source files and a target language, see each job's status, and download the translated files when we deliver.”
My translation jobs
In plain English
A translation and localisation portal is where clients submit jobs with their source files and follow each one to delivery, and the agency hands back translated files on the job that asked for them. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (client and project manager) that shows only what that role should see, and flat pricing with unlimited clients.
What it does
Jobs used to arrive as an email with six attachments, no deadline and "the usual languages, please". In Pory the client uploads the source files, picks the target language and content type, and sets the due date. Project managers can quote straight away instead of writing back for the missing details.
Clients chased deadlines by email because the only status lived in the project manager's head. Each client sees their own jobs move from Received through In translation and Proofreading to Delivered. A launch team in another time zone checks the portal instead of waiting for your office to open.
Deliveries went out as attachments that sank among the client's other suppliers' emails. The project manager uploads the translated files to the job in Pory, labelled by language, and the client downloads them from their own page. Nobody asks for the German files to be sent again in launch week.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, in its detail view, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the records a viewer is allowed to see.
Control
Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
Describe it in a sentence and send the invite. Unlimited clients, flat price.