Hitt Hosting SE Help Center

Every project is created with an industry pack that pre-seeds its phases, gate checklists, terminology, and starter content.

1. Sign in and open the Portal (/portal) — your project list loads under "All Missions" (the noun follows your pack: Programs, Devices, Projects).
2. Click "+ Create New Mission" (or "+ Create Your First Project" on the empty state).
3. Enter the project name (required) and an optional description.
4. If your company has more than one industry pack enabled, pick the vertical in the "Industry" dropdown — this sets the methodology, phases, terminology, and seeded gate criteria (for example Aerospace / SMAD, Defense MBSE / DoD 5000.02, Medical Device / IEC 62304).
5. Optionally choose a project type template (for example a LEO Earth Observation mission or Tactical UAS program) to pre-load realistic content.
6. Click "Create Mission" — phase gates and starter requirements are seeded automatically, and the new card appears at the top of the list.
7. Switch between projects any time with the selector in the portal header (search, pin favorites, or "+ Create New Mission" from its footer).

Tip: Pack choice is per-project, not per-account — one company can run aerospace, defense, and pharma projects side by side.

Two search surfaces cover everything: the quick search bar for the current project and the cross-surface Search page.

1. Press Cmd+K (macOS) or Ctrl+K (Windows/Linux) anywhere in the portal to open the "Search mission..." bar scoped to your current project.
2. Type a requirement number, risk title, page name, or keyword and pick a result to jump straight to it.
3. For a deeper sweep, open Search in the sidebar (/portal/global-search) and type at least 2 characters.
4. Results are grouped into "Requirements", "Risks", "Documents", and "Pack-table rows" so you can see exactly where each hit lives.

The Export / Import page packages a full project export in the format your downstream tools expect.

1. Open Export / Import in the portal (/portal/export).
2. Under "Export Mission Data", choose an "Export Format": JSON (best for backup and re-import), CSV (flat tables for spreadsheets), Excel (.xlsx workbook), Both (JSON + CSV in one package), or ReqIF (for DOORS NG interoperability).
3. Start the export and watch the Export Progress indicator.
4. Review the Export Summary and download the package (multi-file exports come as a ZIP).

Tip: Individual tables (requirements, risks, registers) also have their own CSV export buttons if you only need one dataset.

The Requirements register is where you define, edit, and bulk-manage every requirement in the project.

1. Open the Requirements hub in the sidebar and select the "Requirements" tab.
2. Click "+ Add Requirement" and enter a Req Number (for example REQ-001) and Title.
3. Set the Type (Functional, Performance, Interface, Constraint, Derived), Priority (Low to Critical), and Status (Draft, Approved, Verified).
4. Add a Description and Rationale, then click "Save Requirement".
5. Filter with the search box and the status/type/priority dropdowns; save frequent filters as a Saved View.
6. Select multiple rows to bulk-set Status, Priority, Type, or Verification method (Test, Analysis, Inspection, Demonstration).
7. Click "Export CSV" or "Export JSON" to download the register.

Tip: Parent-child hierarchy is managed in the "Tree" tab of the Requirements hub, and reusable requirements can be pulled in with "Import from Library".

The import wizard brings existing requirement sets in from spreadsheets (CSV) or DOORS (ReqIF), with dedicated migration flows for Jama and DOORS.

1. Open Import & Modeling in the sidebar — the "Import" tab runs a 5-step wizard: Upload → Map Columns → Preview → Importing → Complete.
2. Drag and drop your file (.reqif, .reqifz, or .csv, up to 50 MB) and click "Upload & Parse".
3. For CSV, map your columns to fields — Req Number and Title are required; Description, Type, Priority, Verification Method, Parent Req Number, and more are optional.
4. Review the "Parsed Requirements" preview and pick a conflict resolution: "Skip duplicates", "Overwrite existing", or "Rename imported".
5. Run the import and check the results and "Import History".
6. Migrating from a specific tool? Use "Migrate from Jama Connect" (/portal/import/jama — upload or paste your Jama CSV) or "Migrate from IBM DOORS" (/portal/import/doors — upload the .reqif/.reqifz export).

