Scheduler Onboarding Guide — Unlikely Professionals

Welcome to the Unlikely Professionals portal. This guide covers everything you need to know as a Scheduler — the primary client-side role responsible for submitting projects and managing inspections for your branch.

What Unlikely Professionals Does

Unlikely Professionals (UP) performs building code compliance inspections across Maryland, Washington D.C., and Virginia, primarily focused on structural foundation and water management systems. When a builder constructs or renovates a home, local building codes require third-party verification that the structure meets foundation, waterproofing, drainage, and structural integrity standards. UP inspects the work, certifies compliance, and delivers the certification paperwork the builder needs to close permits.

Why this matters Without UP’s certification, the builder cannot pass final inspection and the homeowner cannot move in. Your role as Scheduler is the critical first step — nothing moves forward until you submit the project.

Your Role: Scheduler

As a Scheduler (scheduler), you are the bridge between the builder and UP. You are the person who gets inspections into the system and keeps the schedule running. Here is what that means practically:

Submitter: You enter new projects into the system via the Intake wizard. This is your primary function.
Scheduler: You manage your branch’s inspection calendar — viewing upcoming inspections, requesting schedule changes, and coordinating timing with builders.
Communicator: You respond to RFIs (Requests for Information) when UP needs additional details about a project, and you create RFIs when you need information from UP.
Monitor: You track the status of your branch’s projects from submission through delivery.

What You Do Not Do

It is equally important to understand the boundaries of your role. The following are handled by UP’s internal team:

Review or return intake submissions (Admin does this)
Review schedule change requests (Admin/Owner does this)
Access the Work Pool or Review Queue
Draft or send certifications or invoices
Access the Drafting Queue, Reporting, or Admin functions

The Big Picture

Every project follows this path. The green boxes show where you are directly involved:

You submit project via Intake

↓

Admin reviews and accepts

↓

You see it on the Calendar — inspection is scheduled

↓

Field Inspector goes on site

↓

Admin reviews inspection data

↓

Admin drafts cert + invoice

↓

Admin sends directly or queues for Owner review

↓

Cert + invoice delivered to your branch

Branch Scoping You only see projects linked to your branch account. You cannot see other branches’ projects, calendars, or data. This is by design — each branch operates independently within the portal.

How to Log In

Navigate to unlikely.works in your web browser.
Enter the username and password provided to you by UP.
You will land on your Dashboard.

Bookmark it Bookmark unlikely.works for quick access. This is the only URL you need.

Your Dashboard

The Dashboard is your home screen. It shows everything you need to act on right now, scoped to your branch. It is divided into four sections:

Section	What It Shows	Action Required
This Week	Inspections scheduled this week for your branch	Review for accuracy. If anything needs to change, submit a schedule change request.
Schedule Changes	Your pending schedule change requests and their status	Check if any have been approved, not approved, or need more info.
Agent RFIs	Requests for information from UP that need your response	Respond promptly. Unanswered RFIs delay your projects.
Recent Projects	Recently submitted or updated projects for your branch	Monitor status changes. Check for non-approvals that need resubmission.

Agent RFIs are time-sensitive When UP sends you an Agent RFI, it means your project is blocked until you respond. RFIs follow an automatic escalation cadence (Day 1, Day 3, Day 5, Day 7+). Respond as quickly as possible to avoid delays.

Sidebar Navigation

The left sidebar gives you access to all portal pages. Here is what each section contains:

Menu	Sub-Item	Purpose
Daily Work	Intake	Submit new projects (your primary task)
	Calendar	View and manage inspections for your branch
	Schedule Changes	Request reschedules, cancellations, holds, or additions
Projects	Projects	Browse all your branch’s projects
	Holding Pool	Projects on hold (awaiting info, weather delay, etc.)
	Desk Review	Projects in desk review status
Communication	RFIs	View and respond to RFIs
Communication	Escalations	View and manage escalations

A productive day follows this pattern. The order matters — handle time-sensitive items first, then move to submissions and monitoring.

Log in to unlikely.works

↓

Check Dashboard — respond to Agent RFIs

↓

Review This Week — verify schedule accuracy

↓

Check Schedule Changes — any confirmed/declined?

↓

Submit new projects via Intake

↓

Check Recent Projects for non-approvals

↓

Submit schedule changes as needed

↓

End of day — verify nothing is pending

Priority Order

