Working as a Comic Production Team

Hero art: Glacias: story by Yaruno; art by Nawa. Initial formatting and lettering by Rahpak; art direction and subsequent formatting and lettering revisions by Sierra Ashevaili Rottman, head of the publishing formatting department. Production examples supplied by Otherworlds Inc.; editorial banner design by Otherworlds Inc.

The Otherworlds Workshop · Making Comics · Guide 8

Guide 8 of 10 · View the complete reading order ↓

The colorist has finished the page. The letterer is waiting for a script correction. The writer believes the correction was settled in a message yesterday. Meanwhile, the artist has uploaded another version of the drawing.

To move forward, the team needs one reliable answer: which versions are approved, and what is the next person cleared to do?

A production process should make that answer easy to find. It should also leave artists room to solve creative problems, give reviewers enough time to respond, and make additional work visible before someone is expected to absorb it.

The earlier guides taught the craft decisions within each stage. Guide 5 introduced useful review notes and stage approvals; Guide 7 applied corrections to lettering. Here we will connect those practices and work through what happens when a handoff fails or a settled decision changes.

1. Agree on the working relationship before the first batch

Start with the actual work being offered. “Comic artist” might mean layouts and finished line art on one project, or drawing, color, and lettering on another. Reference sheets, cover art, promotional crops, and alternate formats can each become substantial assignments. Name the deliverables.

When looking for a collaborator, review sequential pages that resemble the job: recurring characters, the kind of acting or action involved, and comparable finishing demands. Ask about availability and preferred workflow. A portfolio can show visual skill; a conversation about the assignment reveals whether your expectations fit.

Jim Zub’s advice on finding an artist emphasizes clear communication and considering the project from the collaborator’s side. That remains a useful starting point, even though the recruitment websites in his 2012 article are a historical snapshot. [1]

Put the practical agreement in writing: scope, compensation and payment milestones, review rounds, delivery dates, expected files, credit, and what happens if the assignment changes or stops. Resolve ownership and permitted uses through the project’s actual agreement. A production checklist records those decisions; it does not establish rights by itself.

For a shared venture, be equally explicit about which work is unpaid, which costs are shared, and who can commit the team to more work. Keep hoped-for revenue separate from the funds committed to the assignment. If you need a custom trial page, agree on its fee and permitted use before requesting it.

2. Separate making the work from deciding it is ready

For each deliverable, identify the person making it, the people whose input is needed, and the person or agreed group who can authorize the next step. Those responsibilities may overlap. What matters is that the team knows how a decision will be reached.

Do not assume the writer approves everything, the editor can authorize extra spending, or the person uploading a file has approved its contents. Establish those boundaries together.

These are sample responsibilities, not a required staffing structure. A two-person team might share story decisions and appoint one person to record the outcome. If shared approval reaches a deadlock, use an agreed tie-breaking method, revise the proposal, or hold the affected work. Sending contradictory instructions to the artist does not resolve the disagreement.

For a solo creator, these can be different passes through the same page: make it, review it against the brief, then prepare the next stage. A two-person team can keep one shared record rather than creating a separate document for every role.

Production roles also vary with the method. Jim Zub’s published Wayward example uses scanned pencils followed by digital line preparation, rather than a separate conventional inking pass. Build your assignments around your chosen method. [2]

3. Test the handoff from the receiving end

Before moving a large batch, pass one representative page through the actual people and applications involved. Guide 1’s test page helps estimate the project; this test answers a narrower question: can the next contributor use what arrives?

Ask the recipient to open the package, identify the approved version, find the relevant references, and perform one small operation required for their work. A colorist might test whether the supplied line art behaves as expected. A letterer might check whether dialogue can be copied accurately and whether the art matches the script. Agree on the time for this check.

Blambot publishes specific art and script requirements for its own lettering service. Todd Klein likewise recommends accessible script files and checking whether the letterer wants placement notes. These are useful examples of recipient-led requirements; they are not a universal software prescription. [3] [4]

A receipt confirms access. Creative approval confirms the work meets the agreed purpose. Record both when necessary. If the package is unusable, describe the missing item and assign the repair; do not leave the recipient silently reconstructing it.

