ACTIVITY CHECK
Activity Check
Observation of publicly visible activity from a lawful vantage point, with no contact attempted and none made. Scoped in writing before dispatch so that the boundary between observation and contact is a parameter of the assignment rather than a judgement call in the field.
BUYER LENS
Know what this service should answer before you scope it.
What authorized operating question must this service answer, and who remains accountable for the resulting decision?
Good reasons to start here
- A defined matter needs specialized capacity.
- The client needs a documented work product or controlled handoff.
- The service must connect to another MODLAN discipline without blurring responsibility.
What to have defined
- Purpose, scope, owner, jurisdiction, and known constraints.
- Relevant records and evidence already available through an approved channel.
- Client guidelines, escalation expectations, and required handoff context.
What this should inform
A documented service outcome that supports — but does not silently replace — the accountable client's decision.
ACCOUNTABLE OWNERThe authorized client or program owner.CAPABILITIES
Disciplined support built around the matter.
MODLAN scopes each engagement to the authorized assignment, applicable requirements, available evidence, and client objectives. Work is documented for clarity, defensibility, and appropriate downstream review.
Written scope agreed before dispatchObservation from lawful vantage onlyNo contact attempted or madeTime-bounded observation logDocumented negative findingsHand-off criteria to a contact or surveillance assignment
WHEN THIS SERVICE FITS
Built around a defined operational question.
- A matter needs limited observation without subject contact.
- The assignment needs a written, time-bounded observational scope before deciding whether broader surveillance is warranted.
SCOPE
What the engagement can include.
The exact scope is established by the authorized assignment, applicable licensing or professional requirements, and client guidelines.
OPERATING MODEL
Controlled from assignment through handoff.
Scope
Define location, question, time window and explicit no-contact boundary.
Observe
Document only what is publicly observable from a lawful vantage.
Record
Preserve time-bounded observations and non-observations without selective editing.
Handoff
If broader surveillance or contact becomes appropriate, route it as a separate authorized assignment.
WORK PRODUCT
What the matter can produce.
- Observation log
- Relevant imagery where lawful
- Negative findings
- Escalation recommendation where appropriate
CONTROL BOUNDARY
What keeps the work defensible.
- No contact is attempted or made.
- No private-area intrusion or private-conversation audio capture.
- Observed activity is not represented as medical or functional capability.
- Activity Check remains a separate product from contact-based verification.
SERVICE FAQ
Procurement and operating questions.
Is this the same as surveillance?
No. It is a narrower written-scope observation product; broader surveillance is separately authorized.
Will you knock on the door?
No. Contact changes the product and requires separate authority.
Do negative findings matter?
Yes. The absence of responsive activity during the authorized window remains part of the record.
Can this establish disability capability?
No. Observation is reported as observation, not a medical or functional conclusion.
WHERE THIS SITS IN MODLAN
Enterprise Service Delivery
Apply the appropriate MODLAN operating capacity to the defined matter or program objective.
Explore the operating family →MODLAN SERVICESTechnology relationship
Technology is used only where it adds approved value and does not erase the accountable human or system-of-record boundary.
View the full MODLAN service ecosystem →HOW THIS SERVICE CAN SCALE
From assignment to enterprise program—without changing who owns the decision.
A defined objective, scope, owner, evidence/data path, and handoff for a specific matter or task.
Recurring or overflow use of the same capability under established client rules, controls, and escalation paths.
The service becomes one governed lane inside a broader multi-service operating model with explicit dependencies.
PROCUREMENT & IMPLEMENTATION
Questions to resolve before this service enters production.
Enterprise delivery depends on the operating context around the service—not merely the capability itself.
DECISION CONTEXT
This service does not operate in isolation.
The engagement should connect to the correct buyer, adjacent operating layer, and assurance boundary without blurring professional authority or the source of record.
ENTERPRISE JOURNEY
Connect this service to the rest of the operating model.
Move from service selection into the adjacent operational, evidence, integration, assurance, or intelligence layer that the matter actually requires.
MODLAN SYSTEMS
Bring the right people, evidence, and intelligence to the problem.
Contact MODLAN to discuss the authorized scope, geography, timing, and operational requirements for your matter.