Describe how teachers or employees send work to your copy room. Makeform turns the brief into a practical copy request form with requester details, file uploads, page and copy counts, paper and finishing choices, needed-by dates, charge codes, and pickup or delivery instructions.
Route copy requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a complete prompt, tailor it to your copy room, or send it to the Makeform builder. Each sample shows a useful starting structure, not a live production result.
Prompt ready4 formats
Audience
Teachers requesting classroom handouts and packets
Format
File-upload request with production and delivery details
Prompt size
463 chars
Brief qualitySends to builder
Example form structure
File-upload request with production and delivery details
Prompt exampleEditable in builder
Teacher, grade or department, and classroom
Short answerFirst ask
2
When are the copies needed?
Date & time
3
Original pages and finished sets
Number
4
Paper, color, sides, and finishing
Multiple choice
5
Upload the print-ready file
File upload
Suggested routing tags
Suggested
New request
Deadline review
Ready for pickup
Ask for both the original page count and the number of finished sets. Those values are easy to confuse, but together they let staff estimate the actual impressions before accepting a deadline.
Step 1
Request
files, quantities, stock, finishing, and deadline
Step 2
Review
copy staff checks the brief and resolves exceptions
Step 3
Produce
job is printed, finished, and assembled
Step 4
Deliver
requester receives a pickup or delivery update
Why requests go wrong
A file attachment is not a production brief.
Email threads often omit the count, deadline, paper, sides, or finishing. A structured copy request form asks for the complete job before it enters the queue, while leaving room for copy staff to clarify unusual work.
Production details in one submission
Keep the source file beside page count, finished quantity, ink, paper, sides, finishing, and delivery instructions. Staff can review one brief instead of reconstructing a job from messages.
Questions that follow the job
Show booklet binding choices only for booklets, delivery fields only for delivery, and proof instructions only when a proof is requested. The common path stays short without losing special-job detail.
A visible handoff to the copy room
Send a consistent submission to the production inbox or tracking sheet, including the requester's contact and needed-by time. That gives staff a clear record for questions and status updates.
Built around real copy work
One starting form, adapted to four production settings.
Choose the closest workflow, then replace generic options with the paper sizes, stocks, finishing equipment, service windows, and delivery points your team actually supports.
Teacher handouts
A quick path for worksheets, quizzes, and classroom packets: upload, sets, sides, paper, due time, and classroom delivery.
Central reprographics
School, approver, account code, high-volume specifications, finishing, and a destination for jobs produced away from the requester.
Office and training materials
Meeting date, handout style, proof preference, pickup point, and cost allocation for internal business printing.
Assembled packets
Multiple source files, component order, covers, tabs, binding, and packaging instructions for packets that must arrive ready to distribute.
Request workflow
Turn a copy-room checklist into an online intake flow.
Start with the details staff repeatedly chase, organize them in the same order a requester thinks about a job, and publish one copy request form that works from a classroom, office, or phone.
Tell Makeform who submits requests, which jobs you accept, the normal turnaround guidance, available paper and finishing options, and whether departments need account or approval fields.
02
Replace generic choices with your menu
Edit dropdowns to match supported sizes, stocks, colors, bindings, pickup points, and buildings. Mark files, quantity, page count, deadline, and requester contact as required.
03
Branch for special production
Add conditional questions for color work, booklets, packets, wide-format jobs, delivery, or proof approval. Explain cutoff guidance beside the deadline field so requesters can choose realistically.
04
Route a complete request
Publish the form and direct submissions to the people or systems used by your copy room. Include the requester in confirmation messaging and define how staff will communicate questions, readiness, or pickup.
Form vs email vs paper ticket
Choose an intake method that captures the production brief.
The best method is not the one with the fewest boxes. It is the one that gives copy staff enough consistent information to review the job without forcing every requester through irrelevant questions.
Approach
What reaches the copy room
Operational fit
ApproachEmail with an attachment
What reaches the copy roomThe file arrives quickly, but quantity, sides, stock, finishing, account code, and actual deadline may be scattered or missing.
Operational fitUseful for a one-off conversation; inconsistent for a shared production queue.
ApproachPaper copy ticket
What reaches the copy roomA familiar checklist travels with the job, but remote requesters still need another way to deliver files and corrections.
Operational fitPractical at a walk-up counter; harder to route between buildings or preserve as a searchable intake record.
Approach
Generated online copy request form
What reaches the copy roomThe uploaded file, structured specifications, requester, deadline, cost information, and destination arrive together in a repeatable format.
Operational fitStrong for schools and offices with multiple requesters, locations, job types, or production staff.
Field guide
What a useful copy request form should include.
Treat the form as a production brief, not merely an upload box. Six groups of fields cover identity, schedule, source material, output, finishing, and handoff while conditional logic can keep each request focused.
Requester and ownership
Give every job a reachable owner.
Start with the person who can answer a content or production question. In a school, grade, department, room, and building help staff distinguish similar teacher names and plan delivery. In an office, team and project connect the job to its business purpose.
Requester name, work email, phone or extension, department, and location.
School, grade level, classroom, team, project, meeting, or event name.
Approver, cost center, budget code, or internal work-order reference when your process uses one.
Schedule and priority
Separate the real event from the requested deadline.
A needed-by field tells production staff when the requester wants the job; an event or distribution date explains when it becomes unusable. Capturing both prevents an arbitrary rush request from looking the same as materials needed for a fixed exam, training, or board meeting.
Requested completion date and time, plus event or classroom-use date when relevant.
Pickup, interoffice delivery, classroom delivery, or another supported handoff method.
A priority reason or exception note for deadlines outside published service guidance.
Source documents
Collect files with enough context to print the right version.
Require the print-ready file and a recognizable document title. If the workflow accepts several components, gather each file with its page count and position in the final packet. A version label or revision date helps staff avoid producing an older attachment after corrections.
One or more source-file uploads, document title, version, and original page count.
Orientation and final finished size, especially when files must be reduced, enlarged, folded, or cut.
For multi-file packets: component order, exceptions, separator sheets, and an optional example layout.
Quantity and print settings
Make the output count unambiguous.
Finished sets and original pages are different values. Ask for both, then collect the settings that affect every page: monochrome or color, simplex or duplex, paper size, and stock. Use plain labels and examples because requesters may not use print-shop terminology every day.
Number of finished sets, copies, packets, booklets, posters, or other final units.
Black-and-white or color, one-sided or two-sided, and whether blank backs matter between sections.
Paper size, paper color, stock or weight, and any covers that differ from interior pages.
Finishing and assembly
Describe what happens after pages leave the printer.
A job is not finished if it still needs collating, stapling, binding, folding, cutting, drilling, tabs, or packaging. Offer only services your location provides. For packet work, let requesters specify document order and whether components repeat in every set.
Collated or uncollated output, staple position, hole punching, folding, cutting, or padding.
Booklet, comb, coil, tape, or another available binding choice with edge and orientation details.
Covers, tabs, dividers, labels, envelopes, boxes, bands, or other supported assembly and packaging.
Review and handoff
Define how questions, proofs, and completion move.
Some jobs can enter production immediately; others need a proof or staff review because color, quantity, finishing, or file setup is unusual. Ask whether the requester needs to approve a proof, identify the best contact method, and make the final destination explicit.
Proof required, proof format, named approver, and a contact channel for production questions.
Special instructions for color-sensitive pages, mixed stocks, accessibility needs, or assembly exceptions.
Pickup location or delivery destination and the expected method for sending a ready or clarification notice.
Related tools
Connect copy-room intake to nearby school and office workflows.
Build a focused form for approvals, records, equipment, reports, workspace, or general work orders when the request is broader than document reproduction.
Practical answers for teachers, office staff, school administrators, and copy-room teams replacing email or paper production tickets.
What is a copy request form?
A copy request form is an intake form a teacher or employee submits when documents need to be photocopied, printed, finished, assembled, and delivered or held for pickup. It pairs source files with the production brief: requester, deadline, page count, finished quantity, print settings, paper, finishing, account information, and destination.
What fields should a school copy request form include?
Start with teacher name, email, school, grade or department, classroom, document title, file upload, original page count, finished sets, needed-by time, color mode, sides, paper, finishing, and pickup or delivery. Add a cost center, approver, event date, proof choice, or packet assembly fields only when your workflow uses them. Clear examples help distinguish pages from sets.
Can one form handle both simple copies and complex print jobs?
Yes. Keep the first questions common to every job, then use job type and conditional sections for relevant details. A worksheet may need only a file, set count, sides, paper, and deadline. A booklet may reveal final size, cover stock, page order, binding, proof, and packaging. A packet may need several uploads and component order.
How should a form ask for copy quantity?
Ask separately for original page count and finished sets. For example, a 12-page document requested as 30 sets is not 30 total impressions. Name the final unit, such as sets, packets, booklets, posters, or copies of one page. For multiple documents, collect packet quantity and note components that appear only in selected packets.
Can requesters upload several documents for one packet?
Yes. Add a multi-file upload or repeating section and ask for a name, page count, paper, sides, and position for each document. Also collect packet quantity, component order, covers, dividers, binding, packaging, and an optional example. If recipients receive different inserts, explain which component belongs in each version.
How can the copy room manage rush requests and proofs?
Collect both requested completion time and the actual event or classroom-use time, then ask for a reason when the request falls outside normal turnaround guidance. Route exceptions to a staff review status instead of implying that a selected date is automatically accepted. For work requiring a proof, collect the approver's name, proof format, and contact method. The copy room can then clarify feasibility, send a proof, record feedback through its chosen process, and communicate a revised completion plan when necessary.
Is this copy request form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use the copy request form without a response cap. The paid tier removes the Makeform badge. You can still tailor the free form to your school or office, replace sample options with your actual service menu, and test the entire request path before sharing it with teachers or employees.
How should we test the form before sending it to staff?
Submit at least four realistic jobs: a simple one-page handout, a duplex packet, a color or specialty-stock job, and a rush request requiring review. Confirm that required files and quantities cannot be skipped, conditional questions appear for the correct job types, notifications reach the intended team, and pickup or delivery choices match real locations. Ask copy staff to produce from the submitted details alone. Any question they still need to email back should become a clearer field, option, help note, or documented exception path.
Replace incomplete copy-room emails.
Generate a copy request form that carries the file and the full production brief.
Unlimited free forms and responsesFiles and specifications togetherSchool and office ready
