01

Welcome to Unlikely Professionals. This guide covers everything you need to know as a Scheduling Assistant working in the portal.

What We Do

Unlikely Professionals 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. That is us. We inspect the work, certify compliance, and deliver the paperwork the builder needs to close permits.

Why this matters Without our certification, the builder cannot pass final inspection and the homeowner cannot move in. We are a critical link in the construction process.

What the Portal Is

The portal is a custom-built web application that manages every project from the moment a client submits it to the moment they receive their certification package. It replaces spreadsheets, email chains, and manual tracking. Everything — scheduling, inspections, reviews, certifications, invoicing — flows through the portal.

Behind the portal sits SmartSuite (the project database), a FastAPI backend (the engine), and Supabase (a mirror for reporting). You do not need to interact with any of these directly. The portal is your interface to all of it.

Your Role: Scheduling Assistant

As a Scheduling Assistant (scheduler_assistant), you support your scheduler with the day-to-day administrative work that keeps projects moving. Here is what that means practically:

Key distinction You have the same portal navigation as a scheduler, but with narrower permissions. You can submit things (intake requests, schedule changes, RFI responses) but you cannot approve anything. Think of your role as preparing and supporting, while your scheduler and the admin team handle approvals.

The Big Picture

Every project follows this general path. Understanding where you fit in is the single most important thing to internalize:

You or the scheduler submit a project via Intake
Admin reviews and approves the submission
Scheduler arranges the inspection date on the Calendar
Field Inspector goes on site and collects data
Admin reviews data and drafts certification + invoice
Owner gives final approval
You send the cert email to the contact
Cert + invoice delivered to client
Your touchpoints You are involved at the beginning (submitting projects, coordinating the schedule) and at the end (sending cert emails). In between, your job is to respond promptly to any RFIs and keep the scheduler informed of any issues.
02

Accessing the Portal

Open your browser and go to unlikely.report. This is the scheduling assistant domain. Log in with the credentials provided to you.

Important The portal uses role-based domains. unlikely.report is for the scheduling assistant role. Other domains exist for other roles (admin, owner, scheduler, triage, GOA). You should only ever use unlikely.report.

Your Dashboard

After login, you land on your dashboard. It is role-filtered and branch-scoped — you only see what matters to your role and your branch. Here is what each section means:

Dashboard SectionWhat It ShowsWhy It Matters
This WeekInspections scheduled for the current week in your branchGives you an overview of upcoming field activity so you can prepare and coordinate
Schedule ChangesPending schedule change requests you or the scheduler have submittedTrack the status of reschedules, cancellations, and hold requests
Agent RFIsRFIs from the admin team that need your responseUnanswered RFIs block projects from moving forward — respond promptly
Recent ProjectsThe latest projects for your branchQuick access to projects you recently submitted or that recently had activity

Morning Numbers to Check

Every morning, glance at these numbers before doing anything else:

  1. Agent RFI count — Any RFIs waiting for your response? These are your highest priority.
  2. Schedule changes count — Any pending requests? Were any denied that need a new approach?
  3. This week’s inspections — What is coming up? Is there anything you need to coordinate or prepare for?
  4. Recent projects — Any status changes overnight? Any new activity on projects you submitted?
Tip The dashboard is your command center. Start every session here. If the RFI count is above zero, handle those before anything else — they are blocking the admin team from completing certifications.
03

Work through these in order every morning. This priority sequence ensures nothing gets stuck and your scheduler has the support they need.

Agent RFIs are requests from the admin team (Jacob) for missing information on projects in your branch. These are your absolute top priority because an unanswered RFI stops a project from being certified and delivered.

What to Do

  • Open the RFIs page from the sidebar (Field Ops → RFIs)
  • Review each open RFI — read exactly what is being requested
  • Gather the requested information (photos, permit numbers, measurements, clarifications)
  • Respond directly in the portal with the requested data
Escalation cadence Agent RFIs have automatic escalation: initial notification on Day 1, reminder on Day 3, stronger reminder on Day 5, and escalation to your GOA on Day 7+. Responding quickly avoids escalation and keeps projects moving.

