Your first production

اقرأ هذا الدليل بالعربية

1. Set up the production

Choose the correct organization before creating a project. Set its title, language and timezone. Use a small test production first, with your own test crew contacts. Keep the original script as a separate copy.

2. Import and review the screenplay

Open the project's script workspace and import Final Draft (FDX) or Fountain, or paste the script text. Review the preview before applying it. Check scene numbers, Arabic/English headings, character names and locations. Review the created scenes in breakdown; an import needs human review before it drives a shooting schedule.

If the script saves but scene synchronization fails, keep the import open and retry the synchronization. Do not create another production to recover the same import. For subsequent revisions, use the revision workflow and review Ripple's proposed impact before applying changes to a working production.

3. Prepare contacts and one shoot day

For an existing roster, use Contacts → Import Contacts or the project's Crew → Import Roster. Upload CSV/Excel, choose a worksheet, map columns and review all rows before confirming. Crew requires Name, Department and Position. Use international phone numbers stored as text. Resolve duplicate/identity issues first; existing contact details and crew assignments are preserved. Import History records completed imports and helps check an interrupted response. Importing does not send messages or invite users.

Create the crew and cast contacts you need. Check full international phone numbers and email addresses, and assign cast contacts to their characters. Assign the actual location to scheduled scenes. Add coordinates when you need weather or solar information; ProdX does not substitute a reference city for a missing location.

In the schedule workspace, create a shoot day and add its scenes to the stripboard. Review scene order, call time, date and production timezone. Check scene reports and DOODs against your production plan. Rescue previews are planning aids: review their constraints and consequences before applying a recovery option.

4. Publish and verify the call sheet

Generate a call-sheet draft from that shoot day. Review the location, map, contact details, hospital, safety information and each person's call time. Preview the printed output before publishing. Missing information should be completed by the production team, rather than inferred from an empty field.

Publish the draft, then share each recipient's personal link through your approved communication channel. Treat personal links as private access links. Open a test link on a phone and acknowledge the published version. Check that the production workspace records that acknowledgment before rolling out to the rest of the crew. Generating a share link alone does not prove delivery to someone's device.

If the production operator has configured verified inbound messaging, personalized messages include a PX publication reference for replies. Browser confirmation links remain available. A generic message without that reference does not choose a project.

5. Reissue changes and work on set

Edit the draft, review the change and publish the next version. Ask recipients to acknowledge the current version; an earlier acknowledgment does not confirm a new publication. Check exceptions with the production coordinator.

Before losing connectivity, open the on-set view while online and let its shoot-day data load. Keep that view open. Takes, circle flags, scene statuses and set times use a saved device queue. Review its count and sync state when reconnecting. If sync pauses, check access/DPR approval and choose Sync Queue Now; do not log the same take again to clear an uncertain network failure.

Saved snapshots expire after 12 hours. Opening or fully reloading a protected page requires connectivity. Signing out, switching organizations or clearing saved device data discards unsynced actions. See device data and access.

Before a real shoot

Complete this flow with a synthetic scene and a test recipient first. Verify the Arabic view, printed output, current-version acknowledgment and reconnect behavior. Confirm provider delivery with the production operator; local test results do not establish hosted availability or message delivery.