The Decision to Add Seasonal Crew to Your Software
If you operate an experienced US wedding studio hiring seasonal second shooters and assistants, you eventually face a specific software choice. You must decide whether to invite temporary contractors into your main studio management platform as team members, or whether to export their schedules manually. This decision rests on what data the contractor actually needs to see and what your software's permission levels allow them to access.
For this hypothetical job, assume you book the Morgan-Smith Wedding for October 14, 2027. The accepted quote is for a hypothetical $4,500 USD. The project includes three crew roles: one lead photographer, one second shooter, and one assistant. You hire Alex, a seasonal contractor, to fill the second shooter role.
Alex needs to know the venue addresses, the timeline, and their specific working hours. You must evaluate whether adding Alex as a user to the Morgan-Smith Wedding project provides exactly those logistical records or if it unnecessarily exposes the $4,500 USD invoice, the primary contract signed by the couple, and the private client questionnaire responses.
Platform Limitations and Team Member Permissions
When you add a contractor to a project, the software dictates what they can view. You must compare the system's definition of a basic team member against your own requirement for temporary crew visibility.
HoneyBook basic team members cannot view another team member's pipeline. They can act in projects they created or were added to as participants.[1]
If the software allows basic team members to see all files within a project they participate in, Alex will see the client correspondence and financial documents alongside the schedule. If your studio policy dictates that seasonal contractors should not view the financial terms negotiated with the couple, a system that shares the entire project workspace with all participants is inadequate for temporary crew. If your current software structure allows you to restrict invoice and contract views while keeping a user in the project, the existing tool is adequate for your contractors.
Identifying Schedule Mismatches in Shared Projects
Sharing a full project view can also create scheduling confusion if the software does not separate individual crew timelines. Compare the timeline records for the lead photographer and the second shooter on the Morgan-Smith Wedding.
The project record lists the main event coverage from 2:00 PM to 10:00 PM. However, the lead photographer starts at 2:00 PM for preparation photos, while Alex is contracted for 3:00 PM to 10:00 PM to cover the venue setup and arrivals.
If your software only displays a single project-level schedule, adding Alex to the project exposes the 2:00 PM start time directly to them. This is a clear mismatch between the project's overall timeline and the contractor's specific obligation. If Alex relies on the shared project view, they may arrive an hour early. Resolving this mismatch requires either a software tool that supports individual crew schedules within the same project or extracting Alex's specific 3:00 PM start time into a separate document outside the main software.
Verifying Visible Records With a Test Account
Before deciding to invite any contractor to your active software, check exactly what they will see by creating a sample job. Generating a mock project allows you to test the specific user permissions without risking the exposure of real client data.
Studio Ninja's test-job tutorial tells the user to name a job TEST JOB and add themselves as the primary client.[2]
By setting up a test project and inviting a secondary email address of your own as a basic team member, you can log in as the contractor. This lets you inspect the exact fields, tabs, and documents available to that user level. Use a structured list of checks to review the test account.
- Log in using the test contractor account and open the assigned test project.
- Check if the initial accepted quotation and payment schedule are visible.
- Verify whether the main client contract can be viewed or downloaded.
- Look for any private internal studio notes or client questionnaires.
- Check the project timeline to see if individual crew arrival times are separated.
- Confirm if the test account can view communication history between the lead and the client.
Testing Role Assignments in RevePod
If your current tool forces you to share the entire project file with a temporary contractor just to assign them a schedule, you can evaluate how RevePod structures these records. In RevePod, projects record events, crew roles, and deliverables.
When you build a quotation, it records the required crew role quantities, such as one Lead Photographer and one Second Shooter, but it does not assign named people to those roles. This separates the project's requirements from the actual human accounts.
When you create a project from an inquiry with an accepted quotation, RevePod can prefill the schedule, deliverables, payment total, and quote details. The prefilled crew roles and quantities transfer directly to the project, but they remain strictly as required positions rather than named crew assignments or confirmations of availability. This allows the studio owner to outline exactly what coverage is needed for the Morgan-Smith Wedding without automatically linking an external user's account to the client's project file.
Sources & further reading
Try the workflow on one wedding
In RevePod, a project connects the wedding's events, crew assignments, deliverables and payment details. Start with one project and check whether your team can find the next action without reconstructing it from messages.
- Create a project and add its event dates.
- Add the crew roles and assign the people covering each event.
- List the promised deliverables and assign the work before the shoot.
A project record still needs someone to keep it current. Check the plan's team and project limits before moving the rest of your bookings.