Open the Calendar to see what inspections are scheduled for today and this week. Verify that everything looks correct and flag any issues to your scheduler.

What to Look For

  • Today’s inspections: Are sites ready? Any last-minute client communications needed?
  • This week’s outlook: Anything that needs coordination or preparation?
  • Schedule change statuses: Were any of your recent requests approved or denied?

Check with your scheduler to see if there are new projects that need to be submitted through the Intake wizard. You can submit projects exactly the same way a scheduler does.

  • Gather the required information: address, account, SOW items, permit info, and any supporting documents
  • Submit via the Intake wizard (see Section 04 for the full walkthrough)
  • Monitor the submission status — was it approved or rejected?
  • If rejected, read the rejection reason and correct the submission

Check the Escalations page for any active escalations on your branch’s projects. If there is an open escalation thread, read it and provide any information requested.

How escalations work Escalations are for when normal communication (RFIs) is not resolving an issue. They open a threaded message channel on the project that all responsible parties can see. Respond in the thread with the needed information.

Daily Priority Flow

Log in to unlikely.report
Check dashboard — note RFI count and schedule changes
Respond to all open Agent RFIs (highest priority)
Review Calendar — today’s and this week’s inspections
Submit any new intake requests from your scheduler
Check and respond to any escalations
Send any pending cert emails (see Section 10)
04

One of your key responsibilities is submitting new projects through the Intake wizard. You have the same intake capabilities as a scheduler. Nothing enters the system until the admin team approves it, so accuracy in your submission saves everyone time.

The Intake Wizard — 5 Steps

The Intake wizard walks you through a structured 5-step process. Each step must be completed before moving to the next.

StepScreenWhat You Enter
1Project DetailsStreet address, city, state, zip code. The system checks for duplicate addresses automatically.
2Account & BranchSelect the client account and branch. As an assistant, your branch is pre-selected.
3Scope of WorkSelect the products/services to be inspected. These come from the ABSoW (Account-Branch Scope of Work) — the available options are pre-configured for your branch.
4Stage & ReviewSelect the stage (in-production or post-production) and the review type (desk or field). This determines how the project flows after approval.
5Documents & SubmitAttach permits, plans, and supporting documents. Add any notes for the admin team. Submit for approval.

Stage & Review Type

Stage

  • In-production: The construction is still underway. Inspection happens during the build process.
  • Post-production: Construction is complete. Inspection happens after the fact.

Review Type

  • Field review: Requires an on-site inspection visit. This is the most common type.
  • Desk review: Can be evaluated from submitted documents and photos alone. No site visit needed.

The Submission Flow

You complete the 5-step Intake wizard
Submission enters the admin approval queue
Admin reviews your submission
Approved
Project created in the system, ready for scheduling
Rejected
You receive a notification with the rejection reason — fix and resubmit
Tip Double-check the address for typos before submitting. A wrong address creates confusion downstream and may result in the inspector going to the wrong location. Also verify that the correct SOW items are selected — adding or removing items after approval is more work for everyone.
Rejections If your submission is rejected, you will receive both a portal notification and an email explaining what was wrong. Common reasons: duplicate address, missing permit number, incorrect SOW items, or missing documents. Read the reason carefully, correct the issue, and resubmit.
05

Viewing the Calendar

The Calendar page shows all scheduled inspections for your branch. It is a FullCalendar-based view that supports day, week, and month layouts.

Branch scoping The calendar is scoped to your branch. You only see inspections for projects in your branch. If you need to see another branch’s calendar, you cannot — that requires a scheduler or GOA role with broader access.

What Each Calendar Entry Shows

FieldWhat It Tells You
AddressThe project location for this inspection
TimeThe scheduled inspection window
Status colorVisual indicator of the project’s current status
InspectorWho is assigned to perform the inspection

Coordinating with Your Scheduler

You cannot directly schedule inspections — that is the scheduler’s responsibility. However, you play a supporting role:

Calendar sync The calendar syncs with Google Calendar. Changes made in the portal are reflected in the inspector’s Google Calendar automatically. This is a two-way sync, so changes in Google Calendar also appear in the portal.
06

