Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an editable HTML presentation with a 16:9 canvas, previous/next buttons, arrow-key navigation, a slide counter and a one-slide-per-page print layout for [PROJECT] and [AUDIENCE]. The task is: Hiring Plan Deck.
Required content and structure
Connect organizational needs to roles, timing, interview process and budget assumptions.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Prepare organizational needs, role definitions, approved headcount, timing, interview stages and budget assumptions. Identify dependencies such as management capacity or funding.
Layout and behavior
Explain why each role is needed before showing the hiring sequence. Keep proposed roles visually distinct from approved openings and connect timing to business needs.
Task-specific acceptance check
- Distinguish approved headcount from proposed roles.
- Reconcile role counts and cost assumptions across slides.
- A proposed role should not become an advertised opening or approved budget merely through its position on the timeline.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Keep one main idea per slide. Use charts only when actual comparable values are supplied; include units, source dates and limitations. Keep speaker notes separate from visible slide content.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Hiring Plan Deck. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Connect organizational needs to roles, timing, interview process and budget assumptions. Use the following task-specific layout guidance when translating the image into editable elements: Explain why each role is needed before showing the hiring sequence. Keep proposed roles visually distinct from approved openings and connect timing to business needs.
Visual direction from the example brief
ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy.
Slide structure and presentation behavior
Recreate the slide composition as editable title, body, visual and annotation elements. A pictured slide is one view, not evidence of a complete deck. Use the supplied narrative to build any requested additional slides; preserve its typography, margins, color roles and alignment. Explain why each role is needed before showing the hiring sequence. Keep proposed roles visually distinct from approved openings and connect timing to business needs. Keep navigation outside exported slide content. Distinguish approved headcount from proposed roles.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Adapting the reference to slide dimensions
The attached visual reference is a 3:2 concept image, while the requested presentation uses 16:9 slides. Recompose its text, images, charts and spacing as separate editable elements on a 16:9 canvas. Do not stretch the reference or crop the whole composition to force a match. Preserve the hierarchy, keep the supplied content readable, and adapt each slide to its own message.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Hiring Plan Deck Design Prompt
Use this hiring plan deck design prompt to connect organizational needs to roles, timing, interview process and budget assumptions.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Link Roles to the Work They Enable
A hiring plan deck needs more than a list of job titles.
Explain which work requires each role and when that need becomes material. Explain why each role is needed before showing the hiring sequence. Keep proposed roles visually distinct from approved openings and connect timing to business needs.
From the Prompt
Explain why each role is needed before showing the hiring sequence.
Make It Your Own
Connect [BUSINESS_NEEDS] to proposed roles, timing and budget assumptions. Distinguish approved headcount from requested positions and identify dependencies between hires.
Prepare the Hiring Plan Deck Content
The sequence moves from organizational needs to roles and timing. Prepare headcount demand and approved versus proposed roles before turning the plan into a timeline.
Prepare organizational needs, role definitions, approved headcount, timing, interview stages and budget assumptions. Identify dependencies such as management capacity or funding.
From the Prompt
Connect organizational needs to roles, timing, interview process and budget assumptions.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this hiring plan deck. Prepare organizational needs, role definitions, approved headcount, timing, interview stages and budget assumptions. Identify dependencies such as management capacity or funding. Identify missing inputs before replacing them with demonstration content.
Check an Unapproved Role
The final stages separate interview process from budget assumptions. Check that hiring capacity and fully loaded costs support the requested timing rather than presenting aspirational dates as commitments.
Its slide should make approval status and the consequence of delay clear. A proposed start date should not look like a confirmed employee arrival. Reconcile role counts and cost assumptions across slides. A proposed role should not become an advertised opening or approved budget merely through its position on the timeline.
From the Prompt
Distinguish approved headcount from proposed roles.
Make It Your Own
Review the hiring plan deck against this requirement: Distinguish approved headcount from proposed roles. Reconcile role counts and cost assumptions across slides. A proposed role should not become an advertised opening or approved budget merely through its position on the timeline. Preserve approved content and revise only the parts that fail this check.
Review Your Hiring Plan Deck Result
A generated image cannot validate a complete deck or its evidence. Test every slide, keyboard navigation, print layout and any exported file separately.
- Reconcile role counts and cost assumptions across slides. A proposed role should not become an advertised opening or approved budget merely through its position on the timeline.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current hiring plan deck. Reconcile role counts and cost assumptions across slides. A proposed role should not become an advertised opening or approved budget merely through its position on the timeline. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
