These are different levels. The workspace brings your operation together; each project retains its own data and permissions. Within a project, an episode identifies a production unit, and each module can have its own history.

1. Confirm the name and showcode before editing or importing. Episodes with the same number in different projects do not share records.
2. Open modules from the project navigation: Calendar, Post Facility, Assignment, Team, Finance, Editorial, VFX, Sound, Color or Delivery. Reports and documents have separate entry points.
3. Do not equate a calendar version with an editorial cut or a VFX delivery: their version numbers do not have to match.

The Projects card is the entry point for continuing work, opening documents or managing collaboration.

1. Create the project with a name, showcode and working mode. Review the platform, episodes and calendar settings before generating dates.
2. Choose an operational project to track dates and deliveries, or a budget project to scope and quote work. Do not assume both modes offer the same tools.
3. Continue from its card and check the active version. A new project may not yet have a calendar or review cuts.

Project mode, subscription, archive status and permissions work together. Editor access does not remove project-state restrictions.

1. Some operational tools and calendar comparison are unavailable in budget mode. Review duration, capacity and staffing for the quote without inventing milestone completion.
2. Read the confirmation scope before archiving or deleting. These are not equivalent; do not delete work merely to hide it.
3. If everything is read-only, ask the owner to check the subscription, archive status and module permission before repeatedly saving.

Contextual guides point out on-screen controls. This manual explains behavior and limits; Getting started provides a shorter introduction.

1. Open the module guide from navigation when you need to locate a control.
2. Use this manual's index to find a specific feature. Each section has its own shareable explanation link.
3. When requesting support, include the module, action, expected result and error message. Never send passwords, tokens or personal guest links.

Configure the matrix per person and project. It covers Calendar, Post Facility, Assignment, Team, Finance, Editorial, VFX, Sound, Color, Delivery, Reports and project Library.

1. No access: does not allow reading that module. Permissions are not inherited from another shared module.
2. Read only: allows viewing the authorized scope without modifying it.
3. Editor: allows permitted editing operations within the module; it does not make the person an owner or access administrator.
4. Review all twelve modules before sending: several start in read-only mode, while Finance and Library are excluded. Do not assume defaults match your intention.

Share project creates an invitation for a specific email address. New access starts when the recipient accepts, not merely when the link is created.

1. Open Share on the correct project and enter the person's complete email address.
2. Choose access levels by module. For example: Calendar read-only, VFX editing and no Finance access.
3. Select Share project and check the response. At least one module must be enabled.
4. Find the record in Pending and check its modules and expiration. Creating an invitation and sending its email are different outcomes.
5. If email delivery failed but the invitation is pending, the interface may offer Copy secure link for private delivery.

An invitation requires a RushTrack session and explicit acceptance. Registration does not automatically accept the invitation.

1. Open the received link. Sign in if you have an account; otherwise create one using the recipient email and complete the required confirmation.
2. Continue in the same browser. If confirmation opens another tab, check that it returns to the invitation; otherwise reopen the original link.
3. Review the project and modules, then select Accept invitation.
4. If you signed in with another account, sign out and use the recipient account. Do not request broader permissions to resolve an account mismatch.
5. Unshared modules remain locked. Another project requires its own invitation or access.

Pending distinguishes an unaccepted invitation from active access.

1. View modules shows what the recipient will receive; check permissions before resending.
2. Resend reissues the invitation. If asked to wait one minute, do not repeat the action in another tab.
3. Revoke invalidates that invitation after confirmation. To remove already accepted access, use Access instead.
4. If expired, the owner must manage resending it. Changing your computer's date does not reactivate the link.

You do not need to invite someone again to change the matrix of an accepted new-style access grant.

1. In Access, find the person and select Edit permissions.
2. Change the required levels and select Save permissions. Use View modules to verify the result.
3. Ask the person to reload. An open draft may no longer be authorized if access was reduced.
4. If a concurrent-change warning appears, reopen the editor and review the current matrix. Do not blindly overwrite someone else's changes.
5. To remove access, select Remove access and Confirm revocation. This removes shared access, not project work.

Existing members retain their historical permissions. They are not automatically migrated to the new matrix and do not need to accept again.

1. Use Legacy access when the system indicates the person already participates through the earlier mechanism.
2. Manage workspace-derived access in the workspace. A new invitation should not replace that access.
3. Review creation, resend, acceptance, permission changes and revocation in Activity. View details shows previous and new module permissions where applicable.
4. Project Library permission does not open the global Library; Reports must not bypass Finance protection either.

Choose the workflow by the work the person will perform, not only their specialty's name.

1. Share project: a RushTrack account with read or edit access to selected modules.
2. VFX Team / Shot Deck: individual artist access to assigned VFX work, including review, deliveries and shot conversation.
3. Editorial Team / Editorial Deck: editorial group membership for working on corrections and confirming those groups' portions.
4. Editorial or VFX editing permission does not automatically delegate coordination authority over external teams.