Tip: Parent Req Number mapping preserves your requirement hierarchy during CSV import.

Requirements Quality runs INCOSE/EARS rule-based analysis over your register and scores each requirement 0-100.

1. Open the "Quality" tab in the Requirements hub (/portal/req-quality).
2. Click "Analyze Quality" and wait for the analysis to finish.
3. Read the "Overall Score" gauge (80+ is healthy) and the "Rule Statistics" panel.
4. Sort the "Requirement Scores" table low-to-high to find the weakest requirements first.
5. Open a failing requirement’s issues — each includes a concrete suggestion, and some offer a "Fix" link straight to the register.
6. Re-run the analysis after edits to confirm the score improves.

Tip: The analysis never changes your requirements — it only reports issues and suggestions.

The Requirements Traceability Matrix links stakeholder needs through requirements to verification, and measures coverage.

1. Open the "RTM" tab in the Requirements hub (/portal/rtm).
2. Use the stat cards to jump to Stakeholder Needs, Requirements, or Verification.
3. Expand "Coverage Analysis" for the three key metrics: "Upstream (has parent)", "Downstream (has children)", and "Verification method assigned" — each shows a percentage and count.
4. Chase the gaps: requirements without a parent, children, or verification method are your traceability debt.
5. Click "Export CSV" to include the matrix in review evidence.

Verification activities are generated from the Requirements page and managed in the V&V Plan and Verification Hub.

1. Open Requirements and click the "V&V" button on any requirement row to generate draft verification activities for it.
2. Open V&V Plan (/portal/vv-plan) to see the drafts — use the "Dashboard", "Matrix", "Schedule", and "Traceability" tabs to plan and sequence work.
3. In the Matrix tab, edit each activity inline and set its status (Draft, Ready, In Progress, Complete).
4. Check the Traceability tab to confirm every requirement rolls up to a verification method — anything "Unplanned" still needs an activity.
5. Open Verification Hub (/portal/verification-hub) for the KPI overview: Requirements, Planned / In Progress, Verified, and Failed counts plus the method distribution.

Tip: Need drafts fast? "Auto-generate (N)" on the Test Procedures page bulk-creates procedures for requirements that have no test yet, and the Test Case Generator can draft test cases from selected requirements for you to review and edit.

Test procedures capture step-by-step instructions with expected results, then record executions against them.

1. Open Test Procedures (/portal/test-procedures) and click "+ Create Procedure".
2. Fill in the procedure number (for example TP-001), title, description, prerequisites, equipment, and safety notes.
3. Under Test Steps, click "+ Add Step" for each step and enter the instruction and expected result.
4. Under Linked Requirements, select a requirement and click "Link" to tie the procedure into traceability.
5. Click "Create Procedure", then open it and click "Execute Test".
6. Record the test environment and serial number, mark each step Pass, Fail, Skip, or Waived with actual results, and click "Complete Execution" (or "Save Progress" to resume later).

The Test Runs page is the execution log for V&V — failed runs can spawn linked defects automatically.

1. Open Test Runs (/portal/test-runs) and click "+ Log Run".
2. Pick the test procedure and set the Result: Pass, Fail, Blocked, Skipped, or In Progress.
3. Record duration, build version, environment, notes, and an evidence URL if you have one.
4. For a Fail, leave "Auto-create a linked defect" checked and enter the defect title and severity.
5. Click "Log run" — summary stats (Pass / Fail / Blocked / pass rate) update immediately.

The Verification Cross-Reference Matrix (VCRM) shows every requirement, its verification method, activity status, and evidence in one table.

