EDITORS SOP
Remote + In-House Editors |
How work moves through Maximaaz, what you own, and the standards that make the work transferable.
- maximaazadmin
- August 31, 2026
- 6:03 pm
WHY THIS SOP EXISTS This is not a manual for how to edit. Maximaaz expects editors to bring their own craft, judgement and workflow. |
THE MAXIMAAZ PRODUCTION FLOW
BRIEF → FOOTAGE → EDIT → REVIEW → COLOUR → FINAL QA → DELIVERY → ARCHIVE
Use this SOP to understand what happens at each stage, what you are responsible for, and what the next person needs from you.
QUICK NAVIGATION
MOST USED
01 / RESPONSIBILITY
When I receive a job, I am responsible for…
Ownership starts when the job is assigned — not when the timeline opens.
THE EDITOR OWNS THE JOURNEY You are responsible for taking the assigned work from brief to the next agreed stage. That does not mean doing everything yourself. It means making sure the work moves correctly and that the next person has what they need. |
- Understanding the brief, deliverables, deadline and required format.
- Checking that the footage and assets needed to start are available.
- Setting up and maintaining the project correctly.
- Keeping files, versions and working media organised.
- Communicating blockers early rather than waiting for the deadline.
- Updating MM Central so the team can see the real status.
- Preparing clean handoffs when work moves to another editor, colourist or reviewer.
- Completing the required QA before delivery.
MM CENTRAL — DAILY EXPECTATION Before logging into the Maximaaz working system: open MM Central (Link) and check your assigned work. Update the relevant job with today’s status, priority and any blocker. |
WHAT THIS IS NOT Maximaaz does not require hour-by-hour reporting, screenshots of your desktop, screenshots of your folder structure or documentation of every editing decision. We manage outcomes and handoffs — not every minute of your process. |
02 / YOUR WORKFLOW, OUR STANDARD
You are expected to work independently.
Maximaaz standardises the parts of your workflow that affect the team, the project and the client.
WHAT WE STANDARDISE
- Where project files live.
- How files are named.
- How versions are identified.
- How work is handed off.
- How work is delivered.
- How client and Maximaaz assets are protected.
WHAT YOU OWN Your editing technique, shortcuts, desktop setup, personal organisation habits and creative judgement are yours. If they produce a clean, compliant project and a reliable handoff, Maximaaz does not need to prescribe them. |
WHY STANDARDISE FILES? A project rarely ends with the person who started it. Editors change. Projects return for revisions. A colourist may need the edit. A producer may need to find an old version. Another editor may have to take over with little notice. |
THE RULE OF THUMB If your personal workflow works for you but makes the next person stop and ask “Where is that?” — the workflow needs to change. |
03 / STARTING A JOB
From brief to a ready-to-edit project
Do not begin by downloading everything and figuring it out later. Set the job up so the project can survive beyond your machine.
1. READ THE JOB
- Read the brief and check deliverables, aspect ratios, duration, references and deadline.
- Check MM Central for instructions, links, dependencies and existing versions.
- Ask questions before starting if a missing detail could change the edit.
2. GET THE FOOTAGE
- Download from the approved Maximaaz/client source only.
- Do not treat Downloads/Desktop as the project location.
- Move required material into the project structure before building the edit.
- Do not rename camera originals.
3. CREATE THE PROJECT
STANDARD PROJECT STRUCTURE PROJECTNAME_DATE |
4. BEFORE YOU EDIT
- Confirm the project opens correctly.
- Confirm media is online or proxies are correctly linked.
- Confirm the first sequence/version has a clear name.
- Update MM Central when the job is ready to move into active editing.
04 / PROJECT + FOLDER SYSTEM
The folder structure is a handoff tool
Store files where another Maximaaz editor can find them without asking you.
FILE HANDLING RULES • Downloads/Desktop = temporary staging, not project storage. |
WHAT GOES WHERE
LOCATION | USE |
Premiere Proj | Premiere project files and relevant auto-saves. |
After Effects | AEPs, project-specific templates and AE renders/outputs. |
Assets | Footage, images, logos, graphics, fonts, stock and AI-generated material. |
Music | Music and SFX used or supplied for the project. |
Resolve | Resolve project files and colour handoff material. |
Exports | Review and working exports; keep versions identifiable. |
Delivery | Approved final files intended for delivery. |
Archive | Material retained after completion according to project requirements. |
ACCOUNTABILITY WITHOUT MICROMANAGEMENT Editors are not expected to submit daily screenshots of their folder structure. The standard is checked at meaningful gates — handoff, delivery and periodic project audits. The goal is a transferable project, not proof that someone is watching. |
05 / WORKING FILES, NAMING + VERSIONING
Make the latest work obvious
A good filename answers three questions: What is it? Which project is it? Which version is it?
PROJECT NAMING ProjectName_Date → Example: CafeLaunch_20260830 |
EXPORT / SEQUENCE NAMING Project_Deliverable_Format_Version → Example: CafeLaunch_Reel_9x16_v03 |
RESOLVE HANDOFF TO RESOLVE |
VERSIONING
- v01 = first usable version.
- v02 = revision after feedback.
- v03 = next revision, and so on.
- Never use FINAL_FINAL, FINAL_NEW, FINAL2 or similar ambiguous names.
- Never overwrite a version that has already been sent for review or approved.
WHY VERSIONING MATTERS When a producer says “go back to the version before the colour changes” or a client asks for the approved cut, the filename should make the answer obvious. |
06 / REVIEW, COLOUR + HANDOFFS
Every handoff is a promise to the next person
Your job is not just to send a file. Your job is to send enough information and the right files for the next stage to continue without friction.
REVIEW
- Export the requested review version.
- Upload to the approved review/delivery location.
- Update MM Central with the version and what feedback is required.
- Do not silently replace an older review file unless the workflow specifically requires it.
COLOUR / RESOLVE
- Confirm the edit version being sent to colour.
- Create the agreed ToResolve file using the correct project/date/version naming.
- Include all required media or follow the agreed relink/transfer workflow.
- When colour returns, use the matching FromResolve version and keep the relationship between edit and colour versions clear.
HANDOFF MESSAGE
A GOOD HANDOFF SAYS VERSION — what version is this? |
07 / EXPORT, QA + DELIVERY
The export is the deliverable
Do not assume the file is correct because the timeline looks correct. Watch the actual exported file.
BEFORE EXPORT
- Confirm the correct sequence and version.
- Check resolution, aspect ratio, frame rate and required delivery format.
- Check for offline media, missing graphics, accidental overlays or black frames.
WATCH THE EXPORT
- Watch the complete export.
- Check picture, text, captions, names, dates, handles, URLs and CTA.
- Check VO clarity, music/SFX balance, sync and clipping.
- Check the opening and ending carefully.
DELIVERY
- Use the correct filename and version.
- Upload to the approved destination.
- Confirm the uploaded file is the intended file.
- Update MM Central with the delivery status and location.
- Move/store final material in the correct project location.
DO NOT CALL SOMETHING FINAL BECAUSE IT RENDERED Final means it has passed the required checks, is correctly named, is in the right place and is ready for the next person/client. |
08 / SECURITY + PROPRIETARY ASSETS
Access is provided for authorised Maximaaz work
Client material and Maximaaz-created tools are business assets. Handle them accordingly.
CLIENT + PROJECT DATA
- Use only approved storage, transfer and collaboration systems.
- Keep Maximaaz/client accounts and credentials secure. Use 2FA where available.
- Do not move project material to personal cloud storage, personal drives or unapproved devices.
- Do not create public links or share client material outside the authorised workflow.
- Do not upload confidential client material to AI tools or third-party services unless the workflow has been explicitly approved.
- Report accidental exposure, loss or misdelivery immediately — do not try to hide or quietly fix a security incident.
MAXIMAAZ PROPRIETARY ASSETS
THIS INCLUDES LUTs • Presets • Effects • MOGRTs • AE Templates • Scripts • Graphics Systems • Internal Tools • Internal Workflows • Other assets specifically provided as Maximaaz proprietary material. |
- Use proprietary assets only for authorised Maximaaz work.
- Do not use them for personal projects, freelance work or other clients.
- Do not share, sell, publish, distribute or upload them to public libraries or marketplaces.
- Do not pass them to another person unless authorised by Maximaaz.
- Access to an asset does not transfer ownership of the asset.
- Store proprietary assets only in approved locations and remove local copies when instructed or when access is no longer required.
NEED AN ASSET? Request access. Do not source a copy from another editor or create an unofficial distribution chain. |
09 / DEFINITION OF DONE
A job is not complete when the timeline is finished.
A job is complete when the work is organised, delivered, secure and ready for the next person.
FINAL CHECK
- ✓ The correct version has been exported.
- ✓ The export has been watched.
- ✓ Required files are stored correctly.
- ✓ The project can be reopened.
- ✓ Required assets are present.
- ✓ The correct file has been uploaded/delivered.
- ✓ MM Central reflects the current status.
- ✓ No unnecessary copies remain in temporary locations.
- ✓ The project is ready for the next person.
THE HANDOFF TEST Could another Maximaaz editor take over this project without needing you to explain where everything is? |
IF THE ANSWER IS YES The job is done. |