The interface distinguishes commercial limits, project state, permissions and service availability.

1. Collaborator limit: ask the owner to review plan capacity and active access. Duplicate invitations do not solve it.
2. Archived project or read-only subscription: resolve that state first.
3. Activation pending: sending is not enabled when a server dependency is missing. Report the notice to support.
4. Expired session: sign in again. If a response was lost, check Pending, Access and Activity before repeating the action.

Generation prepares a version; Operations works with the resulting calendar. An assistant conversation alone is not a saved version.

1. Choose assisted or manual generation. In chat, describe episodes, shooting, deliveries, cadence and restrictions; review the interpreted parameters.
2. If using voice, review the transcript before generating. For direct control, complete the manual form.
3. Check platform or workflow, first episode, shoot start and shooting days, working days, offset and episode cadence.
4. Configure the shooting country and working-day rules. Do not confuse this with the Post Facility's labor country.
5. Generate and check that the version appears in History, with the correct calendar and intended active version.

Advanced configuration changes calculation logic, not just cell appearance.

1. Review offline/online stages and sequences. Apply changed intervals or processes to the configuration before generating another version.
2. Check milestone dependencies, working days and fixed commitments. An early change can move later dates.
3. Save a preset to reuse parameters. Exporting a preset is not exporting the generated calendar.
4. Recheck the result by episode. Proposals need team review; they do not constitute automatic production approval.

Views read the same plan at different scales. Some view names and availability depend on mode and screen size.

1. Calendar: locate episodes and milestones and open cells for tracking.
2. Gantt, Vertical Gantt and Timeline: examine duration, sequence and overlaps.
3. Milestone: focus on key dates. Heatmap: locate activity concentration and risk.
4. The executive view summarizes the plan. Check version, filters and scope before sharing.

A past date does not prove delivery occurred. Tracking preserves the operational decision and its context.

1. Open the milestone and check date, current status and episode before changing it.
2. Record the appropriate outcome: completed, rescheduled, canceled or postponed, according to available options.
3. Add notes and evidence where available. Links must reference the material and version for that milestone.
4. Save tracking and verify the indicator in Calendar. A visual change is not confirmation if saving failed.

Moving one milestone and propagating a change through dependencies have different consequences.

1. Choose the milestone and new date. Check whether the action affects only it or the dependent chain.
2. Review affected episodes and milestones before confirming; record the reason.
3. Review Team, Assignment and derived costs afterward. Recalculation elsewhere does not give a Calendar editor Finance access.
4. Use versions and comparison to preserve alternatives rather than repeatedly overwriting dates without a reference.

Viewing an earlier version does not necessarily make it active for the whole operation.

1. In History identify the active version and the one to inspect. Use Compare against when available.
2. Use activation to change the operational reference and verify the result after reloading.
3. Archiving removes versions from the main list but keeps them in archived history. Deletion is a separate action with its own confirmation.
4. Calendar editing permission does not guarantee authority to archive, restore or delete entire versions. Ask the owner if those actions are unavailable.

The Post Facility, also called a HUB, represents the infrastructure where work happens.

1. Choose the active facility or create one with a recognizable identity and location.
2. Specify the country where work is performed. It is independent of shooting country and provides a labor and financial reference.
3. Check the selected facility before editing rooms or servers, especially when managing several.
4. Save the configuration so other views can use that capacity.

Entering room counts does not assign them to an episode or person.

1. Define counts by type: offline, online, color, Pro Tools, assistance, remote and other enabled resources.
2. Review shifts and calculated capacity. Avoid listing the same physical workstation under multiple names and inflating availability.
3. Distinguish operational resources from storage infrastructure. Each uses its own units.
4. Use Assignment and the map to connect capacity to the project, rather than changing physical quantities to force occupancy.

Servers stores units, storage type and capacity associated with the active facility.

1. Identify each unit with a useful name and its type, such as Nexis or Color storage.
2. Review capacity and room associations where applicable. Total space is not project operational availability.
3. Infrastructure costs require financial review; recording capacity does not confirm a rate or budget.
4. Save and verify the unit appears in the intended facility.

The map shows resources and distribution by shift. Check automatic proposals against actual availability.

1. Identify nodes, resources and shift assignments. Selectors may show Free, a project or Multi-project.
2. Review concentrations, workstations and periods competing for the same resource.
3. An empty map does not confirm unlimited capacity. Complete facility, calendar and links before evaluating it.

Assignment needs a calendar and facility capacity to interpret demand.

1. Confirm the active calendar version and intended Post Facility.
2. In Link, select the correct facility, not merely one whose name resembles the project.
3. Review required nodes and resources before confirming links.
4. A module editor can change project links without permission to change global rates or inventories.

