Issuance Platform

Introduction

Every new hire at Rising Ground triggers the same invisible checklist: a laptop to assign, software access to grant, a building to let them into. Every departure triggers the reverse, and that's where things get lost. Literally.

With 1,600 employees and staffing changes happening daily, that checklist is not a side task. It's a continuous operation spanning HR, IT, and facilities, three teams, three types of assets, and one question none of them could answer reliably: who has what, right now?

After building Rising Ground's fleet operations platform, we took ownership of this next friction point. Employee Issuance became the second application in what is now a five-app partnership spanning more than two years.

‍

‍

‍

Onboarding ran on memory

Before the app, issuance lived in Excel. An asset was handed over, and somewhere, a spreadsheet was supposed to be updated, by whoever remembered, whenever they got to it. Who has this laptop? Did the new hire ever get building access? The answer depended on a file being current, and with 1,600 employees and daily staffing changes, it never was for long.

A spreadsheet can record an issuance, but it can't run one. It doesn't route a phone request to IT and a key card request to facilities. It doesn't require a reason for a rejection, chase a signature at handoff, or surface every active asset when someone resigns. Excel held the data; the process lived in people's heads.

Do the math on what that means at Rising Ground's scale. With 1,600 employees, even a conservative 20% annual turnover means 320 exits a year. If each departing employee carries just a $1,000 laptop, that's $320,000 of equipment walking toward the door every year, before counting phones, software seats, and key cards. None of it was exactly lost. It was something worse for an operations team: half-disappeared, somewhere in a spreadsheet row nobody trusted, assigned to someone who no longer answered emails.

‍

‍

What we built

Employee Issuance is the system of record for the full life of every asset Rising Ground hands to its people, from request to signed handoff to recovery. Four capabilities carry it:

• A request flow that speaks three languages of "asset". Program requesters open a request for an employee in their own program and add items across three categories, physical assets like laptops and phones, software platforms, and building access, each with notes, and each automatically routed to the department responsible for issuing it. IT sees the phone request; facilities sees the building access.
• Approval with accountability built in. Program managers or super admins from the same department review each request item by item, approve everything in one click, or approve the phone and reject the second laptop. Every rejection requires a written reason and notifies the requester automatically by email.
• Issuance with a signature, not a hallway agreement. Support admins fulfill approved requests from real inventory: the system shows only items not currently assigned to anyone, or lets them register a new item on the spot. The handoff itself closes with a responsibility letter signed by the employee inside the app.
• Offboarding that closes the loop. When an employee leaves, the program team initiates a retrieval, and HR confirms it before anything moves. Every active item assigned to that person surfaces automatically, and each one is resolved explicitly: returned, or documented as unreturnable.

‍

‍

Technical decisions that made this more than an inventory list

The system goes beyond simple record-keeping to enforce actual organizational logic through robust data boundaries:

• Five roles, one truth. The system serves five user personas — super admins, program managers, program requesters, and support admins split by function, with HR holding the exclusive authority to confirm terminations. Each role sees a different app: requesters see their program's employees and requests, support admins see fulfillment queues and pending confirmations. Access is scoped by program and department, so the boundaries that exist in the organization exist in the software.
• Passwordless access for a workforce, not an IT team. Login runs on email plus a one-time code, no passwords to forget or reset across hundreds of occasional users. Onboarding is role-specific: the first time any user signs in, the system walks them through exactly the setup their role needs.
• Notifications as the connective tissue. Every state change, a rejection, an approval, a pending termination, triggers an email to exactly the people who need to act. The workflow doesn't depend on anyone checking the app; the app reaches out.
• One employee dataset across the ecosystem. Employee status drives visibility across Rising Ground's connected applications: a terminated employee is reflected in both Issuance and Fleet, because both draw from the same organizational data.

‍

What changed after launch?

‍

And decisions leave a trail: every approval, rejection, handoff, and retrieval has an owner and a record, the questions that used to require asking three people are answered by opening the app.

‍

‍

What these changes represent in numbers

‍

Asset tracking is the kind of problem teams tolerate for years because no single incident feels expensive enough to fix it. The cost only becomes visible in aggregate, missing laptops, orphaned software seats, access that never got revoked. Rising Ground fixed it by replacing the spreadsheet with a workflow: owners, statuses, signatures, and a closed loop at every exit, connected to the systems that run the rest of their operation.

If your onboarding and offboarding still run on memory and goodwill, we can build the system that closes the loop. Let's talk.