0Open actions
0Secure files
0Active milestones
0Unread alerts
Current actions
Recent files
Timeline
Start here
What should your company provide?
Relystra is looking for evidence of how the work actually happens: the process, real examples, systems involved, volume, measurable baseline, and the people who own decisions. For every item below, we explain why it matters, where to find it, and what to do if it does not exist.
Use representative—not exhaustive—evidence.Three to ten normal examples usually teach more than a giant data dump.
Redact what Relystra does not need.Remove unnecessary customer PII, secrets, credentials, payment information, and unrelated sensitive fields.
Missing is useful information.If an SOP, KPI, systems map, or runbook does not exist, choose “Build with Relystra.” That gap can become part of the work.
Private upload
Share a file securely
Use this for current-state evidence or a specific Relystra request. Select an item above first when possible so the portal can automatically mark the correct requirement as uploaded.
Scope rule: Assigning a portal task to Relystra coordinates existing work; it does not expand signed scope or create a binding deadline.
Portal dates are planning dates unless a signed agreement expressly identifies a binding deadline or service level.
Measurement rule: Movement in a metric does not automatically prove Relystra caused the change. Baselines, measurement windows, assumptions, exclusions, and attribution should be documented.