Indicators compare required and available resources. They help investigate shortages but do not guarantee an external booking.

1. Review required/available rooms, post days, peak staffing and storage resources.
2. Locate periods where stages or projects overlap and compare shifts.
3. If capacity is insufficient, first check dates, links and actual HUB quantities. Do not add fictional resources to clear an alert.
4. Recheck Assignment and Team after rescheduling.

RushTrack combines calendar and assignment data to show required positions and periods.

1. First review project demand and its relationship to the HUB.
2. Check required roles, counts and coverage. An unnamed position is still a staffing requirement.
3. Assign talent to each position and review start and end dates.
4. Entering a person's name in a row does not send a project invitation.

The timeline shows when each position participates, not just who belongs to the team.

1. Check the role's start and end before changing duration.
2. Identify handovers and overlaps on the timeline. Confirm actual availability with the person.
3. After calendar or assignment changes, compare proposed staffing with existing team agreements.
4. Export the available list or timeline view when circulating the work plan.

Operational planning informs costs, but permissions remain separate.

1. Manage profiles and experience in Talent Network; keep this project's specific participation in Team.
2. Review compensation, rates and financial assumptions in Finance, not through a broader operational invitation.
3. Team editors without financial permission should not see compensation or totals. Operational saves preserve existing financial values.

Before changing amounts, check whether you are viewing a project or a consolidated scope.

1. Select scope and review total, fee and cost composition.
2. Open each category: Team, rooms, servers, processes, external services and VFX.
3. Check quantities, periods, rates, currencies and missing data. Zero can mean a pending cost, not free service.
4. If data conflicts or fails to load, do not confirm a budget using an older summary.

Labor country comes from the Post Facility and can differ from shooting country. This manual describes the tool; it does not certify current agreements or rates.

1. For Argentina, review the agreement period and categories, payroll burdens, ARS values and configured exchange rate.
2. For other countries, review the offered monthly USD compensation per person without carrying over SAT rules.
3. Check days, weeks or months used in each calculation and the actual participation period.
4. Validate rates and conditions with the financial owner before approval. Prefilled values do not replace that validation.

The operational reference explains which resource or work creates a cost.

1. Compare quantities and periods with Post Facility, Assignment and Team.
2. Review rooms and servers/storage separately; do not duplicate a unit as a general resource and an additional cost.
3. Complete processes and external services with vendor, currency and amount as requested.
4. Check incorporated VFX quotes and their status before treating them as approved spending.

Budget control preserves an original per project. It records a quote confirmed by an authorized person; it does not independently certify Production's external approval.

1. Wait for the summary to load and resolve pending quotes that block confirmation.
2. Review the breakdown, USD total, fee, approval exchange rate and reference.
3. Confirm only if the amounts and reference match the actual approval.
4. The original remains separate from the current projection and is not recalculated when dates, staffing or currency change.

Additions are recorded separately from the original, in USD. The current projection continues to use current operational data.

1. Record an addition only when an original exists and the scope increase is justified.
2. Review the amount and reference before confirmation; this is not an editable field for retrospectively adjusting the original.
3. Compare the approved total plus additions against the current projection to read savings or overruns.
4. If a response is lost, reload and check whether the record exists before creating another. Retries of the same request are protected against duplication.

Excel allows working with data; PDF provides a fixed output. Neither replaces the project's current record.

1. Confirm scope, currency, date and the budget reference to share.
2. Use available Finance or Reports exports according to your permissions.
3. Check headings, breakdown and totals in the resulting file.
4. Keep current projection distinct from historical approval when explaining differences.

Editorial brings together post-picture-lock notes, coordination, owners, handovers, conversations and notifications. A correction can involve several departments.

1. Work with the full cut and its timecodes; select a note to inspect its context and workflow.
2. Check episode and version before assigning or replying. Identical wording in two cuts does not imply the same correction.
3. An editorial group named VFX participates in that editorial correction; it does not create or change shots in the VFX tracker.
4. Completing an editorial cut does not automatically mark the project's final delivery.

Members and email addresses are managed in Editorial Team, separately from importing and assigning notes.

1. Open the group or department doing the work and add its members. A group can have several people.
2. External members receive scoped editorial access; they do not become VFX tracker members.
3. You can assign notes to an empty group and add members later. Membership changes do not require reassigning every note.
4. When replacing members, check their access. History preserves who completed each task and when, even after they leave the group.

The public Share Link provides video; FIOJSON provides notes. This import workflow does not require connecting a Frame.io account.

1. Open New version and enter the episode, version identifier and cut Share Link.
2. Choose the FIOJSON for that same file. Do not combine one cut's notes with another cut's video.
3. Move from Import to Review and assign. Check note text, author and timecode.
4. The file is analyzed before saving. If it fails, correct the source and retain the form to retry.
5. When updating an existing cut with ongoing work, consult Updating cuts rather than routinely creating an independent import.

