Interactive freight portal
Secure freight visibility for shippers, carriers, agents, staff, and administrators.
NGI's portal experience is designed for shippers, trucking companies and drivers, freight agents, staff, and administrators to reduce phone-only workflows with secure account access, document sharing, load/deal/transaction monitoring, status updates, and request controls.
Internal/Admin Side
NGI Compliance & Carrier Vetting Dashboard
Restricted Access – Super Administrator OnlyFOR INTERNAL USE ONLY: Access to this portal is restricted to authorized NGI personnel. This system provides real-time verification of motor carrier operating authority, safety ratings, and insurance status. Unauthorized use or disclosure of sensitive carrier data is strictly prohibited.
Do not rely on dirty or uncredentialed data.
- Store only vetted carrier, truck, driver-assignment, dispatcher, and insurance records approved by NGI.
- Require source, reviewer, timestamp, expiration date, and next-review date for every credential field.
- Keep rejected, suspended, expired, spoofed, or high-risk records separate from active capacity search results.
No assignment until verification passes.
- Confirm authority, insurance, safety profile, equipment fit, identity, contact authority, and lane capability.
- Document driver readiness through carrier attestation; NGI does not employ drivers.
- Block assignment when credentials expire, records conflict, documents appear altered, or fraud indicators appear.
RED carrier override locks the user account.
- If an agent or staff user attempts to override a RED carrier status, expired authority, revoked status, sanctions flag, altered document, or fraud hold, the live portal must block the action.
- The attempted override must lock the user account for management review and preserve user, timestamp, carrier, reason, and attempted action in the audit trail.
Administrator access: Pamela M. Nadalini should be created as the primary Super Administrator only in the live secure portal. Admin rights should require MFA, role approval, encrypted storage, immutable audit logs, and no shared passwords.
NGI Fortress dashboards
Secure portal controls required by the NGI Shield & Gatekeeper architecture.
The live build should convert these protected concepts into backend-enforced rules with MFA, RBAC, encrypted records, immutable audit logs, and administrator approval workflows.
Keep public trust separate from protected operations.
Public pages may educate and collect intake. Vault pages must protect leads, pricing logic, manuals, carrier vetting, files, and financial records behind approved accounts.
Protected files must be physically blocked.
Internal SOPs, manuals, sensitive documents, pricing rules, credential files, and protected workflows must be blocked by server-side authentication and authorization, not merely hidden from navigation or left unlinked.
Evidence locks before payout or archive.
CDL or driver ID evidence, truck photo, trailer/equipment evidence where applicable, license plate, signed pickup BOL, and timestamped POD should be required before payment release or file closeout.
One-click evidence upload for carrier contacts.
The live carrier/driver workflow must make truck, plate, CDL/authorized ID, pickup BOL, and POD uploads a one-click mobile action with timestamp metadata, account attribution, and upload confirmation.
Two-hour status discipline for active loads.
Active shipments should surface pulse timers, missed-update flags, exception reasons, user identity, and shipper-safe visibility without exposing internal notes.
Block margin leakage from after-the-fact add-ons.
Carrier rates should be treated as all-inclusive unless written approval permits an exception. Deadhead, positioning, or empty-mile requests should be logged, blocked, or escalated.
High-security facility flags require elevated review.
Facility-sensitive, restricted-access, high-value, or special-security loads should trigger extra credential checks, seal documentation, tracking cadence, and executive approval rules.
Red/Amber screen state for high-security loads.
High-security NGI Tactical loads should shift the portal into a Red/Amber visual state so everyone sees that elevated facility, seal, identity, tracking, and approval rules apply.
Every critical action needs attribution.
Uploads, changes, approvals, holds, payment edits, carrier assignments, and closeout releases should preserve user, role, timestamp, device/session, reviewer, and reason.
NADALINI GLOBAL INCFMCSA Entity Type: BrokerMC-1469182USDOT-3949236USDOT Status: ActiveAuthorized for Broker PropertyFMCSA/SAFER Verified: 05/16/2026
Brokerage role notice: NGI is a nationwide licensed transportation freight brokerage. NGI is not a shipper, is not a trucking company, and is not a motor carrier. NGI does not own, lease, or operate trucks, trailers, vessels, aircraft, rail equipment, warehouses, or transportation equipment and does not employ drivers to transport freight. Transportation imagery on this website is illustrative of brokered third-party capacity. Brokered shipments are arranged with appropriately authorized transportation providers only after NGI review and written confirmation.
Secure operations platform
A shipper-facing portal concept built around how freight is quoted, documented, and monitored.
The portal page below defines the intended account, document-sharing, tracking, request-change, audit, fraud-monitoring, and calculator workflows. Before public launch, these features must be connected to secure authentication, encrypted file storage, role-based permissions, audit logs, verified identity controls, and approved data sources for fuel, distance, lane, tax, and fee rules.
Independent agent onboarding
Join the NGI Network through a secure, credentialed workflow.
Your privacy is our priority. All documents are uploaded via a secure, encrypted portal and are used strictly for internal verification purposes.
Registration and identity intake
Collect the applicant's full legal name, email address, phone number, logistics experience, current book of business, and specialized lanes only through an authenticated onboarding session.
Encrypted document verification
Government-issued ID and proof of 1099 history, such as a prior-year 1099 or recent commission statements, must be uploaded through SSL/TLS into encrypted private storage, not a public folder or standard email.
Payment gate
The $49.99 onboarding payment should be processed through Stripe or PayPal. The legal agreement step should remain locked until the payment processor confirms success.
E-signature agreement
The NGI Independent Agent Onboarding, Fee, and Non-Solicitation Agreement should be issued through DocuSign or a comparable e-sign API after verification and payment controls are satisfied.
Authorized NGI administrators only
Sensitive documents and agent records must be viewable only by approved NGI administrators with role permission, MFA where applicable, session controls, and documented review authority.
Every action must be attributable
The live portal should retain user, role, timestamp, IP/session metadata, upload hash, virus scan result, payment confirmation, e-sign status, reviewer, and approval or denial reason.
No public agreement posting: The independent agent onboarding agreement, government IDs, 1099 proof, financial history, and internal verification notes are Vault materials. They must not be public downloads, search-indexed files, or attachments sent through ordinary email.
Role-based accounts
Request the account type that matches the freight relationship.
Choose a role to see what each user group should be able to manage once the secure backend is connected.
Shipper account
Track freight requests, active loads, documents, invoices, and delivery progress.
Shipper users should see quote requests, shipment milestones, document status, messages, estimated charges, and transaction history tied only to their account.
Load, deal, document, and transaction visibility
Dashboard visibility that reduces phone-only shipper updates.
Shipper dashboard previewLoads, documents, messages, and charges
Active loads8
Docs pending3
Transactions$42,860
On-time watch2
| Reference | Lane / account | Type | Status | Next step |
|---|---|---|---|---|
| NGI-1027 | Sarasota, FL to Atlanta, GA | Truckload | In transit | Delivery appointment confirmation |
| NGI-1041 | Agent pipeline: Midwest retail lane | Deal | Under review | Rate and carrier qualification check |
| NGI-1088 | Port / warehouse documents | Document | Pending docs | Upload BOL, POD, or invoice backup |
Operations data desk
Fuel, lane cost, contacts, ratings, commissions, expenses, and profit controls for approved Nadalini Global, Inc. (NGI) users.
This staff-facing portal area is designed for freight agents, NGI brokerage leadership, and administrative staff. The public website shows the intended workflow; live use requires secure login, approved integrations, encrypted database storage, audit logs, and role-based permissions.
Link directly to official gasoline and diesel indexes.
Freight pricing most often relies on on-highway diesel, while gasoline data may still be useful for certain operating analyses. The live calculator should pull current values from approved government or contracted data sources instead of relying on manually copied numbers.
Keep verification links one click away.
Approved staff should be able to verify carrier authority, insurance, safety profile, sanctions restrictions, international screening, and agency guidance before a load is accepted or released.
Maintain a searchable business directory.
The secure backend should maintain drivers, dispatchers, shippers, carriers, companies, referral agents, insurance contacts, FMCSA/DOT resources, regulatory authorities, accounting contacts, and professional vendors.
- Legal name, DBA, role, authority numbers, lane preferences, and equipment notes
- Insurance, W-9, compliance, document, and verification status without exposing Tax IDs by email
- Source links, last verification date, assigned NGI owner, account notes, and audit history
Internal ratings and future-use references
NGI should be able to rate drivers, freight agents, shippers, vendors, carriers, referral sources, and professional contacts using structured internal criteria, not public comments. Each rating should preserve reviewer, date, source load/deal, reason, supporting documentation, correction history, and approval status.
Financial ledger and margin tracking
The live system should accumulate customer revenue, carrier/vendor costs, fuel and accessorial exposure, referral fees, agent commissions, overhead allocations, expenses, gross margin, net profit, and exception approvals by load, customer, agent, and accounting period.
Benchmark Friction: If a proposed load falls below NGI target margin, the live system must require a reason code, such as Weekend Load, Tight Capacity, Shipper Recovery, Strategic Lane, or Executive Exception, before a rate confirmation can generate.
Credential watch and compliance holds
The live portal should track authority status, insurance expiration, identity checks, driver credential attestations, sanctions screening, fraud flags, unauthorized re-brokering concerns, hold status, reinstatement requirements, and reviewer approvals.
Secure document management
Control the documents shippers, carriers, and Nadalini Global, Inc. (NGI) need to trust the file.
The live portal should support secure upload, sharing, review, versioning, and management of rate confirmations, bills of lading, proof of delivery, invoices, insurance certificates, W-9 files, carrier packets, driver documents, agent agreements, customer documents, and status notes. W-9s, Tax IDs, and banking documents must not be collected by standard email.
Rate confirmationApproved
BOL / PODNeeded
Invoice backupReview
Compliance fileComplete
Document upload preview
Choose files for a load.
Preview only: this static site does not upload, share, or store files. A live version must use encrypted transmission, encrypted storage, virus scanning, access controls, audit logging, permissioned sharing, and fraud-monitoring review. W-9s, Tax IDs, and banking documents must be collected only through a secure portal or DocuSign-style workflow.
No documents selected yet.
Carrier / driver assigned-load fields
For assigned loads only, carrier or driver users should be prompted to upload the required pickup, equipment, and delivery evidence for NGI review. NGI does not employ drivers; these fields support documentation from independent motor carriers and their authorized driver or dispatcher contacts.
Required carrier/driver evidence is waiting for assigned-load files.
Live Photo-Gate controls should capture timestamp metadata, user account, load ID, source device, file hash, virus scan status, reviewer approval, version history, and immutable audit trail before documents support closeout, payment, payout release, or customer release.
Automated POD Chase: The live portal should automatically send carrier or dispatcher SMS/approved-message reminders beginning 4 hours after delivery if the timestamped POD has not been uploaded, with escalation history preserved in the file audit trail.
Closeout and archive gate
No load, deal, or file should close until required documents are uploaded, reviewed, approved, and audit-stamped.
Before any load, deal, carrier file, shipper file, agent file, billing file, claim file, or transaction record is closed or archived, the live portal should confirm that the required document set is complete, the financial records match, exceptions are resolved or approved, and an authorized reviewer has released the file for archive.
Update, modify, or cancel requests
Controlled changes with approval history.
Authorized users should be able to request load updates, document corrections, appointment changes, modifications, or cancellations from their respective account. Every change request should require a reason, preserve prior values, notify assigned parties, and remain visible in the audit trail.
Requires approvalReason requiredAudit retained
Audit trail and fraud monitoring
Every critical action should be visible, reviewable, and attributable.
To reduce fraud, misrepresentation, unauthorized changes, and document disputes, the live portal should log who did what, when it happened, what changed, what file was affected, the source account, IP/session metadata, approval status, and the reviewer assigned.
09:42Document uploaded
BOL added by carrier dispatcher; pending staff review.
10:18Change request submitted
Shipper requested appointment modification; reason captured.
10:31Fraud review flag
Duplicate invoice filename and changed remit-to details require administrator approval.
11:05Status approved
Staff verified POD and released status update to assigned accounts.
Lane and load calculator
Estimate the lane before Nadalini Global, Inc. (NGI) confirms the load in writing.
The live portal should connect to verified distance, lane, fuel-index, tax, and accessorial data. Use the Routing and Distance Desk to prepare lane, stop, and transfer details before entering miles. This front-end calculator demonstrates the workflow with editable example values until a live data connection is approved.
Fuel data source recommended for live integration: U.S. Energy Information Administration weekly retail gasoline and on-highway diesel prices.
Self-enforcing compliance engine
Portal rules that protect margin, identity, evidence, and shipper trust.
These requirements come from the 2026-05-19 Web Specs and Master Manual and require backend enforcement, not static-page promises.
Insurance status must be source-stamped.
The live system should show COI verified timestamp/source vs. COI not verified or expired using FMCSA/SAFER or approved third-party verification sources.
Authority age under six months is flagged.
New motor-carrier authority should display a visible caution banner and require elevated review before load assignment.
No Photo equals No Load.
The live portal must block Finalize Load and related actions until Photo-Gate evidence is uploaded, timestamped, and visible in the Photo/Identity Vault.
In Transit and Delivered require evidence.
Photo-Gate status locks should prevent false progress updates when required truck, CDL/ID, pickup BOL, and POD evidence has not been uploaded.
Verified identity before load finalization.
Shipper-facing portal copy should explain that carrier identity artifacts and dock-side truck photos are required before load finalization to reduce ghost-carrier and fraud risk.
Tactical dashboard for sensitive shippers.
Security-sensitive shippers should have a dedicated Fortress Elite Vault view for HSF loads, required identity artifacts, seal records, tracking cadence, and executive approvals.
Vetted shippers and carriers are visually marked.
Approved vetted accounts may receive NGI Platinum visual status after Vault vetting, with server-side badge logic and audit history.
Lead collision prevention.
New leads/customer records should use a 48-hour first-to-file lock with owner, timestamp, lead identifier, activity requirement, and automatic release if no activity is logged.
Agents see only approved records.
Agents may access only their own leads and assigned customer records and may not export or download lead lists without elevated authorization.
Verified identity artifacts stay protected.
The Vault should provide one-click access to approved identity artifacts tied to shipper/load/carrier records without exposing protected files publicly.
BOL/POD documents are audit-logged.
BOLs, PODs, invoices, accessorial support, and shipment documents should live in a role-based Document Vault with versioning and immutable audit history.
Exceptions get a controlled portal.
Over, Short, and Damaged reports should use a protected OS&D Vault with photos, notes, timestamps, claims support, reviewer assignments, and status tracking.
SEO, social, and growth engine
Lead generation must be measurable without compromising privacy or the Vault.
These growth features are developer requirements for the live environment and must be configured with privacy review, consent handling, and administrator controls.
One-click credential download
The public Lobby should provide W-9, MC Authority, and COI once the final authority and insurance PDFs are supplied. Protected agreements and manuals stay out of the public package.
Attribution with consent controls
LinkedIn Insight Tag, Meta Pixel, and Meta Conversion API should not be activated until NGI supplies IDs, privacy disclosures are approved, cookie/consent controls are configured, and data sharing is documented.
Controlled content publishing
A future CMS/blog should allow authorized marketing users to publish shipper-focused content through approval workflows, version history, no access to Vault records, and legal/compliance review where needed.
Security before go-live
The portal must launch with a proper secure backend.
Credential security operating rule: Audit, authentication, privacy, and security provisions must apply to each user and each authorized function. Every login must be individually issued, protected, non-transferable, least-privilege, MFA-enabled where required, logged with user/action/time/session details, and revocable when the relationship, role, or business purpose changes.
Authentication
Role-based accounts, SSL/TLS, strong passwords, multi-factor authentication where applicable, account approval, password reset controls, session timeout, login monitoring, risk review, and no shared credentials. Any compliance inbox, including compliance@nadaliniglobal.com if created, should have 2FA enabled immediately.
Permissions
Shippers, trucking companies, drivers, independent freight agents, staff, administrators, and executives must only see the accounts, loads, deals, documents, financial records, tools, and actions assigned to their authorized role.
Database security
Contact directories, internal ratings, verification notes, commission records, expense records, and profit ledgers must be encrypted at rest, backed up, permissioned, searchable by role, and protected by immutable audit logs.
Financial controls
Commission, expense, and profit records should require approved policies, user permissions, source documents, change history, supervisory review, and export controls before any report is treated as official.
Document protection
Encrypted transmission, encrypted private storage, virus scanning, document versioning, signed download links, upload limits, retention rules, and audit trails. W-9s, Tax IDs, banking details, government IDs, 1099 history, financial records, and agent onboarding documents must never be requested through standard email or stored in a public-facing folder.
Closeout lock
Loads, deals, files, invoices, claims, and account records should remain open until required documents are uploaded, approved, matched to financials, exception-cleared, and released by an authorized reviewer.
Request controls
Updates, modifications, cancellations, document changes, and approvals should be permissioned, reason-coded, timestamped, and retained in the audit history.
Credential watch
Authority, insurance, driver-credential attestations, broker/agent approvals, sanctions checks, and fraud flags should be monitored continuously with expiration alerts and hold/reinstatement workflows.
Fraud monitoring
Identity verification, duplicate-file detection, change alerts, unusual activity review, and misrepresentation flags should be monitored before documents or requests are approved.
Sensitive onboarding data
Government IDs, proof of 1099 history, financial records, Tax IDs, and onboarding agreements must be treated as strictly confidential, encrypted at rest, limited to authorized NGI administrators, and used only for onboarding, verification, compliance review, and approved business administration.
Compliance review
Before launch, NGI should obtain legal, insurance, cybersecurity, tax, privacy, and freight brokerage compliance review for the final portal workflows, including encrypted database storage for applications and sensitive identifiers.