When a client needs to change their inspection schedule, you submit a schedule change request through the portal. The admin team reviews and approves or denies these requests. You can submit schedule change requests, but you cannot approve them.

Request Types

TypeWhen to UseWhat You Provide
RescheduleClient wants a different inspection dateNew preferred date and reason for the change
Cancel InspectionClient wants to cancel a specific visitReason for cancellation
Add InspectionClient needs an additional inspection visitPreferred date and reason (additional work, re-inspection, etc.)
HoldClient wants to pause the project temporarilyReason and expected resume timeline if known
Cancel ProjectClient wants to cancel the entire projectReason for cancellation — use the Cancel Project page in the sidebar

Submitting a Schedule Change

Client contacts you with a schedule change need
Open Schedule Changes from the sidebar
Select the project and request type
Fill in the details: new date (if applicable), reason, any notes
Submit the request — it enters the admin approval queue
Admin reviews your request
Approved
Calendar updated automatically. You are notified.
Denied
You receive the denial reason. Communicate to client or resubmit with changes.
Rush flag If the schedule change is with less than 24 hours’ notice, the system automatically applies a rush flag. This may trigger a rush fee for the client. Be aware of this when communicating with clients about last-minute changes.
Tip When submitting a reschedule, always provide a clear reason. “Client requested” is acceptable, but more detail helps the admin team make faster decisions. For example: “Site not ready — concrete pour delayed to next week” is much more helpful.

Cancelling a Project

Project cancellations are handled separately through the Cancel Project page in the Schedule section of the sidebar. This is a more significant action than cancelling a single inspection visit.

Late cancellations If the inspector has already been dispatched or is en route, a trip charge may apply. The admin team will assess this. Encourage clients to cancel as early as possible to avoid fees.
07

The Projects page gives you a searchable, filterable list of all projects in your branch. This is your reference page — where you go when you need to look up a project, check a status, or provide information to a client who calls.

Read-only access As a scheduling assistant, you have read-only access to the Projects page. You can view project details, search, and filter, but you cannot edit project records. If a project needs changes, coordinate with your scheduler or submit the information through the appropriate channel (RFI response, schedule change request, or new intake).

Searching

Search and the 45-day rule When you use the search function, the 45-day filter is bypassed. This means you can find any project by searching, even if it has aged past 45 days and would otherwise be hidden from your normal views. This is useful when a client calls about an older project.

Filtering & Sorting

Project Statuses

Projects move through these statuses. You will see these throughout the portal:

StatusWhat It Means
IntakeJust submitted, awaiting admin approval
ScheduledInspection date is set, waiting for field visit
In ProgressField inspector is currently working on it
Partially InspectedSome inspection items done, more visits needed
Field CompleteAll field work done — with the admin team for review
Ready for CertReviewed and ready for cert/invoice drafting
CertifiedCert package generated and approved — ready for delivery
DeliveredCert + invoice sent to client — project is done
On HoldPaused — in the Holding Pool
Pending RFIBlocked on an open RFI — someone needs to respond
CancelledProject was cancelled before completion
ClosedFully complete, paid, and closed out
ArchivedOld project moved to long-term storage
Branch scoping You only see projects for your branch. This is automatic and cannot be changed. If a client asks about a project in a different branch, direct them to the appropriate scheduler or GOA for that branch.
08

The Holding Pool

The Holding Pool contains projects that have been placed on hold. This happens when:

Projects in the Holding Pool are not forgotten — they still show up in your view — but they are not in the active workflow. Think of it as a parking lot for projects that are temporarily paused.

Your role with the Holding Pool You can view projects in the Holding Pool but you cannot return them to the schedule yourself. If a client says they are ready to proceed, let your scheduler know. The scheduler or admin team will move the project back to active status.

When Projects Go on Hold

Client requests a pause on their project
You submit a Hold schedule change request
Admin approves the hold
Project moves to Holding Pool with On Hold status
Client ready to resume?
Yes
Notify your scheduler → project returns to scheduling
Not Yet
Stays in Holding Pool. Check again later.