Review and distribution take place in a list. Selecting a note differs from opening it for supervision.

1. Click to toggle selection. Shift-click extends the range; you can also hold the mouse button and drag across notes.
2. Dragging near an edge scrolls the list to continue selecting. Touch devices retain native scrolling.
3. Use search and filters to narrow the batch. Actions on visible notes apply to the filtered notes.
4. Exclude notes that should not be imported and restore them if you change your decision. An excluded note is not an unassigned note.
5. Assign the selection to one or several groups and use Undo to reverse the last distribution change.

The current workflow saves all included notes even when only some, or none, have groups assigned.

1. Review included, assigned and unassigned counts before saving the cut.
2. In Timeline, filter Unassigned, select the batch and choose Assign selection to.
3. Add the necessary groups without restarting existing tasks, confirmations or conversations.
4. Unassigned notes keep the cut open even if the first batch is complete.
5. New assignments are unavailable on historical, canceled or completed cuts.

Status comes from a confirmed action, not a chat message. Current group membership determines who can act.

1. Open the note and check group, instructions and status before starting.
2. Use Start work to record who starts and show Working.
3. For independent groups, use Mark my part complete when finished. This does not complete other groups' tasks.
4. If the version uses handovers, follow Finish and send to… and the indicated workflow sequence.
5. Coordination can manage permitted blocks or reopenings but must not confirm work by impersonating another member.

The board shows one row per correction, its group workflow and the selected note's details.

1. Use search, group/status filters and pagination. Checkboxes select batches; the detail number identifies the open note.
2. Minimize notes and workflow hides the list without losing filters or selection and gives the video more room.
3. Beside the monitor, review each group's state, the actual author of progress and completion date. A note is complete when all its parts are complete.
4. Conversation combines messages and work events. A reply without its own TC may use the note's TC as a labeled reference; it does not create another correction.
5. Batch actions are validated task by task. If a partial failure is reported, check already saved tasks before repeating the batch.

Note conversations and direct messages have different scopes. Email state is not task state.

1. Use the note conversation for information needed by people working on that correction.
2. Private messages in Connected team belong to their participants; they are not the note's shared history.
3. For older draft versions, Send notes to team releases and notifies the entire version, not only the selected row.
4. If email fails, the task and in-app notice may still exist. Check the queue or retry; do not recreate the cut to resend a notice.
5. Sent means the provider accepted the email, not that the person read it or completed their work.

Each external member uses personal access to view and work within their authorized editorial scope.

1. Open your personal link, select the available version and review your group's notes.
2. Use Editorial Deck for review work and Chat for messages. Day/Night/Automatic preferences belong to this space.
3. If email did not arrive, coordination may have a manual link. Renewing an invitation invalidates the previous link: use the latest one.
4. A localhost link is not a public address usable on another computer. Request a link from the correct public environment.
5. Reloading cannot recover revoked or expired access; coordination must review it.

Earlier cuts can retain individual workflows instead of independent groups. They are not automatically converted.

1. Read the dependencies shown for the note. In handover workflows, Online and Sound can progress in parallel; Color/VFX depend on Online.
2. Assistance, Editing or Delivery participate only if included. Not every cut has the same chain.
3. Only the assigned owner confirms their delivery. Blocking or Not applicable requires a reason and follows workflow rules.
4. Reopening a step may invalidate dependent confirmations; it does not reopen every branch.

Updating compares the base cut with the new one before saving. Analysis does not apply decisions to the board.

1. Choose the base cut, new version, public Share Link and FIOJSON for the same new file.
2. If the old cut lacks an exact video reference, also provide its original FIOJSON. Renewing an expired proxy does not authorize substitution with another asset.
3. Run comparison and wait for the result. Video analysis can take several minutes.
4. If activation is pending, contact support. Do not delete the cut to try to enable the feature.

Visual matches help, but uncertain relationships require an explicit human decision.

1. Review continuities and omissions. Open View previous / new frames to inspect the image pair; opening it does not confirm the match.
2. Resolve uncertain or missing matches before applying.
3. For each new note, choose whether it starts a correction, becomes a comment on a continuing correction or is excluded.
4. Assign groups where appropriate, or preserve the reference workflow in legacy individual versions. Adding a comment is not reopening a task.

Apply new version preserves the actual state of continuing work and keeps earlier cuts available for reference.

1. Review all decisions and apply the new version once.
2. Check the resulting cut, notes and tasks. Work retains its authors and dates; a new note added as a comment does not restart a completed task.
3. Omissions remain viewable in the earlier cut. Replacing a cut does not declare it complete.
4. If base corrections change during comparison, run analysis again. Task progress and conversation retain the latest confirmed state when applied.
5. If the preview expires, compare again; do not reuse decisions from a changed base.

