TraceLogic - Pilot Support and Feedback

Submit support message

Required fields are category, subject, and message. Where identity, role, or tenant details are already available from the current session, they are pre-filled to reduce manual entry and support tenant-aware routing.

Pilot routing

Category

Please select a category.

Subject

Please enter a subject.

Submitted by name

Auto-filled from session where available. If not available, please enter your name.

Please enter your name.

Submitted by email

Auto-filled from session where available. If not available, please enter a valid email address.

Please enter a valid email address.

Role

Read-only session role where available. Defaults to guest if no authenticated role is present.

Tenant

Read-only tenant context where available. Defaults to mortgage-tenant-1 for pilot-safe routing.

Message

Please enter your message.

Back to Dashboard Back to Home

Submission context

Read only

Routing endpoint POST /support/feedback

Expected status New support messages should map cleanly to the pilot support messages table in Neon and be reviewed by the TraceLogic pilot team.

Support email admin@tracelogic.ie

Allowed categories Bug Report, Access Issue, Decision Query, General Feedback, Feature Request.

Session user Loading session context…

Session role Loading session context…

Tenant context Loading session context…

Dashboard Home Trust

Synthetic Test Data Prompt

Testing only

Copy this prompt when you need to generate fictional mortgage case documents for intake and RAG testing. Use synthetic data only. Never use real customer, account, property, solicitor, PIP, lender, or servicer information.

Important Synthetic test data is for pilot validation only. It must not contain real customer data, live account numbers, real addresses, real arrears cases, real legal documents, or confidential lender material.

Step 1

Copy the prompt.

Step 2

Paste it into an approved AI tool.

Step 3

Upload the generated fictional document into TraceLogic intake and review the extracted values before evaluation.

You are acting as a senior mortgage operations analyst, arrears support specialist, credit governance reviewer, and synthetic mortgage document generator for TraceLogic.

Objective:
Create realistic synthetic mortgage case document packs that simulate what happens in a real BAU TraceLogic intake stage.

TraceLogic intake context:
In a live BAU scenario, the intake stage is not the final decision stage. It is the controlled case creation and evidence preparation stage.

At intake:
1. The case begins in Draft.
2. The operator either uploads mortgage documents or manually enters case details.
3. If documents are uploaded, AI/RAG extraction produces draft values only.
4. The operator must review extracted values.
5. Missing fields must be completed.
6. Incorrect extracted values must be corrected.
7. Relevant linked accounts must be added or verified.
8. Governance evidence and regulatory preconditions must be confirmed.
9. Only then can the case proceed to deterministic decision evaluation.

The synthetic documents must test:
- RAG extraction from realistic mortgage documents.
- Field population into the editable intake workspace.
- Missing field detection.
- Human review and correction.
- Governance evidence verification.
- Route-specific field visibility.
- Correct handling of different forbearance options.
- Correct preparation of the case for deterministic evaluation.

Important rules:
Use only fictional customers, fictional addresses, fictional account references, fictional organisations, fictional PIP names, fictional solicitor names, fictional document references, and fictional case IDs.
Do not use any real lender, mortgage servicer, bank, regulator, customer, company, solicitor firm, PIP firm, or real customer name.
The documents must feel realistic for BAU mortgage operations, but they must contain no real personal data.

Required synthetic case types:
Create 10 separate synthetic mortgage case document packs.

Case 1: Standard Rate Modification
Case 2: Term Extension
Case 3: Arrears Capitalisation
Case 4: Split Mortgage
Case 5: Loan Modification with combined rate change, term extension, and arrears capitalisation
Case 6: Part and Part Arrangement
Case 7: Temporary Interest Only Arrangement
Case 8: Personal Insolvency Arrangement, PIA creditor review
Case 9: Customer or adviser-led forbearance request
Case 10: No ARA Offered governed path

Each case must simulate material a BAU operator might upload into TraceLogic intake, such as:
- Customer request letter
- Arrears support review note
- Standard Financial Statement summary
- Forbearance proposal note
- PIA proposal
- Internal ARA recommendation
- Credit committee support note
- Repayment capacity assessment
- Valuation and security summary
- Borrower communication record
- Vulnerability note where relevant
- Appeal or no-ARA communication where relevant

For each synthetic case, produce:

1. Main Mortgage Case Proposal Document
Write this as a realistic business document that a mortgage operations team could receive or prepare before intake review.

It must include:
- Case reference
- Account reference
- Customer name
- Property address
- Jurisdiction
- Forbearance route
- Current balance
- Arrears position
- Current repayment
- Current rate
- Maturity date
- Borrower circumstances
- Financial position
- Proposed treatment
- Reason for recommendation
- Alternative options considered
- Rejected options and reasons
- Regulatory notices or borrower communication
- Supporting evidence references
- Any missing or pending items