Agent RFIs — These are blocking your projects. Respond first.
Not Approved submissions — Fix and resubmit before submitting new ones.
Schedule verification — Confirm this week’s inspections are correct.
New project submissions — Enter today’s batch of new projects.
Schedule change requests — Reschedules, cancellations, holds.
Escalations — Handle any open escalations.

Batch your submissions If you have multiple projects to submit, do them all in one sitting. The Intake wizard is designed for efficient back-to-back submissions. Batching reduces context-switching and helps you catch errors.

This is your primary function. The Intake wizard is a 5-step process that captures everything UP needs to schedule and perform an inspection. Complete, accurate submissions move faster — incomplete ones get not approved and you have to start over.

Incomplete submissions cost time A not approved submission means the project goes back to the beginning. The builder is waiting, and every non-approval adds at least a day of delay. Take the extra minute to verify your data before hitting Submit.

The 5-Step Intake Wizard

Your account is pre-selected based on your branch. If your login is associated with multiple accounts, choose the correct one from the dropdown. This determines which branch the project belongs to and affects who can see it.

Why this matters The account determines billing, contact routing, and branch scoping. If the wrong account is selected, the project will be invisible to the correct scheduler and billed to the wrong entity.

Enter the full street address of the job site. This is the single most important piece of data in the submission.

Field	Required	Notes
Street Address	Yes	Full street address including unit/lot number if applicable
City	Yes	City or town name
State	Yes	MD, DC, or VA
ZIP Code	Yes	5-digit ZIP
Permit Number	No	Strongly recommended. Helps UP cross-reference with the jurisdiction.
Lot/Block	No	Include if available — helps with new-construction sites that lack a street number.

>>> DOWNSTREAM IMPACT — PERMIT NUMBER <<<

A missing permit number does not just delay acceptance — it prevents the entire project from moving forward. Without a permit number, the system cannot:

Match the project to jurisdiction records
Validate the scope of work against the permitted scope
Generate the certification package for the project
Issue the invoice

This directly delays the ability to close the permit with the county. An RFI will be issued back to you requesting the permit number, adding days to the timeline. Always include the permit number at intake when you have it.

New construction For new-construction sites where the street address has not been assigned yet, use the lot/block number and subdivision name. Example: “Lot 42, Block 3, Willowbrook Estates.”

The SOW defines what UP will inspect. Select one or more products from the list and specify quantities. Each product corresponds to a specific type of inspection.

Common products you will encounter:

Product	What It Covers	Typical Quantity
FND (Foundation)	Foundation waterproofing and drainage systems	1 per structure
RTW (Retaining Wall)	Retaining wall drainage and structural compliance	1 per wall system
WTR (Waterproofing)	Below-grade waterproofing membrane inspection	1 per structure
ENC (Encapsulation)	Crawl space encapsulation systems	1 per crawl space
PSI (Post-Tension Inspection)	Post-tension slab/cable systems	1 per slab
UND (Underpinning)	Foundation underpinning systems	Varies (by pier count)

Select the right products If you select the wrong product, the inspector will arrive prepared for the wrong type of inspection. This wastes a trip and delays the project. When in doubt, check with your superintendent or create a Client RFI to ask UP.

Multiple products on one project A single project can have multiple SOW items. For example, a new home might need both FND and RTW inspections. Add all items that apply — do not create separate projects for each inspection type at the same address.

Upload any supporting documents. The more you provide upfront, the smoother the process. Documents can include:

Building plans / drawings — Foundation plans, site plans, structural details
Permits — Building permit, grading permit
Product specs — Manufacturer specs for waterproofing membranes, drainage systems, etc.
Photos — Site photos showing current condition
Previous inspection reports — If this is a re-inspection or follow-up

Accepted formats PDF, JPG, PNG, HEIC. Maximum file size is 25 MB per file. For large plan sets, combine into a single PDF when possible.

The final step captures when and how the inspection should happen:

Field	Options	What It Means
Stage	In Production / Post-Production	In Production = work is still underway, inspection during construction. Post-Production = work is complete, final inspection.
Review Type	Desk / Field	Desk = document-only review (no site visit). Field = physical on-site inspection required.

Most submissions are Post-Production + Field The vast majority of projects are submitted after the work is complete and require a field inspection. If you are unsure which to select, Post-Production + Field is almost always correct.

Review your submission carefully, then click Submit. You will see a confirmation screen with the submission details.

What Happens After You Submit

You submit via Intake wizard

↓

