> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rescueconsole.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Matching Adoption Applications to Animal Placement Needs

> Define what an animal needs in a home, and every application is automatically checked against the household—conflicts named, decision yours.

The placement matching feature helps you see at a glance how well an applicant's household matches what an animal needs—before you pick up the phone. When you record an animal's placement needs and an application comes in, RescueConsole checks the two against each other automatically and shows you exactly where they align, where they conflict, and where you need to ask more questions. The decision always stays with you.

## Recording an Animal's Placement Needs

On each animal record, a **Placement Needs** card lets you define what kind of home the animal requires. Each need can be marked as:

<CardGroup cols={2}>
  <Card title="Fine" icon="circle-check">
    This is not a concern for this animal. The household's situation matches or exceeds what the animal needs.
  </Card>

  <Card title="Conflict" icon="circle-xmark">
    There is a known incompatibility between the animal's needs and what the household has described.
  </Card>

  <Card title="Question" icon="circle-question">
    The information available raises a question to bring up on the phone call or meet and greet. Not a disqualifier, but something to explore.
  </Card>

  <Card title="Not Assessed" icon="circle">
    This need has not been evaluated yet. An unknown is never treated as a pass.
  </Card>
</CardGroup>

<Note>
  **Not Assessed is never a pass.** If a need has not been evaluated, RescueConsole surfaces it as an open question rather than assuming it is fine. This means gaps in your assessment are visible rather than invisible—you can see what still needs to be answered before making a placement decision.
</Note>

### Placement Need Categories

The placement needs card covers the factors that matter most for a successful placement:

<Accordion title="Children">
  Whether the animal is suitable for homes with children, and if so, the minimum age. You can mark fine for any age, set a minimum age threshold, mark as a conflict (not suitable for homes with children), or leave not assessed.
</Accordion>

<Accordion title="Other Dogs">
  How the animal does with other dogs in the home—fine, needs to be the only dog, requires a meet before placement, or not yet assessed.
</Accordion>

<Accordion title="Other Cats">
  How the animal does with cats—fine, not suitable for homes with cats, or not yet assessed.
</Accordion>

<Accordion title="Fenced Yard">
  Whether a fenced yard is required, preferred, or not necessary for this animal.
</Accordion>

<Accordion title="Hours Alone">
  The maximum number of hours this animal can reasonably be left alone each day.
</Accordion>

## How Applications Are Checked

When an application comes in for an animal, RescueConsole automatically compares the applicant's household information against the animal's recorded placement needs. You don't need to do this manually—the comparison is waiting for you when you open the application.

The result is a side-by-side view:

* Each placement need is shown next to the corresponding detail from the application
* Items that **match** are marked clearly
* Items that **conflict** are named explicitly—for example, "Animal needs minimum age 8; household has a 4-year-old"
* Items that are **questions** are flagged for your follow-up
* Items that are **not assessed** remain visible as open

<Note>
  RescueConsole names conflicts—it does not score applications or rank adopters. There is no algorithm making placement decisions. The system shows you what it found; you decide what it means. Every coordinator brings judgment, relationship knowledge, and context that no automated score can replace.
</Note>

### Applicant Preference Order Is Preserved

If an applicant listed animals in a preferred order, that order is preserved in the matching view. You can see which animal is the applicant's first choice and which are alternatives, so you have the full picture when deciding whether to move forward or suggest a different animal.

## Approving, Denying, and Asking More Questions

From the application view, your coordinator can:

* **Approve** the application to move toward adoption
* **Deny** the application with a reason recorded on file
* **Schedule a meet and greet** to gather more information before making a decision

## Scheduling a Meet and Greet

Scheduling a meet and greet from an application does more than put a time on the calendar.

<Steps>
  <Step title="Open the application and click Schedule Meet and Greet">
    Select the date, time, and location for the meeting.
  </Step>

  <Step title="Name who the applicant is meeting">
    Choose the staff member, foster, or volunteer who will host the meet and greet. This person is named on the appointment.
  </Step>

  <Step title="Each named person receives a task">
    RescueConsole creates a task for everyone involved—the coordinator, the host, and anyone else named—so no one misses their role in the meeting.
  </Step>

  <Step title="The appointment appears on the calendar">
    The meet and greet appears on the organization calendar, visible to anyone with calendar access. It is linked to the application and the animal record.
  </Step>
</Steps>

<Tip>
  Naming the foster or volunteer who will host the meet and greet means they receive a task and see the appointment on their calendar—no separate message needed to coordinate logistics.
</Tip>