Consent and request operations
Document workspaceReference request tracker for a UK tenancy application
A tracker should show who owns the next action and what state a request has reached without copying the private reference response or contact narrative into the coordination table.
- Market
- UK
- Jurisdiction
- United Kingdom
- Updated
Short answer
Create one row per requested reference with the requested subject and period, contact permission status, recipient-approved route, request owner, sent time, delivery state, response state and next action. Keep delivery separate from response and store no testimonial content in the tracker. Respect a defined contact boundary, record scope changes, and close each row when answered, declined, withdrawn or escalated to the recipient.
Continue in RentFiles
Turn this guide into a clear application pack
Enter and check details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application or decide the outcome.
- Prepare a structured rental application PDF with RentFiles.
- Fill your application before you choose whether to pay for a PDF export.
- RentFiles helps organise the file; the agent or landlord decides the application outcome.
Working checklist
Collect consent and route fields
Record whether the person has agreed to the named recipient, purpose and contact route. Permission for one application does not automatically cover another. Confirm whether the recipient sends the request directly, expects applicant coordination or uses another process before marking the row ready to send.
Add scope wording that tells the contact what period or relationship is relevant without coaching their answer. If the recipient changes the question, return to the person for confirmation rather than silently expanding the request. The tracker should preserve both the old scope and the date of the change.
- Permission state
- Named recipient
- Approved route
- Scope wording
- Scope change
Working checklist
Close and audit every request row
At closeout, confirm the final request, delivery and response states, the last permitted action and whether the recipient needs an alternative question. Remove duplicate drafts and obsolete contact exports. Keep only a minimal operational record within the applicant's control, subject to current purpose and any applicable obligation.
Stop if consent is absent, scope changed without confirmation, a response is inferred or another person's words are copied into the tracker. RentFiles can structure applicant-entered details into a PDF but does not run reference workflows, send invitations, verify delivery, read responses or decide the application.
- Final state
- Last action
- Alternative question
- Obsolete copy removed
- No inferred response
Action plan
Separate request, delivery and response states
Use draft, ready, sent and closed for the request; unknown, delivered or failed for delivery; and awaiting, responded, declined or unable to confirm for response. These state groups prevent a sent request from appearing answered or a delivery acknowledgement from appearing to validate the content.
Record timestamps only for observed events. Do not backfill sent or responded because someone remembers that contact probably occurred. When a platform controls delivery, describe only the status visible to the applicant and avoid claiming what the recipient or contact saw beyond that evidence.
- Request state
- Delivery state
- Response state
- Observed time
- Platform limitation
Useful context
Define the tracker's operational job
Start from the recipient's reference request and identify the subject and period before naming a contact. The tracker coordinates permission, routing and status. It should not contain opinions, scores, private reasons for a response or a copy of the statement another person supplies.
Assign each row a unique neutral identifier so status updates do not expose contact names in dashboards or filenames. Keep the contact directory in a controlled location linked to the row. This separation lets the applicant share operational progress internally without broadly distributing another person's details.
- Request subject
- Covered period
- Neutral row ID
- Contact directory
- Request owner
Keep in view
Keep the tracker privacy-light
Store only the minimum contact-routing metadata needed for coordination. Keep phone numbers, email addresses, reference text and private discussion out of the activity table. Limit access, use neutral exports and remove temporary contact lists after the request reaches a final state and the applicant reviews their purpose.
ICO wording supports limiting personal information to the stated purpose. It does not prescribe request routes, contact intervals or acceptable reference content. Those details come from the recipient and the person's consent, while any legal claim requires independently appropriate authority.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- Minimum metadata
- Reference text excluded
- Access limited
- Temporary list review
- Authority boundary
Questions
Common questions
Clear answers for the decisions people usually pause on.
Should the reference response be stored in the tracker?
No. Keep the tracker operational and store any recipient-requested response through its proper controlled route rather than copying private content broadly.
Does sent mean a reference request was delivered?
No. Request, delivery and response are separate states. Record only the state the applicant can actually observe.
How often should the applicant follow up?
This page sets no universal interval. Respect the person's permission and contact boundary, and ask the recipient how to handle delay.
What if the recipient changes the reference question?
Record the new scope and return to the contact for confirmation before expanding what they are being asked to address.
Does RentFiles send or track reference requests?
No. RentFiles organises applicant-entered details into a PDF. It does not contact referees, monitor delivery, read responses or decide outcomes.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Enter and check details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application or decide the outcome.
Fill your application before payment