Change-since-start review

Local planning guide

St Kilda rental application refresh workflow

An application can become stale while it is being prepared, so the final review should identify actual changes rather than rely on the date a folder was created.

Market: AU
Jurisdiction: Victoria, Melbourne
Updated: 2026-07-22

Short answer

Record the starting source and preparation date for each property instruction, applicant fact and selected file. Before handoff, ask whether the source changed, the fact changed or only the working copy changed. Reopen current instructions, verify applicant-owned details and rebuild sharing copies when their source changed. Label unchecked items unresolved; do not invent a universal freshness period or call a file current merely because it was recently downloaded.

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.

Fill your application before payment Use the free Rental Document Status Check

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.

Useful context

Orient around changes since preparation began

Create a register row for the application form, recipient messages, key applicant facts and each proposed attachment. Record the original check date and source owner. The task is to discover changes, not to apply a single age limit to unlike records or claim that St Kilda recipients use a shared validity window.

Classify the refresh outcome as unchanged after recheck, changed, source unavailable or not rechecked. Avoid the word current when no comparison occurred. A new download may reproduce old information, while an older source may still accurately cover the requested historical period; purpose and source determine the question.

Starting source
Original check
Refresh owner
Outcome state
Purpose

Working checklist

Map what must be reopened

Prioritise sources that control the recipient route, property label, requested fields and applicant statements likely to change. Link every row to the place where the authoritative version can be reopened. A copied instruction in a note is not enough when the underlying form or message remains available for comparison.

For attachments, distinguish source content from sharing-copy format. A source can remain unchanged while the prepared PDF is cropped, renamed or incomplete. Conversely, the sharing copy can open perfectly while the underlying fact changed. Give those checks separate columns and separate outcomes.

Instruction source
Applicant fact source
Source-content check
Sharing-copy check
Difference note

Working checklist

Reconcile the refreshed application set

Immediately before handoff, compare the refreshed register with entered fields and final filenames. Every changed item should point to the new source and every unchanged label should follow an actual recheck. Preview page order and recipient context from the final folder, not a general source archive.

Record the handoff version and refresh time without copying private values into the log. If a change appears after the freeze, pause and create another version. Do not patch one file silently while leaving contradictory dates or labels in the form, manifest or explanatory note.

Register agreement
Source link
Final preview
Refresh time
New-version trigger

Action plan

Plan the refresh before viewing or sending

Choose a refresh owner and a sensible checkpoint based on the applicant's workflow, not an invented local deadline. Reconfirm the recipient's current form after any property update or long pause. Ask a specific question where a field, route or requested period has become unclear.

Do not create new sensitive copies during an early planning check. First determine whether the applicant still intends to proceed and what changed. Rebuild only the sharing set needed for the confirmed request, then remove superseded temporary copies to keep an obsolete version from returning during upload.

Refresh owner
Proceed decision
Current form
Clarification
Superseded copy removal

Keep in view

Bound freshness and local claims

This page states no St Kilda document age rule, application deadline, standard update frequency or recipient preference. A recipient can define its process, and a genuine rule needs appropriate official authority. When neither source answers a freshness question, mark it unresolved and ask rather than applying a guessed interval.

The OAIC wording supports selecting relevant information and handling sensitive material carefully. It does not make a refreshed file acceptable. RentFiles can organise applicant-entered details into a structured PDF but does not monitor source changes, inspect attachments, submit them or decide the application outcome.

Provide information relevant to the recipient's application process and handle identity or financial material carefully.

No local age rule
No update frequency
Recipient clarification
Relevant information
Product boundary

Questions

Common questions

Clear answers for the decisions people usually pause on.

How recent must a St Kilda application file be?

This page sets no universal period. Check what the file shows, the recipient's current request and any appropriately scoped authoritative requirement.

Does a new download make a document current?

Not automatically. Compare the visible content and covered period with the source and purpose instead of relying on the download timestamp.

When can an item be labelled unchanged?

Only after reopening the relevant source and comparing it with the recorded version. Otherwise use not rechecked or source unavailable.

What if a fact changes after the final freeze?

Pause the handoff, update the source-linked record and create a newly checked version across the form, manifest and sharing set.

Does RentFiles monitor St Kilda application changes?

No. RentFiles structures details the applicant enters into a PDF. It does not monitor sources, inspect files, submit applications or decide outcomes.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack