How often should sanctions screening be run?

Run sanctions screening before you accept a new customer or guest, when relevant sanctions lists change, when identifying details change, and before later activity that requires a fresh check. Set additional recurring checks according to your obligations and customer relationships, rather than treating a daily or annual interval as a universal rule. A clear result at sign-up does not establish that a later booking or transaction is permitted.

How often should sanctions screening be run?

Use event-driven screening plus a documented recurring schedule where your obligations and relationships require one. Initial screening establishes a starting point. Subsequent screening addresses changes that make that starting point outdated.

For a 2026 policy, separate the moment you collect information from the moment you approve a booking, payment, or other activity. The guide to sanctions screening at sign-up covers the first checkpoint. Your ongoing process must address what happens afterward.

These checkpoints complement one another. A recurring schedule is not a substitute for responding to a relevant list update, and a sign-up check is not a permanent approval.

Why this matters

Sanctions screening asks whether a person, organization, or activity falls within applicable restrictions. Identity verification asks whether someone is who they claim to be. Neither answer substitutes for the other.

For an independent rental host, that distinction keeps the workflow practical. You need a clear guest-verification process and a separate understanding of which restrictions apply to your business. A professional guest experience does not require turning every booking conversation into a compliance discussion.

Your 2026 policy should explain when checks happen, who reviews possible matches, and which decisions wait for review. A schedule without an owner or a response process is incomplete.

Initial screening: before the first approval

Screen before you approve the activity covered by your policy. For a rental host, connect that checkpoint to a defined booking decision, rather than leaving it somewhere between the inquiry and arrival.

Collect enough identifying information to distinguish the guest from another person with a similar name. Depending on the list entry and available information, useful details include a full name, date of birth, nationality, address, or identity-document information. Collect only what your process needs and handle it under applicable privacy requirements.

Initial screening gives you a documented decision point. Its limitation is time: the result reflects the information and lists used for that check, not every future change.

Record the check and the decision separately. A screening result tells you what the search returned. Your approval record should show how any potential match was resolved and who made the decision.

List updates: review affected existing relationships

A sanctions list can change after a guest or customer has passed screening. Additions, amendments, and removals all matter, but they do not have identical consequences.

Your process should identify relevant updates and assess existing relationships against them. Confirm whether your provider checks existing records when lists change or only uses current lists when you request a new check. Those are different services.

For an independent host, focus on relationships with a decision still ahead: an upcoming stay, a repeat booking, or an unresolved payment. Keep record retention separate from active screening scope. Retaining a past guest record does not, by itself, define whether that guest belongs in your ongoing screening population.

Do not assume that a current list means current customer screening. Ask when the list changed, when the customer was checked, and whether the update triggered a new assessment.

Customer changes: recheck material identifying details

Re-screen when a material change affects the information used to identify the person or organization. Examples include a corrected legal name, new identifying information, or a change in an organization's ownership.

For rental bookings, a change in the booking guest deserves a clear response. A result for the original guest does not establish anything about a different person who takes over the reservation.

Distinguish identity changes from ordinary booking edits. Moving an arrival date does not change who the guest is, although it can move the decision far enough from the original check to warrant another review under your policy.

The benefit of this trigger is precision: you revisit records that changed. Its limitation is visibility. If staff do not record a replacement guest or updated information, the screening process cannot respond to it.

Later activity: check before the relevant decision

A repeat guest is a familiar guest, not a permanently cleared guest. Your policy should state when a later booking or payment requires another check.

For an ongoing customer relationship, place screening where it can inform the decision. A check completed after an activity has already occurred cannot serve as the pre-approval control for that activity.

Keep the distinction between screening and permission clear. A sanctions search is one input; applicable restrictions can also concern location, ownership, the activity itself, or other parties involved. A name search alone does not resolve every sanctions question.

In 2026, review your actual booking journey and identify where acceptance happens. Then assign the check to that checkpoint. Do not let an old result travel indefinitely from one reservation to the next without a stated rule.

Recurring screening: set a schedule you can explain

There is no universal US rule requiring every business to screen every customer daily. OFAC's *A Framework for OFAC Compliance Commitments* describes a risk-based approach to compliance, including risk assessment and internal controls; it does not supply one screening interval for every business.

Choose a recurring schedule based on your applicable requirements, the duration of customer relationships, relevant activity, and the way your other screening triggers operate. Document the reasoning, not just the calendar setting.

A recurring check provides a regular opportunity to identify changes. Its limitation is the interval between checks. Relevant list updates and material customer changes still need their own response.