1. Open Verification Hub and switch to the "Verification Matrix (VCRM)" tab.
2. Filter by Method (Test, Analysis, Inspection, Demonstration) or Coverage (Unplanned, Planned, In Progress, Verified, Failed).
3. Click the evidence 📎 button on an activity row to open the evidence drawer.
4. Under "Attach new", pick a Kind (Note, File upload, Image upload, External link, Log, Analysis result, or Demo video), add a title and description, and click "Attach" (files up to 25 MB).
5. Set the activity status to Complete — the Coverage column rolls up to Verified (on pass) or Failed.
6. Click "Export CSV" for a spreadsheet copy, or "Register as Deliverable" to save the VCRM into the document register.

Tip: Individual evidence items have a "Register as doc" button to promote them into the document register on their own.

The Risk Register scores every risk as Probability x Consequence on a 1-25 scale, with owners and mitigation strategies.

1. Open Risk Management in the sidebar and select the "Register" tab.
2. Click "+ Add Risk" and enter a Title, Category (Technical, Schedule, Cost, Programmatic), and Description.
3. Set "Probability (1-5)" — from 1 Rare to 5 Almost Certain — and "Consequence (1-5)" — from 1 Negligible to 5 Catastrophic; the 1-25 risk score is computed for you.
4. Assign an Owner and describe the Mitigation strategy.
5. Save, then track each risk through its status: Open, Mitigated, Accepted, Watch, or Closed.
6. Filter by severity band (Critical ≥16, High 12-15, Medium 6-11, Low 1-5) and use the bulk bar to update several risks at once.

Tip: Half-finished entry? The form auto-saves a draft and offers "Restore" when you come back.

The Burn-down page visualizes risk reduction over time, including the classic 5x5 likelihood-vs-consequence heatmap.

1. Open the "Burn-down" tab in the Risk Management hub (/portal/risk-burndown).
2. Read the "Risk Heatmap — Likelihood vs Consequence" 5x5 grid to see where your open risks cluster.
3. Check "Risk Level Distribution" and "Status Breakdown" for the register-wide picture.
4. Follow the "Predictive Analytics — Risk Reduction Trend" and "Mitigation Effectiveness" sections to see whether mitigations are actually retiring risk.
5. Review "Milestone Risk Gates" for the percentage of risks resolved ahead of each gate.
6. Click "Export CSV" for reporting.

Phase gates track pack-seeded readiness criteria per gate — the page title follows your pack ("Phase Gates", "Milestone Reviews", or "Design Reviews").

1. Open "Phase Gates" in the sidebar (/portal/phase-gate).
2. If a gate has no items yet, click "Generate Standard Checklist Items" to seed your pack’s criteria (SRR/PDR/CDR for aerospace, milestones for defense, and so on).
3. Select a gate tab — each shows its readiness percentage.
4. Click an item’s status button to cycle Red (not met) → Yellow (partial) → Green (met) → N/A (not applicable).
5. Click "+ Add Item" to add a custom criterion ("Criterion — what must be true to pass this gate") — custom items behave exactly like the seeded defaults, and "Reset" restores pack defaults.
6. Click "Export PDF" or "Export CSV" for the gate review package.

Tip: "Auto-Score Gate" can suggest statuses from your project data for you to review and apply, and the Gate Readiness Predictor (/portal/gate-readiness) estimates pass probability with top blockers.

The Review Tracker manages review events, board composition, and Review Item Discrepancies (RIDs) with agendas and minutes.

1. Open the "Reviews" tab (/portal/reviews) and click "+ Add Review".
2. Pick the Review Type (your pack’s gates — SRR, PDR, CDR…), set the Date, Status (Planned, In Progress, Complete), Attendees, and Notes, then click "Add Review".
3. On the "Board" tab, click "+ Add Member" to build the review board — roles are Chair, Secretary, Reviewer, and Guest, scoped to one review type or all.
4. On the "RIDs" tab, click "+ Add RID" to log discrepancies with a Severity (Critical, Major, Minor, Observation), assignee, and due date; track them through Open, In-Work, Closed, or Deferred.
5. Prepare the "Agenda" and record "Minutes" on their tabs; watch the "Metrics" tab for review health.
6. Click "Export CSV" and "Export RIDs CSV" to distribute.