Earlier notes, drawings and video references retain their origin; they must not be treated as markers on the new video.

1. Use the version selector to view earlier notes and video. Replaced versions are read-only.
2. To delete, coordination opens Options beside the selector and chooses Delete cut. The confirmation requires typing ELIMINAR.
3. If descendants exist, resolve the later cut first. Deleting the current cut restores its parent as current; with no cuts left, a new import is possible.
4. Members, external Frame.io video and other versions are preserved.

A shot represents a camera shot; a note is an observation on a frame. Several notes can belong to one shot.

1. The cut is the video version locating the shots; an artist/vendor delivery is a different dimension of history.
2. A FIOJSON note supplies an observation's TC. It is not automatically used as IN, nor is the next note taken as OUT.
3. An empty tracker's first import starts at v001. Residual historical references must not make it start at a later number.
4. Reimporting the same asset through another Share Link does not by itself mean a new cut exists.

Identity combines project context with episode, scene and shot number. Check it before saving.

1. Add a shot and enter episode, scene/number, reference and work scope.
2. Enter TC IN and OUT using the media's FPS and source TC. Verify duration before confirming.
3. Assign an owner or vendor, status and required materials; do not leave scope only in an external conversation.
4. Save, or use Save and add another. If the shot is missing, clear filters and check column sorting.

Source selection changes preparation: review comments and tabular trackers are different inputs.

1. In Import choose Frame.io or Excel / Google Sheets. Frame.io supports exports such as FIOJSON, XML, EDL, CSV or TXT according to the screen; spreadsheet input offers XLSX, Sheets or paste.
2. For video and notes, use the Share Link and export of the same asset. Check episode, version, FPS and TC reference.
3. For spreadsheets, check headers, shot identity, timecodes and required fields; inspect differences before import.
4. Do not confirm uncertain episodes or links. Correct the source and review the preview again.

Before shots are written, video is analyzed for shot boundaries and notes sharing the same context are grouped.

1. Wait for Analyzing shots. A clear, authorized playback source for the correct asset is required; a protected or seeking proxy may be rejected.
2. Notes from the same shot are grouped while preserving each note's text, author, date and TC.
3. Review resulting IN/OUT and thumbnails. Dissolves and visually similar shots may require manual adjustment by coordination.
4. Resolve access or decoding errors before retrying; do not invent OUT to hide failed analysis.
5. For legacy records without OUT, reimporting FIOJSON can prepare missing ranges without duplicating notes; alternatively define a valid manual range.

Playback uses an internal end-exclusive range [IN, OUT). The interface and spreadsheets display the last included frame as OUT.

1. At 24 fps, IN 00:00:00:00 and visible OUT 00:00:01:11 include 36 frames: duration 00:01:12.
2. Do not add or subtract another frame when exporting or importing through the interface; internal conversion already preserves the range.
3. EDL/XML retain their end-exclusive editorial conventions. Check format, FPS and source TC across sources.
4. Without valid OUT, the monitor shows the IN frame without playing or seeking beyond it.
5. An out-of-range historical note is preserved and flagged; it does not allow seeking outside the shot.

The VFX monitor covers the complete shot range. Selecting a note changes the reference, not the boundaries.

1. Open the shot and choose a note. The monitor uses its original TC within the cut context.
2. Add comments or drawings on an allowed frame with the correct version selected.
3. Do not mentally move an old note to another cut's TC; earlier references remain in history.
4. Editorial's viewer works with the full cut and does not receive the VFX shot range.

General shows accumulated work for current shots. Versions shows notes imported from a particular cut, even the latest one.

1. In General read Shots in cut. In a version view read Shots with notes; the version button counts notes, several of which can share a row.
2. The episode selector counts historical shots, including omitted ones, so its count can differ from visible rows.
3. Use Show omitted to inspect shots removed from the cut: gray, faded, struck through and marked with the removal version.
4. Colors identify cut provenance, not approval. General retains the entry color; version views use the selected cut's color.
5. Version views, including their player, are read-only. Return to the current scope for permitted edits.

Filters narrow work without deleting data. Visible selection and the entire project are different scopes.

1. Filter by episode, status, owner or text. Search note context to locate a review.
2. Sort using headers. File, Shot, TC, Duration, Owner, Status, Work scope, Version and Created help inspect records.
3. Check filters and selection before bulk actions. Do not assume rows outside visible results are included.
4. If a shot is missing, clear filters and check omitted shots/history before recreating it.

Read operational status together with evidence. A chat message does not deliver a shot.

1. Record review or delivery with the relevant control and link the correct material.
2. In Shot Deck, artists submit review or final evidence through an explicit delivery action.
3. A final shot is locked against normal artist editing. If changes are needed, request reopening with an explanation.
4. Coordination reviews the request and history. Final VFX status does not equal full master acceptance in Delivery.

