REO teams should divide work by responsibility and authority. Runners document the property in the field. Administrators and virtual assistants organize assignments, data, photos, and deadlines. Agents select comparables, make adjustments, and develop valuation conclusions. Brokers resolve material exceptions and approve the finished work.

The titles can vary, and one person may perform several roles. The important control is that each task has an owner, each handoff has a defined standard, and no one makes decisions beyond their qualifications, authorization, or the client’s requirements.

Software should make those boundaries visible. It should not flatten the entire brokerage into one shared login, one undifferentiated task list, or one person trying to remember every assignment status.

Start with responsibilities, not job titles

“Administrator,” “VA,” “runner,” and even “agent” can mean different things across REO brokerages.

Define each role by:

• the work it performs;

• the information it needs;

• the decisions it can make;

• the systems it may access;

• the output it must produce;

• the person who reviews that output; and

• the conditions that require escalation.

This is more useful than assuming every virtual assistant or field runner works the same way.

State licensing rules, client agreements, MLS terms, portal permissions, employment arrangements, and brokerage policy may affect who can perform a specific task. The brokerage should set its role boundaries accordingly.

The five operating roles

A controlled REO workflow commonly includes five operating roles.

One person can occupy more than one row. The work should still pass through the same controls.

What the runner should own

The runner or field representative owns current, accurate field documentation.

Typical responsibilities include:

• confirming the property address;

• following access and inspection instructions;

• documenting occupancy indicators;

• capturing required exterior and interior photos;

• photographing condition and damage;

• recording observable property characteristics;

• noting access, utility, safety, or preservation concerns;

• completing the assigned inspection checklist; and

• submitting the field record by the required time.

The runner should not be expected to infer the valuation from the inspection.

A useful field report describes what was observed. It distinguishes a visible condition from a conclusion that requires further analysis. For example, “water staining visible on the ceiling” is an observation. The cause, repair scope, and valuation effect may require review by other qualified people.

Runner handoff standard

Before the field stage is marked complete, confirm:

• the correct property was visited;

• required views are present;

• photos are clear and assigned to the correct asset;

• captions or field labels are accurate;

• condition issues are documented;

• unanswered checklist items are identified;

• access limitations are explained; and

• urgent concerns are escalated.

AI-generated captions can accelerate photo organization. In REOEngine internal testing across more than 1,000 property photos, more than 95% received a correct caption. A person should still review the caption, especially when the photo shows damage or an ambiguous area.

What the administrator should own

The administrator keeps assignments organized and moving.

Typical responsibilities include:

• receiving or creating the assignment record;

• confirming the client, asset, report type, and due date;

• organizing client instructions;

• assigning field and preparation tasks;

• scheduling access or inspections;

• collecting documents;

• tracking missing inputs;

• maintaining status and priority;

• routing completed work to the next role;

• recording communications; and

• confirming that the final submission status is captured.

The administrator’s value is not limited to data entry. A strong administrator protects the workflow from forgotten tasks and incomplete handoffs.

Administrator handoff standard

The valuation should not begin until the file contains:

• the correct assignment information;

• current client instructions;

• available subject-property records;

• inspection results or a documented exception;

• required photos;

• MLS or source documents needed for preparation;

• the requested value definitions; and

• identified due dates and escalation needs.

An administrator can confirm that the required inputs are present. The agent determines whether the evidence is professionally sufficient.

What the virtual assistant should own

A virtual assistant can provide adaptable remote capacity for defined preparation and submission tasks.

Depending on authorization, training, and applicable rules, a VA may:

• prepare the assignment file;

• import or organize MLS reports;

• verify that expected fields were captured;

• separate active and sold candidates;

• organize a candidate comparable pool;

• format property and repair information;

• organize photos and review draft captions;

• prepare routine report sections;

• run checklist-based completeness review;

• track due dates;

• identify exceptions for escalation;

• prepare the approved handoff; and

• manually enter an approved report into a client portal when authorized.

The VA should work from documented procedures and know when to stop.

An unexpected property type, conflicting living-area source, out-of-boundary comparable, unclear repair item, or portal discrepancy should not be resolved by guessing. It should be routed to the person responsible for the decision.