Trade studies score design alternatives against weighted criteria so the winning option is defensible.

1. Open Trade Studies (/portal/trades) and click "+ New Trade Study".
2. Name the study (for example "Architecture Alternatives") and describe what is being decided.
3. Click "+ Criterion" for each evaluation criterion and assign weights.
4. Click "+ Alternative" for each candidate option.
5. Enter scores in the matrix for every alternative against every criterion.
6. Review the "Side-by-Side Comparison" and "Radar Comparison" views — the weighted totals identify the leading alternative.

The Decisions page keeps a formal decision log alongside multiple analysis methods for analysis of alternatives.

1. Open Decisions & Trade Studies (/portal/decisions) and click "+ Log Decision".
2. Record the decision, rationale, alternatives considered, and decision-maker in the "Log New Decision" form.
3. For quantitative backup, switch to the "Weighted Scoring" or "Pugh Matrix" tab.
4. Click "Add Criterion" and "Add Option", then score each cell.
5. Use the "Decision Tree" and "Sensitivity" tabs to test how robust the outcome is.
6. The "Audit Trail" tab keeps the history of every recorded decision — export the log with "Export CSV".

The SysML Modeler is a visual block-diagram editor with round-trip traceability to your project data.

1. Open SysML Modeler (/portal/sysml-modeler) and click "+ New Diagram".
2. Pick a diagram type: Block Definition Diagram (BDD), Internal Block Diagram (IBD), Requirements Diagram, Activity Diagram, or Package Diagram.
3. Drag elements from the "Elements" palette onto the canvas — projects with an industry pack also get a pack-specific stencil section (for example "Aerospace Stencil").
4. Connect blocks with the connector tools: composition, aggregation, generalization, dependency, and the traceability connectors (satisfy, verify, derive, trace).
5. Use "Layout" and "Align" to tidy the diagram, then click "Validate" to check it and "Save" to persist.
6. Click "Export JSON" to take the model to other tools.

Tip: "Auto Generate" can seed a diagram from existing project structure so you are not starting from a blank canvas.

The Document Register is the central list of every project document with status, version, and content tracking.

1. Open Document Register (/portal/documents) and click "+ Add Document".
2. Enter the document number, title, type, status, and version — statuses run Draft, In Review, Approved, Released, Superseded.
3. Click a document to open its preview panel with metadata, attached files, and any generated content sections.
4. To edit generated content in place, click "✎ Edit Content", make your changes section by section, and click "Save Changes".
5. Use "Generate V&V Docs" to bulk-create or refresh test and analysis report documents from your verification activities.
6. Filter by search, type, or status, and use bulk status updates when a review cycle completes.

Baselines freeze a snapshot of your requirements at a milestone so later changes are visible and auditable.

1. Open Requirement Baselines (/portal/baselines).
2. Use the "Create New Baseline" form to freeze the current requirement set — typically at a gate like SRR or PDR.
3. Check "Baseline Recommendations" and the "Baseline Timeline" to keep a healthy cadence.
4. To compare, pick two baselines in the Compare selector and review the "Detailed Baseline Comparison" diff (added, removed, and changed requirements).
5. Open any baseline for its detail page: "Baseline Notes", "Changes from Previous Baseline", and CSV export.
6. Cycle the baseline approval status once the review board accepts it.

Pack deliverable templates generate draft documents you can edit before registering them as project deliverables.

1. Open Deliverables (/portal/deliverables).
2. In the "Auto-Generate Deliverables" panel, pick a template from your industry pack (each shows its phase and document code).
3. Review the generated draft in the editable preview and adjust the content.
4. Register it — the document lands in the Document Register as an editable deliverable.
5. Track delivery with the status toggles: Not Started, In Progress, Ready, Delivered.
6. Add anything the templates do not cover with the manual "New Deliverable" form.