Export produces output for the selected context; it does not change shot status.

1. Choose the available format and scope in Export and review episode, filters and version.
2. Check identity, timecodes and duration in Excel before sharing or reusing the sheet.
3. To publish Frame.io notes, the Share Link must allow comments and point to the correct asset. This sends content outside RushTrack.
4. Do not assume automatic bidirectional synchronization of every field. Check what each integration action imports or publishes.

Reconform seeks visual continuity across assets while preserving shot identity and history.

1. Confirm the base cut and new asset. Use the matching FIOJSON and video, not just a similar filename.
2. Maintain authorized access to both media sources. Blurred or protected copies cannot confirm reliable visual relationships.
3. Automatically imported shots retain the note's interior reference as identity evidence, separately from shot IN.
4. Wait for comparison to finish before evaluating candidates.

A continuity proposal is a visual hypothesis to review, especially after editing changes.

1. Compare the earlier reference with images from the new cut and their temporal sequence.
2. Review ambiguous associations and absent shots. Do not force continuity to preserve a count or number.
3. Check that new boundaries belong to the actual shot, not its neighbor.
4. If multiple existing identities could receive the same note, resolve the conflict before saving.

Earlier notes retain their original TCs. Omitting from the current version does not erase history.

1. Check General and the new version's note view separately.
2. Use Show omitted and earlier cuts to review removed work.
3. When reimporting the same cut, existing manual ranges are respected, and repeating the same comments must not add copies or new versions.
4. If import fails, check the message and actual state before retrying. Do not roll back the entire project or delete the tracker to fix an editorial problem.

VFX Team manages individual, revocable access. It is not the general Share project matrix.

1. In Team, enter the artist's email and identity and send an invitation through the available workflow.
2. Review status: inactive, active, expired or revoked. Created access does not prove work occurred.
3. Assign the appropriate shots and verify scope before privately sharing the personal link.
4. Revocation preserves history and conversations; it does not erase the person's work.

Artist chat and shot context preserve what was requested, from whom and for which material.

1. Choose the artist or shot before writing instructions.
2. Use evidence actions for review or final delivery, in addition to conversation.
3. For a final shot needing changes, the artist submits Request reopening with a reason; the message alone does not reopen work.
4. Do not copy personal links into conversations with people outside that access scope.

Vendors brings together companies, contacts, packages and quotes. The vendor and assigned artist are not necessarily the same entity.

1. Create or review the vendor record before linking it to shots or packages.
2. When preparing a package, check shots, scope, references and recipient.
3. Keep active packages separate from archived ones. Review confirmation and financial impact before archiving.
4. Do not assume editing a vendor record replaces recorded quotes.

A vendor quote retains its document, date, currency, amount and terms. Approval is explicit.

1. Open the package and upload the quote document with date, valid amount and currency.
2. Check payment terms; the approval workflow requires them where applicable.
3. Use Approve quote / Approve and award only after reviewing vendor, scope and amount.
4. Check Finance incorporation status and the resulting record. Do not duplicate a manually entered cost when a financial link already exists.
5. If pending or failed, inspect confirmed state before resubmitting.

Each record retains episode, sequence, performer, line, timecodes and the reason for the intervention.

1. Create or import the sequence and complete performer and line; they are essential to a usable record.
2. Enter TC IN/OUT, FPS and source TC. A compatible Frame.io link can supply a reference and thumbnail.
3. Choose creative, audibility or technical type; add owner, estimated minutes and notes.
4. Follow actual progress through Identified → Approved → Scheduled → Recorded → Review → Final.
5. Filter by episode or performer to prepare the call without losing each line's reference.

Sessions group sequences to organize time, studio and responsibilities.

1. Create a session with date, start, end, studio and an internal HUB or external location.
2. Set operator and coordination; select the approved sequences to record.
3. Confirmation moves selected sequences to Scheduled, not Recorded.
4. Update session status to draft, confirmed, completed or rescheduled as appropriate.
5. After recording, review sequences and individual status before marking the whole session complete.

Technical configuration records requirements and validation. RushTrack does not install plugins or license studio software.

1. Enter Pro Tools version, license model and workstation count.
2. Specify sample rate, bit depth, delivery format, loudness, true peak, naming and specification link.
3. Record plugins with version, license, workstations and observations.
4. Compare requirements with the selected studio and mark compatibility pending, compatible or with issues, including who validated it and when.

5.1, stereo, M&E and stems are tracked as deliveries with their own type and version.

1. Create a delivery with episode, type, version, date, Frame.io reference and notes.
2. Update status: draft, review, changes, approved or final.
3. Archiving in Library is available for approved/final states. If status moves backward, review its archive condition.
4. An approved mix does not replace acceptance of the project's Delivery chain.

A shared schedule temporarily publishes recording sessions; it is not workspace editing permission.