VA handoff standard

Before routing the file to the agent, confirm:

• imported information matches the source documents;

• active and sold candidates are organized correctly;

• potential boundary exceptions are visible;

• missing subject information is identified;

• photos and repairs are connected to the property;

• routine drafts are clearly marked for review;

• unresolved questions are collected rather than hidden; and

• no final valuation decision has been made on the agent’s behalf.

Before portal entry, the VA should receive one broker-approved record and explicit authority to enter it.

What the agent should own

The agent owns the market and valuation analysis.

Typical responsibilities include:

• confirming the subject’s competitive market area;

• reviewing candidate properties;

• selecting the final active and sold comparables;

• handling non-conforming-property tradeoffs;

• determining adjustments;

• analyzing condition and repairs;

• reconciling the requested values;

• reviewing market conditions;

• editing subject and valuation narratives;

• resolving material preparation questions; and

• completing the valuation for broker review.

Software and staff can prepare the evidence. The agent decides how that evidence should be used.

Agent handoff standard

Before routing the BPO for approval, confirm:

• the final comparable set is professionally supportable;

• meaningful assignment exceptions are explained;

• adjustment directions and amounts have been reviewed;

• requested values follow from the evidence;

• repairs, condition, photos, and values agree;

• market comments are current;

• AI-generated or reused language has been edited;

• warnings and missing information are resolved; and

• the file is ready for a complete broker review.

The broker should receive a finished analysis, not a collection of unresolved production tasks.

What the broker should own

The broker owns the control environment and final professional accountability.

Typical responsibilities include:

• setting brokerage procedures;

• defining role and permission boundaries;

• approving client-specific workflows;

• reviewing material exceptions;

• resolving difficult comparable or valuation issues;

• confirming quality-control standards;

• reviewing the final opinion of value;

• approving narratives and conclusions;

• authorizing the final handoff; and

• overseeing corrections or post-approval changes.

The depth of broker review may vary with the assignment, team structure, licensing, client requirements, and staff experience. The workflow should make the consequential decisions easy to identify.

Broker approval standard

Approval should confirm:

• the assignment requirements were followed;

• comparable selection is defensible;

• adjustments and value reconciliation are supportable;

• material condition and repair issues are handled coherently;

• narratives agree with the evidence;

• required review findings are resolved;

• one final version is controlled; and

• portal-entry personnel have a complete approved handoff.

Approval should be a deliberate workflow state, not an assumption that occurs when someone starts entering the portal.

How the handoffs should work

A well-designed REO workflow moves work forward only when the next role has what it needs.

1. Assignment intake to field work

The runner receives:

• the correct property;

• inspection type;

• access instructions;

• due date;

• required checklist; and

• photo requirements.

The runner returns a complete field record or a documented access exception.

2. Field work to file preparation

The administrator or VA receives:

• inspection observations;

• photos;

• captions or labels;

• condition issues;

• access notes; and

• identified follow-up needs.

The preparation role attaches the evidence to the correct asset and identifies missing items.

3. Preparation to agent analysis

The agent receives:

• a complete subject record;

• source documents;

• organized candidate comparables;

• visible assignment boundaries;

• repair and photo information;

• routine drafts; and

• a consolidated list of exceptions.

The agent performs the market analysis and valuation decisions.

4. Agent analysis to broker review

The broker receives:

• the selected comparable set;

• adjustment grid;

• requested value conclusions;

• condition and repair analysis;

• narratives and market comments;

• quality-control results; and

• clearly explained exceptions.

The broker resolves material concerns and approves one final record.

5. Approval to portal entry

The authorized portal-entry person receives:

• final approved values;

• selected comparables and adjustments;

• repairs;

• narratives;

• market conditions;

• photos and captions;

• required attachments; and

• clear submission instructions.

That person enters the approved information without independently revising the valuation.

Responsibility matrix

This matrix is a practical starting point. Adapt it to applicable requirements and team qualifications.

“Support” does not mean authority to make the final professional decision.

Use role-based access—not shared access