Live Document Generation builds structured engineering documents straight from your current project data.

1. Open Live Docs (/portal/live-docs).
2. Pick a document template card — the document is generated from live project data, so it always reflects the current state.
3. Review the output, then use "Copy HTML", "Download HTML", or "Print" to take it wherever it needs to go.
4. Regenerate any time — the content is rebuilt from the database on each run.

Tip: Live Docs output is export-only. To get a generated document INTO the register, use Deliverables ("Auto-Generate Deliverables") or the register’s own "Generate V&V Docs".

All design changes flow through formal change requests with impact assessment and a status workflow.

1. Open Change Requests (/portal/changes) and click "+ New Change Request".
2. Describe the change and set its Impact — the review board assesses effects on mass, power, schedule, and cost.
3. Submit — the request starts in "Submitted" and moves through Under Review, Approved (or Rejected), Implemented, and Closed via the workflow buttons on each row.
4. While a request is "Under Review", click "Request Approval" to spawn a multi-party sign-off chain.
5. Watch the approval indicator on the row (⏳ pending, ✅ approved, ❌ rejected) and advance the status as the change lands.

Approvals collects every sign-off chain — design reviews, baseline freezes, control packets, and change boards — in one queue.

1. Open Approvals (/portal/approvals) — stat tiles show Pending, Approved, and Rejected chains.
2. Each approval card lists its role slots; pending slots show "Awaiting {role}".
3. If a slot is waiting on you, click "Sign" to approve or "Reject" to send it back.
4. Once every slot is signed, the chain finalizes automatically and the parent item (change request, baseline, review) updates.
5. Filter by status to audit past chains.

CCB Sessions tracks scheduled change-board meetings with agendas, per-item decisions, and an audit trail.

1. Open CCB Sessions (/portal/ccb-sessions) and click "+ Schedule Session".
2. Set the scheduled date and time, an optional location, and the agenda summary.
3. Click "Schedule" — the session card shows its status (Scheduled, In Progress, Completed, Cancelled).
4. After the meeting, session cards display each agenda item’s decision tag (approved, rejected, deferred, pending) with rationale for the record.

Tip: Decisions themselves are executed on the change requests and approval chains — the session page is the meeting record.

Every industry pack ships register pages (hazard logs, control matrices, inspection trackers, and more) that share one powerful table toolkit.

1. Open any pack register from the sidebar — the summary strip shows Total, Closed, Open, % Complete, and Overdue counts automatically.
2. Narrow the view with the search box and the filter chips that appear for every status-style column; "Clear" resets everything.
3. Click "+ Row" to add entries, or "⚡ Starter" on an empty register to load the pack’s starter template.
4. Select multiple rows to open the bulk bar: "Set status…" updates them together, "Export selected" downloads a CSV, "Delete N" removes them.
5. Click "↥ Import" to paste CSV or TSV rows (header row matching the column names), preview the parse, and confirm with "Import N rows".
6. Click "↧ CSV" any time for a full export.

Tip: The row editor (✎) includes promotion buttons like "→ Create risk" and "→ Create action item" so register findings can escalate into the main risk register.

Register pages with document templates can generate audit-ready documents, and coverage panels show implementation progress per category.

1. Open a register that ships templates (for example NIST 800-53 Rev 5 Controls at /portal/nist-800-53).
2. Pick a template if the page offers more than one, then click the generate button (for example "Generate FedRAMP SSP → register").
3. The document is saved into the Document Register as an editable draft — follow the "✓ … in register →" link to open it.
4. Use the "↧ .md" button instead if you just want a markdown download.
5. Watch the coverage panel (for example "800-53 Family Coverage") — per-category bars fill as rows reach closed/implemented status.

Link columns tie register rows to your backbone entities so traceability spans every pack tool.

