RAW & bracket intake
Chunked, resumable uploads sized for full bracket sets and video source footage, grouped by the job rather than a dated folder.

Feature — Production
Assignment, style notes, revisions, QC and payout tracking — so production is a managed part of the business rather than a folder someone remembers to check.
The problem
One editor and five shoots a week runs fine on messages and folders. Three editors and thirty shoots does not. The failure is rarely skill — it is that the brief, the files, the revision history and the pay record live in four different systems, and only the owner's memory joins them.
The fix is unglamorous: make the job the unit of work, and make every production event write to it.
What you get
Chunked, resumable uploads sized for full bracket sets and video source footage, grouped by the job rather than a dated folder.
Work is routed to an editor with the property, the brief and the ordered services already attached.
Your look is recorded against the work instead of re-explained in every hand-off message.
Notes are written against the job so a second pass references the actual set, not a paraphrase of it.
Nothing reaches a client until the owner has looked at it and approved the delivery.
Editor pay is derived from the finished work on the job, so production cost and client revenue sit on the same record.
The production loop
Brackets and clips land on the job, resumable and grouped by property.
An editor takes the job with brief and style notes attached.
The edit is done against the actual order, not a folder of loose files.
Notes are recorded on the job and answered with a new pass.
The owner signs off before the client sees anything.
Client payment and editor payout both reference the same work.
| What | Ad-hoc production | RELMX production |
|---|---|---|
| Where the files live | Shared drive folders per shoot | Attached to the job record |
| How the editor knows the brief | A message, if it was written | Carried with the assignment |
| Revision history | Email thread | Notes on the job |
| Quality gate | Whoever remembers to look | Explicit approval step before delivery |
| Editor pay | Counted up at month end | Tracked per finished unit of work |
FAQ
Jobs are assigned to an editor inside the platform, with the brief and the uploaded brackets or clips already attached. There is no separate email with a link and a paragraph of instructions.
The platform is built around a production team with editor roles, assignment and payout tracking, so a media company can run its own editors on the same rails the RELMX editing service uses.
Revision notes are written against the job, so the request, the version it applies to and the returned files stay in one place. Nobody has to reconstruct what was asked for from a thread.
The photographer or account owner reviews the finished set and either approves the delivery or sends it back for another pass.
Payout is tracked per unit of finished work on the job, so what an editor is owed is derived from the production record rather than rebuilt from file counts at the end of the month.
If you would rather not staff production at all, outsourcing the editing runs on exactly the same rails.
Create a workspace and run one job through assignment, revisions and approval.