Annapolis-built visit readiness for cleared teams

Clear the meeting before it hits the calendar.

Type the email of the person you need to meet. Severn Signal charts their site, finds the right POC, watches the deadlines, and tells you when you're Cleared to Dock — without turning your FSO into a one-person email crab pot.

That's it — the crew picks it up from there. No classified details here or anywhere in the app.

Open the full Helm Launch Safe Harbor TEM
Cleared to Dock Tide Clock Safe Harbor TEM
Annapolis at golden hour: the Maryland State House dome and St. Anne's spire on the skyline, Thomas Point Shoal Lighthouse, the Chesapeake Bay Bridge, and a sloop under sail on the Severn A layered travel-poster style illustration. A dark sloop with cream sails heels gently in the foreground; the Annapolis skyline stands in silhouette to the left; Thomas Point Shoal Lighthouse rises on screwpile legs from the water; the Bay Bridge and a low sun sit on the horizon, with the sun's path glinting on the water.

The promise

Severn Signal

Severn Signal makes the compliant path the easy path. If the cleared visit is ready, it is Cleared to Dock. If it is not, convert only that occurrence to an unclassified Safe Harbor TEM — and keep the cleared visit workflow moving.

Everything the cleared visit needed, in one place

Not another calendar link. A visit-readiness system.

Calendars only know time. Severn Signal knows whether the visit request is submitted, acknowledged, covered by the right window, routed to the right POC, and safe to finalize.

Sail Plans

One-time or recurring cleared-visit workflows with calendar holds, room needs, visitors, host POCs, visitor FSOs, and readiness gates.

Harbor Charts

Each company/site's process on record: visitor-control mailbox, room scheduler, escort rules, lead time, computer rules, and last-verified date.

Season Pass tracking

Actual VR start/end dates, shorter-than-expected windows, renewal reminders, and whether every upcoming occurrence is covered.

Dockmaster discovery

A magic-link routing flow that lets any recipient say "I'm the right POC," forward to the correct Dockmaster, or convert to a TEM — no blame, no dead ends.

Safe Harbor TEM

When a VR misses the tide, convert only that occurrence to an unclassified Technical Exchange Meeting, pass the scope check, launch an approved bridge, and keep the cleared visit open.

Secure Logbook

Manual-first, consent-first notes for sensitive unclassified meetings: decisions, RFIs, risks, action items, redaction state, and no audio retention by default.

From calendar hold to cleared-to-dock

A helpful path forward, even when security says "not yet."

  1. Draft Sail PlanRequester enters purpose, host site, visitors, room needs, desired window, and known POCs. A calendar hold protects the slot.
  2. Find the DockmasterSevern Signal routes a POC discovery link to the host business/security side until the right person claims it.
  3. Rig the RequestGenerate the visit-request checklist, packet language, missing fields, and FSO handoff.
  4. Watch the Tide ClockLead time, VR validity, room readiness, host acknowledgement, and recurring renewal dates are tracked automatically.
  5. Cleared to Dock or Safe HarborSend the final invite only when ready; otherwise convert just this occurrence to an unclassified TEM and keep momentum.

A real thread, anonymized

Fifteen emails. Eight days. One meeting.

Drawn from a real coordination thread between a visiting team, their host, and two security offices — details changed, pain intact. Every step below is a piece of missing shared state: a hosting rule nobody knew, an identifier nobody had on hand, a name without contact details, a "successful" submission the customer's process doesn't accept. Severn Signal reduces the entire sequence to two human decisions.

How it actually went

  1. The visiting team's security lead writes to the host facility: a cleared meeting is on the books in three weeks — where should the visit requests go, and what's the facility's cage code?
  2. The reply opens with an obstacle: subcontractors may not host visits in this building, so a prime-side sponsor must be named. It also questions why the cage code is needed at all.
  3. The visitor side explains its own security process requires the code, and volunteers to chase down a prime point of contact.
  4. The cage code arrives — along with a warning that the visit request must come through an approved method.
  5. The requesters are asked directly: who on the prime side can own this visit?
  6. The usual prime-side lead turns out to be on extended leave. A backup is reached; a name is promised shortly.
  7. The visitor side notes it can't open its internal certification case until that name lands.
  8. The thread closes for the holiday weekend. The request sits.
  9. Five days on, the visitor side circles back — still waiting on the POC name.
  10. The name is finally confirmed, nearly a week after the first email.
  11. The visitor side offers to relay it to the host's security officer.
  12. The relay goes out, with a note that the certifications will follow by fax.
  13. Then the follow-up: a name alone can't go on the visit request — the form also needs the POC's email address and phone number.
  14. Two days after everything seems settled, word comes back: the requests did arrive through the official system — but the facility's internal process still requires fax or password-protected email.
  15. One final wrinkle: that channel could only certify the lower access level, and the meeting requires the higher one. Everything is re-sent by fax.

