FSD
FSD OS
Internal staff only
Forgot your password? Ask the founder or admin to reset it.
FSD
Two-factor check

Scan this code with Google Authenticator or Microsoft Authenticator on your phone. You only do this once.

Two-factor setup code
Can't scan? Enter this key instead
FSD
FSD OS
Daily
Today: action queue Founder report Sites
Strategy
Portfolio Cash
Team
People and logins How it works

Today: what to fix first

Connecting
Example data. This is a made-up day to show how the queue works. Nothing here is real.
No field reports in the last 14 days yet. Reports appear here the moment a site manager presses send.

Action queue

Every problem a site manager reports becomes one line here, ranked by cost and urgency. Work from the top. Press Start when someone owns it and Done when it is fixed.

Field visit route

Ranked by the total weight of today's open problems at each site.

Sites that have not reported

Recurring problems, last 7 days

Founder daily report

Connecting
Example data. Nothing here is real.

Fill rate, last 14 days

Guards present or covered, as a share of guards required. Dashed line: September, before the system.

Why guards left, last 14 days

Highest-risk sites this week

Decisions for the founder

Sites today

Connecting

All sites, today's reports beside September's shortage. Sort by any column.

SiteContract guardsRequired todayPresent + coveredUncoveredExposure EGPOpen issuesLast reportSept shortage
Contract portfolio, September 2026

Keep, fix, or exit

Every contract classified on its own numbers. Finance sets the all-in monthly cost per guard (salary, housing, food, uniform, share of overhead); it is saved for everyone.

ClientContractInvoicedGap %ShortageKPIEquip.TermsGuardsPer guardEst. marginClass
Keep and invest: gap under 8%, terms 30 days or less Keep, fix terms: gap under 8%, terms over 30 days Fix staffing: gap 8 to 30% Critical: gap 30% or more, or negative margin
Cash, September 2026

Receivables against payroll

Each client's payment terms tie up that many days of invoices. This is why the company cannot pay guards on the 5th today, and what shorter terms on new contracts would free.

Invoiced value by payment terms

What shorter terms would free

30days

Pricing gate: no new contract above 30 days, target 15.

Admin and founder only

People and logins

Create a login for each site manager and each internal staff member. Passwords are shown once when created: copy them and hand them over in person. Internal staff set up two-factor on their first sign-in.

New site manager

Sites this manager reports for

New internal staff

Everyone with a login

NameRoleLoginSitesStatus

Activity log

The last 100 changes: reports filed, issues closed, logins created and changed.

WhenWhoWhatItem
For everyone on the team, interns included

How FSD OS works

Two apps share one secure database. Site managers use the field app on their phone. Internal staff use this OS. The moment a manager presses send, the OS turns the answers into ranked problems for operations and daily numbers for the founder.

1. Field appSite manager signs in with a code and files the shift report. About 3 minutes.
→
2. DatabaseSaved instantly. Each manager can only file for their own sites.
→
3. Rule bookEach answer is checked against the rules below. A rule that fires becomes an issue with a score, owner and deadline.
→
4. Action queueOperations, HR and finance work their issues from the top, marking Started and Done.
→
5. Founder reportFill rate, money at risk, exits, incidents and trend, written as one paragraph.

A normal day

08:00Day shift starts. Site manager counts who is present.
by 11:00Site manager files the day shift report. Late sites appear under "not reported".
11:30Head of operations works the queue top down: calls first, then assigns, then plans the visit route.
12:00 to 18:00Field visits in route order. Mark issues Done as they are fixed.
by 23:00Night shift report filed.
23:30Head of operations checks night items marked Call now.
Next morningFounder reads the Founder report. Two minutes.

Who sees what

Site managerField app only, own sites only. Never sees the OS.
Head of operationsQueue, founder report, sites, money at risk.
HR managerQueue (HR, payroll, housing issues under Mine), founder report, sites. No contract money.
Finance managerEverything above plus Portfolio and Cash; sets cost per guard.
FounderEverything, plus People and logins and the activity log.

Security, in plain words

  • Every table in the database has rules saying exactly who may read and write it. The rules are enforced by the database itself, so a bug in the app cannot leak data.
  • Internal staff must pass a two-factor check (a 6-digit code from a phone app) or the database shows them nothing.
  • Site managers can only file reports for their own sites, for today or yesterday. They cannot see other sites, any money, or the OS.
  • Nobody can sign up. Every login is created on the People page by the founder or admin.
  • Every report filed, issue closed and login changed is written to the activity log.
  • The OS signs out after 60 minutes without activity.
  • The app loads no outside code. It runs only the files in this project.

What the field form asks, and why

SectionQuestionWhy it is askedFeeds rule

Rule book

Generated from the same rules the queue uses. Score 80 or more lands in "Call now", 60 to 79 in "Today", lower in "This week". A rule that fires at the same site on 3 of the last 7 days gets 10 extra points and a "recurring" tag.

RuleFires whenScoreOwnerDeadlineIf it keeps recurring

How money at risk is counted

Each uncovered guard costs one day of that site's contract price per guard, because that is what the client deducts. The founder report adds these up for the month and projects the month-end total against September's real shortage deduction.

Setup and next steps

Tick a step when it is done. Ticks are shared.