4. Track the next action, including the reviewer’s

Use the review states introduced in Guide 1: work in progress, awaiting review, revision requested, and approved. Give each of those states an owner and a next action. “Awaiting review” should identify the reviewer and the agreed response date. “Blocked” should identify what is missing and who can resolve it.

Track a page and stage together when several passes are active. A page may have approved line art while color is still in progress. One green “done” label can hide that difference.

These times are invented for the exercise. A real board should name the people and use calendar dates as well as a time zone. The artist and reviewer agree to their respective checkpoints before the work is scheduled.

Reserve reviewer time when you reserve artist time. In this example, if the Wednesday decision is late, the coordinator contacts the reviewer or agreed backup. The artist can take up an independent task while the coordinator confirms a new review time. Finished drawing that depends on R01 stays on hold. Silence does not change its approval status.

Zub describes prioritizing replies when another person cannot proceed without them, and communicating schedule problems early. The board makes those dependencies visible to the whole team. [5]

Before starting more work, inspect what is waiting. Five additional finished pages will not solve a missing design decision affecting all five. At the same time, hold only the work that depends on that decision. An unrelated prop study may still be able to move forward.

5. Give each review a question and a decision

Use the small work-in-progress checkpoints from Guide 5. State what is ready to assess, what remains rough, and which decision will allow work to continue.

For The Parcel, “Does panel 4 preserve the concealed contents?” is a usable question at the rough stage. A discussion of finished wood texture can wait. This keeps the review focused without asking the artist to polish an entire page merely to demonstrate progress.

Use the precise feedback method from Guide 5, then add a way to resolve and close the notes:

1. Collect: reviewers comment on the same identified proof before the agreed cutoff.
2. Resolve: the responsible approver reconciles conflicts and separates required fixes, questions, and optional suggestions.
3. Assign: each required change gets an owner; uncertain effort is discussed before a new date is promised.
4. Verify: someone checks the returned version against the note’s intended result.

If one reviewer wants the creature visible early and another wants to preserve the surprise, the artist should not have to choose which authority to obey. Return to the agreed story objective and record the decision. Leave execution open where possible: preserving a reveal does not require dictating every contour.

Ask for clarification when a note’s purpose is unclear. An artist can propose another solution that preserves the agreed result; the reviewer can explain why a constraint matters. Record which solution was accepted before the next pass.

Record decisions from calls in the shared production record. Link to useful discussion, but give collaborators the resolved instruction without requiring them to reconstruct a long conversation. Choose a regular channel, reasonable response windows, and an urgent-contact method together; constant availability is not a production plan.

6. Follow one revision through to closure

Our two-page teaching comic, The Parcel, continues from Guide 2. A courier cuts a parcel’s seal on page 1. The lid remains down until page 2, where a small creature is revealed. The courier then offers water and settles beside it.

Imagine a rough accidentally shows the creature’s ears in page 1, panel 4. The following record is an invented production exercise, not a record of an Otherworlds commission.

The artist reporting a fix and the reviewer accepting it are separate events. That distinction prevents a note from disappearing merely because a new file arrived.

When the request changes the assignment

Now imagine the team intentionally decides to reveal the creature on page 1 after approving the original sequence. That is a new direction. Before anyone redraws, identify the affected script beats, page compositions, references, art, and lettering. Ask each affected contributor what the change requires.

The authorized decision-maker can accept the extra work and revised dates, reduce another part of the assignment by agreement, or keep the approved sequence. Record the chosen scope before work resumes. If the team changes the story, issue a revised script and identify which earlier approvals are superseded.

Some problems are shared: an ambiguous brief, a missed review, or contradictory references may have caused the mismatch. Resolve responsibility through the working agreement and the evidence. Calling something a “small correction” does not make the labor small.

Klein specifically warns against treating the first lettered proof as an opportunity for major script rewriting. His example shows how a late upstream decision creates extra work for a downstream collaborator. [4]

Adapt the checkpoint to the way you make the comic

