Daily quotas: guests vs signed-in users
Cost Analysis and Project Plan Analysis share a single daily counter. The limit depends on whether you are signed in:
- Guest (Logged Out): Shared tools (Cost Analysis + Project Plan Analysis) = 1 submission per 24 hours.
- User (Logged In): Shared tools (Cost Analysis + Project Plan Analysis) = 3 submissions per 24 hours.
Internally, the app keeps one shared counter per user identifier (User ID when signed in, key when logged out). Any successful submission increments this shared counter.
User Status | Shared Tools | Total Daily Limit
-----------|-----------------------------------------------|-------------------
Guest | Cost Analysis + Project Plan Analysis | 1 Submission
User | Cost Analysis + Project Plan Analysis | 3 Submissions
If / Then rules for daily validation
The backend enforces the quota, and the UI surfaces the current status and disables buttons when a limit is reached. The core rules are:
- IF a guest user has already submitted a Cost Analysis, THEN the Project Plan Analysis submit button is disabled for 24 hours.
- IF a logged-in user has performed 2 Cost Analyses and 1 Project Plan Analysis, THEN they have reached their limit of 3 and cannot submit any further requests today.
- IF any submission (Cost or Project Plan) is successful, THEN increment the shared counter assigned to that specific identifier.
The indicator above the tools shows the current count and whether you are in the guest tier or signed-in tier. When you hit your limit, the affected buttons become disabled and the UI will suggest signing in (or trying again after 24 hours).
Getting started in 60 seconds
Open the session
If you are using the free daily allowance, you can run 1 report per day without signing in. To unlock 3 reports per day and enable Reports Library and saved history, use Login / Register and sign in first.
Use
Advisor to run a new analysis. Enter a prompt, optionally attach a project file, then click
Submit.
The response streams into the chat area. If the server returns downloadable artifacts (PDF, DOCX, ZIP), they appear under
Downloads.
- Open Advisor from the left menu.
- Type a concrete goal (example: “Review my project plan, score it, and list top risks with mitigation”).
- Attach a file only when the analysis depends on that document.
- Submit, then wait for the streamed report to finish.
How to write prompts that produce better reports
The fastest way to get a high quality report is to specify scope, output format, and decision criteria.
When possible, provide context such as delivery model, timeline horizon, team size, and major constraints.
- Scope: what to evaluate (schedule, resourcing, risks, governance, delivery readiness).
- Outputs: what you want back (score, grade, executive summary, risk register, action plan).
- Constraints: budget, due dates, staffing, tools, compliance requirements.
- Style: concise executive view vs deep diagnostic view.
Example prompt: “Score this plan. Provide a 10 item risk list with severity and mitigation. Highlight schedule compression and missing dependencies. End with a prioritized 14 day action plan.”
File attachments: what to upload and what not to upload
Upload only documents that materially impact the analysis such as a project plan, a backlog export, a charter, a BRD, or a RAID log.
Keep sensitive secrets out of uploads. If your file contains credentials or keys, remove them before uploading.
- Recommended: PDF, DOCX, XLSX exports, CSV exports, and structured text files.
- Large files: the platform may take longer to process, and streaming will start after ingestion completes.
- Personal data: avoid uploading personal identifiers unless required for your legitimate workflow.
Streaming behavior: why you see partial output
When the server streams, the report arrives in chunks to improve time to first result. During streaming you can scroll, copy text, and wait for the final “Completed” note.
If a run returns a non-stream JSON response, it will still be displayed and may include a downloads section.
- If the output looks incomplete, wait for the completion note.
- If you navigate away and come back, the streamed output remains in the chat log for that page session.
- Use the Reports Library for durable, account-scoped access to prior runs.
Reports Library: what it is and how it works
Reports Library stores prior analyses under your user account. A “Plan” is the logical project key, and each analysis is saved as a “Version”.
This enables you to reopen a report without rerunning analysis, compare versions over time, and track grading trends.
- You must be signed in to access Reports Library.
- Click a Plan to load its Versions.
- Click a Version to reopen its report in the Advisor view.
- Use the search box to filter by project key or filename.
Grades and scores: what “96.7%”, “A”, and “Good” mean
A score is a numeric measurement expressed as a percentage. A grade may be a letter (A, B, C) or a qualitative label (Excellent, Good, Needs Work).
Depending on the report, you may see one or more of these. The Library cards show the best available value for quick scanning.
- Percentage: a precise score used for trend tracking.
- Letter grade: a categorical mapping for executive reporting.
- Label: a human-friendly summary (example: Good).
Authentication: Login, Register, Logout
Authentication uses ASP.NET Identity cookies. When signed in, your library data is user-scoped, and the Reports Library menu item is enabled.
If you log out while viewing the library, the UI automatically returns you to Advisor to prevent user-scoped calls from failing.
- If “Reports Library” is disabled, sign in first.
- If you see an access prompt when opening the library, complete sign in and the library will load.
- If authentication fails, verify username or email and password.
Troubleshooting: common issues and fixes
If something does not load, the page will show an in-app modal instead of a browser alert. Most issues are caused by authentication, network conditions, or a server error response.
- “Sign in to access Reports Library”: you are not authenticated. Use Login / Register.
- “Failed to load plans”: check server logs for the library endpoint and confirm the API path is reachable.
- “Failed to load version”: the version may not exist or is not owned by your user. Refresh and retry.
- Empty results: run at least one analysis so a plan and version exist in storage.
- File not shown: reselect the file and confirm the filename updates next to “Attach file”.
Keyboard shortcuts and UI tips
Use productivity shortcuts to work faster. The layout is optimized for both desktop and laptop screens, and long help content scrolls inside this panel.
- Ctrl + Enter: Submit the prompt from the text box.
- Escape: Close open modals (auth modal or error modal).
- Arrow keys: Navigate testimonials when focused on the carousel.
- Theme toggle: top-right button switches light and dark themes.
Privacy and data handling
Reports Library is designed to be user-scoped. Only authenticated users can list and open their own plans and versions.
Store only what is necessary for your workflow and avoid including secrets or credentials in uploaded files.
- Plans and versions are filtered by authenticated user ID.
- Requests without a valid identity do not return library data.
- Operational logs may capture error details for reliability and support.