Desk Review

The Desk Review page shows projects that are undergoing a post-production, office-based review. Unlike a field review (which requires an on-site inspection), desk review projects are evaluated entirely from submitted documentation.

When a project’s intake is marked as post-production stage with desk review type, it follows a streamlined path:

Desk review tip When submitting a desk review project through Intake, make sure all supporting documents are attached upfront. Since there is no field visit, the admin team relies entirely on what you provide. Missing documents mean an RFI, which delays the project.
09

RFIs (Requests for Information) and escalations are the two communication tools built into the portal. Understanding when and how to use each one is essential.

Agent RFIs — Responding to the Admin Team

Agent RFIs are requests sent to you by the admin team (Jacob). They need specific information to complete a project’s certification. When you receive one, the project’s SLA clock is paused — meaning the faster you respond, the faster the project gets delivered.

Common Agent RFI Requests

Request TypeWhat They NeedWhere to Find It
Missing photosSpecific construction photos that were not in the field reportContact the client or check project files
Permit informationPermit number, issuing jurisdiction, or permit documentThe client’s records or the local permitting office
SOW clarificationQuantity discrepancies or unclear scope itemsVerify with the client what was actually built/installed
Test resultsPSI readings, torque values, or other measurement dataField team records or client-provided documentation
Plan documentsConstruction plans, engineering drawingsThe client’s project files

How to Respond to an Agent RFI

You receive a notification about an open Agent RFI
Open the RFI from the Field Ops → RFIs page
Read exactly what is being requested
Gather the requested information (contact client if needed)
Respond in the portal with the data, documents, or photos requested
Admin reviews your response and resolves the RFI → SLA clock restarts
Tip Be thorough in your response. If they ask for a photo of the foundation drain tile, send a clear photo with a note confirming the location. A vague or incomplete response just results in another RFI, which delays the project further.

Client RFIs — Requesting Information from the Admin Team

You can also create Client RFIs when you need information from the admin team. Common situations:

To create a Client RFI, navigate to Field Ops → RFIs and use the create function. Specify the project and describe what you need. The admin team will see it in their RFI queue and respond.

Escalations

Escalations are for when normal communication channels (RFIs) are not resolving an issue. Use them sparingly — they are a strong signal that something is wrong.

Issue cannot be resolved through RFIs
Open Field Ops → Escalations and create an escalation on the project
Instant notification sent to all responsible parties
Threaded message channel opens (project-scoped)
Communicate in the thread until the issue is resolved
Resolution logged to audit trail
Escalation limits Maximum 5 escalations per project. All escalation activity is logged to the Comm Log and audit trail. Use escalations only when RFIs and normal communication have failed to resolve the issue.
10

One of your unique capabilities as a scheduling assistant is the ability to send certification emails to contacts. This is a Phase 3B feature that allows you to email cert links directly from the portal.

When Certs Are Ready

After the admin team drafts a certification package and the owner approves it, the project reaches Certified status. At that point, the cert is ready to be delivered to the client contact.

Sending a Cert Email

Project reaches Certified status
Cert delivery is triggered (may be automatic or manual)
You can send the cert email to the appropriate contact
The email contains a link to the cert package
Project status advances to Delivered

What the Email Contains

Verify before sending Always verify the recipient email address before sending a cert email. Sending a certification to the wrong contact is a serious issue. If you are unsure about the correct contact, check with your scheduler or the admin team first.
Routing Cert emails are routed based on the account and branch configuration. The system automatically selects the correct contact based on the project’s account-branch settings. In most cases, you simply confirm and send.
Delivery tracking Every cert email is logged in the system. You can see the delivery status on the project detail page. If a client says they did not receive their cert, check the delivery log before resending.
11

This is one of the most important system rules to understand. It directly affects what you can and cannot see in the portal.

What It Is

If a project sits for more than 45 days after its last inspection without being certified and delivered, it automatically transfers to the Triage Team. When this happens, you and your scheduler lose access to the project in your normal views.

Why It Exists