Submission enters the Admin Review Queue

↓

Admin reviews: is the data complete?

↓

Yes — Approved

Project created in the system

↓

Appears on your Calendar and Projects page

No — Not Approved

You receive a non-approval notification with reason

↓

Fix the issue and resubmit

What Makes a Good Submission

Do	Do Not
Include the full, correct street address	Submit with partial or abbreviated addresses
Select all applicable SOW products	Create multiple projects for the same address
Attach plans and permits if available	Submit without any supporting documents
Include the permit number when you have it	Guess at the permit number
Double-check the account/branch selection	Submit under the wrong account
Add notes if there are special access instructions	Assume the inspector knows the site

Non-approval notification If your submission is not approved, you will receive an email notification explaining the reason. Check your inbox (and spam folder) if you see a project disappear from your pending list. You will also see a portal notification.

Duplicate Detection & Adding Visits

The system automatically checks for existing projects at the same address or with the same permit number. If a match is found, you will see a Potential Duplicate Detected warning with three options:

Option	When to Use	What Happens
Add Visit to Existing Project	You need to schedule an additional inspection for a project that already exists (e.g., a follow-up visit)	A new site visit is added to the existing project. No duplicate project is created.
This Is a New Project	The address match is coincidental — different scope of work, different permit, or a new engagement	Submission proceeds normally. Admins are notified of the potential overlap for review.
Contact Scheduler Instead	You are unsure and want to check with someone before proceeding	Blocks the submission. Contact your scheduler or admin to determine the right path.

Do not create duplicate projects If you need to add a follow-up visit to an existing project, use Add Visit to Existing Project during intake, or ask an admin to add it from the project detail page. Creating a second project at the same address causes data conflicts and billing errors.

The Calendar page shows all scheduled inspections for your branch. It uses a full interactive calendar (FullCalendar) with day, week, and month views.

What You See on the Calendar

Scheduled inspections for your branch only (other branches are hidden)
Color-coded by inspection type (FND, RTW, WTR, etc.)
Click any event to see project details: address, SOW items, status, inspector assigned

Calendar Views

View	Best For
Day	Seeing the detailed schedule for a specific date
Week	Planning and verifying the current or upcoming week
Month	Getting an overview of how busy a period is

Calendar is read-only for scheduling You cannot drag and drop events or directly change dates on the calendar. To change an inspection date, use the Schedule Changes feature (see Section 06). The calendar reflects what has been confirmed.

Using the Calendar Effectively

Start of day: Check today’s view to see what inspections are happening.
Start of week: Switch to week view and verify all scheduled inspections are still valid. If a builder has changed their timeline, submit a schedule change immediately.
Before submitting new projects: Check the calendar density. If a day is already packed, the inspector may not be able to fit another inspection. UP may need to schedule it for a different day.

Coordinate with your builders The most common source of schedule changes is builders who change their timeline without telling you. Make it a habit to confirm with your builders at least 48 hours before a scheduled inspection to avoid last-minute changes and rush fees.

When an inspection date needs to change, you submit a schedule change request. You cannot change the schedule directly — all changes require Admin or Owner review.

Types of Schedule Changes

Type	When to Use	What Happens
Reschedule	The inspection needs to move to a different date	Admin confirms, calendar updates to the new date
Cancel Inspection	A specific inspection visit needs to be cancelled (not the whole project)	Admin confirms, inspection is removed from calendar
Add Inspection	An additional inspection visit is needed (e.g., re-inspection after corrections)	Admin confirms, new inspection added to calendar
Hold	The project needs to pause temporarily (weather, construction delay, etc.)	Admin confirms, project moves to Holding Pool until released
Cancel Project	The entire project should be cancelled	Admin confirms, project status changes to Closed with `cancelled` flag

How to Submit a Schedule Change

Navigate to Daily Work → Schedule Changes (or click on the project and select “Request Change”).
Select the project from your branch’s project list.
Choose the change type (Reschedule, Cancel Inspection, Add, Hold).
For reschedules: select the preferred new date.
Add a reason for the change (required).
Submit the request.

Rush flag: less than 24 hours notice If you submit a schedule change with less than 24 hours until the scheduled inspection, the system automatically flags it as a rush. Rush changes may incur a trip charge or missed appointment fee if the inspector has already been dispatched or is en route. Always try to submit schedule changes at least 24 hours in advance.

Schedule Change Lifecycle

You submit a schedule change request

