Candidate Evaluation & Preview

PDF Reference Candidates

A structured way to generate or retain pdf reference candidates within Candidate Evaluation & Preview, while keeping automation, zero-chase and scheduled workflows context connected from source record to authorised handoff.

Book a walkthrough Explore the parent feature area

What it does

What PDF Reference Candidates does in Proplix

PDF Reference Candidates is part of Proplix Automation, Zero-Chase & Scheduled Workflows and is designed to generate or retain pdf reference candidates within Candidate Evaluation & Preview. It stays connected to the relevant automation rule, candidate or queue record, so the team can work from one controlled record instead of recreating the same information in inboxes, spreadsheets or notes.

Candidate evaluation, preview and pre-execution checks. In practical terms, PDF Reference Candidates supports candidate evaluation, preview and pre-execution checks. Where the same context matters to candidate evaluation, approvals, action execution, scheduling and escalation, Proplix can reuse the existing record while permissions and workflow state govern what each user can see or change.

Why it matters

Why this capability matters for automation, zero-chase and scheduled workflows

Operational workflows become unreliable when pdf reference candidates is handled differently by each team member. Automation executes against the wrong candidate, without sufficient authority or without a usable audit trail. As volumes grow, that creates repeated checking, inconsistent handovers and duplicated data entry.

Using PDF Reference Candidates inside Proplix reduces that ambiguity by keeping the action close to the automation rule, candidate or queue record and the wider automation, zero-chase and scheduled workflows workflow. The objective is to make existing work more predictable, reviewable and easier to hand over.

When it is useful

Where PDF Reference Candidates adds operational value

This section focuses on the specific operational context for this capability.

The operational question

PDF Reference Candidates is most useful when the team needs to generate or retain pdf reference candidates within Candidate Evaluation & Preview while avoiding a situation where automation executes against the wrong candidate, without sufficient authority or without a usable audit trail. The capability gives that situation an explicit place in the workflow instead of leaving staff to infer the answer from unrelated activity.

What good control looks like

A useful record should show the relevant automation rule, candidate or queue record, current workflow state, material evidence and any authorised decision that affects candidate evaluation, approvals, action execution, scheduling and escalation. Exceptions should remain visible rather than being hidden by the normal path.

How it works

How PDF Reference Candidates fits into the workflow

The exact path depends on the user role, but the source record, evidence, permission or decision state and downstream handoff should remain connected.

01
Start from the correct context
Open the relevant automation rule, candidate or queue record before using pdf reference candidates. Starting from the authoritative record reduces the risk of applying the action to the wrong case or record.
02
Confirm the required information
Review the fields, state and rule conditions, candidate previews, queue decisions, execution logs and schedules needed for the action. Keep missing or contradictory information visible for review.
03
Use the structured Proplix control
Carry out pdf reference candidates through the relevant Proplix workflow so the result is recorded consistently instead of relying on free-text notes or local conventions.
04
Review connected outcomes
Check the candidate evaluation, approvals, action execution, scheduling and escalation and any connected document, financial, communication or reporting view so downstream users receive a coherent state.
05
Retain a reviewable history
Keep significant changes and authorised automation approval and exception decisions connected to the record so a later user can understand what happened and why the workflow progressed or stopped.

Core capability

What this feature helps the team control

Connected source record

Keep pdf reference candidates attached to the authoritative automation rule, candidate or queue record instead of maintaining another independent copy.

Permission-aware workflow

Make the current state clear while limiting sensitive actions and information to authorised roles.

Evidence and exceptions

Keep rule conditions, candidate previews, queue decisions, execution logs and schedules close to the workflow and surface incomplete, rejected or exceptional states for review.

Downstream consistency

Reuse the same operating context across candidate evaluation, approvals, action execution, scheduling and escalation, communications and reporting where appropriate.

Real-world workflow

What this looks like in practice

Consider a normal operating case where the team needs to generate or retain pdf reference candidates within Candidate Evaluation & Preview while avoiding a situation where automation executes against the wrong candidate, without sufficient authority or without a usable audit trail. An authorised user handles PDF Reference Candidates from the relevant automation rule, candidate or queue record instead of opening a separate spreadsheet, creating an unrelated note or relying on an inbox-only instruction.

The immediate benefit is continuity. Another colleague can see the current position, the connected context and what is expected next. If the record later moves into candidate evaluation, approvals, action execution, scheduling and escalation, the receiving team starts from the same controlled information rather than asking users to supply the same facts again.

Implementation standard

How to introduce PDF Reference Candidates into a live operation

A strong implementation defines the source record, responsible role, exception path and audit requirement before the workflow is used at scale.

Before rolling out PDF Reference Candidates, agree the business meaning of the capability in plain language. Define who owns the underlying automation rule, candidate or queue record, which event should trigger the action and which role is responsible for reviewing or approving the result.

Identify the authoritative source for the values used by pdf reference candidates. Reuse existing Proplix data where appropriate instead of creating another copy simply because a different screen needs to display it.

Test the normal case and the main exceptions before relying on the capability at scale. Include missing information, rejected or expired evidence, changes after approval and at least one case where the workflow should stop rather than progress.

Who uses it

Built for authorised teams responsible for automation, zero-chase and scheduled workflows

