DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Forge Film Room

Stop Copy Pasting, Start Relating in Slate

Follow one Related Records pattern through tour-guide follow-up, school visits and event logistics, with practical checks for joins, content blocks and missing context.

A camera faces a wooden lectern while diagram cards lie across a rehearsal table.
Follow the relationship before writing the paragraph.

THE IDEA, IN A MINUTE

Make the relationship part of the message.

This Forge Film Room rehearsal follows three communication projects through the same sequence: store a relationship, retrieve its context, simplify the decision and render a useful message. The design becomes reusable when the missing-data branches are as deliberate as the happy path.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Begin with the connection that changes the message

A tour follow-up should know which guide the visitor met. A school-visit message should reach the contact who participated. An event reminder should carry the directions for the activity someone selected. Each depends on a relationship that a copied template can easily lose.

Stop Copy Pasting, Start Relating takes those three projects into the Forge Film Room. The rehearsal builds on the RARE live demonstration, tracing a common architecture: Related Records hold context, Configurable Joins retrieve it, exports simplify decisions, and Liquid markup or content blocks assemble the message.

Choose the structure for the actual problem. A stable detail that belongs directly to an event may need only a field. A genuinely different audience or schedule may deserve a separate template. Related Records become useful when another person, event or reusable detail changes what the message should say.

In the recording · 04:43 ↗

Prove which row you found

The tour-guide example begins with attendance and a form response. The path moves to the umbrella event, then to the related event that carries the guide, then to the guide record. Filtering the related-record join to the intended dataset matters when the event also holds parking or activity details.

Finding that record is only the first step. The build adds field-value joins for the guide information used in the message, such as major, activities and advice. Export those raw values before building comparisons. Seeing the expected guide name and fields is a better starting point than debugging a polished paragraph around the wrong person.

Name each join for the decision it supports. A clear name helps a colleague distinguish the record that identifies the guide from the field that supplies a piece of the guide’s story.

In the recording · 12:37 ↗

Make the writing decision visible

The rehearsal recommends a decision table before Liquid markup. Put the available signal, the intended branch and the missing-data response beside one another. A shared major might select one paragraph; a different major might select a broader academic connection; a weak match might use the guide’s general advice.

Comparison exports make those choices manageable. Use a consistent convention for yes and no across the instance, then keep the email logic simple. Coalesce can choose the first available talking point, but the order expresses an editorial priority. Review that priority and what happens when every candidate is blank.

Read the assembled messages, not just the individual blocks. Two good paragraphs can still repeat an idea or leave an awkward transition when an optional section disappears. A follow-up sequence should add useful context instead of retelling the same match in every email.

In the recording · 20:53 ↗

Match the recipient and the voice

The school-visit pattern uses a standalone Deliver. Its recipient is the contact associated with the visit, and its opening comes from the counselor tied to that event. Those are separate relationships to verify.

The safeguards check that the contact and visit point to the same school, the visit is recent, the contact is active and an email address exists. That prevents an old event or a contact attached to several organizations from becoming an unintended send.

A predictable content-block naming convention selects the counselor’s reusable greeting. The use case and staff identifier form the code, with a deliberate fallback code when the specific voice is unavailable. Event notes can add visit-specific text; hide the optional section and its spacing when that note is blank.

In the recording · 25:52 ↗

Let logistics change without rewriting the template

For campus visits, the umbrella registration owns the communication while a selected related event can own parking, check-in or special instructions. A detail record supplies a code; the corresponding content block supplies the directions.

Check the selected event, template and date together. Two activities on the same day can both be plausible matches, so date alone is insufficient. Sorting and filtering must recover the activity relevant to that registration.

The same context can control whether a message sends at all. A particular activity might need a waiver, or an event detail might trigger a parking update. Keep the eligibility rule distinct from the text selection so both can be tested.

In the recording · 33:16 ↗

Design the missing branch

A fallback is a design decision. General advice may work when a guide has no matching interest, while a missing guide could require suppression. Missing critical logistics should not become confident but unverified directions.

The rehearsal places fallback codes in exports so a shared content-block collection can support several uses. It also calls for exposing missing setup to staff. Record who maintains each relationship, code and reusable paragraph so an apparently complete template does not conceal an unfinished setup.

In the recording · 39:33 ↗

Debug in the order the message is built

Confirm the relationship and recipient first. Inspect the retrieved row, export its raw values, test the flags, then render the message. Include missing fields, multiple matching records and expired events in the review.

Start with one recurring message and one clean relationship path. Once its selection rules and fallback behavior are understandable, reuse that pattern for the next project.

In the recording · 41:08 ↗

03 / A SMALL EXPERIMENT

Trace a message through three tests

Choose one recurring communication. For each case, identify the relationship, the selected row and the response the recipient should see.

Two events, one day

A fictional visitor has an umbrella registration and two related activities on the same date. Only one activity owns the needed check-in instructions. Is matching the date enough?

Compare your reasoning

No. Identify the registered activity and intended template as well as the date. Inspect the retrieved event and detail record before rendering its content block.

Revisit this moment · 36:20 ↗
A guide, but no shared topic

The correct guide is attached, but the fields used for shared-major and activity paragraphs are blank. What should the message do?

Compare your reasoning

Keep the confirmed relationship separate from missing talking points. Use a reviewed general guide note when appropriate, or suppress the message if required content is absent. Render the result and inspect transitions.

Revisit this moment · 20:53 ↗
A contact at two schools

A fictional school contact appears under two organizations, and an old visit is also eligible in the query. Which checks should happen before choosing a greeting?

Compare your reasoning

Match the contact to the visit’s school, constrain the intended recent visit, and confirm active contact status and email. Then verify the event counselor and content-block code.

Revisit this moment · 27:37 ↗
Build a test card to take with you

Notes stay in this tab. Reloading clears them.

04 / INSIDE THE STUDIO

The seams are part
of the story.

Behind the episode

During the comparison example, David spots a misleading label and clarifies that the comparison is between the tour guide’s major and the attendee’s major. The rehearsal makes a useful review point visible: a flag needs a clear meaning before it becomes a writing rule.

Revisit the studio moment · 15:43 ↗

Stop Copy Pasting, Start Relating

The closing song returns to the episode’s sequence: relationship, retrieval, decision and message. This link opens the music in the full recording.

Hear the song in the episode

Art from the workshop

Forge Film Room artwork: a rehearsal space for tracing how a presentation and its underlying system work.

Open the artwork ↗

KEEP THE IDEA MOVING

Where would you take it next?