Implementation Tracker
The Implementation Tracker is a shared workspace inside NetSuite that you and the FullClarity team use to run a SuiteApp implementation — logging issues as you find them, recording user-acceptance test results, and keeping everyone in sync without separate spreadsheets or email threads.
What it is
When you take on a new FullClarity SuiteApp, there's a period — usually a few weeks — where the configuration is being shaped to your business, real users are exercising it for the first time, and small adjustments are being made before the system goes live. During that period there are two kinds of conversations that have to happen:
- Issues — anything that isn't working the way you expect, or anything you'd like changed before go-live. You log them, the FullClarity team picks them up, you both watch the status until it's resolved.
- User acceptance testing (UAT) — a structured walkthrough of representative scenarios to confirm the system behaves correctly. You run each scenario, record pass or fail, and where it fails you log an issue against it.
The Implementation Tracker brings both of those into one screen inside NetSuite, side-by-side with the records being tested. No external login, no separate URL — it's just a tab in your NetSuite account.
Who it's for
- Customer project managers and end users who are participating in the implementation — logging issues, running test scenarios, marking results.
- NetSuite administrators at the customer site, who install the tracker bundle and connect it to FullClarity using a one-time configuration record.
- FullClarity consultants facilitating the implementation, who watch issues and UAT progress from their side of the connection.
Where you'll find it
Once the bundle is installed and configured, the tracker is reachable from a FullClarity → Implementation Tracker menu entry in your NetSuite account. Opening it loads a two-tab workspace — Issues and UAT — inside the standard NetSuite chrome.
How it connects to FullClarity
The tracker is bound to a single FullClarity engagement. An engagement is FullClarity's record of the work being done for your account — typically one engagement per implementation project. When FullClarity sets up your engagement, they provide a short configuration payload (an API URL, an authentication token, and an engagement key) that you paste once into a single record in your NetSuite account. From then on, anything you log in the tracker is visible to the FullClarity team on their side, and anything they update flows back to your tracker.
If you have more than one implementation running at once (for example, a Project Financials rollout and a separate Subcontracts rollout on a later schedule), each one has its own engagement and its own tracker configuration.
What's logged where
| Kind of thing | Where it goes |
|---|---|
| "This field name is wrong, can you change it?" | An issue, on the Issues tab |
| "Step 3 of the progress-claim test didn't produce the expected total" | A UAT result of fail, with an issue logged from it |
| "We've completed Cycle 1 of UAT" | The cycle gets signed off by an authorised user, locking its results |
| "We've found a related FullClarity transaction to link the issue to" | A NetSuite URL on the issue |
What it isn't
The tracker is not a long-term project management tool or a permanent ticketing system. It's scoped to the implementation period — from kick-off through go-live and any agreed stabilisation window. Once the implementation is signed off and the engagement is closed, the tracker for that engagement is read-only for historical reference. Day-to-day support tickets after go-live are raised through FullClarity's normal support channel, not through the tracker.
Next steps
- Quick start — open the tracker, log your first issue, record your first UAT result.
- Install & configure — for the NetSuite administrator setting up the bundle and connecting it to FullClarity.
- Log an issue — the issue form and what each field is for.
- Run a UAT cycle — recording results and signing off a cycle.