1. Review sessions and timezone before enabling the available schedule link.
2. Share only with people who should view that schedule.
3. Disable publication when its scope changes or it is no longer needed. Do not confuse it with a project invitation.

The pipeline documents how images will be prepared and finished. It does not perform a conform or transform video.

1. In Edit pipeline enter studio, colorist, grading platform, workflow and working space.
2. Record camera, codec, camera space, IDT, show LUT and metadata.
3. Configure HDR/SDR outputs, format, display space, nits, output transform and mastering monitor.
4. Enter calibration date, resolution, aspect ratio, FPS and naming; save and check persistence status.
5. Initial values, such as ACES or an EXR format, are editable starting points, not universal client specifications.

Technical exchange requires more than a software name.

1. Record plate format, color space, bit depth, compression and handles.
2. Define the reference recipe: CDL/LUT/CLF and reference frame according to the agreed pipeline.
3. Validate requirements with VFX before preparing material. Documenting handles does not add frames to a file.
4. Communicate recipe changes to the team; already exported plates do not change automatically.

Color retains a review record per episode: status, actual date, reviewer, approver, evidence and notes.

1. Check dates from Calendar: Color review, notes and final.
2. Update status according to progress: pending, preparation, review, notes, correction, approved or final.
3. Complete reviewer, approval, actual date and evidence link.
4. This record is not an unlimited library of versioned renders. Use appropriate references and delivery history to retain files.
5. Check All saved. On save failure or conflict, preserve your draft and reload before retrying.

A chain identifies a commitment; attempts preserve each submission or resubmission.

1. Create a chain with episode, platform/destination, asset type, language, date and owner.
2. Choose the correct type: IMF, ProRes Master, Supplemental IMF, textless, audio, subtitles or another type.
3. Add destination references and notes. Netflix references may include Movie, Package or Source Request identifiers.
4. Compare the date with Calendar. Do not combine different language/type deliverables into one identity for convenience.

Creating a record does not transfer the master or prove its recipient received it.

1. Add a delivery to the chain with version label and date.
2. Record filename, checksum when available and a verifiable evidence link.
3. Complete status and notes. Preserve the previous attempt when redelivering.
4. Ensure evidence matches that file and version, not a generic link always pointing to the latest file.

QC and acceptance are different stages. A technical pass does not automatically mean final acceptance.

1. For the attempt, enter QC status, feedback date and report link.
2. Record blockers, issues, FYIs and notes so the team knows what to fix.
3. Failed or Fix notes moves the chain to correction; inspection or QC passed is reflected in the QC stage.
4. Create a new attempt when redelivering and keep the earlier one as evidence.
5. Mark acceptance only when it matches the actual outcome and review the entire chain's status.

The documented workflow is manual: chains, versions, states and QC are recorded in RushTrack. Backlot synchronization is paused in the documented configuration.

1. Do not put Netflix credentials in notes or links to try to activate synchronization.
2. Master transfer continues through the destination's tools; saving a delivery in RushTrack does not transfer it.
3. A server integration can only be enabled with facility authorization and configuration.
4. If another installation has synchronization enabled, check query time and outcome. Processed is not automatic final acceptance.

Master Library organizes deliveries and evidence with project and episode context.

1. Open Library and choose a project you can access.
2. Enter the episode and locate milestone, delivery code, date and version or evidence.
3. Search by name or reference to narrow results; check the source project before opening material.
4. External links retain their provider's access conditions. Appearing in Library does not make a file public.

The documents panel manages files with category, title and description within the selected project.

1. Open project Documents / Library and review categories and results.
2. To upload, choose a file and complete category, title and description. Respect the displayed storage limit.
3. Wait for confirmation and verify the file appears. A failed upload is not a completed upload.
4. Editing and deletion depend on permission. Read the confirmation before deleting a file.

Project library permission does not grant access to all organizational files.

1. With a module grant, stay within the project panel. Global Library is not an automatic extension of that grant.
2. Finance and VFX documents retain their contextual access checks.
3. For a denied file, request an owner permission review. Do not duplicate it into a less protected category to bypass the control.

Reports collects existing module outputs. It is not an independent copy for correcting project data.

1. Identify the source section: Calendar, Team or Finance.
2. Review project, mode, current version and export permission.
3. Choose Excel to work with data or PDF for fixed output, depending on available formats.
4. Wait for Preparing file and check success or failure before downloading again.

Interpreting a report requires knowing its scope and point in time.

1. Open the file and check project name, dates, currency, totals and version.
2. Correct errors in the source module, then export again.
3. A locked financial section may mean restricted access, not a missing budget.
4. Do not publish personal or financial information in an open channel merely because it was exportable.

Overview brings operational signals together; it does not replace module records.

1. Review upcoming commitments, activity and alerts to decide priorities.
2. Confirm which project each signal belongs to.
3. Open its source to inspect or correct it. One indicator does not prove the entire project is up to date.