↓

Less than 24 hours notice?

↓

Yes

Auto-flagged as RUSH

No

Normal priority

↓

Request enters Admin’s queue

↓

Admin reviews

↓

Approved

Calendar/status updated

Not Approved

You receive notification with reason

Tracking Your Requests

All your schedule change requests appear on the Schedule Changes page with their current status:

Status	Meaning
Pending	Submitted, waiting for Admin review
Approved	Change has been applied
Not Approved	Change was not approved — check the reason

The Projects page is your master list of all projects belonging to your branch. You can search, filter, and view details for any project you have access to. Each project row includes a pipeline indicator — a compact dot-and-line graphic showing exactly where the project sits in its lifecycle (green = completed stages, blue = current stage, grey = upcoming stages, amber = on hold).

Searching for Projects

You can search by any of these fields:

Address — Street address (partial match works)
R-Number — The project’s unique identifier (e.g., R-12345)
Permit number — If one was provided at intake

Filtering by Status

Use the status filter to narrow your view. Here are the statuses you will encounter most often:

Status	What It Means	Your Action
Intake	Just submitted, awaiting Admin review	Wait for review. Check for non-approval notifications.
Scheduled	Accepted and inspection date set	Verify the date works. Submit schedule change if not.
In Progress	Inspection is underway or partially complete (includes multi-visit projects)	No action needed. Inspector is handling it.
Field Complete	All inspections done, awaiting Admin review. Any open RFIs or missing items are tracked here.	Check your RFIs — you may need to respond if items are outstanding.
Ready for Cert	Inspection passed, certification being prepared	No action needed. Almost done.
Certified	Certification issued	No action needed. Cert has been or will be delivered.
Invoiced	Cert + invoice sent to your branch	Complete. Check your email for the delivery.
Closed	Fully complete, paid, and closed out	No action needed.
Flags (can apply to any project regardless of status):
On Hold	Project paused — visible in Holding Pool (retains current status)	Submit a schedule change to release when ready.
Cancelled	Project was cancelled (status set to Closed with `cancelled` flag)	No action needed.

Project Detail View

Click any project to see its full details:

Address, account, and submission date
SOW items and quantities
Current status and status history
Attached documents
Inspection dates and results
Any RFIs or escalations associated with the project

You can see but not edit The Projects page is primarily a viewing tool. You cannot edit project data directly. If something is wrong, create a Client RFI or contact UP to request a correction.

Holding Pool

The Holding Pool shows all of your branch’s projects that are currently on hold. Projects land here when:

You submitted a “Hold” schedule change request and it was confirmed
UP placed the project on hold (e.g., waiting for information, weather conditions, site not ready)
A project was paused due to an unresolved RFI

Each project in the Holding Pool shows the reason it was placed on hold and when it was paused.

Watch the 45-day clock Projects on hold still count against the 45-day rule (see Section 10). If a project sits on hold for too long, it will transfer to triage and you will lose access. Check your Holding Pool regularly and release projects as soon as they are ready to move forward.

Releasing a Project from Hold

Find the project in the Holding Pool.
Submit a schedule change request of type “Add Inspection” or “Reschedule” with the new desired date.
Once confirmed, the project moves back to an active status and appears on the calendar.

Desk Review

The Desk Review page shows projects in your branch that are undergoing a document-only review (no physical site visit). These are projects where the review type was set to “Desk” during intake.

Desk reviews are less common than field inspections. They are typically used for:

Plan reviews before construction begins
Follow-up reviews where sufficient photographic evidence exists
Compliance verification based on submitted documentation

Your role with desk reviews You may be asked to provide additional documents via an Agent RFI during the desk review process. Otherwise, desk reviews proceed without your involvement — the Admin handles them internally.

RFIs (Requests for Information) are the formal way to exchange questions between you and UP. There are two types, and the direction of the question determines your role.

Two Types of RFIs

Type	Direction	Your Role
Agent RFI	UP → You	Respond. UP is asking you for information about a project. This is time-sensitive.
Client RFI	You → UP	Create. You are asking UP a question about a project, process, or requirement.

Responding to Agent RFIs

When UP sends you an Agent RFI, it appears on your Dashboard under “Agent RFIs” and on the RFIs page. Here is the process:

Agent RFI appears on your Dashboard

↓

Click to view the RFI details and question

↓

Gather the requested information

↓

Type your response and upload any requested files (see below)

↓

Submit your response

