Standardize the backdrop, framing and lighting of team headshots, not the people. Use a separate authorized reference for each colleague and let each person approve their own portrait. A visual system should make a directory coherent without replacing individual faces with a generic corporate look.
Define the shared rules before generating
Start with where the images will appear: a directory, a speaker page or a proposal document. Choose one framing rule that works there. Decide whether backgrounds should be plain or gently textured and whether the light comes from the same side in every portrait. Keep these decisions separate from personal appearance.
An original working brief might specify an upper-torso crop, muted slate background and soft light from camera left. It should not require identical jawlines, smiles, hairstyles or skin tones. Avoid occupational props that could imply credentials or roles the person does not hold.
Keep a compact approval sheet
| Shared decision | Individual decision | Review owner |
|---|---|---|
| Background color and crop | Facial features and hair | Person pictured |
| General lighting direction | Glasses and visible marks | Person pictured |
| Export shape and file naming | Clothing suitability | Person and project lead |
| Directory layout | Public-use permission | Organization and person |
This is an external planning sheet, not a claim that Imagild has bulk approval or organizational permission-management features. Save it with your project notes and process photographs through the currently supported upload workflow.
Test two visibly different references first
Choose consenting colleagues with different hair, clothing or glasses. Apply the same visual brief separately. Compare the results as a pair: does the lighting feel related, and do both people still look like themselves? A brief that works for one person may flatten another person's face or lose the edge of dark hair.
Adjust the shared rules before spending on the rest of the set. Do not fix a problem by requesting that everyone resemble the most successful result. An identity reference and a style reference are different things.
Example instruction with a clear boundary
Use only this uploaded person as the identity reference. Keep their facial proportions, hairstyle, complexion and glasses. Apply our shared framing: upper torso, relaxed shoulders, soft side light and a quiet slate studio background. Keep their individual expression natural. Do not copy another colleague's facial shape or invent a company badge.
Keep a record of which source belongs to which person. Review names separately from image generation; place directory text in an editable layout rather than hoping the model writes it correctly.
Learn from a specialist without borrowing its promises
Aragon's official headshot walkthrough separates input preparation and professional use questions. We use that useful workflow structure here, but do not transfer its package sizes, turnaround or marketing claims to Imagild. No measured team-production benchmark is reported in this guide.
Questions before publishing
Is one colleague's approval enough for the whole team?
No. Have every pictured person review their own appearance and intended use. A project manager's style approval does not replace personal consent.
Can I generate the whole team in one composite?
For directory portraits, individual files are easier to inspect and correct. Group generation adds identity and spacing risks. This guide does not promise a batch feature.
Open the Skill Market for individual portraits. Review the displayed point cost and approve a small pilot before expanding the project.
Filled decision record: individual approval
This is a constructed review exercise, not a reported generation, software test or audience study. Its purpose is to make the acceptance decision reproducible for the next reviewer.
| Review item | Hypothetical evidence or requirement | Decision and next action |
|---|---|---|
| Failure observed in the candidate | One person approves the shared background but another face is wrong. | Hold the affected candidate; name this failure before changing anything else. |
| Protected result | Separate style approval from each subject likeness approval. | Compare against the approved source and intended sequence, not the attractiveness of an isolated frame. |
| Bounded next action | Hold that individual file while retaining accepted portraits. | Make this change first, then inspect the same acceptance criterion again. |
Keep the actual source version and the rejected candidate distinguishable. A planning correction does not prove a later output follows it, and a successful individual frame does not approve the complete clip or sequence. Record which requirement is still unresolved rather than silently labeling the whole deliverable final.
For the next handoff, include the approved requirement, the evidence that supports it and this specific unresolved action. This record belongs to the editorial workflow; it is not a claim that Imagild enforces these constraints automatically.
Documentation and production boundary
Runway: Creating with Gen-4 Image References is a vendor-specific workflow reference. The decision record above is our original manual review method. Use Imagild's current film planning workspace for supported planning steps and inspect the current interface before choosing an input or generation mode. Do not infer an available control from another vendor's documentation.