2. Intake Extraction Appendix
Provide a structured appendix using the exact TraceLogic field names and expected values.

3. JSON Expected Extraction Object
Provide a valid JSON object using exact TraceLogic field names.

4. CSV-Style Key-Value Expected Extraction Table
Provide the same expected values in this format:
field_name,value

5. BAU Intake Review Note
For each case, explain:
- Which fields should be extracted automatically from the document.
- Which fields a BAU operator would likely need to manually confirm.
- Which fields should appear as missing if not supplied.
- Which governance evidence checkboxes should be confirmed before submission.
- Whether the case should proceed to decision evaluation or remain blocked pending more information.

6. Test Expectation Summary
For each case, state what TraceLogic should test:
- Route recognition
- Field extraction
- Missing field detection
- Linked account handling
- Governance evidence readiness
- Deterministic evaluation readiness
- Any execution gate or replay implications

TraceLogic intake fields to use:

Case Identification:
- case_id
- modification_type
- account_id
- customer_name
- property_address
- jurisdiction

Allowed modification_type values:
- standard
- term_extension
- capitalisation
- split
- loan_modification
- part_and_part
- temporary_interest_only
- pia

Allowed jurisdiction values:
- IE_CCMA
- IE_MARP
- UK_FCA
- UK_MCOB
- out_of_scope

Proposal Route and Ownership:
- proposal_route
- request_initiator
- proposal_source
- proposal_author
- formal_proposal_owner
- lender_role
- creditor_review_required
- customer_acceptance_required
- court_or_isi_dependency
- proposal_received_date
- proposal_expiry_or_response_deadline
- proposal_document_reference
- proposal_lifecycle_status
- case_legal_status

Allowed proposal_route examples:
- internal_ara
- internal_loan_modification
- pia_creditor_review
- customer_request
- adviser_led_request
- no_ara_offered
- other

PIA and Legal Stage Controls:
- pip_involved
- pip_name
- protective_certificate_granted
- protective_certificate_expiry_date
- isi_reference
- court_review_required
- court_approval_received
- creditor_meeting_or_voting_outcome
- court_order_document_reference

Alternative Repayment Arrangement Options Documentation:
- options_considered
- options_rejected
- reason_each_option_rejected
- reason_selected_option_is_sustainable
- borrower_specific_justification
- borrower_explanation_generated
- advantages_explained
- disadvantages_explained
- independent_advice_notice_required
- appeal_rights_required
- borrower_notice_document_reference

No ARA Offered Path:
- no_ara_offered
- no_ara_reasons
- borrower_appeal_available
- appeal_submitted
- appeal_upheld
- appeal_rejected

Borrower Acceptance:
- borrower_acceptance_required
- borrower_acceptance_received
- borrower_acceptance_date
- borrower_acceptance_document_reference

Arrangement Terms and Monitoring:
- arrangement_duration_type
- review_date_required
- review_frequency
- arrangement_expiry_date
- post_arrangement_monitoring_required
- first_payment_due_date
- first_payment_received
- arrangement_performing
- missed_payment_after_arrangement
- review_triggered
- breach_of_arrangement

Joint Borrowers, Consent, and Third-Party Data:
- joint_borrowers_present
- all_borrowers_notified
- all_required_consents_received
- representative_authority_verified
- third_party_data_present
- third_party_data_processing_basis

Exposure Metadata:
- curbal
- pay_rate_now
- maturity_date
- monthly_repayment
- original_loan_amount
- property_value
- loan_origination_date

Arrears Profile:
- arrears_lme
- months_in_arrears
- arrears_days
- arrears_status

Affordability Indicators:
- affordability_status
- net_monthly_income
- monthly_expenditure

Security Details:
- property_type
- valuation_date
- ltv_ratio

Regulatory Context:
- regulatory_context

Customer Vulnerability:
- vulnerability_present
- vulnerability_notes

Aggregate Exposure:
- total_exposure
- exposure_required

Proposed Modification:
- new_rate
- new_maturity_date
- proposed_monthly_repayment
- capitalisation_amount
- tio_rate
- tio_duration_months
- tio_effective_date
- tio_review_date
- pia_payment_amount
- pia_end_date
- proposed_active_balance
- proposed_warehoused_balance

Repayment Classification:
- repayment_method
- rate_structure
- arrangement_type
- repayment_other_description

Reference Rate:
- ref_rate_type
- ref_rate_value
- ref_rate_margin

Account Structure:
- primary_account_id
- account_type
- case_group_id
- linked_accounts_count
- account_relationship
- marp_status

Statutory Proof:
- valuation_validity_status
- credit_bureau_snapshot
- cooling_off_status
- statutory_proof_timestamp
- statutory_proof_hash

