The system where every NDP shoot lives, from booking to upload
Jira is our shoot management system. Every time an agent schedules a photo shoot, the system automatically creates one or more Jira cards for that job. You'll use Jira on both desktop and the mobile app — get signed into both before your first shoot.
Both versions show the same cards and fields. Desktop is required for first-time setup (pinning fields). Mobile is handy on site when you need to check access instructions or add a note to the editor.
Every shoot card moves left to right through five stages
When a shoot is booked, the card appears in the Scheduled column. Use the blue button at the top of the card to move it forward through each stage. Never drag and drop — use the button.
| Stage | What It Means | Who Triggers It |
|---|---|---|
| Scheduled | Shoot booked, card created | Auto-created when agent books |
| Acknowledged | You've confirmed the shoot is on your radar | You move it forward |
| At Listing | You're on site, shoot is in progress | You move it forward when you arrive |
| Shoot Complete | Shooting done, ready to upload | You move it forward when done shooting |
| Uploaded | Files in Dropbox, card closed out | You move it forward after upload (requires raw photo count) |
Dragging and dropping a card between columns may produce errors. Always use the blue stage transition button at the top of the card.
Once a card is moved to Uploaded, it will no longer be visible for Media Pros. Make sure everything is complete before advancing.
The long title string at the top of every card is packed with info
Card titles follow this format:
[YYMMDD] [Time] [Agent Last Name] [Address] [Service]
Example: 260528 05.00 PM Hinton 413 Erin Court Photo Pack
| Part | What It Means | Example |
|---|---|---|
260528 | Shoot date (YYMMDD) | May 28, 2026 |
05.00 PM | Shoot start time | 5:00 PM |
Hinton | Agent's last name — not a city | Agent's account last name |
413 Erin Court | First part of the property address | Listing address |
Photo Pack | Service being captured on this card | Product type |
A city-sounding word in the title (Marietta, Stockbridge) may actually be the last name on the client's account, not the shoot location. For example: NONL Marietta (NONLMarietta@MarkSpain.com).
Each product has its own Jira card — all linked together
If a shoot includes multiple products (e.g., Photo Pack + Zillow 3D + Floor Plan), each product gets its own Jira card. All cards for the same shoot are linked together under Linked Work Items.
Open Linked Work Items on any card and click through to see the other products for the same shoot. All agent and property details are duplicated across each card — that's expected.
Make sure you complete and advance each card individually for every product you captured on site. Don't just close the main card and assume the others are done.
Read these before every shoot — every single time
These fields live in the Key Details section of every card. Make a habit of checking them before you leave for a job.
One of the most important fields. Clients can have standing editing preferences saved here (e.g., "Do not digitally add fires to fireplaces"). You may also need to add a note while on site.
If there's already something in this field, add your note after the existing text. Do not delete or replace what's there.
If a client makes a special request on site (e.g., "Photoshop the car out of the driveway"), open the app and add the note right then. Don't wait until you get home — you'll forget.
Filled out by the agent when they booked. This tells you who will meet you on site, any lock box codes, or whether the property is vacant. Always read this before every shoot.
Even if Access Instructions says the property is vacant and flexible, always go at the scheduled time. If you want to change it, run it through operations first. Clients often forget what they told us and will expect you at the booked time.
Also filled out by the agent — may include special notes about the property, like a finished in-law suite above the garage. Read this too.
Most other fields in Jira are used by the operations team and don't pertain to the Media Pro role. Don't be overwhelmed. Examples you can skip:
All five stages and what triggers each move
| Stage | Meaning | Who/What Triggers It |
|---|---|---|
| Scheduled | Shoot booked, card created | Auto-created when agent books |
| Acknowledged | You've seen and confirmed the job | You move it forward |
| At Listing | You're on site, shoot is in progress | You move it forward when you arrive |
| Shoot Complete | Shooting done, ready to upload | You move it forward when done shooting |
| Uploaded | Files in Dropbox, card closed | You move it forward after upload — requires raw photo count. See Upload Guide. |
Once a card is moved to Uploaded, it will no longer be visible for Media Pros.
Photo package counts and common upload questions
The Number of Expected Outputs field will match one of these delivered photo counts:
| Package Size | Delivered Photos (to client) |
|---|---|
| Small | 15 |
| Medium | 25 |
| Large | 35 |
| XL | 45 |
| Extra Photos Add-On | Varies — separate card |
The Number of Expected Outputs is how many edited photos the client receives. The Number of Raw Photos is the actual file count you upload to Dropbox — these are different numbers.
If you have more than one Jira card for a shoot (e.g. aerial, amenity, or community photos), each card has its own Raw Media Folder link. Upload those photos to their respective Jira cards.
If a card is labeled "Additional Photos" (for example, an agent ordered a 45-pack and added 20 more on top), you can upload those additional photos together with the main photo pack card — they do not need a separate upload. Enter 0 as the number of raw files on the Additional Photos card itself.