1. In a register row, find a link cell — unlinked cells show a dashed chip like "+ requirement".
2. Click the chip to open the "Link a requirement" (or risk/document) modal.
3. Search the candidate list and click the entity to link it — the cell now shows a solid chip.
4. For document links, the modal can also generate a new document from a template ("Generate & link") or create a "+ Blank editable document".
5. Click the × on a chip to unlink; linked rows appear in the Trace, Link Graph, and Audit Drop outputs automatically.

AI Ingest turns pasted text or a URL into structured register rows that you review before anything is inserted.

1. On a register page, click "✨ AI Ingest" in the header.
2. Paste source text (meeting notes, a spec excerpt, an audit report) or enter a URL, and optionally add an instruction like "only Critical and High severity".
3. Click "Preview rows" and wait for extraction.
4. Review the preview table — nothing is saved yet; use "↺ Re-extract" to try again with different instructions.
5. Click "Insert N rows" to add the reviewed rows to the register.

Tip: AI Ingest requires the AI bundle (included with Professional and Enterprise). The per-row "AI" button can also draft empty text fields — it never overwrites content you wrote.

Entity Trace answers "what references this requirement/risk/document?" across every register in the project.

1. On a requirements, risks, or documents list, click the "Trace" button on a row.
2. The Entity Trace page (/portal/trace) opens with every pack-table row that links to that entity, grouped by page.
3. Follow any row link to jump to the register it lives in.
4. Download a markdown trace report for review packages or audits.

The Link Graph shows every backbone entity with every register row that links to it — gaps are unmet traceability.

1. Open Link Graph (/portal/link-graph).
2. Use "Search entities…" to find a specific requirement, risk, or document.
3. Scan for entities with no linked rows — those are coverage gaps worth closing before a gate review.
4. Click "↧ Report" for a markdown link report you can attach to review evidence.

Program Rollup aggregates open/closed/overdue counts from every register page and packages a full audit bundle on demand.

1. Open Program Rollup (/portal/rollup) — every register in the project is listed, sorted by attention (overdue first).
2. Click "◉ Snapshot" to record the current counts; from two snapshots onward, trend sparklines appear for open and overdue items.
3. Click "↧ Rollup" for a markdown summary of the current state.
4. Click "⤓ Audit Drop" to build a ZIP containing every document, the rollup, the link graph, and a per-entity trace — a complete audit evidence bundle.
5. The ZIP downloads as audit-drop-YYYY-MM-DD.zip.

Tip: Snapshot weekly — the sparklines only render once at least two snapshots exist.

The RMF page organizes your NIST SP 800-37 Risk Management Framework work — categorization through continuous monitoring — to support your authorization effort.

1. Open RMF Authorization to Operate (/portal/rmf).
2. Step 1: categorize the system (FIPS 199 impact levels).
3. Step 2: select controls (NIST 800-53 Rev. 5 baseline).
4. Step 3: implement and document — generate the System Security Plan (SSP) as an editable register document.
5. Step 4: assess and manage POA&M items for gaps.
6. Step 5: run continuous monitoring (ConMon) and record the authorization decision when your authorizing official issues it.

Tip: This tooling organizes and documents your compliance program — authorization decisions themselves always come from your authorizing official.

The NIST 800-53 Rev 5 register tracks per-control implementation status and generates the SSP foundation from it.

1. Open NIST 800-53 Rev 5 Controls (/portal/nist-800-53).
2. Track each control’s implementation status, responsible role, inheritance source, and last review date in the register.
3. Use the filter chips to focus on a control family or status.
4. Watch "800-53 Family Coverage" — the per-family bars fill as controls reach Implemented.
5. Generate the FedRAMP-style SSP document into the register when you need a documentation snapshot.

The CMMC Compliance Tracker follows practice coverage with per-control evidence links and POA&M tracking to support your assessment preparation.

