From kickoff to the first payment run.
How a Journey implementation runs: what happens each week, who does what on each side, and what we need from you before we arrive on site.
The weeks move with how quickly your data clears the readiness gate. The order does not.
Eight phases, in the order the data allows.
Each phase depends on the one before it. A project cannot be configured until its grant table exists, a tenancy cannot be imported until its unit and household are in, and a payment run cannot be previewed until every tenancy carries its rent math.
The import happens at your desk, not over email.
Once your biggest project's data clears the readiness gate, our implementation team comes to you for three days. The people who ran the data request run the import, with your data owner and accounting lead beside them.
Items surface in every import: a grant with two HMIS codes, a rent roster that only carries HAP, an owner paid through two accounts. Each one gets worked the same day — what it means for the project setup, what the options are, and which resolution holds up at month end. The decision goes in the log, and the import keeps moving.
- ✓ Personal data is stripped on your systems before any file leaves them, and re-joined on your machine before upload.
- ✓ Imports run in dependency order, so a tenancy never lands ahead of its unit, household or voucher.
- ✓ Every decision made in the room is written to the onboarding hub the same day.
I wanted to take a moment to thank you and your team for the successful implementation of Padmission. I speak for the whole team when I say everyone involved has been very responsive, solution focused, and has demonstrated their knowledge of the product throughout the process. I'm especially thankful for the implementation on-site team. Daniel and Kenneth were professional, positive, and acutely focused during their time here which contributed to the successful launch. I also appreciated the "think tank" approach as we identified items that needed to be addressed and worked through what the implications would be and the best resolution.
Four people and four files.
Name the people at kickoff and start pulling the files the same week. The rent roster and the project table are the long poles; everything else can follow.
The people
Drives adoption on your side and carries questions between end users and the project team.
Produces the source extracts and runs the local script that strips personal data before anything is shared.
Owns bank accounts, payment accounts and the month-end run; reviews the first HAP and URP preview.
Owns users, roles and permissions in Journey once configuration is handed over.
The files
One row per assisted tenancy: contract rent, tenant rent, utility allowance, HAP, URP, move-in and lease dates, next recertification, and the program code it belongs to. If your roster only carries HAP, a HUD-50058 or certifications export fills the gap.
One row per project, sub-project, grant or funder, with its HMIS code, intervention, rental assistance type, payment standard basis and the behaviors it tracks: inspections, lease renewals, recertifications, month-end payments.
Per member, with the HMIS ID and relationship to head of household. Missing values are imported with a flagged placeholder and corrected after.
Tax classification, 1099 status and ACH details for each property owner, so owner records import complete rather than blank.
Before you commit to a date.
- How long does a Journey implementation take?
- Most run eight to twelve weeks from kickoff to the first project going live. The order of the phases does not change; the weeks do, and they move with how quickly your data clears the readiness gate.
- Do our existing tenancies and payment history carry over?
- Yes. Assisted tenancies are imported with their rent math, lease dates and recertification dates, and prior-period HAP and URP transactions can be imported ahead of go-live so the first month-end in Journey reconciles to the last one outside it.
- Who needs to attend training?
- Everyone who will touch a tenancy or a payment: program managers, household specialists, property specialists, inspectors and accounting. Sessions are by role, so nobody sits through a workflow they will not run.
- What happens after go-live?
- A wrap-up sets out what ongoing support looks like and the service levels in your agreement, followed by reviews at one month and three months. The onboarding hub stays open as the record of every decision made during the implementation.
Bring your go-live date. We'll work backwards from it.
A conversation with someone who has run an implementation: what your weeks look like, which files to start pulling now, and who you need on your side.