Projects that sit too long become problematic — data goes stale, clients get frustrated, and revenue does not get collected. The 45-day rule is the system’s way of escalating stuck projects so they get resolved.

What Happens at 45 Days

Project reaches 45+ days since last inspection
System auto-transfers project to Triage Team
You and your scheduler lose portal access to the project
Your GOA (branch manager) retains full visibility
Triage team works the project to close-out
Invoice routes back to the originating branch GOA
Loss of access Once a project transfers to triage, it disappears from your dashboard, calendar, and normal project views. You can still find it by searching on the Projects page (search bypasses the 45-day filter), but you cannot take any actions on it. The triage team handles everything from that point.

How to Prevent Triage Transfers

PreventionHow
Respond to RFIs promptlyThe most common reason projects stall is an unanswered RFI. Respond within 24 hours when possible.
Follow up with clientsIf you submitted a project and it seems stuck, check on it. Is the site ready? Is there missing information?
Communicate with your schedulerIf you see a project approaching 30+ days with no movement, flag it to your scheduler immediately.
Watch for Pending RFI projectsThese are actively blocked. If the RFI is addressed to you, respond immediately.
Tip Think of 30 days as your warning threshold. If a project has been sitting for 30 days, you have 15 days to get it moving before it transfers to triage. Be proactive.
12

Before you log off each day, run through this checklist. It takes 5 minutes and prevents things from slipping through the cracks overnight.

#CheckWhy
1All Agent RFIs responded to — no open RFIs waiting for your inputUnanswered RFIs block projects and start the escalation clock. Responding before EOD prevents overnight escalation.
2Schedule change status — check if any requests were approved or denied todayIf a request was denied, you may need to communicate with the client or submit a revised request tomorrow.
3Tomorrow’s inspections — glance at the Calendar for tomorrowAre any sites potentially not ready? Flag issues to your scheduler now rather than in the morning.
4Pending intake submissions — any rejections you have not yet addressed?A rejected intake sitting overnight means the project loses another day. Fix and resubmit if possible.
5Escalation threads — any active escalations you have not responded to?Escalations are high-priority. Unresponsive participants reflect poorly on your branch.
6Cert emails — any certs ready to send that you have not sent yet?A cert sitting unsent is a delivery delay. Send before you leave if possible.
Good habit If you can clear even one pending item before logging off, do it. Morning-you will thank afternoon-you. A clean dashboard at end-of-day means a smooth start tomorrow.
13
TermDefinition
SOWScope of Work. The list of specific inspection items for a project. Each SOW line is a product/service that gets inspected and billed. Example: “Blower Door Test × 1” or “Insulation Inspection × 3 units.”
ABSoWAccount-Branch Scope of Work. The standard SOW template for your account and branch. Defines what products/services are available when you submit intake. Individual project SOWs are derived from the ABSoW.
PSoWProject Scope of Work. The specific SOW for an individual project — what is actually being inspected on this particular job.
RFIRequest for Information. A formal request for missing data. Agent RFIs come from the admin team to you. Client RFIs go from you to the admin team. Agent RFIs pause the SLA clock while open.
SLAService Level Agreement. The commitment to deliver cert + invoice within 3 business days of final inspection. Tracked automatically. RFI response time directly affects SLA performance.
Cert PackageThe certification document(s) delivered to the client confirming their project meets building code requirements. Generated as PDF. You can send these via email to contacts.
BranchA subdivision of a client account. Your portal access is scoped to your branch — you only see projects within your branch. Large builders may have multiple branches (e.g., “Valley Park” and “Mount Pleasant” under the same account).
AccountA client company. Each account can have one or more branches. Your branch belongs to an account.
GOAGeneral Office Admin. Your client-side branch manager. Has broader visibility than schedulers and assistants. Receives invoices and escalation notifications. Retains access when projects transfer to triage.
SchedulerYour direct lead on the client side. Manages the branch calendar, approves schedule changes, and oversees day-to-day scheduling operations. You support this person.
TriageProjects that exceeded the 45-day threshold. Handled by a dedicated triage team to close out. You lose access when a project transfers to triage.
Trip ChargeA fee charged when the field inspector arrives on site but cannot complete the inspection (e.g., site not ready, late cancellation). Tracked and invoiced separately.
Rush FlagAutomatically applied to schedule changes made with less than 24 hours’ notice. May trigger additional fees.
Desk ReviewA post-production review performed entirely from submitted documentation (no field visit needed). Faster path to certification when the construction is already complete.
Holding PoolThe queue of paused projects. Projects go here when a Hold request is approved. They stay until the hold reason is resolved.
EscalationA high-priority communication channel opened on a project when normal RFIs are not resolving an issue. Notifies all responsible parties instantly. Maximum 5 per project.
14