1. Open CMMC Compliance Tracker (/portal/cmmc-tracker).
2. Record each practice’s status and link evidence — generate an evidence document per control or follow the "Open →" link to existing evidence.
3. Track remediation items in the POA&M section; overdue items are flagged automatically.
4. Use the coverage view to see which domains still have open practices before an assessment.

Compliance Management aggregates framework status, waivers, and a compliance matrix across the standards your project tracks.

1. Open Compliance Management (/portal/compliance).
2. Review the "Compliance Score" and "Compliance by Category" cards for the big picture.
3. Work the "Compliance Matrix" — each row tracks a standard’s applicability and status, with per-row document generation.
4. Log formal exceptions in the "Waiver / Deviation Tracker".
5. Use "Quick Actions" to jump to the framework reference and related tools.

Contract Management tracks contracts end-to-end and links them to cost accounts, requirements, risks, and documents.

1. Open Contract Management (/portal/contract-management) and click "+ New Contract".
2. Enter the contract number (for example FA8808-25-C-0042), title, type, cost and fee values, vendor, contracting office and officer, and the period of performance.
3. Click "Create Contract" — it starts in Draft; use "Activate" when awarded and "Archive" when closed out.
4. Click "Set as main" on your primary contract so it appears on the Executive Summary.
5. Filter by status chips to review Draft, Active, and Archived contracts.

The CDRL / SDRL Manager tracks DID-mapped contract deliverables with due dates and milestone dependencies.

1. Open CDRL / SDRL Manager (/portal/cdrl-manager) — stat cards show Total, Overdue, Due ≤ 30 days, Delivered, and Pending.
2. Click "+ New CDRL Item" and fill the row inline: sequence number, title (for example "System Engineering Plan"), DID (for example DI-MGMT-81024B), frequency, due date, milestone, type (CDRL/SDRL), and status.
3. Advance each item through Pending, In work, Submitted, Delivered (or Rejected) as it moves.
4. Watch for red rows — past-due items that have not been delivered.
5. Click "+ Status Report Doc" to generate a CDRL status report into the document register.

Cost Tracking manages a WBS chart of accounts with line items, baselines, commitments, and variance analysis.

1. Open Cost Tracking (/portal/cost-tracking).
2. On the "Accounts" tab, click "+ New Account" to build your WBS chart of accounts.
3. Add estimates, actuals, commitments, and contingency as line items on the "Entries" tab.
4. Freeze a cost baseline on the "Baselines" tab, and record vendor POs under "Commitments".
5. Use "Variance Analysis", "Cost S-Curve", and "vs Baseline" tabs to see where actuals diverge from plan.
6. Export everything from the "Exports" tab.

Tip: Cost Tracking is part of the Cost Tracking bundle ($14/mo on Starter/Pro; included with Enterprise).

The Earned Value page computes BAC, PV, EV, and AC with CPI/SPI indices and EAC forecasting, and records snapshots for trending.

1. Open Earned Value (/portal/evm).
2. Review the metric cards: Budget at Completion (BAC), Planned Value (PV), Earned Value (EV), and Actual Cost (AC).
3. Check the performance indices — SV, CV, SPI, and CPI — for schedule and cost health.
4. Compare EAC methods (for example remaining work at current CPI, or a bottom-up re-estimate) and select the one you report.
5. Click "Save Snapshot" to record the period — snapshots build the CPI/SPI trend history.
6. Click "Export CSV" for reporting.

Team Management handles invitations two ways: direct email invites or a shareable company invite token.

1. Open Team Management (/portal/team) and click "Add Member".
2. Enter the colleague’s email under "Email Address" and pick a "Portal Role" (Member, Engineer, Lead Engineer, Systems Engineer, Program Manager, or Company Admin).
3. Click "Send Invite" — existing accounts join immediately; new users receive an invitation link by email.
4. Track outstanding invites under "Pending Invitations", where you can "Resend" or "Revoke".
5. Alternatively, share the Company Invite Token (click to reveal, then "Copy") — new members enter it at registration.

