A practical guide to BUILDiQ, FIXiQ, client portal access, record handling, and the way project and property information should be treated.
This page is written for plain-language client support and is pending final legal/policy review. For formal commitments, use the applicable engagement agreement and reviewed privacy policy.
Ask your Lionsgate contact to confirm the right portal, role, property or project scope, and client audience.
Send the record type, property or project, date, and correction needed. Keep private details out of the request unless they are required.
Use project/property records that support the engagement. Do not upload unrelated private, resident, legal, insurance, or dispute material without a clear purpose.
Start with BUILDiQ when the problem is tied to a construction project, capital work, OAC coordination, reporting, schedule, cost, turnover, or owner-side representation. Start with FIXiQ when the problem is tied to an operating property, recurring maintenance, board continuity, property records, vendors, resident requests, or operational memory.
BUILDiQ supports owners with project review, owner representation, construction-management coordination, meeting records, field reporting, risk tracking, and decision support. It is designed to help ownership understand what is happening, what is exposed, and what decision needs to be made next.
FIXiQ organizes property operations around memory: requests, work orders, vendors, building context, documents, reports, approvals, and board or manager decisions. The goal is to keep the property from losing context when people, vendors, boards, or managers change.
Portal access is provisioned by Lionsgate for approved client users. Access is scoped by division, role, property, project, and audience. If a user cannot see a record, the first check is whether their role and scope are correct.
No. Portal records, reports, summaries, and operational recommendations support decision-making. They do not replace legal, engineering, architectural, accounting, insurance, regulatory, or other professional advice where that advice is required.
No. Client records are used to deliver Lionsgate services, operate the portals, support project or property workflows, and maintain engagement records. They are not sold as advertising data or data-broker records.
Depending on the engagement, records may include project documents, property documents, reports, photos, communications, work orders, approvals, vendor information, contact information, operational notes, and related metadata. Sensitive information should only be uploaded when it is required for the engagement.
Use the portal only for records that belong in the engagement. Avoid unnecessary resident, legal, insurance, dispute, financial, or private personal information. When sensitive material is required, it should be clearly identified and access should be limited to the appropriate users.
Contact the Lionsgate team through the portal context or concierge channel and identify the record, property or project, and what needs review. We treat corrections as operational record work, not as hidden edits.
BUILDiQ and FIXiQ handle operational information that can affect projects, boards, residents, vendors, and owners. The working principle is simple: collect what is needed, keep it scoped, and show the source context when information drives a decision.
Access should be limited to the property, project, role, and audience a user is authorized to work with.
Records are collected and used to deliver project, property, advisory, reporting, and support workflows.
The portals preserve context so ownership, boards, managers, and operators do not lose the history needed to make decisions.
Sensitive files should be uploaded only when needed, labelled clearly, and limited to the people who need them.
Where automation assists retrieval, drafting, triage, or summaries, outputs remain operator-support tools and should be checked against visible source records.
Client records are not sold as advertising data or data-broker records.
Use the concierge channel or call the appropriate division. Avoid sending sensitive record details until the correct portal or engagement context is confirmed.