↓

UP reviews your response and project moves forward

Uploading Files from an RFI

RFIs can request specific document types. When you open an RFI, the upload interface shows only the fields relevant to what is being requested. You can upload files directly from the RFI — each upload is automatically recorded as part of your response.

Document Type	Where It Goes	Notes
Drive Logs	photos-and-drivelogs/	CSV, Excel, or text PDF with PSI/torque readings. The system auto-parses pier data and saves structured JSON for the cert pipeline. Scanned/image PDFs are flagged for manual review.
Photos	PHOTOS/	Construction photos requested by the admin team.
Plans	PLANS/	Foundation or structural plans, engineering drawings.
Permits	PERMITS/	Building permits, jurisdiction documents.

Multi-category RFIs An RFI may request multiple document types at once (e.g., “Photos + Drive Logs”). When this happens, the upload interface shows separate upload fields for each requested type. Upload each category to the correct field — the system routes each file to the proper project folder automatically.

Drive log auto-parsing When you upload drive logs, the system automatically extracts PSI and torque readings from the file and saves structured data to the project’s DRIVELOGS/driving_log.json. This data feeds directly into the certification sparkline charts and driving log table — no manual data entry needed.

RFI escalation cadence Agent RFIs follow an automatic reminder schedule. If you do not respond:
Day 1: Initial RFI sent
Day 3: First reminder
Day 5: Second reminder
Day 7+: Escalation to your branch manager (GOA)

Do not wait for reminders. Respond as soon as you have the information.

Creating Client RFIs

When you need to ask UP a question, create a Client RFI:

Navigate to Communication → RFIs.
Click “New RFI.”
Select the project this question relates to.
Type your question clearly and specifically.
Attach any supporting documents if relevant.
Submit.

Be specific Vague questions get vague answers. Instead of “What do I need?”, ask “The builder says the foundation waterproofing is complete but has not backfilled yet — should we schedule the inspection before or after backfill?”

Common Agent RFI Topics

Topic	What UP Needs	Where to Get It
Missing plans	Foundation or structural plans	Builder or architect
Permit number	Building permit number for the jurisdiction	Builder or jurisdiction website
Site access	Gate codes, contact on site, access instructions	Builder or site superintendent
Product specifications	Manufacturer specs for installed materials	Builder or material supplier
Scope clarification	Confirmation of what was actually installed	Builder or site superintendent
Photo documentation	Photos of specific conditions at the site	Builder or site superintendent

Escalations

Escalations are for situations that go beyond a normal RFI — when something is wrong, urgent, or requires management attention. Use the Escalations page under Communication to:

View escalations related to your branch’s projects
Respond to escalations raised by UP (similar to responding to an RFI, but higher priority)
Create an escalation when you need urgent attention on an issue

When to escalate vs. when to RFI Use an RFI for routine questions (missing documents, scope clarification, scheduling questions). Use an escalation for urgent problems (inspector could not access site, safety concern, major discrepancy, missed inspection with no notification). There is a limit of 5 escalations per project.

The 45-day rule is the single most important system rule to understand as a Scheduler. It directly affects your access to projects.

Critical rule Any project that has been in the system for more than 45 days without reaching a terminal status (Certified, Invoiced, or Closed) is automatically transferred to the Triage team. Once transferred, you lose access to the project entirely. You will no longer see it on your Projects page, Calendar, or Dashboard.

How the 45-Day Clock Works

Event	Effect on Clock
Project submitted (Intake)	Clock starts
Project accepted, scheduled, inspected	Clock continues running
Project placed on hold	Clock continues running (hold does NOT pause it)
RFI sent to you (Agent RFI)	Clock continues running
Day 45 reached	Project auto-transfers to Triage
Project reaches terminal status before day 45	Clock stops — no transfer

What Happens When a Project Transfers to Triage

Project hits 45 days

↓

Auto-transferred to Triage team

↓

You lose access — project disappears from your view

↓

Triage team investigates and resolves

↓

Can it be returned to normal workflow?

↓

Yes

Triage returns it — you regain access

No

Triage resolves or closes it

How to Prevent 45-Day Transfers

Respond to RFIs immediately. The number one cause of delayed projects is unanswered RFIs. Every day you wait is a day closer to 45.
Do not leave projects on hold indefinitely. If a project is on hold, the clock is still running. Release it or cancel it.
Monitor your projects regularly. Check the Projects page weekly for anything that has been sitting too long.
Submit complete intake data. Incomplete submissions lead to non-approvals, resubmissions, and wasted time on the clock.
Coordinate with builders early. If the builder is not ready for inspection, either do not submit yet or submit and immediately place on hold (but be aware the clock runs during hold).