Each person should see and change only what the role requires.

Role-based access can separate:

• field assignments;

• subject-property information;

• candidate-comparable preparation;

• valuation decisions;

• quality-control findings;

• broker approval;

• portal credentials;

• billing or client information; and

• administrative configuration.

Shared accounts weaken accountability. They make it difficult to determine who changed a value, approved a narrative, uploaded a photo, or submitted an assignment.

The property record should retain the work and status across roles while preserving the history of consequential changes.

Common REO team handoff failures

Most team problems occur between roles.

Common failures include:

• the runner uploads photos without identifying damage;

• field observations remain in a text message instead of the property record;

• an administrator routes the wrong client instructions;

• a VA hides an exception instead of escalating it;

• the agent changes a comparable without updating the adjustments and narrative;

• the broker approves one version while portal entry uses another;

• portal-entry staff change a value to clear a validation message;

• multiple people assume someone else is tracking the due date; and

• prior BPO information is copied into an MSR without confirming what changed.

The fix is not simply more communication.

The workflow should define:

• the required output of each role;

• the condition for marking the stage complete;

• the reviewer;

• the escalation trigger; and

• the source of truth for the next person.

Design queues around the next action

Each team member needs a focused view of the work waiting for that role.

A runner needs properties requiring visits. An administrator needs unassigned, overdue, or incomplete preparation tasks. An agent needs files ready for market analysis. A broker needs valuations ready for approval. Portal-entry personnel need only approved files ready for submission.

A useful queue answers:

• What is ready for me?

• What is due first?

• What is blocked?

• What information is missing?

• Who owns the next action?

• What requires escalation?

One undifferentiated list forces every person to reconstruct the workflow repeatedly.

A small team still needs separate controls

In a small brokerage, one person may serve as administrator, agent, broker, and portal-entry operator.

The workflow stages should still remain distinct.

That person should:

1. complete the preparation stage;

2. perform the valuation;

3. run quality control;

4. deliberately approve the final version; and

5. enter only that approved version into the portal.

Separating the stages reduces the risk of editing and approving simultaneously without a complete review.

Role design is about controlled responsibilities, not headcount.

REO team-workflow checklist

Use this checklist when designing or reviewing the team’s operating model.

Role definition

• Every recurring task has an owner.

• Each role has a documented output.

• Professional decisions have an accountable agent or broker.

• Licensing, client, MLS, and portal requirements are reflected.

• One person holding multiple roles still follows separate workflow stages.

Access and security

• Permissions match job responsibilities.

• Shared accounts are avoided.

• Portal and MLS credentials are handled according to applicable rules.

• Outsourced providers receive only necessary access.

• Offboarding removes access promptly.

• Consequential changes remain attributable.

Handoffs

• Each stage has a completion standard.

• Missing information is visible.

• Exceptions have a defined escalation path.

• The next role receives one organized record.

• Due dates and priorities remain attached to the assignment.

Valuation control

• Final comparables are selected by a qualified agent or broker.

• Adjustment and value decisions remain professionally controlled.

• AI-generated language and captions are reviewed.

• Material quality-control findings are resolved.

• Broker approval is a distinct recorded step.

Portal submission

• Portal entry begins only after approval.

• The authorized person works from one final record.

• Portal validation does not trigger unauthorized valuation changes.

• Substantive discrepancies return for review.

• Submission confirmation and status are retained.

The best division of labor protects judgment

REO work becomes easier to scale when every task has a clear owner and every professional decision remains with the appropriate person.

Runners provide current field evidence. Administrators control assignments and deadlines. Virtual assistants add flexible preparation and entry capacity. Agents perform the market and valuation analysis. Brokers set the standards, resolve material issues, and approve the final work.

Automation connects those roles. It can organize the assignment, import MLS data, draft routine language, caption photos, apply completeness checks, preserve the property record, and route the approved handoff.

The result should not be less human accountability. It should be fewer dropped tasks, cleaner handoffs, and more time for the judgment that only the agent and broker can provide.

Return to the REO Operations Library for more practical guidance on REO valuation and brokerage operations.