Agenda shows project-derived events in the selected time view.

1. Choose the period and available filters.
2. Open a commitment to check episode, milestone and status in context.
3. If a date is unexpected, check active version and tracking in the source calendar.
4. Sharing or synchronizing a schedule does not grant project editing permission.

A milestone retains planned date, status and evidence. The cross-project list does not create another calendar.

1. Identify project, episode and milestone before acting.
2. Distinguish due dates from completion; review tracking and actual date where available.
3. Return to Calendar for dependencies or changes affecting the chain.

The global Deliveries view shows commitments; project Delivery retains technical chains and attempts.

1. Filter by period or status to find upcoming, pending or correction work.
2. Inspect evidence and the project link before marking an outcome.
3. Open Delivery to record QC or a technical redelivery. An aggregate signal is not definitive chain acceptance.

Selection defines notice scope. Check the full summary, not only the first visible items.

1. Select milestones needing notice and open Create notification.
2. Check project and milestone list; expand remaining items if abbreviated.
3. Enter valid email addresses, notice timing and channels that are actually configured.
4. Save or activate the rule and review it in Notifications. Avoid duplicate rules for the same purpose.

Delivery depends on an enabled, configured channel. A saved rule does not prove message delivery.

1. Use Slack only when its connection is ready. Checking its box is insufficient.
2. A test sends a real notice: review recipients before running it.
3. Distinguish saving, activation and delivery outcome. For a failed channel, inspect its specific message.
4. Editorial notifications belong to their own task/email workflow; they do not automatically become milestone rules.

Notifications guide action; they do not complete milestones or tasks.

1. Review active rules when dates, owners or scope change.
2. Disable obsolete rules and check lead time and frequency before resending.
3. Budget mode does not offer all the operational calendar alert tools.

Professional identity is reusable; its participation period is defined in Team.

1. Enter name, role, seniority, location, specialties, skills and relevant professional links.
2. Review email and phone before sharing. Keep only information you should administer.
3. Maintain verifiable experience and history. A complete profile does not guarantee availability for another project.
4. Search for the person before creating a profile to avoid fragmenting their history.

Finding a person and assigning a position differs from inviting them to edit RushTrack.

1. Search by name, role or available directory attributes.
2. Review profile and experience; confirm availability and conditions with the person.
3. Link them to the planned Team position and review participation dates.
4. If access is needed, use the appropriate collaboration workflow: project, VFX or Editorial.

Professional outputs may include contact information, specialties, experience and portfolio links.

1. Review the view or content before sending.
2. Do not assume a link or summary hides email and phone automatically; check included fields.
3. Share only with suitable recipients and appropriate authorization. Sharing a profile grants no project or Finance access.

This manual searches public instructions. Workspace search queries authorized operational records.

1. Enter at least two characters in Search and use specific identifiers: project, showcode, shot, file or person.
2. Read each result's category and project: Project, Library, Milestone, VFX, ADR, Sound, Frame.io, File, Talent or a workspace destination.
3. If results are limited, refine the term before concluding a record does not exist.
4. You can clear recent browser searches without deleting RushTrack records.

Rule out context or visibility differences before creating another record.

1. Confirm account, project, episode and selected version.
2. Clear filters and check pagination. In VFX check General, Versions and Show omitted; in Editorial check cut and Unassigned.
3. Check module permission and access status. Denial does not imply data deletion.
4. If unresolved, report the identifier and last known sighting without deleting or reimporting the whole project.

Some modules check draft revisions to avoid overwriting another person's concurrent changes.

1. Keep your draft text somewhere safe before reloading.
2. Reload and review confirmed state. Reapply only changes still appropriate.
3. If permission was reduced or revoked, ask the owner to review access rather than trying an alternative saving route.
4. A visual change with a save error is not persisted. After a lost response, inspect the record before repeating an irreversible operation.

Link, asset, external authorization and FPS must agree. A visible thumbnail does not prove video is playable.

1. Check that Share Link and export refer to the same file and version.
2. Check link expiration/protection and authorized playback availability. Never put credentials in notes.
3. For VFX without OUT, a still frame is expected behavior, not necessarily a playback failure.
4. If analysis fails, keep the message and source for review; do not change another module to try to fix it.

These terms recur across modules but have distinct meanings.

1. FIOJSON: exported comments and references; Share Link: link to external material; asset: the provider's file identity.
2. TC: a frame address; FPS: frame rate; IN/OUT: shot boundaries; handles: extra frames requested for exchange.
3. Reconform: review of correspondence between cuts; omitted: removed from the current cut without deleting history.
4. Evidence: verifiable reference to work or submission; QC: quality control; acceptance: recorded final decision.
5. Module editor: scoped operational permission; coordination: workflow-specific authority; group member: a person authorized to work on that portion.