These capabilities support the people who create, review, approve or rely on this part of the Proplix operating model.

Operations managers

Automation owners

Compliance teams

Authorised administrators

Operational considerations

Keep data quality, permissions and authorised judgement aligned

Data quality remains important. Authorised users should keep the underlying automation rule, candidate or queue record current and resolve material inconsistencies close to the point where they arise.

Permissions should reflect responsibility. Users who can change significant workflow state, financial information, evidence or compliance outcomes should have access appropriate to their role.

Proplix automation follows configured rules and permissions. It does not replace required human judgement or authorisation for sensitive decisions.

Connected Proplix capabilities

Related features in Automation, Zero-Chase & Scheduled Workflows

These related pages sit close to PDF Reference Candidates in the wider automation, zero-chase and scheduled workflows architecture.

Part of the parent feature areaAutomation, Zero-Chase & Scheduled Workflows · 52 capabilities

Explore all capabilities →

How does it work?

Technical flow & related Help Centre guides

Start with the primary guide for this capability, then use the related maintained guides for the surrounding workflow, evidence, access or handoff.

Primary guideChoose an integration that solves a real taskPlan a connected workflow around a clear operational outcome.Related guideBuild an audit pack that tells a clear storyCollect selected records and evidence into a reviewable output.Related guidePlan AI assistance with human reviewUse AI assistance while retaining human review before operational decisions.Related guidePlan secure API access for a Proplix workflowPrepare record scope, permissions and validation for a controlled connection.

Frequently asked questions

Questions about PDF Reference Candidates

What is PDF Reference Candidates in Proplix?

PDF Reference Candidates is a Automation, Zero-Chase & Scheduled Workflows capability designed to generate or retain pdf reference candidates within Candidate Evaluation & Preview, with the action kept inside the wider automation, zero-chase and scheduled workflows record.

When is PDF Reference Candidates most useful?

It is particularly useful when the team needs to generate or retain pdf reference candidates within Candidate Evaluation & Preview while avoiding a situation where automation executes against the wrong candidate, without sufficient authority or without a usable audit trail. A structured workflow gives authorised staff a shared current position without reconstructing context from separate systems.

Who should use or review PDF Reference Candidates?

The exact users depend on your organisation, but access should be limited to the authorised roles responsible for the relevant source information, review, decision or handoff.

Does PDF Reference Candidates replace professional or legal judgement?

Proplix automation follows configured rules and permissions. It does not replace required human judgement or authorisation for sensitive decisions.

See it in context

See how Proplix can structure automation, zero-chase and scheduled workflows

A walkthrough can focus on the workflows, evidence, access and handoffs relevant to your organisation.

Book a Proplix walkthrough →

Working with the capability

How Pdf Reference Candidates fits into dependable property operations

A credible workflow connects everyday actions with the records and responsibility needed to explain the outcome later. This capability belongs inside the daily operating record, where property context, relationships, tasks, documents and decisions can be followed together instead of being reconstructed from separate systems.

01 · People and permissions

Give each role enough context to act

Operational staff need a clear next action; managers need ownership and exceptions; clients and external participants need only the information their role permits. The practical value comes from serving those views without creating parallel versions of the truth. For Pdf Reference Candidates, that means access should follow an evidenced business need and change when responsibility changes.

02 · Handover and evidence

Keep the reason beside the action

A useful workflow records who received the work, what they checked, what remains outstanding and why a decision was made. That creates a handover another authorised colleague can understand without relying on private inbox history. This makes the Pdf Reference Candidates record more useful during absence, escalation, service review or a later audit.

03 · Exceptions

Design for the case that does not fit

Property work includes incomplete forms, late evidence, changed instructions, unavailable suppliers and circumstances requiring discretion. The system should expose those exceptions, preserve notes and direct them to an authorised person instead of silently forcing a misleading “complete” status.

04 · Implementation

Configure from representative work

Implementation should begin with real examples from the organisation: a recent case that went well, one that stalled and one that exposed missing information. Those examples reveal the fields, permissions, notifications and escalation points the configured workflow actually needs. Document what remains outside the system as well, so teams understand the boundary between Proplix, connected services and professional responsibility.

05 · Review

Measure whether the work is improving

A sensible review looks at completion time, avoidable follow-up, unresolved exceptions, record quality and the amount of manual reconciliation still required. The aim is dependable work and clearer service, not automation for its own sake. Review findings with the people completing Pdf Reference Candidates work, because a dashboard may not reveal the manual workaround being used beside it.

06 · Ongoing control

Keep guidance, permissions and records current

Ownership, legislation, services and internal policies change. Schedule periodic checks of access, templates, notifications, integrations and retained information. Record material changes and brief affected users so the configured workflow continues to reflect the organisation’s approved way of working.

Proplix supports structured workflow and evidence handling; it does not provide legal advice or remove the need for competent human review. Discuss your organisation, migration or integration requirements through the central secure enquiry route.

Discuss Pdf Reference Candidates requirements →

Plan your next step

Bring a typical case, the systems you use and the main problem you want to solve. Together we can map the records, responsibilities and checks needed for a useful first release.

Explore software integrations, compare enterprise modules or discuss a custom property workflow. The agreed scope will explain what is included, what needs configuration and how your team will be supported.

Search Proplix