Tip: Toggle the "Role Permissions Matrix" to see exactly which capabilities each portal role grants before assigning.

Project-level roles (separate from portal roles) control who can edit requirements, approve gates, sign off reviews, and more within each project.

1. With a project selected, open Team Roles (/portal/roles).
2. Click "+ Add Member", pick the team member and one of the 14 project roles — from Owner and Chief Engineer through Reviewer and Viewer.
3. Check the capability matrix to see what each role can do across the 13 capabilities (Edit Requirements, Approve Gate Reviews, Export Data, and more).
4. Use the "Compare Roles" tab to see two roles side by side with Match/Differ badges before choosing.
5. Review the "History" and "Analytics" tabs to audit role changes over time.

White-Label Configuration rebrands the portal with your name, logo, colors, and a custom domain (Enterprise).

1. Open White-Label Configuration (/portal/white-label).
2. Pick a preset theme or set your own Primary, Accent, Background, and Text colors in the Color Theme Builder.
3. Set the "Application Title" and upload a logo ("Choose File" — PNG/SVG/JPEG/WebP up to 256 KB) or paste a Logo URL and Favicon URL.
4. Check the Live Preview of the header and sidebar as you go.
5. For a custom domain, enter it (for example portal.yourcompany.com) and follow the CNAME setup steps shown.
6. Click "Save Configuration" (or "Reset" to discard). Use "Export as JSON" to reuse the brand kit across environments.

The Audit Log records who did what, when, and from where across your organization.

1. Open Audit Log (/portal/audit-log).
2. Filter by user, action, or date range to narrow the trail.
3. Click "Export CSV" to hand the log to auditors or ingest it elsewhere.

Tip: Enterprise plans add audit log export integrations (Splunk, Datadog, CloudWatch, syslog) and a signed append-only trail.

Plans run Starter ($14.99/mo), Professional ($39/mo), and Enterprise ($249/mo) — all managed from the subscription page.

1. Open Account → Subscription (/portal/account/subscription).
2. Under "Plan Options", each tier card is marked "Current", "Upgrade", or "Downgrade" relative to your plan.
3. Click the tier you want — checkout opens with your choice pre-selected; pick monthly or annual billing (annual saves roughly two months).
4. Enterprise on a team account shows "Request admin approval" instead — your company admin confirms the change.
5. To cancel, use "Cancel Subscription" and confirm; "Resume Subscription" undoes a pending cancellation.

Six add-on bundles (AI Intelligence, Compliance & Audit, Collaboration, Training Academy, Integrations & Tooling, Cost Tracking) extend Starter and Professional plans.

1. Open Account → Subscription (/portal/account/subscription).
2. Scroll to "Feature Bundles" — active bundles are listed with a "Remove" option, available ones with their price.
3. Click "Add" on the bundle you want — it activates on your existing subscription immediately, no checkout redirect.
4. Professional already includes the AI and Collaboration bundles; Enterprise includes all six.

Your first industry pack is included free; add more verticals any time to unlock their methodology, phases, registers, and calculators.

1. Open Account → Subscription (/portal/account/subscription) and scroll to "Industry Packs".
2. Your active packs are listed — the first shows "Included".
3. Under "Add another industry", find the pack you need among the 20 industry packs (plus Generic SE) and note its monthly or annual price.
4. Click "Add" — the pack activates immediately and its tools, terminology, and templates appear on projects using that vertical.
5. Click "Remove" on a pack you no longer need to drop it from the next invoice.

Coupon codes are applied at checkout before you subscribe.

1. Start checkout from the Pricing page or Account → Subscription (/checkout).
2. In step 1, find "Have a coupon?" and enter your code (for example LAUNCH20).
3. Click "Apply" — a confirmation shows the discount description once validated.
4. Complete payment; the discount is applied to your subscription per the coupon’s terms.

Tip: Coupon links work too — a URL with ?coupon=CODE pre-fills the field for you.