Rule of thumb If a project is approaching 30 days without being inspected, treat it as urgent. You have 15 days left. Contact UP immediately to understand what is blocking it and take action.

Conversations live inside each project, not on a separate page. Open any project, scroll to the Correspondence section, and you will see the full message thread alongside the project’s files, site visits, and certifications.

How It Works

A red dot appears on project rows in the Projects table and on calendar events when there are unread messages for that project. Click through to the project to read and reply. Messages are delivered in real time via WebSocket — no need to refresh the page.

Starting a Conversation

If a project has no conversation yet, type a message in the compose area of the Correspondence section and send. A conversation is auto-created and linked to the project. You can also click + new message to choose a type (general, RFI, or review).

Scheduling Team Inbox

You are part of the Scheduling team. Conversations assigned to your team appear in your shared inbox. When you click into an unassigned conversation and start typing, the system automatically claims it for you — this prevents two people from responding to the same message at the same time (collision detection).

Ask Friday

The ask friday action in the compose bar invokes Friday, the portal’s AI assistant, directly in the thread. As a scheduler, you get Friday’s Staff voice — it can look up project status, check calendar availability, and answer questions about the scheduling workflow. Friday will not expose financial data or internal pricing. Friday’s responses are visible to everyone on the team.

Mobile & PWA

The portal supports “Add to Home Screen” on your phone for an app-like experience. Messages work offline — if you lose connection, your messages queue locally and send automatically when you reconnect. Push notifications are supported if you enable them in your browser.

Notification Preferences

Click the gear icon in the notification panel to configure how you receive alerts. You can choose portal notifications, email fallback (for when you are offline), and Do Not Disturb hours. Notifications consolidate within a 2-minute window so you do not get spammed.

Replaces email Use project conversations instead of email for anything project-related. Conversations are permanently attached to the project record, searchable in the sidebar search bar, and visible to the entire team. Email threads get lost — project conversations do not.

Before logging off, run through this checklist. It takes two minutes and prevents problems from carrying over to the next day.

#	Check	Where
1	All Agent RFIs responded to?	Dashboard → Agent RFIs
2	Tomorrow’s inspections verified with builders?	Calendar → Tomorrow
3	Any not approved submissions resubmitted?	Dashboard → Recent Projects
4	Schedule change requests submitted for any known changes?	Daily Work → Schedule Changes
5	Holding Pool reviewed — anything ready to release?	Projects → Holding Pool
6	No projects approaching 30+ days without resolution?	Projects → Projects (sort by date)
7	Open escalations addressed?	Communication → Escalations

Two-minute habit This checklist is fast. Making it a daily habit will prevent the most common problems: forgotten RFIs, surprise schedule changes, and projects silently aging toward the 45-day cutoff.

Term	Definition
Agent RFI	A Request for Information sent by UP to you. You must respond.
Branch	Your company’s office or division. All your projects, calendar, and data are scoped to your branch.
Cert / Certification	The official compliance certificate issued by UP after a passing inspection.
Client RFI	A Request for Information you send to UP. You are asking the question.
Desk Review	A document-only review that does not require a physical site visit.
ENC	Encapsulation — crawl space encapsulation system inspection.
Escalation	A high-priority issue that requires management attention. Limit: 5 per project.
Field Inspection	A physical, on-site inspection by UP’s field inspector.
FND	Foundation — foundation waterproofing and drainage system inspection.
GOA	General Office Admin. Your branch manager on the client side.
Holding Pool	Where projects go when placed on hold. The 45-day clock still runs.
Intake	The process of submitting a new project to UP via the 5-step wizard.
In Production	Stage setting: work is still underway at the site.
Post-Production	Stage setting: all work is complete, ready for final inspection.
PSI	Post-Tension Inspection — post-tension slab/cable system inspection.
R-Number	The unique project identifier assigned by the system (e.g., R-12345).
RTW	Retaining Wall — retaining wall drainage and structural compliance inspection.
Rush Flag	Auto-applied when a schedule change is submitted with less than 24 hours notice. May trigger fees.
Schedule Change	A formal request to modify an inspection date, add/remove an inspection, or hold/cancel a project.
SOW	Scope of Work — the list of inspection products and quantities for a project.
Triage	UP’s internal team that handles projects older than 45 days. If your project goes to triage, you lose access.
Trip Charge	A fee that may apply when an inspector arrives on site but cannot perform the inspection (site not ready, access unavailable, last-minute cancellation).
UND	Underpinning — foundation underpinning system inspection.
UP	Unlikely Professionals — the inspection company.
WTR	Waterproofing — below-grade waterproofing membrane inspection.