Do not describe an interval as legally required unless you can identify the requirement that makes it so. If a contract, regulator, or internal policy sets the cadence, name that source in your operating procedure.

Why sanctions screening frequency varies

The right cadence depends on what you must check and when you must act. Use these factors to explain your 2026 schedule:

• Applicable restrictions. Identify the sanctions regimes and restrictions relevant to your business and activity.
• Relationship duration. A single booking and a continuing customer relationship create different screening checkpoints.
• Later activity. Repeat bookings, payments, and other approval decisions affect when an earlier result needs refreshing.
• List updates. Establish how relevant changes reach your process and which existing records receive a new check.
• Customer information changes. Define which changes trigger re-screening and who records them.
• Provider coverage. Verify which lists, update processes, and ongoing checks the service actually supplies.

Frequency cannot repair incomplete coverage. Checking repeatedly against the wrong lists, or searching a record with insufficient identifying details, leaves the underlying problem unchanged.

How do you turn the policy into a workable routine?

Use a sequence your team can follow without interpreting a long policy during every booking. Give each checkpoint an owner and define what happens when the result needs review.

1. Initial screening. Collect the necessary identifying details and screen before the first covered approval.
2. List updates. Establish how relevant changes trigger checks of existing relationships.
3. Customer changes. Route material updates back through screening before relying on the old result.
4. Match review. Compare identifying details, record the outcome, and resolve the issue before the affected decision.

This sequence separates routine checks from exceptions. It also makes a useful provider checklist: ask which steps the service performs and which remain your responsibility.

*A screening routine needs both repeat-check triggers and a clear path for reviewing matches.*

Test the procedure against an ordinary hosting situation: a returning guest makes a new reservation, then changes the person named on the booking. Your procedure should tell you whether to recheck the returning guest, check the replacement guest, or pause the decision while information is clarified.

Avoid collecting identity documents through improvised message threads simply because a match needs review. Use an appropriate collection process, limit access, and retain information according to your policy and applicable obligations.

Where guest verification fits for independent hosts

Checktiv is best for independent short-term rental hosts who want professional guest verification through a zero-code shared link. Checktiv, by Autohost, provides a straightforward way to verify guests without building a technical integration.

The stated setup journey is 3 steps in 5 minutes: sign up, get a link, and review the verification. The shared-link approach gives you a clear guest-facing action and a review point before your hosting decision.

That convenience does not establish sanctions-list coverage or ongoing re-screening. Before treating any guest-verification service as a sanctions control, confirm what its checks include, how list updates are handled, and whether existing guest records receive new checks.

The Checktiv guest-verification workflow belongs in the identity-collection and review part of your process. Your sanctions policy must still define the required checks, timing, and response to potential matches.

Does a possible match mean you must reject the guest?

A possible name match is not a confirmed sanctions match. Compare the guest's identifying details with the list entry and document why the record matches or differs.

A similar name alone does not establish that the guest is the listed person. Conversely, a spelling difference alone does not establish that the guest is unrelated to the listing. Use the information attached to the entry rather than deciding from the name alone.

If the match is confirmed or remains unresolved, follow the applicable restrictions and obtain qualified guidance before proceeding. Do not substitute a routine booking approval for a sanctions decision.

Can an unlisted company still be subject to sanctions?

Yes. Under OFAC's 50 Percent Rule, an entity owned 50% or more, directly or indirectly and in the aggregate, by blocked persons is also considered blocked. The entity does not need its own separate list entry for that rule to apply.

This matters when your customer or counterparty is an organization rather than an individual guest. Searching only the organization's name does not resolve ownership-based restrictions.

Keep this check proportionate to the relationship. An ordinary individual guest and a company booking require different identifying information; your procedure should distinguish them rather than collecting corporate ownership information from every traveler.

What should your screening record contain?

Keep enough information to reconstruct the decision. Record who was screened, when the check occurred, the service or lists used, any potential matches, the review outcome, and the person responsible for approval.

Also record the trigger. A sign-up check, a list-update check, and a replacement-guest check answer different operational questions even if the final result is the same.

Review your 2026 procedure when the business process or applicable requirements change. A policy that describes an old booking journey will not reliably guide the current one. Check that the documented workflow matches what your team actually does.

One last thing

The most useful question is not just when you last checked a guest. Ask what changed since that check and which decision comes next. That connects the screening result to the booking you are actually approving.

Use Checktiv for a simple guest-verification experience, and keep your sanctions timing explicit. Your hosting workflow should make the next action clear without treating an identity result as permanent permission.

Related guides

• Identity verification for short-term rental hosts
• Sanctions screening software options
• PEP and adverse media screening tools compared