TWO COLUMN / THE RELAY TEMPLATE
A clean horizontal header spans a main work column and a right-side supporting column. Relay is built for experience that combines hands-on delivery with coordination.
Create and export your resume with CVura.Product Designer
Portland, OR · jordan@example.com
Product designer making complex workflows feel simple. Experienced in research, accessible interfaces, and working closely with engineering teams.
Fieldwork Studio
Common Ground
Product design · User research · Prototyping · Figma · Accessibility · Design systems
BFA, Communication Design · Pacific Northwest College of Art · 2021
THE DESIGN THINKING
The header establishes one identity before the body divides into two reading areas. Supporting facts remain visible without interrupting the chronology.
WHEN TO CHOOSE RELAY
Relay connects a unified header with a two-column body. The header provides one starting point while the columns separate work evidence from concise supporting details. Keep the main explanation in the experience area and avoid turning the secondary column into another essay. Test the actual contact line, longest employer name and education entry before committing to the layout. After export, inspect both the visual page and the copied text so the division remains useful outside the browser preview.
Use Relay when the contribution lies in making an interface work: reservations and housekeeping, purchasing and receiving, or support and implementation. Name the teams and the unresolved issue. A reader should understand the handoff without needing to know your former employer’s internal terminology or reporting structure.
A role may combine completing tasks with preparing the next stage. The main column can show both when the examples have different purposes. Explain the practical work and the coordination separately enough that the reader does not confuse your own delivery with the output of a whole operation.
Systems and short factual qualifications can remain visible on the right while the chronology carries the story. Keep those entries brief. If a system requires a long explanation to establish your capability, place that explanation in the relevant experience rather than compressing it into the supporting area.
A FICTIONAL WORKED EXAMPLE
In this fictional scenario, Mei coordinates group arrivals at a hotel. Her draft says she liaised with all departments but gives no example. Relay lets her explain a specific handover between reservations, front desk, and housekeeping. She identifies what information was confirmed and how outstanding room-readiness questions were assigned, showing coordination without claiming that every department reported to her.
Liaised with departments to ensure smooth hotel operations.
Prepared group-arrival handovers with confirmed booking details, room-readiness questions, and named follow-up owners across reservations, front desk, and housekeeping.
The revision replaces a broad collaboration claim with the information that made the handover useful. It explains how the information was organized and what the receiving colleague could do next. Relay’s main column can show the coordination while the supporting facts identify relevant systems. Mei’s next bullet can explain a different responsibility, such as handling schedule changes, rather than repeating liaised with teams in another form.
FROM SAMPLE TO YOUR RESUME
Identify the source of the information, the checks you performed, and the person who needed the next action. Choose the part that demonstrates your contribution. This note helps prevent a coordination bullet from implying that you controlled every decision on both sides of the interface.
Separate each role clearly and keep its dates close. Within the role, use examples that show distinct dependencies or responsibilities. Relay’s two areas should not make the work history feel fragmented; the main column still needs a straightforward account of what you did and when.
After reviewing the visual preview, check the order in which text can be selected or extracted. Supporting details should not interrupt a role or attach to the wrong date. If the application asks for a simpler file, use the same evidence in a single-column layout rather than relying on visual appearance alone.
TRY THIS WEBSITE LAYOUT
Free browser template. No account. Example details are fictional.
THE FINAL EDIT
Contact between teams is an activity, not a complete explanation of value. Name the information clarified, dependency resolved, or follow-up established. A concrete handoff makes coordination understandable and gives you a better basis for discussing the work at interview.
Your handover may support a delivery or service outcome without causing every part of it. Describe the contribution and shared result accurately. Avoid presenting another team’s technical work, room preparation, or shipment completion as your personal execution merely because you coordinated the information.
GOOD QUESTIONS
Yes, particularly where shipment updates, supplier confirmations, or receiving information pass between teams. Explain the dates and responsibilities clearly. The layout can organize the evidence, but the wording must distinguish confirmed milestones from estimates.
Include a system in a bullet when it explains the work. Otherwise a concise supporting list may be enough. Repeating the same tool names under every position can crowd out the distinct coordination problems you handled.
The browser layout has a set structure. Write substantive explanations within the existing experience field and keep skills and education concise. If you need a different section arrangement, use the saved text in a document workflow that supports it.
PUT THE IDEA TO WORK
Fictional practice case: Pavan coordinates dispatch for the fictional Birch Office Systems. Deliveries depend on installation crews confirming access and timing. His Relay resume lists warehouse and installation tasks separately, so the reader misses the coordination work that connects them.
Describe checking installation readiness before confirming a dispatch date. Identify the information Pavan needed from the crew and what he updated for the warehouse. This gives the main work column a connected operational story.
Keep responsibility for the schedule separate from physically delivering or installing the equipment. A sentence can show useful ownership of the handoff without implying that Pavan performed every stage or controlled all delays.
Use Relay's right column for concise systems knowledge and education. Leave explanations of dependencies in the main narrative. A sidebar list of team names would consume space without showing how the teams relied on his work.
Trace one item from readiness confirmation to dispatch. The resume should identify Pavan's contribution and the point at which another team took over. Check that dates remain attached to their roles when copying text from the exported file.
Make operational experience specificA USEFUL NEXT READ
Explore a front desk resume example with guest reception and reservation systems evidence, annotated bullets and a fictional sample.
Explore the exampleExplore a supply chain resume example with shipment coordination and inventory analysis evidence, annotated bullets and a fictional sample.
Explore the exampleCOMPARE THE TRADEOFFS
Made for a varied background
Put the important part in focus
YOUR NEXT STEP
Take the writing ideas from this example into your next application. Choose a layout in CVura, prepare your resume and export the format you need.