Portal Access

Item	Value
Portal URL	unlikely.works
Your Role	scheduler
Scope	Branch-level (you only see your branch’s data)

What You Can Do

Action	Where
Submit new projects	Daily Work → Intake
View inspection calendar	Daily Work → Calendar
Request schedule changes	Daily Work → Schedule Changes
Cancel a project	Action Center or project detail page
Browse your projects	Projects → Projects
View projects on hold	Projects → Holding Pool
View desk reviews	Projects → Desk Review
Respond to Agent RFIs	Communication → RFIs
Create Client RFIs	Communication → RFIs
Handle escalations	Communication → Escalations

What You Cannot Do

Action	Who Does It
Review/return intake submissions	Admin (Jacob)
Review schedule changes	Admin / Owner
Access Work Pool or Review Queue	Admin / Owner
Draft or send certifications	Admin (sends directly or queues for Owner review)
Draft or send invoices	Admin (sends directly or queues for Owner review)
Access Reporting or Admin settings	Owner (Dustin)
See other branches’ projects	Each branch sees only its own

Who to Contact

Situation	Contact	Method
Question about a project or inspection	UP Admin (Jacob)	Client RFI via portal
Urgent issue or complaint	UP Admin or Owner	Escalation via portal
Cannot log in or portal issue	Dustin (Owner)	Email or phone
Builder needs information from UP	UP Admin (Jacob)	Client RFI via portal
Schedule conflict or change needed	Self-service	Daily Work → Schedule Changes
New project to submit	Self-service	Daily Work → Intake

Key Thresholds

Threshold	Value	What Happens
Triage transfer	45 days	Project auto-transfers to triage — you lose access
Rush flag	< 24 hrs	Schedule change with less than 24hr notice — auto-flagged, may trigger fee
RFI escalation	Day 1→3→5→7+	Automatic reminder cadence for unanswered Agent RFIs
Max escalations	5 per project	Hard limit on escalation count per project
Warning zone	30 days	If a project is at 30 days without resolution, treat as urgent

Daily Priority Order

Respond to Agent RFIs
Fix and resubmit not approved intake submissions
Verify today’s and tomorrow’s inspection schedule
Submit new projects via Intake
Submit schedule change requests
Handle escalations
Review Holding Pool for projects ready to release

Emergency Procedures

If the portal is down Contact Dustin (Owner) directly by phone or email. Do not attempt to submit projects through other channels. Wait for the portal to be restored.

If an inspector does not show up Create an escalation immediately via Communication → Escalations. Include the project R-number, scheduled date/time, and site contact information. UP will investigate and reschedule.

If you are unsure about something Create a Client RFI. There is no penalty for asking questions. It is far better to ask than to submit incorrect data or miss a deadline.

Who’s Who

Sidebar Navigation

What Unlikely Professionals Does

Your Role: Scheduler

What You Do Not Do

The Big Picture

How to Log In

Your Dashboard

Sidebar Navigation

Priority Order

The 5-Step Intake Wizard

What Happens After You Submit

What Makes a Good Submission

Duplicate Detection & Adding Visits

What You See on the Calendar

Calendar Views

Using the Calendar Effectively

Types of Schedule Changes

How to Submit a Schedule Change

Schedule Change Lifecycle

Tracking Your Requests

Searching for Projects

Filtering by Status

Project Detail View

Holding Pool

Releasing a Project from Hold

Desk Review

Two Types of RFIs

Responding to Agent RFIs

Uploading Files from an RFI

Creating Client RFIs

Common Agent RFI Topics

Escalations

How the 45-Day Clock Works

What Happens When a Project Transfers to Triage

How to Prevent 45-Day Transfers

How It Works

Starting a Conversation

Scheduling Team Inbox

Ask Friday

Mobile & PWA

Notification Preferences

Portal Access

What You Can Do

What You Cannot Do

Who to Contact

Key Thresholds

Daily Priority Order

Emergency Procedures