Portal Access

ItemValue
Your portal URLunlikely.report
Your rolescheduler_assistant
ScopeBranch-scoped (you only see your branch’s projects)
LoginCredentials provided by your scheduler or admin

What You Can and Cannot Do

You Can

  • Submit new projects via Intake
  • View the Calendar (your branch)
  • Submit schedule change requests
  • Submit project cancellation requests
  • View projects (read-only)
  • View the Holding Pool
  • View the Desk Review queue
  • Respond to Agent RFIs
  • Create Client RFIs
  • Create and participate in escalations
  • Send cert emails to contacts
  • Search for any project (bypasses 45-day filter)

You Cannot

  • Edit project records (read-only access)
  • Approve schedule change requests
  • Approve intake submissions
  • Draft or approve certifications
  • Draft or approve invoices
  • See projects outside your branch
  • Access projects that transferred to triage (except via search)
  • Return projects from the Holding Pool

Who to Contact

SituationContactMethod
Need to schedule or reschedule an inspectionYour SchedulerDirect communication + schedule change request in portal
Responding to a request for missing dataAdmin Team (Jacob)Agent RFI response in portal
Question about cert status or inspection resultsAdmin Team (Jacob)Client RFI via portal
Branch-level issue or billing questionGOA (branch manager)Direct communication or escalation via portal
Issue that RFIs cannot resolveAll partiesEscalation via portal
Portal access problem or system issueDustin (Owner)Direct message via your scheduler

Daily Priority Order

  1. Respond to all open Agent RFIs
  2. Review and respond to active escalations
  3. Check schedule change request statuses
  4. Review the Calendar for today and tomorrow
  5. Submit any new intake requests
  6. Send pending cert emails
  7. Check for rejected intake submissions and resubmit

Key Thresholds

ThresholdValueWhat Happens
Cert + invoice SLA3 biz daysAfter final inspection — clock pauses during open RFIs
Triage transfer45 daysAuto-transfer to triage team — you lose access
Rush flag< 24 hrsSchedule change with less than 24hr notice — may trigger fee
Max escalations5 per projectHard limit on escalation count
RFI escalationDay 1→3→5→7+Automatic reminder cadence for Agent RFIs sent to you

Your Sidebar Navigation

SectionPagesWhat You Do There
DashboardDashboardYour home screen — check counts, upcoming inspections, pending items
ScheduleIntakeSubmit new projects via the 5-step wizard
CalendarView your branch’s inspection schedule
Schedule ChangesSubmit reschedule, cancel, hold, or add-inspection requests
Cancel ProjectSubmit a full project cancellation request
ProjectsProjectsSearch and view your branch’s projects (read-only)
Holding PoolView paused projects
Desk ReviewView projects in desk review status
Field OpsRFIsRespond to Agent RFIs, create Client RFIs
EscalationsCreate and participate in escalation threads

Emergency Procedures

If the portal is down Contact your scheduler immediately. Do not attempt to use any backend systems. If urgent communication is needed, use your normal phone/email channels until the portal is restored.
If you sent a cert email to the wrong contact Contact your scheduler and the admin team (Jacob) immediately. Do not attempt to recall or resend on your own. Every delivery is logged, and the correction needs to be tracked properly.
If you are unsure about something Ask your scheduler. There is no penalty for asking questions, especially during onboarding. It is far better to ask than to submit something incorrectly. Your scheduler is your first point of contact for any uncertainty.