When APIWORX begins implementing a new integration, an onboarding project is created in the customer portal. The project surfaces the implementation phases — discovery, design, build, validation, go-live — along with the owner for each task, expected dates, and any items waiting on customer input. Reviewing the project weekly keeps both teams aligned and prevents "we thought you were doing that" handoff gaps.
Stakeholders who need visibility but should not own tasks can be added as portal viewers. They will see the same milestone view without being able to edit project assignments. For tasks assigned to the customer team — such as providing API credentials, uploading sample data, or approving field mappings — completing them quickly is the single biggest factor in keeping the project on schedule. Each task includes a description of what is needed and the format expected.
If a project is at risk because of an internal blocker, use the project comments to flag it to the implementation lead. That signal lets the APIWORX team adjust the schedule, propose a workaround, or reprioritize internal work. Onboarding projects close out only after acceptance criteria are met and the integration is in stable production operation, so the view also serves as your historical record of what was delivered.
What to keep in mind
- Review the project weekly to keep both teams aligned on owners and dates.
- Customer-side tasks are usually the critical path — complete them first.
- Use comments to flag blockers early so the schedule can be adjusted.
- Closed projects remain visible as a record of what was delivered.