If you work from a full script, check the rough against its current story requirements. If you deliberately develop dialogue after the drawing, reserve a copy-review checkpoint before lettering and name who reconciles the text with what the artist has drawn. The team still needs a settled input for each handoff, even when the creative order changes.

For a vertical episode, use stable scene and panel identifiers and review enough surrounding sequence to judge the transition. A crop may be sufficient to check a costume fix; it cannot establish whether a reveal lands at the right point in the scroll. Choose the review unit for the decision being made.

From our studio: turn a visual comparison into a revision brief

These two Glacias layouts show why a revision needs a stated purpose. The internal studio guide prepared by Sierra Ashevaili Rottman, Otherworlds’ art director and head of the publishing formatting department, identifies layout A as the approach to revise and layout B as the preferred direction for this scene: keep the larger illustration continuous behind smaller panels, and clarify the order of the exchange near the bottom. That is a scene-specific decision, not a rule that every comic should use overlapping panels.

Open either image for a larger view. Glacias: story by Yaruno; art by Nawa. Production examples supplied by Otherworlds Inc., reproduced from screenshots with the application interface cropped away. Series credits: Team Glacias. Initial formatting and lettering by Rahpak. Sierra Ashevaili Rottman leads the publishing formatting department as art director, authored the studio guide, and takes over after Rahpak’s initial pass for further formatting and lettering revisions.

Illustrative revision brief · Based on the supplied comparison

Purpose: preserve the scale of the dragon scene while making the dialogue sequence unambiguous.
Assigned work: the layout contributor restores the continuous background and repositions the inset panels; the person handling lettering checks the affected balloons. One person may hold both responsibilities.
Keep: the approved dialogue and story beats. A layout revision does not authorize a script rewrite.
Return: a versioned editable page, a reading proof, and a short list of the panels and balloons moved. Flag missing source artwork before attempting to reconstruct it.

The reviewer can then check three observable results:

1. The background remains continuous behind the insets, without accidental gaps or covered focal details.
2. The human’s question about helping the dragon comes before the dragon’s answer about growing stronger.
3. Every line in the approved copy is present, with clear speaker attribution and readable lettering at the intended reading size.

Record each result against the returned version. If the composition passes but the lettering still needs work, approve the layout for the next pass and keep the lettering note open. The sample brief above is written for this lesson; it is not a transcript of the studio’s correspondence or evidence that either screenshot received final publication approval.

7. Keep the approved files recoverable

Choose one shared place where the team can find current approved materials. Use stable page identifiers and versioned filenames, such as Parcel_p001_rough_v004. Put approval in the production record: which file, who approved it, when, and for what next step.

Keep editable work, review proofs, and delivery exports distinguishable. Retain previous approved versions rather than overwriting the only copy. If a new pass fails, the team should be able to recover the earlier decision without hunting through chat attachments.

For example, the approved record may point to script v1.0, page 1 rough v04, and page 2 rough v02. Those numbers do not need to match; their relationship needs to be clear. When the art changes after lettering begins, tell the letterer which panels changed and whether the canvas or panel boundaries moved.

Comic Book School’s 2021 anthology instructions specified naming and designated submission folders so editors could find revised material. That historical example illustrates the value of a predictable delivery location; its export specifications should not be treated as requirements for your project. [6]

Include required linked assets and notes about fonts or other licensed resources. Confirm what can be transferred and what the next person must obtain separately. Keep an independent backup of agreed project materials and test opening a restored file. A second filename in the same working folder is not a recovery plan.

Sierra’s internal studio guide also uses editable panel borders and balloon outlines to reduce repeated manual work. Agree which elements must remain independently adjustable in the handoff, then ask the recipient to make a small test change. A flattened reading proof can show the result; it cannot establish that the working file is usable.

Specify what an approval permits

“Approved for finished drawing” settles the rough’s decisions. It does not approve the later color pass, lettering, export, or publication. When the finished page is assembled, name who checks that the latest approved art and copy have been used together, and who can authorize delivery.

If only a word is corrected, check the resulting lettering and any layout it affects; you do not need to reopen an unrelated character-design decision. If the story action changes, identify every dependent approval that needs another look.

