01Requirement
↓Network handoff02Evidence submitted
↓net-handoff-r1.xlsx03Approved · E. BrooksHard gate
Multi-site deployment control
Every site ready before dispatch—or the truck does not roll.
ServSignal holds readiness requirements, evidence, and owners against every site, blocks dispatch until hard gates clear, then keeps the installed technical record as a permanent passport.
- Contributors are never billed as full seats
- Customer owns the record
- AI assistance is optional
Sites requiring attention
| Site | Ready | Dispatch |
|---|---|---|
NRG-0142Paramus Route 17 | 85% | Blocked |
NRG-0117Danbury Fair | 78% | Blocked |
NRG-0203Stamford Broad | 91% | At risk |
NRG-0088Yonkers Central | 96% | Needs review |
NRG-0151Nashua Amherst | 100% | Dispatchable |
Illustrative synthetic workspace. No customer data or performance claim is represented.
How ServSignal works
- 01Define readiness
Product UI is the proof
Every requirement, blocker, and approval stays attached to its site.
Blocker queueWave 3
- IDF-2 uplink not releasedHard gate
- Electrical permit missingOverdue
- Rack elevation unreviewedReview
- Manager training in progressSoft risk
Never cleared by a rising percentage
- ✓14 of 14 units reconciled
- ✓Four required tests passed
- ✓Approver authorized to sign
PassportAssetsAudit
The permanent record
The passport is the part that lasts.
Programs close. The estate does not. Every accepted site keeps its interfaces, assignments, evidence, and verification history in one record that survives the rollout that created it.
Open the asset registry- 01Interface and IP assignment records
- 02Installed serials and space assignments
- 03Frozen pre-dispatch readiness snapshot
- 04Required test results and evidence
- 05Revision-bound acceptance history
- 06Verification freshness and warranty exposure
Control by construction
Deployment control with visible limits.
Deterministic gates
Dispatchability is the conjunction of named controls, stamped with its last evaluation time. There is no weighted score or silent override.
Evidence with provenance
Every value records its source, author or extractor, timestamp, and verification method. AI extraction proposes; it never confirms.
Scoped collaboration
Site contacts, vendors, and field contributors see only what their assignment and field policy allow.
Revision-bound acceptance
Signing freezes a revision. Corrections create a new revision that references the accepted record instead of rewriting it.
Questions, answered
Know the boundary before you roll out.
Does a rising completion percentage ever unblock a site?
No. Completion is descriptive; dispatchability is a deterministic result. Every required hard gate must pass or carry an authorized, visible waiver before a site can become dispatchable.
What happens to readiness once the technician arrives?
ServSignal freezes the trusted pre-dispatch snapshot, then opens the field package for reconciliation, tests, deviations, and evidence. The installation record keeps the original readiness decision intact.
Who pays for site contacts and assigned vendors?
Plans are based on the active estate under management. Scoped site contacts, field contributors, and assigned external collaborators can complete their work without a full administrative seat.
Which controls are enforced in production?
Authentication, tenant scoping, resource authorization, server-side transitions, protected downloads, and revision-bound acceptance are implemented in the application. Provider-dependent capabilities are activated only after their configuration and evidence gates pass; the security page records those boundaries without claiming certification.
Run one wave end to end
Put readiness control into production.
Start with a bounded program and the complete readiness-to-acceptance chain. Assigned contributors never require a full administrative seat.