With Severn Signal

  • Hosting rules are known before the invitation goes out. The Harbor Chart records that this facility requires a prime-side host — so the right sponsor is named on day one, not discovered a week in.
  • Cage code, channels, and lead times live on the site card. Structured fields the visitor's security team can see from the start. Nobody has to ask, and nobody has to justify asking.
  • POC discovery routes itself. The claim link hops past the on-leave lead to the backup, and claiming captures email and phone in the same click — the "sorry, I also need her contact info" email is never written.
  • Autopilot does the checking-in. Waiting states re-nudge every two business days. Long weekends don't stall the visit.
  • "Submitted" never impersonates "accepted." The site card records which transmission channels the host's customer actually accepts — if it's fax or password-protected email only, the plan says so before anyone submits, and readiness stays red until the VR went through an approved channel.
  • Access level is a gate, not a day-of surprise. The plan records which accesses the meeting requires, and readiness checks that the certs passed cover that level — because some channels can only pass a lower one.
  • One shared plan, no human message bus. Prime security, visitor security, and the requester see the same checklist. Nothing is relayed; everything is entered once.

Result: two human actions — the POC clicks "that's me," and the visitor's security team submits the VR.

Interactive prototype

Open the Helm

Create a Sail Plan, calculate readiness, route the Dockmaster discovery link, export the visit packet, place a hold vs. final invite, convert an occurrence to Safe Harbor TEM, and write a Logbook note. Entries persist locally in your browser only.

Plan details

1 · What & where

Cleared visits track the visit request; a TEM from the start skips VR checks.

2 · When

3 · Who

The certs must cover these — some channels can only pass a lower level than the meeting requires.
Readiness confirmations
Calendar state
A hold protects the slot with a neutral title. The final invite unlocks only at Cleared to Dock / Ready to Launch.

Dockmaster discovery

Send a routing link instead of a blame-y email chain. Whoever receives it can claim it, forward it, or suggest a TEM. (Simulated in this prototype.)

Recipient view — simulate:

No routing activity yet.

Got a "who is the POC?" email? Draft your reply

The Chart Room

New aboard? Here's the vocabulary.

Every Severn Signal term maps to a plain cleared-industry concept. Flavor on the surface, compliance underneath.

Sail Plan
A visit workflow — one meeting, everything it needs to be ready.
Standing Sail Plan
A recurring meeting workflow (weekly, biweekly, monthly, quarterly).
Season Pass
The VR / visit-authorization validity window that actually got approved.
Tide Clock
Lead-time and renewal countdowns, so nothing expires silently.
Dockmaster
The correct host business or security POC for the visit.
Harbor Chart
Your directory of each company or site's process and POCs.
Crab Trap
A blocker: missing POC, unconfirmed room, unsubmitted request.
Signal Flags
Readiness statuses, from Draft to Small Craft Advisory.
Cleared to Dock
Every essential is confirmed — safe to send the final invite.
Safe Harbor TEM
An unclassified Technical Exchange Meeting used as a compliant fallback for one occurrence.
Logbook
Secure, consent-first meeting notes with a redaction state.
Ego Alley
Annapolis's famous boat-parade channel. Here: where email chains go to circle.

Compliance posture

Pro-security. Anti-chaos.

Severn Signal does not grant access, bypass security, or replace official systems. It helps the authorized people gather the right details, route the request, track deadlines, and choose a compliant fallback when a cleared visit is not ready — so security teams receive complete, timely, properly routed requests.

No classified content in the app.

No classified content in calendar invites.

FSO-controlled packet handoff.

Official security systems remain authoritative.

Safe Harbor TEM is unclassified-only.

Severn Signal coordinates readiness; it never grants access.

Early access · limited berths this season

Join the founding crew.

Severn Signal is in private beta with a small group of cleared-industry teams. Founding crew members shape the product — and lock in preferred terms when pricing arrives at general availability.

Solo FSO

Founding Crew

Packet builder, VR reminders, POC discovery, Safe Harbor TEM, personal Logbook.

Small Contractor

Private Beta

Shared Sail Plans, Harbor Charts, recurring Season Pass tracking, team approvals, templates.

Host Portal

By Invitation

Visitor-control intake, room rules, verified POC routing, policy pages, audit evidence, API readiness.

Request a berth

A short note about your team and the visits you coordinate is all it takes. Berths are limited while we work closely with each crew.

Ready to stop the email crab walk?

Make the compliant path the easy path.

Start with a Sail Plan. If the visit is ready, clear the dock. If not, convert one occurrence to Safe Harbor TEM and keep momentum.

Open the Helm