LuxHub DIALux freelance Fixed Bounty: what becomes locked after acceptance?

The short answer: review the whole record before the project locks

For freelance lighting calculation jobs online, a visible bounty is useful only when it sits beside a clear scope, required output, expected effort and named deadline. In the intended LuxHub Fixed Bounty workflow, an eligible DIALux freelancer reviews those facts first, then accepts the stated price only when the project fits. Acceptance should lock the agreed scope, bounty and deadline so the mission does not quietly become a different job afterwards.

LuxHub's public specialist portal is an English-only demo with fictional data, no real projects and actions that remain on the page. It currently illustrates sample gross bounties in USD, expected effort, deadlines, locked briefs, deliverables and QA checks. It does not prove production project availability or a live acceptance route, so approved specialists must confirm the controls in their own account. Joining never guarantees approval, compatible projects, selection, income or immediate work.

Separate the stated bounty from the work it is meant to buy

A Fixed Bounty project presents one stated price rather than asking the freelancer to set a price. Before accepting, match that amount to the actual work: modelled areas, drawing revisions, exact photometric files, calculation criteria, deliverable formats, reporting language, revision allowance and QA evidence. A number without those boundaries is not enough information for a responsible commitment.

Also distinguish gross bounty from any illustrated fee or estimated net amount shown by the platform. The fictional public demo displays those fields separately, which is a useful reading habit even though it is not evidence of a production payout. Ask which figure becomes part of the project record and which conditions could legitimately change it before you rely on the amount.

Check what locks when you accept

A useful locked record should identify the project scope, required DIALux output, bounty, deadline with time zone, supplied-material summary and any agreed revision allowance. The demo acceptance message says the deadline, scope and estimated net payout become locked locally. Because the demo cannot update a real record, treat this as an interface illustration and verify the production behaviour before accepting paid work.

Locking does not make missing information disappear. If the plan revision is uncertain, the IES or LDT file is unverified, the maintenance basis is absent or the requested standard is unclear, resolve that before acceptance or use the platform's documented clarification route. A freelancer should not accept a fixed amount on the assumption that the brief will become clearer later.

Use progress stages and QA checks to protect the promised outcome

After acceptance, progress stages should connect the locked brief to delivery rather than create new scope. A practical sequence can cover material review, model setup, calculation, self-check, deliverable upload and QA response. The checklist should name objective evidence such as dimensions matching the supplied plan, documented maintenance assumptions, result values reconciling with the editable project and required report views being present.

QA is not permission to add unrelated areas or a different calculation method without agreement. If review reveals a genuine error within the locked brief, correct it through the recorded workflow. If the customer requests additional rooms, another luminaire option or a different report package, that is a scope decision that should be handled through the platform's approved process rather than absorbed informally.

Understand the other response model before you click

Not every opportunity should be treated as a Fixed Bounty. In the intended LuxHub model, a Fixed Bounty mission lets an eligible freelancer accept the stated price after reviewing the preview. An Open Quote mission instead lets an eligible freelancer propose a price and proposed delivery time. Submitting an Open Quote is a proposal, not an acceptance, and a project should not be described as offering both choices unless its preview actually does.

The current public demo illustrates fictional fixed-bounty cards and a local accept action, but it does not demonstrate a production Open Quote form. Approved freelancers should verify which response model is enabled on the specific preview. If the project needs a different commercial response from the one shown, do not force it through the wrong button.

A Brazil example: convert the deadline before judging the bounty

A remote DIALux freelancer in Brazil may review a project whose deadline is stated in Malaysia, Europe or another region. Convert both the delivery deadline and the expected clarification window to your actual local time before accepting. A price can look workable until the named time zone reveals that a review or upload is due during unavailable hours.

This Brazil perspective is a scheduling example, not a claim about local LuxHub demand or availability. Freelancers worldwide should confirm the controlling time zone, public holidays, language requirement and the hours needed for modelling, checking and upload. The freedom to decline unsuitable work is more useful than accepting a fixed bounty that cannot support a checked delivery.

Follow the complete discovery route before making a price decision

LuxHub may email an approved freelancer when a compatible project matches the person's skills, work preferences and availability. The email is an alert and entry point, not the whole project experience. Its call to action should lead to the relevant first-party available-project board or protected preview. Approved freelancers should also be able to browse compatible opportunities on the board instead of depending only on email.

From the preview, inspect the brief, scope, supplied files or safe material summary, bounty or customer budget, expected effort and deadline. Then use only the response model shown: accept a reviewed Fixed Bounty, propose a price and delivery time for an Open Quote, or decline when the mission does not fit. The public demo does not verify that these production routes are enabled; unapproved readers should use the LuxHub join queue rather than attempting a protected project link.

A quick decision check before you join

1. 01
   Read the outcome first

   Confirm modelled areas, calculation criteria, files, deliverables, report language and revision allowance.

2. 02
   Reconcile price fields

   Distinguish the stated gross bounty from any fee illustration or estimated net figure before relying on it.

3. 03
   Translate the deadline

   Convert the named deadline and clarification window to your real local time and available hours.

4. 04
   Resolve missing inputs

   Clarify drawing revisions, photometric files, maintenance assumptions and standards before acceptance.

5. 05
   Confirm the response model

   Accept only a Fixed Bounty; use a proposal for an Open Quote and do not confuse the two actions.

6. 06
   Verify production controls

   The public portal is fictional, so confirm locking, stages, QA and project access inside an approved account.