CCR and Regulatory Reporting:
- ccr_required
- ccr_trigger_reason
- ccr_status
- ccr_reference
- ccr_timestamp

Data Freshness:
- intake_timestamp
- last_updated_timestamp
- data_ttl_hours
- freshness_status

Exception Governance:
- exception_required
- override_type
- override_reason
- exception_justification
- second_level_approval_required
- exception_approved_by
- exception_approved_at
- exception_policy_reference
- exception_tag

Confidence and Data Origin:
- classification_confidence
- confidence_threshold_status
- field_trace_status
- reference_effective_rate
- reference_captured_at

Governance evidence checkboxes to simulate:

Financial Assessment:
- Standard Financial Statement on record
- Repayment capacity documented

Regulatory Compliance:
- Alternative arrangements assessed
- Regulatory disclosures issued
- Borrower response window elapsed
- Formal arrears notice issued where required

Decision Justification:
- Suitability statement recorded
- Rejected options documented

Route-specific rules:

For standard:
Include new_rate, new_maturity_date, proposed_monthly_repayment.

For term_extension:
Include new_maturity_date and proposed_monthly_repayment.

For capitalisation:
Include capitalisation_amount and proposed_monthly_repayment.

For split:
Include proposed_active_balance, proposed_warehoused_balance, new_rate if relevant, new_maturity_date if relevant, proposed_monthly_repayment, and capitalisation_amount if applicable.

For loan_modification:
Use a realistic combination of new_rate, new_maturity_date, proposed_monthly_repayment, and capitalisation_amount.

For part_and_part:
Include repayment_method as part_and_part and provide a clear explanation of the capital and interest portion and interest-only portion.

For temporary_interest_only:
Include tio_rate, tio_duration_months, tio_effective_date, tio_review_date, and proposed_monthly_repayment.

For pia:
Include PIA/legal controls such as pip_involved, pip_name, protective_certificate_granted, isi_reference, creditor_review_required, court_or_isi_dependency, pia_payment_amount, and pia_end_date.

For no_ara_offered:
Set no_ara_offered to true.
Include no_ara_reasons, borrower_appeal_available, appeal fields, borrower notice reference, and rejected options.
Do not create a normal proposed modification as if an ARA was offered.

BAU realism requirements:
Each synthetic case must contain natural wording that may not exactly match the field names.

Use phrases such as:
- current mortgage balance
- present repayment
- arrears outstanding
- revised monthly instalment
- proposed new maturity
- temporary interest only period
- warehoused balance
- customer has accepted the arrangement
- borrower has not yet returned signed acceptance
- protective certificate granted
- creditor review pending
- no sustainable ARA identified

Include deliberate variation:
Some cases should have complete evidence and be ready for decision evaluation.
Some cases should have missing information that a BAU operator must complete.
Some cases should have borrower acceptance pending.
Some cases should have legal or ISI dependency pending.
Some cases should include vulnerability.
Some cases should include linked accounts.
Some cases should include CCR required.
Some cases should include no exception.
Some cases should include an exception requiring second-level approval.

Output structure:
Start with a summary table showing:
- Case number
- Case ID
- Customer name
- Modification type
- Proposal route
- Main test purpose
- Expected intake status

Then provide each case in this structure:

CASE [number]: [case title]

A. Main Synthetic Mortgage Document
Write the full realistic document.

B. Expected TraceLogic JSON Extraction
Provide valid JSON using exact TraceLogic field names.

C. CSV-Style Field Mapping
Provide field_name,value format.

D. BAU Intake Review Note
Explain what the operator should verify, correct, or complete.

E. Governance Evidence Checklist
List which governance evidence items should be confirmed before proceeding.

F. Expected TraceLogic Behaviour
State whether the case should:
- Proceed to decision evaluation
- Remain in draft pending missing information
- Be blocked because governance evidence is incomplete
- Be treated as a non-execution path
- Require manager review or exception approval

Quality checks before final answer:
- Every case_id must be unique.
- Every account_id must be unique.
- Values must be internally consistent.
- Dates must be realistic.
- Numeric fields must be extraction-friendly.
- JSON must be valid.
- The modification_type must match the proposed modification fields.
- PIA fields must only be populated for PIA cases unless explicitly marked not applicable.
- Temporary interest only fields must only be populated for temporary interest only cases.
- Split mortgage fields must only be populated for split mortgage cases.
- No ARA Offered must not contain a normal proposed ARA as if accepted.
- Borrower acceptance must be pending, received, or not required depending on the case lifecycle.
- Do not fabricate final decision outcomes. These documents are for intake preparation and decision evaluation testing, not for bypassing manager review or deterministic governance.

Send a pilot support message