(Notes)

Contacting every landowner during selection: invitation links, tutorials, announcements and a usage log

In urban renewal selection, invitation links go out over LINE, the sign-in page and tutorials suit older owners, and the back office shows who signed in and read announcements.

Polish Design engineering team・2026-11-14

Contents

During selection, owners are numerous, older on average and scattered across places. The case team needs to know where each one stands in order to make contact at the right time. Article 5 of the Enforcement Rules for Rights Transformation requires the implementer to survey the owners' wishes on assigned positions, and the system has a matching set of features: invitations, tutorials, announcements and a usage log, so the case team can contact every owner and keep track of reading and sign-in status. These features are part of Urbird|Urban renewal, from plan to handover.

A corner of an older neighborhood, apartment balconies lined with potted plants and a quiet lane under the trees.
A corner of an older neighborhood, apartment balconies lined with potted plants and a quiet lane under the trees.

Invitations and sign-in: one link to get started

The case team creates the owner record in the back office, the system generates a one-time invitation link, and the case team sends it over LINE. The owner opens the link, confirms identity, writes down the password and signs in with it from then on. Older owners only have to complete this one step.

The sign-in page is designed for older users. Type is enlarged, and the password appears in a monospaced font in three groups that are easy to copy by hand. After the password is shown, the screen offers no action that leads to another page, and no confirmation pop-ups appear, so a stray tap on a phone does not break the flow. A show key lets owners see what was typed. For a missing or forgotten password, the screen tells the owner to contact the building lead. Help points to the building lead and the case team, and it can be found on every screen.

Fig. 1The case team sends the invitation, the owner sets a password, and help stays on screen throughout
Create record
Send invitation
Open link
Daily sign-in
Case team
Owner
System
1
Case teamCreate the owner record in the back office
2
SystemGenerate a one-time invitation link
3
Case teamSend it to the owner over LINE
4
OwnerConfirm identity and write down the passwordThe password is shown once
5
SystemDatabase stores only a password hashEven the case team cannot look it up
6
OwnerSign in on the large-type pageHelp options are on screen

Based on the invitation and sign-in flow of . Field details on the sign-in screen follow the delivered version.

Tutorial videos: played inside the platform

The platform includes a full tutorial of about 6 and a half minutes, also split into 7 units: signing in, viewing the home, registering a selection, the second and third choices, editing, viewing in 3D, and the member center. Each unit plays only its own segment, so owners watch just the part needed.

Videos play in a dialog without leaving the site. When it is closed, the screen returns to where it was, so older owners do not lose the way back. There are 4 entry points: the overview, the sign-in page, a small link inside the selection form, and the member center. Wherever an owner gets stuck, the matching video is nearby.

Announcements: who has read and who has not

When editing an announcement in the back office, the team can add text, images and video. A cover image of 1440 × 810 is recommended and is cropped to 16:9 on the owner side, and video can be a YouTube link or an https mp4 file. Each announcement gets one category, owners filter by category, and an important one can be pinned. A live preview on the right shows what owners will see.

After publishing, the list shows view counts and the share of owners who have read each announcement. Expanding one shows who read it, how many times, and who has not, and a click on a row opens that owner's member page. Only owners are counted, and test accounts are excluded.

Reminders also reach the owner side. A pinned announcement that has not been read pops up as soon as the owner enters the site, and the menu shows a red dot with the unread count. Important notices do not wait for owners to go looking.

A person looks down at a clipboard and ticks the first of three checkboxes, leaving the other two blank.

Usage log: check each owner's sign-in status

The usage log has one row per owner. Columns include last sign-in, shown as online if the latest record falls within 6 minutes; days signed in; number of visits; time spent, both total and per-visit average; units viewed; number of features used; and device, whether phone, tablet or computer.

There are 8 tracked features: sunlight and monsoon wind, surroundings, entering the interior, walking inside, window views from inside, the full unit report, tutorial videos and selection registration. The case team sees not only whether an owner came, but how far the owner got.

Time spent is counted conservatively. The tab must be in the foreground with an action within 2 minutes, and watching a tutorial video counts, while time spent in LINE or with the screen locked does not. The figure stays close to the time an owner actually spends looking.

Fig. 2Each of the three quick filters leads to one follow-up action
  1. Open the usage logOne row per owner
  2. Pick a quick filter
  • Never signed in
    Call, or ask the building lead to visit
  • Signed in
    Open the daily detail and the units viewedShows which units the owner cares about
  • Signed in today
    Send a reminder or reply the same dayThe last sign-in time is listed for each owner

The time window can be set to 7, 30 or 90 days.

Opening any row shows one entry per day: first and last sign-in times, number of visits, time spent, units viewed, features used and device. Each day is measured in Taiwan time.

