Vendor Portal Terms Property Managers Should Know

A vendor portal is a web application that gives contractors a controlled way to see the work assigned to them, submit documents, and record what they did, without being given an account in the property's core systems. Scoping one goes wrong mainly because the vocabulary is unfamiliar: a property manager approves a specification containing terms that carry very different costs, and discovers the difference during build. This glossary covers the terms that actually change the quotation. As a Singapore-based AV and IPTV integrator Prestige Solutions builds these portals alongside the systems they administer, and the same handful of words decide the scope every time.

What do the access and identity terms mean?

Access terminology is where most of the early misunderstanding sits, because several terms sound interchangeable and are not. Getting these right at specification time is what determines whether a contractor's leaving date is a two-minute administrative action or a week of uncertainty about which systems they can still reach.

• Onboarding — the process of admitting a company to the portal: verifying the entity, collecting insurance and certification documents, and creating its first administrator account.
• Provisioning — creating and removing individual user accounts within an already-onboarded company. This is the routine action; onboarding happens once.
• Delegated administration — allowing the contractor's own administrator to add and remove their staff, rather than routing every change through the property. Cheaper to run, and it requires trusting the contractor to remove leavers.
• Single sign-on (SSO) — letting users authenticate with an existing corporate identity rather than a portal-specific password. Valuable for internal staff, frequently impractical for small contractors who have no corporate identity provider.
• Site scope — the set of properties a user can see. The most commonly misconfigured setting, and the usual explanation when someone reports that records are missing.

The practical decision here is between delegated administration and central control. Central control is safer and generates a steady administrative load on the property team. Delegated administration removes that load and makes offboarding depend on the contractor. Most properties end up delegating and adding a periodic access review to compensate.

What do the work and scheduling terms mean?

The second cluster of terms describes the work itself. These are the ones that determine how many screens the portal needs, because each distinct state in the lifecycle of a job is typically a view, a permission, and a notification.

SLA clocks deserve particular attention during specification. The measurement is trivial; the rules are not. A clock that keeps running while the portal is waiting for the property's own approval will produce numbers the contractor disputes, and the dispute will be correct.

What do the record and compliance terms mean?

The third cluster is about what the portal keeps, and it is the part most likely to be underspecified because it produces nothing visible day to day. It becomes visible during an audit, an insurance claim, or a dispute about whether a contractor attended.

• Audit trail — an append-only record of who changed what and when. Distinct from a change history that can be edited; the difference matters only when something is contested.
• Document expiry — tracking the validity dates on insurance certificates and trade licences, with automated notice before lapse. Without it, expiry is discovered when a claim is made.
• Attendance evidence — the proof that someone was on site, whether that is a scanned asset tag, a geotagged photo, or a signed acknowledgement from staff.
• Retention period — how long records are kept before deletion. Set this deliberately; the default of keeping everything forever is a decision too, and rarely the intended one.
• Export — the ability to extract records in a portable format. The property's insurance against being locked into the portal, and often omitted from a first specification.

Document expiry tracking is the highest-value item in this list relative to its build cost. A contractor working on site with lapsed insurance is a risk the property carries, and the portal is the only place where that information already exists in a structured form.

Which terms are commonly confused?

Three pairs cause most of the scope disputes, and all three are worth resolving explicitly in the specification rather than during user acceptance testing.

Onboarding and provisioning are the first. A specification saying contractors can self-manage onboarding usually means provisioning, because no property allows a company to admit itself without document verification. The second pair is notification and escalation: a notification tells someone something happened, while an escalation routes to a different person when nobody acts. Escalation needs a rule set and an owner, and costs several times what a notification does.

The third is reporting and dashboard. A dashboard shows current state to someone looking at it now; reporting produces a document about a past period that somebody else will read. They share data and almost nothing else, and a specification that names one while describing the other reliably produces a build the property manager does not recognise.

Budget and Price Guidance in Singapore

Vendor portal quotations in Singapore vary widely for the same nominal brief, almost entirely because the terms above were read differently. Pricing the clusters separately makes the comparison meaningful and shows where scope can be deferred to a later phase.

Frequently Asked Questions

What is the difference between onboarding and provisioning?

Onboarding admits a company to the portal once, with entity verification and document collection. Provisioning creates and removes the individual user accounts inside that company, and happens continuously. Specifications that let contractors self-serve almost always mean provisioning, because no property allows a company to admit itself unverified.

Should contractors manage their own user accounts?

In most cases yes, with a periodic access review as the compensating control. Central account management is safer in principle and creates a steady administrative load that the property team eventually deprioritises. Delegated administration with a quarterly review of who still holds access is more likely to remain accurate a year in.

Why do SLA measurements get disputed?

Because the pause rules were never agreed. A clock that keeps running while the portal waits for the property's own approval will report a contractor breach that the contractor did not cause. Define what stops the clock before the portal is built, not after the first performance review.

Is single sign-on worth requiring for a vendor portal?

For internal staff, usually. For contractors, often not, because smaller firms have no corporate identity provider to connect to and the requirement becomes an onboarding obstacle. A common answer is single sign-on for internal users and portal-managed credentials with multi-factor authentication for external ones.

How long should portal records be retained?

Long enough to cover the property's insurance and contractual exposure, decided explicitly rather than inherited as a default. Keeping everything indefinitely is also a decision, and it is rarely the one that was intended. Pair the retention period with an export capability so records outlive the portal itself.

Recommended next step

Contact Prestige Solutions to walk through your site drawings and current operating pattern. Call +65 8010 2337, message us on WhatsApp, or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.