Guide 9 covers destination-specific exports and proofs. Here, establish who prepares them, who checks them, and which approved source files they must use. Keep the authority to publish explicit as well.

8. Plan for pauses, departures, and accurate credit

People become unavailable. Agree early on how to report a delay, whom to contact if a review stalls, and how the project will pause if no workable replacement exists. A delayed reply is a reason to follow the agreed contact process, not permission to invent a new availability commitment for someone.

When a contributor leaves, make a handover record: completed work, unfinished work, current files, unresolved decisions, amounts or milestones still to reconcile, and permitted next uses under the agreement. Confirm that any replacement has the access and information needed. Do not assume that receiving an image automatically includes every editable source file or permission to reassign it.

Maintain a credit roster while the work is happening. Record each contributor’s preferred name, actual contribution, relevant pages or assets, agreed credit wording, and where it will appear. Include work that can disappear into a broad “art” label, such as flats, background assistance, lettering, or production design, when applicable.

Send the proposed credits to contributors to confirm spelling and contribution descriptions before publication. Resolve uncertainty instead of guessing a stage-specific role from a finished image. Track cover, interior, and promotional artwork separately if their contributors differ.

Workshop: run a handoff without explaining it aloud

Choose one page from your comic or use The Parcel. Begin with the page, stage, current files, person responsible, next action, review question, and due date. Add the remaining fields as the assignment requires them; keep project-wide agreements and credits linked rather than copying them onto every page. Send the record with the files to a collaborator. If you work alone, return to it in a later session as the person responsible for the next stage.

PROJECT / PAGE / STAGE:
DELIVERABLE AND PURPOSE:
MAKER / RECEIVING CONTRIBUTOR:
REVIEWER / FINAL DECISION-MAKER:
SCOPE OR BUDGET DECISION-MAKER:

CURRENT FILES AND EXACT VERSIONS:
APPROVED REFERENCES / SCRIPT:
STATE / NEXT ACTION / PERSON RESPONSIBLE:
SUBMISSION DATE / REVIEW DATE / TIME ZONE:
DEPENDENCY OR BLOCKER:

REVIEW QUESTION:
REQUIRED CHANGES: note ID / location / result needed / owner
CHANGE IMPACT: affected stages / effort / agreed timing and fee
RETURNED VERSION / VERIFICATION RESULT:
APPROVAL: version / person / date / next stage authorized

HANDOFF: included files / missing items / recipient confirmation
RECOVERY: approved copy / backup location / access owner
CREDITS: preferred name / contribution / asset / placement / confirmed
PAUSE OR DEPARTURE: contact / handover / unresolved commitments

Ask the recipient to identify the current version, the next action, the decision-maker, and anything preventing work. Then introduce one hypothetical change: an altered line of dialogue, a moved reveal, or a missing editable file. Record the affected tasks, agree on the response, and carry one note through verification.

Finish by asking what information was hard to find. Improve the record before adding more fields. A small team should be able to maintain it during a busy week.

Common failures and the smallest useful repair

Completion standard

• The next contributor can open the required files and identify the approved versions.
• Every active task has a person responsible, a next action, and an agreed checkpoint.
• Review authority and permission to change scope are clear.
• Required revisions remain visible until their results are verified.
• A late change produces an explicit impact decision and updated approvals.
• The team can distinguish approval for another work stage from authority to deliver or publish.
• Approved work can be recovered, and credits can be traced to actual contributions.

When another person can pick up the record and continue without reconstructing yesterday’s conversation, the process is doing useful work.

Series continuity and resource review: October 28, 2026. Publication requirements remain subject to the linked service’s current instructions.

Continue Exploring

Strengthen the plan behind the assignment, then revisit how a page moves from rough decisions to finished art.

GUIDE 1Planning a Comic You Can FinishBy The Otherworlds DeskDefine the reader, format, scope, team, and a plan grounded in actual work.Read the article → GUIDE 5From Rough Layouts to Finished Comic ArtBy The Otherworlds DeskSee how a Lunora page develops through rough layout, line art, color, and useful review.Read the article →