Only people signed in to the back office can read these records, and owners never see the records, so owners can concentrate on choosing a home. The stated purpose of the Personal Data Protection Act, in Article 1, is to regulate the collection, processing and use of personal data so as to prevent harm to personality rights and to promote proper use of personal data. The usage log serves to help and look after owners.

Intent summary: what each owner cares about

Each owner has a member page, and its intent summary condenses how the owner looks at units: the units viewed longest and most often, preferred unit types and floors, the floor band viewed most, and whether these preferences match the registered choices. Figures are weighted by time spent and marked as a coordination reference only. Before a phone call, the case team already knows which unit to start with.

Case officers can also add AI contact suggestions (added per project) before calling. The suggestion reads the usage log, the preference summary and announcement reads, and ranks the owners worth contacting today with a stated reason for each, such as never signed in, viewed for a long time without saving choices, or announcements left unread. The case officer still decides whom to call.

How the case team uses it: situation, where to look, next step

The table maps common situations to a place in the system and a follow-up. The case team can work through the rows in order from the back office.

SituationWhere to lookNext step
Never signed inUsage log, filter Never signed inCall, or ask the building lead to visit
Signed in, not yet registeredMember list category Not yet registered, plus the units viewed in the usage logSee which units the owner viewed and start from those
Long viewing time, nothing savedIntent summary on the member pageCheck preferred unit types and floors against the choices, then add explanation
Announcement unreadNot yet read list in the announcement readersSend a reminder
Over-allocation not confirmedOver-selection tab in the war roomContact the owner to confirm
Position conflictConflict card in the war roomProduce the selection reference and discuss it with the owner
Consent form not yet signedBack-office marker showing the number of trials and the time the prompt appearedPlan a visit and explanation from the trial record

Member center: all seven stations in view

The Urban Renewal Act provides in Article 43 that reconstruction zones are in principle carried out through rights transformation. After signing in to the member center, an owner sees a progress bar with seven stations in order: business plan, rights value assessment, simulated selection, formal selection, filing, construction and handover. The current station is derived from the round schedule, and stations without data yet are marked as pending.

The member center also holds the owner's own details, the units and parking spaces held, a summary of choices, and a selection certificate that can be downloaded as a PDF. Owners know where things stand, and the case team gets asked about progress less often.

After selection: the same list carries on

After selection ends, the demolition notice can reuse the existing announcements and read list, added per project. The notice runs in five steps:

  1. Send: the case officer delivers the notice content, deadline and contact number to every unit, and written notices go out under the legal procedure with the mailing record logged alongside.
  2. Pop-up: the pinned notice appears the moment an owner enters, and the owner presses "Read and understood" after reading.
  3. Sort: the system splits owners into three lists: confirmed, read but not confirmed, and not yet read.
  4. Follow up: units that have not read it or never signed in join the call list, a tap on the name dials, the building lead helps where needed, and every contact is logged.
  5. Complete: the case officer logs each move-out unit by unit, the record can be exported, and the member center progress updates.
A street corner with two buildings under construction, scaffolding and tower cranes above, pedestrians walking past.
A street corner with two buildings under construction, scaffolding and tower cranes above, pedestrians walking past.

Teams and situations that fit

Communities with many owners, scattered residences and a high share of older owners benefit most from invitation links, tutorial videos and the usage log. The building lead is the contact person among owners, so the system names the building lead and the case team as the people to ask, on the sign-in page, in the selection reference and in the gentle prompt.

Next step

The full feature set is described on the urban renewal system page, and the urban renewal system case shows how it runs in practice. When the invitation flow or announcements need adjusting for a community, the team can discuss requirements with the development team.

(Contact)

Start a project.

Three steps to a clear direction and budget range.

  1. 01Book the first meeting: choose a time. A full specification is not required.
  2. 02A 15 to 30 minute online consultation: direction, budget range, and draft timeline.
  3. 03After materials are reviewed, a quote and delivery specification follows in about 3 to 5 working days.
Email
hello@polish-design.com.tw
Mailing address
3F, No. 191-1, Zhifu Rd., Zhongshan Dist., Taipei 104, Taiwan

Book the first meeting

Monday to Friday, 16:00–18:0030 minutes online

Choose a time, then confirm with a Google account or an email address. A confirmed booking can be added to the calendar.

Choose a time

Or send the details first

Not ready to pick a time yet: leave the project details here and the team replies by email. A meeting can still be booked right after sending.

More details (optional): service, stage, links, source

Information is used only to evaluate this project.

ISO/IEC 27001:2022 certificate

(Certificate)

ISO/IEC 27001:2022

Certification body
ARES International Certification
Scope
The development process for interactive immersive 3D systems, and network and infrastructure operations and management.

Verify with ARES

Urbird

Urban renewal you can see.

Before construction begins, landowners can walk through their new homes. From consent forms to demolition notices, everything runs in one system.

More than 100 modules, AI features included, combined to each developer’s needs.