Describe your photography service and review process. Makeform turns it into a photo request form for shoots, archive searches, event coverage, or image-use requests.
Route requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose an example, tailor its details, or send it to the Makeform builder. This structure is a planning preview.
Audience
Departments requesting original photography
Format
Brief with schedule and deliverables
Prompt size
259 chars
Example form structure
Brief with schedule and deliverables
Requester, department, and project
Preferred and backup shoot dates
Subjects, location, and shot list
Where will the photos appear?
Reference images or brand brief
Suggested routing tags
New shoot
Archive search
Usage review
Ask for channel and publication date so the team can choose dimensions, resolution, and deadline.
Step 1
Request
purpose, images, audience, and deadline
Step 2
Triage
new shoot, archive search, or usage review
Step 3
Clarify
confirm scope, access, formats, and timing
Step 4
Deliver
share files and record the outcome
A usable photography brief
A message saying “we need photos Friday” omits the audience, shot list, access, format, and deadline. A structured form collects them upfront.
Require subjects, location, dates, priority moments, on-site contact, and access notes before scheduling.
Use different follow-ups for a new shoot, an archive search, event coverage, or a request to use an existing image.
Send shoot briefs to production, archive searches to the asset manager, and image-use requests to the person responsible for review.
Four request paths
Start with request type, then reveal fields for that path.
Capture goals, subjects, references, schedule, location, shot list, and outputs.
Search by people, event, date, keywords, orientation, and placement.
Gather the run of show, priority moments, credentials, and access.
Record the asset, publication, channel, dates, edits, caption, and credit.
Request workflow
Describe request types, production details, and routing. Review the result, then publish.
List who submits, which request paths you accept, required details, and each recipient.
Replace sample options with your channels, formats, locations, lead times, and project codes.
Reveal shoot logistics only for new photography, require an asset ID for reuse, and ask archive-search clues only when needed.
Share or embed the form, notify the right owner, and keep the request details together while the team responds.
Form vs email vs generic brief
Photography requests combine creative intent with practical constraints. Structured intake preserves both and reduces follow-up.
Field guide
Fields vary for new shoots, existing assets, and proposed image use. These six sections are a practical starting point.
Requester and ownership
Capture the requester, team, contact, project owner, and job code. For external requests, add the organization.
Purpose and audience
Connect the image to its message and audience. Ask what it communicates, who will see it, and where it appears.
Subjects and references
For shoots, request subjects and priority shots. For archive searches, gather names, locations, events, dates, and keywords.
Output specifications
The destination determines crop, orientation, dimensions, resolution, and file type. Ask for every placement and its priority.
Schedule and logistics
Separate shoot and publication dates. Ask for backup windows, venue access, an on-site contact, review time, and final deadline.
Use and review context
For reuse, capture the asset, publication, audience, channel, dates, territory, edits, caption, and credit. State that submission requests review; it does not grant permission.
Related tools
Connect intake with shoot questionnaires, booking, contest entries, creative briefs, and release workflows.
Brief new photography with subjects, dates, locations, references, and deliverables.
Open toolGather a couple's story, locations, timing, style, and session details.
Open toolCollect wedding schedule, venue, package, contact, and photography preferences.
Open toolAccept photo entries with entrant details, categories, image uploads, titles, and submission notes.
Open toolCapture goals, audience, message, deliverables, references, stakeholders, and timeline.
Open toolCollect the organization's photo release wording and participant responses separately.
Open toolFAQ
Practical answers for photographers, creative teams, communications offices, and organizations centralizing image requests.
It is an intake form for new photography, event coverage, existing images, or review of proposed image use. It gathers purpose, subjects, schedule, outputs, references, and contact details consistently.
Include requester, request type, goal, audience, subject or asset, channel, dimensions, orientation, dates, deadline, and references. Add access and a shot list for shoots, or asset and use details for existing images.
Yes. Use a request-type choice and conditional logic. Reveal shoot logistics for new photography, search clues for archive requests, and publication and credit questions for proposed image use.
Add uploads for screenshots, mood boards, run-of-show documents, or brand guidance, plus a URL field. Explain whether each reference demonstrates composition, setting, color, or a specific asset.
No. State that submission starts a review and does not grant permission. Ask requesters to wait for a separate decision, and use wording and review rules supplied by the organization.
Ask separately for shoot, selection, edit, and publication dates. Show lead-time guidance, require a reason for urgency, and route exceptions to the scheduler without promising the requested date.
Yes. Makeform offers unlimited free forms and responses. Generate, edit, publish, and collect requests without a form or response cap; the paid tier removes the Makeform badge.
Responses arrive in your Makeform workspace. Configure notifications or connect Slack, Google Sheets, or Zapier. Route by request type so each reviewer receives relevant details.
Turn every photo ask into a usable brief.
