Organizations / Companies · Planned
Randomized scheduling and operational oversight.
A professional workspace for authorized administrators, groups, departments and evidence workflows. Your organization's records remain in systems you control.
The random scheduling and accountability service is free. Test kits and any laboratory testing are purchased separately.
Planned, not yet available
The organization workspace is being designed and is not offered today. Nothing on this page is a service you can sign up for yet. The console shown above is a prototype.
Planned capabilities
Built for program administration
Neutral, auditable process tools. Status values describe where an assignment is in your process, not a medical or personal judgment.
Randomized assigned testing days
Frequency, eligible days, time zone and selection rules are set per program. Days are chosen in advance on your organization's node, with a verifiable commitment and no rerolls.
Departments and programs
Organize participants by department and program, each with its own written, versioned policy. Department administrators see only their scope.
Process statuses
Assigned, acknowledged, submitted, awaiting review, completed, pending, inconclusive and disputed. Corrections are recorded, never silently overwritten.
Exceptions queue
Missed acknowledgements, disputes and other exceptions are listed for an authorized reviewer. There are no automatic sanctions.
Audit events and reports
Policy approvals, assignment creation, reviews and record downloads are logged. Disclosure reports show which role can access which fields, and who did.
Records leave only from your node
Authorized records can be downloaded as CSV or JSON from your organization's server, where lawful. P in the Cup has no access to the source data.
Planned workflow
How it works for you
-
Provision your node and roles
The organization owner sets up its own server, including TLS, backups, retention and key custody, then invites administrators and assigns roles and departments.
-
Publish a program policy
A program administrator writes the policy, sets frequency and eligible days, and records version approval. Participants acknowledge the policy and data notice before any assignment.
-
Assignments are generated in advance
Your node selects assigned testing days for each period using secure randomness and a verifiable commitment. Administrators do not hand-pick people or dates, and overrides are audited.
-
Acknowledge, submit, review
Participants acknowledge an assignment, follow the instructions and submit status if the program authorizes it. Reviewers resolve each item, and every step is recorded in the audit log.
Two interfaces
Administrator console and participant view
Administrator console
- Dashboard: assigned, acknowledged, awaiting review, exceptions
- Programs, departments and policy versions
- Assignment queue with department filter
- Reports and audit events
- Role, access and node settings
Participant view
- Assigned testing day
- Acknowledge
- Instructions
- Status, and submission if authorized
- Policy and data notice
The organization workspace is deliberately plain and work-style throughout, for administrators and participants alike.
Planned roles
Least-privilege access
Each role sees only what its job requires. Real identities are hidden from administrators who are not authorized to see them, and there is no operator back door.
| Role | Purpose |
|---|---|
| Owner | Provisions the organization's node, backups, retention, TLS and key custody; names the first administrators. |
| Privacy / security admin | Sets access rules, retention and disclosure reports; reviews who accessed which fields. |
| Program admin | Writes and versions program policies; configures frequency, eligible days and time zone. |
| Department admin | Manages participants and assignments within one department only. |
| Reviewer | Narrow access to resolve submissions and exceptions assigned to them. |
| Participant | Sees their own assignments, instructions, status, policy and data notice. |
| Auditor | Read-only access to audit events and reports. |
Data ownership · Planned
Your records stay on your organization's node
- Customer-owned node. Rosters, assignments, submissions and audit records are planned to live on a server your organization operates, on its own domain, with its own storage, keys, logs, backups and outbound mail.
- No central participant database. P in the Cup distributes the software. It does not intend to hold names, contact details, rosters, schedules or results, and sends no default telemetry from your node.
- Honest limits. Software updates and network traffic still carry risks that your organization must manage, such as verifying signed releases. We do not claim zero metadata or zero breach risk.
Anonymous mode is limited to aggregate voluntary programs
Anonymous-to-administrator participation is planned only for separate, voluntary programs that report aggregate totals, and only when the group is large enough. It is never available for an identified employee testing process. If your program identifies participants, participants are told so, and it is not described to them as anonymous.
Software does not make a program compliant
Professional or regulated testing may require an accredited laboratory, chain-of-custody procedures, review by a medical review officer, written notices, a lawful written policy and compliance with the laws where you operate. P in the Cup is scheduling and record-keeping software. It does not collect specimens, verify results or make any program compliant with any law or testing regime. Get independent legal advice before starting any workplace program.
Questions
Organization FAQ
Where are our participants' records stored?
In the planned design, on a node your organization runs and controls. P in the Cup does not intend to store rosters, assignments or results on its own servers.
Can participants be anonymous to the employer?
Not in an identified testing program. Anonymous participation is planned only for separate voluntary programs that report aggregate totals for large enough groups.
Does using P in the Cup make our program legally compliant?
No. Laboratory testing, chain of custody, medical review, notices and policy requirements depend on your setting and jurisdiction. The software alone never makes a program compliant.
Can an administrator choose who is tested on a given day?
No. Assigned testing days are generated in advance by your node under the program's rules. Any override is recorded in the audit log.
What does it cost?
The random scheduling and accountability service is free. Test kits and any laboratory testing are purchased separately. Your organization also runs and pays for its own node hosting.
Next step
Help shape the organization workspace
A contact address will be published here before launch.
Page last updated